home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
DP Tool Club 31
/
CDASC_31_1996_juillet_aout.iso
/
vrac
/
del2faq.zip
/
ALLFAQ.ZIP
/
DELSEC03.FAQ
< prev
next >
Wrap
Text File
|
1996-02-07
|
49KB
|
1,175 lines
Delphi Up and Running
In general the installation of Delphi is really simple and can
be done without any headaches. Unfortunately for some people their
insallation of Delphi (TP or TDW) is not so perfect. This document
has been created to help out in those situations. The following
document contains information related to possible problems that
other users of Delphi have encountered, as well as a listing of
Technical Information (TI's) that can be found on our TechFax line,
also some of the TI's can also be found on CompuServe, and on our
internet site.
TI's (Technical Information) can be found :
- by calling the TechFax Line at (800) 822-4269
- Compuserve: (Go Delphi) Library "From Borland"
- Web: see below for specific locations.
- BBS: 408-431-5096 Section: ?
[ Common TI's ]
Web: ftp://ftp.borland.com/techinfo/techdocs/language/delphi/ti
TI 2841 Delphi Consultants and Training Centers.
TI 2777 Running Delphi from CD.
/techinfo/techdocs/language/cpp/bcpp/ti
TI 1171 Bug Report Form.
TI 1561 Clean Boot.
TI 1736 Keeping BC++ 4.x and BP/TPW on the same system.
/techinfo/techdocs/database/paradox/pdoxwin/ti
TI 1283 Clean Boot under Windows.
TI 2733 Troubleshooting IDAPI Error Messages
TI 2734 Paradox 5.0 Installation Questions and Answers.
[ Update's and Patches ]
TDSVGA.ZIP Newer DLL's for Turbo Debugger for Windows
CompuServe : (Go Delphi) from library 2.
BBS:
WEB: ftp://ftp.borland.com/techinfo/techdocs/other/misc
VCLPATCH.ZIP Patch for the Visual Component Library source.
DELCSPAT.ZIP Patch for Delphi 1.00 Client Server.
DELPATCH.ZIP Patch for Delphi 1.00
WEB: ftp:ftp.borland.com/techinfo/techdocs/language/delphi/patch
DLPGRP.ZIP
CompuServe: Delphi Forum (Go Delphi) in the "From Borland" section.
WEB: ftp://ftp.borland.com//techinfo/techdocs/language/delphi/gen
BBS:
The Following Questions and Answers (Q&A) have been placed into
sections to make accessing them easier. Please note that a Q&A may
be placed into a section different than the one you feel it should be
in.
Sections
-----------------------------
1. Delphi Install
2. Delphi Up and Running
3. IDAPI and BDE
4. Tutors
5. VBX related issues
6. TPW - Turbo Pascal for Windows
7. TDW - Turbo Debugger for Windows
8. Delphi under OS2
9. Delphi under NT
10. Miscellaneous Issues
----------------------------------------------------------------------
[ 1. Delphi Install ]
Q: How can I determine what version of Delphi I have ?
A: Look at the executables, the time on version 1.00 is 8:00 and
the time on the Update CD is 8:02.
----------
Q: While installing Delphi from the CD, file corruption errors
are occuring, is there something wrong with the CD?
A: It is virtually impossible that the CD is actually corrupt. This
error usually stems from corruption of the file occuring while it
is being copied. It occurs most often on faster computers (DX4's
and faster Processors) with fast hard drives.
The computer needs to be slowed down:
- Try pressing the turbo switch to drop the CPU speed. (Didn't
you always wonder what those things were for ?)
- If your computer does not have a turbo switch, or that did not
help, then try disabling your Video Rom Shadowing (from the
BIOS), disabling Smartdrive (config.sys), and turning off
Windows caching (config.sys).
If the above is not successful, then a Hard Drive Install is
necessary. Copy the install directories off of the CD (with
the computer slowed) and try doing a hard drive installation.
-----------
Q: I'm trying to install the Client/Server version of Delphi 1.0, and
it gets to Disk 16 or 17 and gives the error "unable to unpak
destination file" on the file W3DBLIB.DLL. What's going on?
A: This appears to be a bug on the part of the install engine. If you
are running Windows off a network, and have chosen the Windows LAN
setup option, Delphi will normally install all Windows\System files
in the Delphi\WinSys directory. However, if the file W3DBLIB.DLL is
already installed under Windows\System, the install engine will try
to overwrite it rather than placing it in the Delphi\WinSys directory,
and will fail (with the above error) if the file or directory is
marked read-only (as is often the case if Windows is being run off
a network). To get past this, have your network administrator
temporarily enable write access to the Windows\System directory,
and clear the read-only flag for the file W3DBLIB.DLL so that it
can be overwritten (or rename it temporarily and compare/restore
it after the installation). Then click on "Retry". The installation
will now be able to proceed to the end.
If turning on write access makes you uneasy, click on "Cancel" and exit
the installation. Then have your network administrator temporarily
rename the file, and re-run the installation. Renaming the file will
fool the installation as to the existance of this file, and the install
program will create and place the new file under the proper directory
(Delphi\WinSys). Then your admin. can rename the file back to its
original name.
If you do not have adminstrator access, cancel the installation and
do a manual install. To do a manual install, simply xcopy the entire
RUNIMAGE directory to your hard drive, except for the RUNIMAGE\WINDOWS
directory. Have the adminstrator place all of the files in RUNIMAGE\
WINDOWS onto the network's Windows directory, and likewise all of the
files under RUNIMAGE\WINDOWS\SYSTEM into the network's Windows\System
directory. See one of the above Q&A's about what modifications you'll
need to make to your path and the WIN.INI settings, and download the
file DLPGRP.ZIP to create the program icons and group needed to complete
the manual installation.
-----------------------------
Q: I would like to completely remove Delphi from my system before
trying to reinstall it.
A: There is a TI for this process. It covers NT, Win 95 and 3.1
or Tech Document : *********
-----------
Q: I am installing Delphi and I get an error message: "No
ExtVer Method" in the file ODBCDRV.PAK ..\INSTALL\DISK3. Where
is this method?
A: This is a known bug. There are, however, some options to try:
1. Clean boot. (TI 1561) and try re-installing.
2. If that fails, try to do a Disk install by copying the INSTALL
subdirectory from the CD to a temporary directory on the hard
drive and running SETUP.EXE from there.
3. If steps 1 and 2 fail, try running Delphi from the CD ROM
(TI 2777) and if it works, copy the RunImage directory from the
CD to the hard drive.
Apparently this error can be circumvented if the install is done
without installing DBD and/or Local Interbase.
----------
Q: If I have a dual boot machine, say 95 and NT, and Delphi has
been installed under 95. Why can I can not run Delphi under NT?
A: Two installations are necessary; one per operating system.
However, all the Delphi's files should be installed to the
same location so as not to waste valuable hard disk space. The
reason for the dual installations is that the install process
alters certain files for initialization and confirguration
purposes, and copies other files into the operating system's
area. Eg. WINDOWS\SYSTEM.
---------------------------------------------------------------------
[ 2. Delphi Up and Running ]
Q: I'm trying to run my Delphi application, or one of the sample
apps, that uses the ReportSmith runtime. When it goes to
launch the ReportSmith runtime, it gives the error message:
"Unable to load RS_RUN.EXE", but I have RS_RUN installed. What
is going on?
A: Go to your Windows directory, and make sure you have the file
RS_RUN.INI. If not, create the file, and in it make sure you
have the entry
[RS_Runtime]
ExePath=C:\RS_RUN
where C:\RS_RUN corresponds to your particular path to RS_RUN
(the above is the default directory when installed). Then quit Delphi,
restart, and try running your program again. You should now be able
to get past the error.
-------------
Q: I'm having problems running any project in Delphi when Lotus
Notes is running. It quits Delphi when I try to run even just
a blank form without giving any errors.
A: The problem seems to be with the Integrated Debugger being on. Go
to Option|Environment and disable Integrated Debugging.
------------
Q: In Delphi, when I run any project (even a blank form), it kicks
me out to DOS without any errors. It compiles fine and creates
an EXE for the project. When EXE is ran from File Manager, it runs
fine. How can I run my project from Delphi?
A: It is a debugger conflict. There are two ways to fix this.
First, remove the conflicting software. The second option is to
disable the integrated debugger by un-selecting Options|Environment|
Integrated Debugging.
Q: After installing the Delphi Update, when I go to Server
Manager, the only things that are not greyed are the first
and the last icon on the speedbar. The boxes on the bottom of the
speedbars are blank also.
Before the update was installed, more icons were
accessible, and Local Server was in the left box with its
corresponding properties on the right. How can I bring that
back?
A: Click the first icon (i.e., Login to an InterBase server).
User Name should be SYSDBA. Then type in 'masterkey' as your password
and click on OK. You should have the old settings back like before.
-----------------
Q: When I click on the Delphi icon, I get the error message
"COMPOBJ.DLL caused a GPF at 0003:2EED".
A: COMPOBJ.DLL is part of the Windows OLE subsystem. Double
check your OLE installation. It's not uncommon to discover
that you have a partial OLE installation, or mixed versions
of OLE modules, or a corrupted OLEREG.DAT file. Delphi's
TOLEContainer component requires/loads OLE, and Delphi's
component library (COMPLIB.DCL), where TOLEComponent
resides, is loaded when Delphi starts up.
To check your OLE installaion, look in your WINDOWS\SYSTEM
directory to see if you have these files with these
time/date stamps:
filename date time version
----------------------------------------
BOLE16D.DLL 02/15/95 8:00 1.00 *
OLE2.DLL 09/4/94 8:07 2.02
OLE2.REG 09/4/94 8:07 2.02
OLE2CONV.DLL 09/4/94 8:07 2.10
OLE2DISP.DLL 09/4/94 8:07 2.02
OLE2NLS.DLL 09/4/94 8:07 2.02
OLE2PROX.DLL 09/4/94 8:07 2.02
STDOLE.TBL 09/4/94 8:07 1.10
COMPOBJ.DLL 10/3/94 13:16 2.02
STORAGE.DLL 09/4/94 8:07 2.02
TYPELIB.DLL 09/4/94 8:07 2.02
* The only Borland DLL - all others are from Microsoft.
The problem is with the different versions of OLE, Borland
distributes Microsoft's OLE v2.02, Windows 3.1 installs OLE
v2.0. The only exception from the list above is BOLE16D.DLL
which is Borland's.
If you are unsuccessful at finding or correcting your OLE
configuration problem then you can rebuild the Delphi
component library without the TOLEContainer. This will
allow you to use Delphi (without OLE support) until you can
get OLE straighted out. Not having to load OLE when Delphi
starts up will cut Delphi's load time almost in half, and
reduce memory use by about 1Mb.
To rebuild the Delphi component library without the TOLEContainer,
first make sure you've exited Delphi. Then go to your
Windows\System directory and edit Delphi.INI. Look for the line
that reads:
ComponentLibrary=C:\DELPHI\BIN\COMPLIB.DCL
and change it to read:
ComponentLibrary=
Save and Exit from the Delphi.INI file. Start up Delphi .
Delphi will give you an error message saying that it could
not load the component library. Just click OK. Choose
Options | Install Components and type in a new filename under the
Library filename (such as c:\Delphi\bin\newlib.dcl). Click on the
Add button, click on the Browse button. Change to the Delphi\lib
directory. Choose STDREG.DCU and click on the OK button. Repeat
(from clicking on the Add button) and add the following *.DCU
files: VBXREG, STDREG, DBREG, SYSREG, DDEREG, SWITCH, GAUGE, PICT,
CHART2FX, SAMPREG, and LIBEXPT. Now click on the OK button and
the library will compile and load for you.
-----------
Q: Do you have any useful IDE navigation tips?
A: If you have a form open, F12 puts you in the editor in that form's
code. F12 in the editor takes you to the form corresponding to
the active page of code. So the editor can serve as a navigation
aid for getting between forms.
-----------
Q: I'm trying to start Delphi and I get the error message "Can
not open C:\DELPHI\BIN\COMPLIB.DCL".
A: This error message can occur for many reasons: Either SHARE or
VSHARE have not been loaded, or possiibly using the wrong
parameters for share (should be F:4096 L:40). The IDAPI section
of the WIN.INI file could be bad or missing. The IDAPI section
should be similiar to the following:
[IDAPI]
CONFIGFIL01=C:\IDAPI\IDAPI.CFG
DLLPATH=C:\IDAPI
COMPLIB.DCL could be corrupted. Get a new copy from the CD
\RUNIMAGE\DELPHI\BIN\COMPLIB.DCL
Assuming all of the above is as it should be, compare these
files with the ones on the runimage:
Win 3.1 Win 95 Win NT QJS QJS
C:\WINDOWS\SYSTEM\COMPOBJ.DLL 108,544 30,976
C:\WINDOWS\SYSTEM\OLE2.DLL 302,592 39,744
C:\WINDOWS\SYSTEM\STORAGE.DLL 157,696 4,208
C:\Delphi\BIN\COMPLIB.DCL 1,058,784
If any of these files are the wrong size, back them up, and copy
over new ones from the CD. (From the RunImage directory)
If all the above fails, it is possibe that the Windows install
is bad. Some possible things to check:
VER.DLL 9,008
USER.EXE 264,016
KRNL386.EXE 76,400
----------
Q: Adobe Acrobat gives the message "Could not find Adobe Type
Manager" when I try to access the Delphi on-line manuals.
I am running under Win NT. How can I fix this problem?
A: Download version 2.1 of the Acrobat Reader. This new version
works under NT, and supports a wider range of printers as well.
CompuServe: Adobe Applications Forum (GO ADOBEAPP).
WEB: http://www.adobe.com
A current work around to the problem is to add the line:
ATMOption=1
to the [Abode Viewer] section of ACROREAD.INI. Then copy it to
ACROEXCH.INI (both files should be in your \WINNT35 directory).
If you do not have ACROEXCH.INI, then copy ACROREAD.INI and name
it ACROEXCH.INI. Fonts may still show up incorrectly or poorly,
but you will still be able to run Acrobat.
----------- QJS QJS
Q: I am writing an MDI application using Delphi. When I minimize
an MDI child, a General Protection Fault(GPF) occurs.
A: This is a known problem, for which there is a patch available.
Download the patch (DELPATCH.ZIP), apply it, and then rebuild
the Library.
To find this file see the list of files at the start of this
document.
----------
Q. How can I easily create the Delphi folder and icons ?
A. There is a program for creating the Delphi program group and
associated icons. The name of the file is DLPGRP.ZIP.
To find this file see the list of files at the start of this
document.
-----------
Q. What is W8LOSS.EXE used for?
A. W8LOSS.EXE is a command line tool that optimizes your exectuable
for size and load time. It is equivalent to choosing
OPTIONS | PROJECT | LINKER and turning on for 'optimize for size and
load time.' Use this tool if you are experiencing difficulty from
using the option from within the IDE.
-----------
Q. I did a manual install, what do I have to add to my WIN.INI and path
for Delphi to function correctly? (Assuming Installed to C:)
A. Add "C:\IBLOCAL\BIN;C:\DELPHI\BIN" to the path in the AUTOEXEC.BAT
Add the following lines to the WIN.INI file:
[IDAPI]
DLLPATH=C:\IDAPI
CONFIGFILE01=C:\IDAPI\IDAPI.CFG
[Borland Language Drivers]
LDPath=C:\IDAPI\LANGDRV
[BWCC]
BitmapLibrary=BWCC.DLL
[Interbase]
RootDirectory=C:\IBLOCAL
[Paradox Engine]
UserName=PxEngine
NetNamePath=C:\
MaxTables=64
RecBufs=64
MaxLocks=64
MaxFiles=64
SwapSize=64
[DDE Servers]
DBD=C:\DBD\DBD
[DBD]
WORKDIR=C:\DBD
PRIVDIR=C:\DBD\DBDPRIV
----------
Q: When I try printing my source files from within Delphi using
File | Print, the output doesn't look right. It's printing junk
characters, or is printing some of the output right, but not all
of it.
A: Delphi uses the standard Windows print function calls to print
the source files. Try opening up the *.PAS file in Notepad, and
printing from there. If it is still not printing properly, then
you need to find an updated printer driver that is fully
compatible with your particular printer. Contact your printer
manufacturer to get an updated printer driver. If it prints
fine from Notepad, try changing Delphi's editor font by going to
the Options | Environment menu item within Delphi, selecting the
Editor Display tab, and clicking on the down arrow button of the
Editor Font box to get a selection of the alternative fonts you
can try. Try all of the different fonts. Also, try turning off
syntax highlighting by selecting the Editor Options tab and
making sure the Syntax Highlighting option is not checked. If
none of these works, your best bet is to try another printer
driver. Delphi uses some of the latest TrueType technology, and
your current printer driver might need to be updated to support
the latest TrueType capabilities. So, even if it printed fine
from Notepad, it may still require an updated driver in order to
handle the fonts shipped with Delphi. Contact your printer
manufacturer for obtaining a newer printer driver.
----------
Q: I had Quattro Pro running on a network, and after I installed
Delphi, none of the users can run Quattro Pro anymore. They get
a "Cannot load language driver" error. How can this be fixed?
A: Most likely what happened is the IDAPI directory on the network was
updated. The version of IDAPI that comes with Delphi is compatible
with Quattro Pro, with only a slight modification. For each client
that will be accessing IDAPI on the network, be surethe following
section is added to their WIN.INI file:
[Borland Language Drivers]
LDPath=F:\IDAPI\LANGDRV
Where F: should be replaced by the network drive letter that is
housing IDAPI, and \IDAPI\LANGDRV should contain any necessary
path changes to reflect the correct path. Users should now be
able to now use Quattro Pro with the new IDAPI that came with
Delphi.
-----------
Q. The Install program for Delphi will not start. I am receiving
the error: "Cannot execute INSTALL.EXE or one of its components."
A. This error is generated when the install program can not unpack some
of the files integral to launching itself.
There are a few things that can be tried when this happens. First
and foremost, one must always Clean Boot (TI 1561) to make sure
that the problem is not as simple as a memory conflict with another
program. If this fails, check to be sure that TEMP is pointing
to a valid location, that has enough space to unpack files (about
10-15 megs). Remember, Delphi will install a slew of DLL's to
the WINDOWS\SYSTEM directory, so it is important that the drive that
Windows is on has at least 10 megs free.
If this fails to cure the problem, try a hard drive install. This
entails copying the diskettes to a temporary directory on the hard
drive, and running the install from there. Jump starting the
install program will be the next line of defense.
Copy INSTXTRA.PAK, INSTRUN.EX_, BAMGR16.DL_, and INSTALL.INI
to a temporary directory.
Expand the *.??_ files by running EXPAND.EXE.
Run INSTRUN.EXE with INSTALL.INI as a parameter.
A Manual install would be the last line of defense. This is only
a viable option if you have the CD. It requires copying the
runimage onto your hard drive, and manually creating the program
groups, and manually massaging the appropriate INI files.
(See previous QA)
-----------
Q: I have just installed Delphi, and when I double-click on the
Delphi icon, the program begins to load, but then it flashes a
message box on the screen for a second and then quits back out to
Program Manager before ever loading Delphi completely. Or, the
splash screen will appear, but then Delphi will just shut down
(without any error messages or warnings). Any ideas what's wrong?
A: Try switching your video driver down to standard VGA by going to
the Windows Setup utility (in the Main group). If this fixes it,
you will need to get an updated video driver from your video card
manufacturer (most manufacturers have updated video drivers for
Delphi now).
If this does not work, try deleting DELPHI.INI from your Windows
directory and then restaring Delphi (DELPHI.INI will automaticly
be recreated). If this still does not resolve the problem, try
backing up C:\DELPHI\BIN\DELPHI.EXE, and copying a fresh
DELPHI.EXE from the CD rom (\RUNIMAGE\DELPHI\BIN\DELPHI.EXE), in
case the executable has become corrupted.
If this does not do it, then the problem stems from a conflict
with your particular system configuration. To resolve the problem
you will need to make sure your system is running on an absolutely
"clean", or minimal configuration. (TI 1561) and (TI 1283).
To receive these TI's see the list of TI's at the start of this
document for step-by-step information on how to do a DOS and
Windows clean boot.
----------
Q: My FormExpert does not run, or does not appear?
A: Note: Online help regarding this is is wrong.
1. Make sure that [Experts] section in DELPHI.INI has the following:
FormExpert = MyDrive:\DELPHI\BIN\EXPTDEMO.DLL
2. Close Delphi, backup DELPHI.INI, then delete it, start Delphi and
FormExpert again.
3. Backup EXPTDEMO.DLL, and copy a new one off the Delphi CD ROM
from the Runimage subdirectory.
-----------
Q. Why do I get the message 'Unable to load RPTSMITH.EXE' when I double
click on the TReport component on the form? It should bring up
ReportSmith.
A. Either the [ReportSmith] section is missing or incorrect in the
DELPHI.INI file. Make sure that it specifies the correct path.
[ReportSmith]
ExePath=C:\RPTSMITH
----------
Q: I am running Delphi in Windows95, and now the text in my
dialog boxes and error messages, appear in some garbage font.
A: Check to see if you have any MonoType fonts installed on your
system. Go to your Windows\Fonts directory, and remove or rename
any MonoType font (you can move it out of the Fonts folder onto
the desktop or another folder if you wish). The MonoType fonts
get installed by other products you have put on your system (such
as the MonoType sorts font installed by Ami Pro). Moving them out
of the Fonts folder will get Delphi's dialogs to appear normally
again.
-----------
Q: My Delphi Application runs fine as long as it is running under
Delphi's IDE or Turbo Debugger, but if it is run from the Program
Manager, it either hangs the system or causes a stack fault.
A: Check to see it you have any DLL's in your current working directory
that might be an older version of something that should be in
the WINDOWS\SYSTEM directory. Either delete or move the DLL's
elsewhere and everything should work fine.
-----------
Q: I already have Paradox for Windows and/or dBase for Windows. Will
Delphi's version of the Borland Database Engine coexist with these
products?
A: Yes, Delphi's newer version of the Borland Database Engine
(DBE aka IDAPI) has been certified with Paradox for Windows and
dBase for Windows.
Always install Delphi's IDAPI and SQL Links over any earlier
versions on your system.
-----------
Q: Where is the Language Reference Guide for Delphi ?
A: The Language Reference Guide is available separately.
Call the Order Desk at 800-331-0877 for pricing
information.
---------------------------------------------------------------------
[ 3. IDAPI and BDE ]
Q: When I move my application to another machine, I get the message
"Error initializing IDAPI $2108" or something similar. What's
going on?
A: If your application is a database application, then you need to
install IDAPI on any machine where you run that application.
See DEPLOY.TXT (located in the Delphi directory) for instructions.
If IDAPI is already installed make sure that the path to the IDAPI
directory is in the DOS PATH statement and also that there is an
[IDAPI] section in the Windows WIN.INI file with correct path
information. See the example below:
[IDAPI]
DLLPATH=C:\IDAPI
CONFIGFILE01=C:\IDAPI\IDAPI.CFG
-----------
Q: When I click on the 'Database Desktop' or the 'Database Engine
Configuration' icons, I get the error message "multiple net files
found". How do I resolve this?
A: Search your system for *.LCK files and delete them.
(LCK files are locks)
----------
Q: I get an error while trying to launch the Database Desktop, or
while trying to access a table. It says, "Could not initialize
IDAPI" followed by a particular IDAPI error message, and then
forces me to click "Ok", and quits. How can I fix this?
A: There are number of things you can check for that may be causing
this error:
First, make sure that the IDAPI paths in the [IDAPI] section of
your WIN.INI are set correctly. Go to your Windows directory and
look at your WIN.INI file. In particular, check that the following
lines:
[IDAPI]
DLLPATH=C:\IDAPI
CONFIGFILE01=C:\IDAPI\IDAPI.CFG
are set to the correct paths. Often, if IDAPI was moved from a
network or to another drive, these paths were not updated to
reflect the change. Also, check the private directory setting by
double-clicking on the Database Desktop Local Configuration icon.
Sometimes the path accidentally gets set to a shared directory or
a network drive during the installation. The private directory
should be pointing to a non-shared directory on your local drive
(eg. C:\DBD\DBDPRIV). Also, check the other paths settings
within the Database Desktop Local Configuration to verify the paths
are correct.
If this still doesn't resolve the problem, check your Net Control
File Directory (NETDIR) setting for the Paradox driver by opening
the BDE Configuration Utility, and, if you are not attempting to
open a table on the network, try setting it to a place on your local
drive (e.g.: C:\). If it is pointing to a drive on the network,
or you wish to open a table out on the network, make sure that
the directory exists, and that you have read/write access to it.
In addition, everyone who has IDAPI installed on their machine and
has their NETDIR setting pointing to a directory on the network MUST
all have this NETDIR set to the SAME directory. Until you can
determine this, scan the entire network for *.NET and *.LCK files,
and delete them all. A PDOXUSRS.NET file will be recreated in the
directory you have the NETDIR set to. Then make sure everyone points
to this directory to prevent multiple net control files from being
created.
Lastly, you can backup the IDAPI.CFG file from your IDAPI directory,
and copy a fresh one over from the runimage off the CD rom. If you
had created aliases before backing up the IDAPI.CFG file, they will
need to be re-created if you copy over a new IDAPI.CFG. This can be
done easily using the merge function within the Alias section of the
BDE Configuration Utility. Refer to the Database Engine
Configuration Help for more information regarding merging.
In addition to the above, you should already have share loaded with
the correct parameters. Make sure you have the line:
C:\DOS\SHARE.EXE /F:4096 /L:40
somewhere in your autoexec.bat file.
Should you be running Delphi on a Novel Lantastic 6.0 network,
there is a known problem with the latest version of IDAPI that will
not allow you to use Paradox tables on the network (possibly giving
you this error). Borland is aware of this, and is currently
working on a fix for it. Meanwhile, as a possible temporary work
around, you can try to switch your network driver down to an
earlier version of Lantastic, such as Lantastic 5.0. This has been
known to work for most users as a temporary solution until a fix
is available.
Finally, if you are still unable to get passed this error, you may
wish to consult two Technical Information documents Borland has
available: TI 2733 and TI 2734. These documents contain solutions
to specific IDAPI error messages (e.g. "not initialized for
accessing network files", or "call to undefined dynalink", or
"directory is busy") and so go into greater depth in addressing
IDAPI problems. The TI's can be obtained either through:
To receive these TI's see the list of TI's at the start of this
document.
----------
Q: I ran the BDE installation program to deploy my application, and
now I am getting an error message: "Could not find language
driver". What is wrong?
A: The install program will not create a Language driver sudirectory
if you install BDE to a _network_ drive. You will have to manually
unpack LANGDRV.PAK, using UNPAQ.EXE, into IDAPI\LANGDRV (You will
have to manually create the LANGDRV sub-directory.)
---------------------------------------------------------------------
[ 4. Delphi Tutor ]
Q: I'm trying to run the Delphi tutors, but it's really SLOW.
What's going on?
A: Two observations:
1) Running the tutors doubles the memory requirements for running
Delphi.
2) The Tutors do a lot of background work to keep track of what
the IDE is doing, and what you are doing to the IDE, to try
to keep the class on topic. This makes the Tutors'
manipulation of Delphi much slower than if you were running
Delphi by itself.
If you don't need to create OLE client applications right away,
you can remove the TOLEContainer component from Delphi's component
library. Not having to load OLE when Delphi starts up will cut
Delphi's load time almost in half, and reduce memory use by about
1 Mb.
To remove the OLE component from Delphi 1.xx's component library,
go to Options | Install Components and remove the OLEREG unit
from the left-hand listbox. Click OK and the component library
will be recompiled without OLE.
----------
Q. Why do I get the message "To run the interactive tutors, you must
change the Delphi configuration slightly..." when I start the
interactive tutors?
A. This happens because you are not running with the default settings
of Delphi. Backup your current DELPHI.INI file in the Windows
directory and then copy DELPHI.CBT file to DELPHI.INI. The tutors
will now work correctly. When finished with the tutors the old
DELPHI.INI will need to be restored.
-----------
Q. The interactive tutors don't appear to be working correctly. How
do I get them to work?
A. See previous answer.
-----------
Q: When I try to run the interactive tutors I get the message "Error
creating Process: Insufficient memory to run the interactive
tutors."
A: The interactive tutors have a larger memory requirement than
Delphi, on the order of twice the amount. Check to make sure you
have enough memory to run the tutors. You can still run the
tutorials without 12 or 16 megs, but make sure that you are
running Windows in 386 Enhanced mode, and that you have a large
enough swap file set. If you think you have enough RAM, but are
getting the error message, try increasing your swap file anyway
in the Virtual Memory option of the 386 Enhanced control panel.
Windows may be trying to swap out things to disk to accomodate
the Delphi tutorial, and if the swap file is too small, it may
have trouble doing this. Finally, clean boot your machine's
Dos and Windows configuration, to make certain nothing you have
loaded in memory besides the bare minimum is hogging or corrupting
vital memory space necessary to run the tutors.
Download TI 1561 (TI1561.ZIP) and TI 1283(TI1293.ZIP) for detailed
instructions on how to "Clean Boot" your machine.
Directions to these files are provided at the begining of this
document.
---------------------------------------------------------------------
[ 5. VBX related issues ]
Q: Why does my VBX not load or it crashes Delphi when I try to
load it.
A: Most likely the VBX you are trying to use is a Visual Basic(VB)
2.0 or 3.0 compatible VBX. Delphi can only use VB 1.0 compatible
VBX's.
-----------
Q: Since installing Delphi, a few VB apps I have are having
problems. What's going on?"
A: From the INSTALL.TXT file located in ..\Delphi directory:
__________________________________________________________
|
| 2. BEFORE YOU RUN SETUP
| -----------------------
| .
| .
| .
| o VBX controls - SETUP installs the following VBX files
| into the \WINDOWS\SYSTEM directory that will
| overwrite any existing VBX files with the same name:
|
| GAUGE.VBX
| SWITCH.VBX
| PICT.VBX
| CHART2FX.VBX
|
| Before running SETUP, check for filename collisions
| and backup your existing copies of these files.
|
| .
| .
| .
| _______________________________________________________
The original files that may have been overwritten could
have been part of your VB application. If this is the case
do the following steps (we will use GAUGE.VBX as an
example):
1) Go into Delphi and Remove the GAUGE.VBX from the
Component Palette:
a) Select Options | Install Components from the menu.
b) Select(Highlight) the GAUGE from the Installed Units
list.
c) Click on the REMOVE button (it will disappear from the
list).
d) Click on the OK button. Delphi will now re-compile
the component library.
e) Exit Delphi .
2) From the File Manager Rename the GAUGE.VBX to something
like BIGAUGE.VBX.
3) Go back into Delphi and Add the BIGAUGE.VBX to the
Component Palette:
a) Select Options | Install Components from the menu.
b) Click on the VBX button.
c) Select the VBX you want (BIGAUGE.VBX in this case).
d) Click on the OK button in the Install VBX File Dialog
Box.
f) Click on the OK button in the Install Components
Dialog Box. Delphi will now re-compile the component
library.
4) Copy the VBX (GAUGE.VBX) that your VB application uses
to the \Windows\System directory.
This should fix any conflicts.
-----------
Q: After installing Delphi, every time I start NetCom's NetCruiser
application (which is a VB app), it comes up with 'NETCRUZ An
error has occurred in your application. If you choose ignore...'
A: Delphi installed a "GAUGE.VBX" over the one from Visual Basic(VB).
The one that Delphi installed is incompatible with the VB version
(See above Q&A).
----------
Q: I am trying to install a VBX component into the Component
Library, using the Options | Install Components... menu item.
After I add the component and I hit 'Ok' in the Install Components
dialog box, the dialog box closes, and the component library
begins to rebuild itself (as it should). But, when I go to the
component palette to look for the new component, it isn't there!
The installation of the component didn't report any errors. What
did I do wrong?
A: Close Delphi, and check the attributes of COMPLIB*.*, using File
Manager, or the DOS 'attrib' command. Sometimes, the files
COMPLIB.DCL and COMPLIB.~DC become marked as read-only. Make sure
the are NOT set to read-only. If COMPLIB.DCL is marked as
read-only, then the component library will be unable to save any
changes you make to it, such as installing or removing a component.
A less obvious but similar situation will arise if the file
COMPLIB.~DC is also marked as read-only. This file is the backup
file for COMPLIB.DCL. When the component library goes to rebuild
itself, it backs up the current version of the library,
COMPLIB.DCL, to the file COMPLIB.~DC. But, if this file is marked
read-only, COMPLIB.DCL cannot be backed up, and if COMPLIB.DCL
can not be backed up, the component library will not attempt to
modify itself. Be sure that both COMPLIB.DCL and COMPLIB.~DC do
not have their read-only attributes set.
-----------
Q: I am trying to install a new component or VBX to my component
library, and after selecting the component or VBX in the
Options | Install Components dialog box, I hit "OK" to return back
to Delphi, and I get the error message "File not found
[filename.dcu]" when it tries to rebuild the component library.
The file is on my hard drive, and the 'Search Path' edit box inside
the Install Components dialog box has the correct path. Why is
it that Delphi can see the component when I add it, but not when
it tries to rebuild the component library?
A: Try checking the length of the search path in the edit box within
the Install Components dialog box. This phenomenon could be
explained if the search path is too long; Delphi will only
take the first 68 characters of the path and Delphi 1.02 will take
will only take the first 127 characters of the path. So, if your
search path is greater than 127 characters, and the component you
added appended its location to the end of the search path, it
effectively will not be part of the search path, and when the
component library tries to rebuild itself, it will not be able to
find your newly added component. Try moving the path containing
the component to the front of the search path, and see if that works.
If it does, you will need to shorten your path, perhaps by renaming
directories to shorter names, or moving subdirectories up one level
in your directory hierarchy.
---------------------------------------------------------------------
[ TPW 1.5 ]
Q: I'm trying to install TPW 1.5, and the installation stops after
unpacking a few files on Disk 1. The installation just quits,
and returns to the install screen without an error message.
A: The installation program may be trying to decompress a file that
is already on your hard drive, and, more importantly, is marked
as read-only. If a file that the installation program is trying
to write to is marked read-only, the installation program will
be unable to overwrite this file, and the installation will fail.
Check the attributes of the file BWCC.DLL, which resides in your
WINDOWS\SYSTEM subdirectory. You can do this by typing the command
ATTRIB C:\WINDOWS\SYSTEM\BWCC.DLL from a DOS prompt (making any
necessary changes to the path to your WINDOWS\SYSTEM directory).
If the file is marked read-only (has an 'R' on the status line next
to the file), change the attribute so that it is no longer Read-
Only.
You can do this by typing: ATTRIB -R C:\WINDOWS\SYSTEM\BWCC.DLL.
Then rerun the installation. You should now be able to proceed
through the installation as normally expected.
---------------------------------------------------------------------
[ 7. TDW - Turbo Debugger for Windows ]
Q: When I click on the TDW icon my screen goes blank or is scrambled.
A: The Turbo Debugger video DLL you are using is most likely
incompatible with your Windows video graphics driver. Download
TDSVGA.ZIP and try either TDWGUI.DLL or TDSVGA.DLL.
Then follow the instructions in the readme file.
To find this file see the list of files at the start of this
document.
-----------
Q: When I exit Turbo Debugger for Windows my machine hangs.
A: The Turbo Debugger video DLL you are using is probably
incompatible with your Windows graphics driver. Download
TDSVGA.ZIP and try either TDWGUI.DLL or TDSVGA.DLL. Then
follow the instructions in the readme file.
To find this file see the list of files at the start of this
document.
-----------
Q: "When I click on TDW, I get the error message 'Cannot
load WINDEBUG.DLL'. What should I do?"
A: This error occurs when trying to use the debugger from TPW 1.0
with Windows 3.1. TPW 1.0 was designed to be used with Windows 3.0.
There are two solutions to this problem. The recommended
solution is to upgrade to TPW 1.5 or BP 7.0.
Call the order desk at (800) 331-0877 for pricing information.
The other solution is to reinstall Windows 3.0.
-----------
Q: "I just installed Borland C++ 4.x, and I have TPW 1.5 or BP 7.0.
Why am I having problems getting the Pascal Turbo Debugger for
Windows to work correctly?"
A: Look at TI 1736
To receive this TI see the list of TI's at the start of this
document.
----------
Q: How can I get TDW 3.1 to run under Win95?
A: Turbo Degugger for Windows 3.1 is not designed to run under
Windows 95. However, there is a work around to get it working
under Win95 that should work for you. Download TDSVGA.ZIP, unzip
it and follow the instructions in the README file.
To find this file see the list of files at the start of this
document.
---------------------------------------------------------------------
[ 8. OS2 Delphi ]
Q: I am trying to run Delphi under OS/2 Warp (for Windows)
with the fixpak installed. I am experiencing a General Protection
Fault(GPF) in TOOLHELP.DLL at 0001:0626 whenever I try to close
any generated application. Any of the example programs
demonstrate this. From then on, I can't exit Delphi . I get
three msg boxes:
1) Debug process running...
2) Terminating an app the usual way is better...
3) Unable to kill the process. I get the same three dlg's
if I try to exit Delphi . I have to kill it from the
windows list. Has anybody seen this error under Warp?
A: This only occurs under Warp when the fixpak has been installed.
Try restoring Warp without the fixpak. You can remove the fixpak
altogether, or you can try the following:
The fixpack asked for an archive directory before it updated the
system. Several packed files are stored there. You simply execute
the unpack command on them and you are ready to go. Just execute
"UNPACK USERS.SCR" etc. and make sure they are in the right directory.
USERS.SCR and WINSMSG.DLL belong in your windows system directory.
WINOS2.COM belongs in the windows directory (Parent of System).
Disclaimer: This fix has not been approved by IBM.
-----------
Q: I am trying to run Delphi under OS/2 2.1X and am experiencing
the same problems as in the previous question.
A: Delphi has only been extensivly tested under Warp, and does
not work correclty under this version of OS/2
---------
Q: I'm running under OS/2 Warp and I'm having problems getting
Acrobat to work. Any ideas?
A: Go to the Acrobat Win-OS/2 session settings and set the
Win ATM selection to 'ON'. You might also want to do the
same in the Win-OS/2 setup (in the system setup folder).
----------
Q: I am running OS/2 Warp (no fixpak) and cannot run the default
form in Delphi without total system hangup. The mouse
does not respond, all escapes to OS/2 unavailable,
ctrl-alt-delete ignored.
A: Try turning off your ROM-Shadowing in your computers BIOS.
-----------
Q: How do I change video driver under OS/2 to a standard VGA?
A: One of the simplest ways to temporarily change the video
driver to VGA is:
1) Reboot the computer.
2) Wait for the OS/2 symbol.
3) As soon as the symbol appears press ALT and F1 together, That should
take you to the blue Recovery Choices Screen
4) Once in the Recovery Choices, select V : Reset primary
video display to VGA and reboot.
---------------------------------------------------------------------
[ 9. Delphi under NT
Q: I am getting an error with my PVCS. It is trying to access
a file PVCSVMW.DLL and I have PVCSVMN.DLL. How do I run PVCS
under NT ?
A: You need to contact Intersolve (800) 547-7827, they will supply
a that should remedy the problem.
---------------------------------------------------------------------
[ 10. Miscellaneous Issues]
Q: How do I deploy my application on other machines?
A: Read DEPLOY.TXT (located in the Delphi directory) for
instructions.
-----------
Q: Is there a list of book on Delphi ?
A: Yes, look at TI 2776.
To receive this TI, see the list of TI's at the start of this
document.
-----------
Q: I'm thinking about buying Delphi 1.00. Where can I find more
information?
A: Yes look at TI 2767 and TI 2768
To receive these TI's see the list of TI's at the start of this
document.
-----------
Q: How do I enable the Version Control capabilities of Delphi?
A: Click on Help | Topic Search, enter in 'Version control'
and follow the instructions. This feature is only
available with the Client/Server edition.
-----------
Q: I'm getting the error message "Out of Memory" or "Out of System
Resources", but I have plenty of memory available!
A: Try changing video driver to the Windows standard (vanilla-
flavored) VGA driver. To change your video driver, click on the
Windows Setup icon, then choose Options | Change System Settings.
If the error message doesn't appear any more, then the video
driver you were using isn't behaving properly. Contact the
manufacturer of your video driver to get the latest version. The
reason for this strange behavior is that The exception is raised
when a call to Create a Window returns an error code rather than
a window handle.
-----------
Q: I think I've found a bug in the product, how do I report
it?
A: Look at the TI 1171 and follow the instructions.
To receive this TI see the list of TI's at the start of this
document.
-----------
Q: I would like to apply to be a Beta tester for the next version
of Delphi. Where I can get more information?
A: You need to call us at Borland, (408) 431-1000, and ask for the
Developer Relations program.