delsec03.txt

《Delphi开发人员指南》配书原码

	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 TechFax
	(800-822-4269), Compuserve (GO DELPHI), ftp (ftp.borland.com), or
	the BBS (408-431-5096) as 'ti2733.zip' and 'ti2734.zip'.
	

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 just 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's 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 worked, 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 another driver.


Q:      I had Quattro Pro running on a network, and after I installed 
	Delphi and overwrote the IDAPI that was on the network, none of
	the users can run Quattro Pro anymore.  They get a "Cannot load
	language driver" error.  How can I fix this?

A:      The version of IDAPI that comes with Delphi is compatible with 
	Quattro Pro, with only slight modification.  For each client that
	will be accessing IDAPI on the network, be sure the 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 it's 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 in case this happens.
		First and foremost, one must always clean boot to make
	sure that the problem isn't 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 doesn't work, try deleting delphi.ini from
	your Windows directory and then restaring Delphi (delphi.ini will
	get recreated).  If this still doesn't 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 doesn't 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.  Download Technical Information Document 1561 and
	1283 from TechFax (call 1-800-822-4269) for step-by-step information
	on how to do a DOS and Windows clean boot.


Q:      I am trying to install a vbx or 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 cannot 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 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.


Q:      I am installing from the CD, and I am getting file corruption
	errors.  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 when it
	is being copied.  It is most often on faster computers (DX4's and
	P5's mainly) with faster hard drives.
	   Try slowing down the computer.  This is most easily accomplished
	with the turbo switch (Didn't you always wonder what those things were
	for?) If your computer doesn't have a turbo switch, try disabling your
	video Rom shadowing, disabling Smartdrive, turning off Windows 
	caching, or a combination of all of the above.
	   If you still are having problems, copy the install directories
	off of the CD (with the computer slowed) and try doing a hard drive
	install.


Q:      I am installing Delphi and I get an error message: "No ExtVer Method"
	in the file ODBCDRV.PAK ..\install\disk3. Where is the method?

A:      This is a known bug. There are, however, some options to try:
	1. Clean boot.(TI 1561)
	2. Disk install. Copy an INSTALL subdirectory from the Delphi CD to 
	   the temporary directory on the hard drive and run SETUP.EXE from 
	   there.
	3. Try to run Delphi from the CD ROM (ti 2777) and if it works, copy 
	   the Runimage directory to the hard drive.
	
	Apparently this error can be circumvented  if you install without DBD 
	and/or Local Interbase.


Q:      I want to apply to be a Beta tester for the 32-bit version of Delphi. 
	Where I can get more information?

A:      You need to call us at Borland, [phone], and ask for the
	Developer Relations program.


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.)


Q:      My FormExpert does not run, or does not appear. What do I need to do?

A:      1. Make sure that [Experts] section in delphi.ini has 
	   FormExpert=Mydrive:\delphi\bin\exptdemo.dll
	2. Close Delphi, backup DELPHI.INI, delete DELPHI.INI, 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.  e.g.

   [ReportSmith]
   ExePath=C:\RPTSMITH


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.  What's going on?

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 the installation program is trying to write to is already on
    your system, and 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.


Q:  If I have a dual boot machine, say 95 and NT, and I've installed Delphi
    using 95, but I can't run Delphi under NT.  What's going on?

A:  Two installations are necessary; one per operating system.  However, all
    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. E.g. WINDOWS\SYSTEM.

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 workaround to get it working under Win95 that should
    work for you.
    Download TDSVGA.ZIP from the BBS under our C++ Conference.  Unzip it
    and follow the instructions in the readme.

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 if 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 this DLL 
    elsewhere and everything should work fine.

Q:  I am running Delphi in Windows95, and now the text, in my dialog boxes
    and error messages, appear in some garbage font.  What's going on?

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.