PRODUCT : Borland C++ NUMBER : 1010 VERSION : 3.X OS : DOS WIN DATE : October 19, 1993 PAGE : 1/13 TITLE : Installing and Configuring Borland C++ INSTALLATION AND CONFIGURATION PROBLEMS ======================================= Instructions for installing Borland/Turbo C++ can be found in the User's Guide and in the online text file README, which is contained on Disk One. This document is provided for those that are having difficulties installing or configuring. It will explain some of the most common issues that cause Borland/Turbo C++ to not be able to run, explain how to do a clean boot, and contains the most common errors received during installation and configuration and how to resolve them. At the end of the document there is a listing of the minimum system requirements needed in order to install the Borland/Turbo C++ compiler. If you are having problems running Borland C++ under OS/2 in a Dos box you need the Technical Information Document number 1373. If you are having problems running Borland C++ for OS/2 you will need to get Technical Information Document number 1301. If you try the procedures outlined in this document and are still having problems, you should contact Borland Technical Support. COMMON INSTALLATION PROBLEMS ============================== 1) One of the most common reasons for the install to fail is because of insufficient hard disk space. You should check to make sure you have enough hard disk space to install the product (see the section on Minimum System Requirements). 2) Another reason for an unsuccessful install is if there is a conflict with some other software on your computer. The best way to test this is to do a clean boot (see section on Booting Clean) and then try to run the install again. 3) You could also have problems installing if you copied between disk sizes, 3 1/2 to 5 1/4 or vise versa, or did not use the Dos diskcopy command. If you copied between sizes, please call the Disk Replacement service(800/621-3132) for the right size disks. If you use diskcopy to copy between disks of the same size and still have a problem, please call Borland Technical PRODUCT : Borland C++ NUMBER : 1010 VERSION : 3.X OS : DOS WIN DATE : October 19, 1993 PAGE : 2/13 TITLE : Installing and Configuring Borland C++ Support. COMMON CONFIGURATION PROBLEMS ============================== Most configuration problems which will prevent the product from running result from one of the three problems: 1) A need to run the configuration routine, DPMIINST.EXE If you are getting a specific error message, look it up in the error section to see if you need to run DPMIINST.EXE. Even if you are not getting an error message, it is usually a good idea to run DPMIINST.EXE because the Borland C++ compilers may need to 'learn' particulars about enabling protected mode on your system. You should do a clean boot before running this (see section on Booting Clean). In particular, the line DOS=HIGH, or any other devices that get loaded high, in your config.sys will cause DPMIINST.EXE to not be able to run. DPMIINST.EXE needs to be able to access high memory and if anything else is loaded in high memory, it will not be allowed to. DPMIINST.EXE is found in your Borlandc(or tc)\bin directory. Once you have done a clean boot (see section on Booting Clean) and are in the bin directory type DPMIINST and follow the instructions it gives you. 2) Insufficient Available Extended Memory The Borland C++ compilers need at least 1MB of extended memory (a total of 2MB on the machine) free in order to run. However, the compilers that run under Windows need 2MB of extended memory because Windows needs at least 1MB for itself (a total of 3MB on the machine). The easiest way to free up memory is to do a clean boot (see section on Booting Clean). PRODUCT : Borland C++ NUMBER : 1010 VERSION : 3.X OS : DOS WIN DATE : October 19, 1993 PAGE : 3/13 TITLE : Installing and Configuring Borland C++ To check if you have enough extended memory go to the Dos prompt and type mem if running Dos 5.0 or later. The output of the Dos 5.0 mem and Dos 6.0 mem look slightly different. Included is an example of both and the line you should check for extended memory. DOS 5 VERSION OF MEM =================== 651264 bytes total conventional memory 651264 bytes available to MS-DOS 487520 largest executable program size 1048576 bytes total EMS memory 1048576 bytes free EMS memory 7340032 bytes total contiguous extended memory 0 bytes available contiguous extended memory 1048576 bytes available XMS memory <======= should be at 64Kb High Memory Area available least 1024000 bytes,twice as much for windows DOS 6 VERSION OF MEM ==================== Memory Type Total = Used + Free ---------------- ------ ------ ------ Conventional 640K 160K 480K Upper 0K 0K 0K Adapter RAM/ROM 384K 384K 0K Extended (XMS) 7168K 6912K ===>256K<====== should be at ---------------- ------ ------ ------ least 1024k, Total memory 8192K 7456K 736K twice as much for windows Total under 1 MB 640K 160K 480K Total Expanded (EMS) 256K (262144 bytes) Free Expanded (EMS) 144K (147456 bytes) Largest executable program size 480K (491536 bytes) Largest free upper memory block 0K (0 bytes) MS-DOS is resident in the high memory area. PRODUCT : Borland C++ NUMBER : 1010 VERSION : 3.X OS : DOS WIN DATE : October 19, 1993 PAGE : 4/13 TITLE : Installing and Configuring Borland C++ **NOTE**:If you have other problems with using Dos 6.0 you will want to get Technical Information Document number 1393. 3) Hardware Incompatibility While the memory interface specification used by Borland/Turbo C++ is becoming an industry standard, it is fairly new to the computer industry. Because of this, older BIOS, particularly those dated 1988 or earlier(1989 is borderline) may need to be upgraded. You may also need to turn off any CPU and disk caches and shadow ram in your CMOS setup (see your computer documentation on how to access your CMOS settings). 4) Conflicts with other software running on your computer In order to find out if this is the problem you are having, you should do a clean boot (see section on Booting Clean). If the Borland/Turbo C++ works after doing this, then something in your config.sys or autoexec.bat conflicts with the Borland product. This could be anything from a memory manager to a mouse driver. 5) Conflicts with the use of DOS High Memory or Extended Memory Some products use extended memory in a manner which is very difficult to detect. The VDISK disk cache is an example of such a program. Older versions of PCKWIK and NCACHE may also cause problems Some device drivers, such as some hard disk managers and network adapters, may use a page in the DOS high memory area which must be made unavailable for use by Borland C++. To use such products safely, you must use a memory manager that will not allow other programs to try and use these areas of memory. For example: PRODUCT : Borland C++ NUMBER : 1010 VERSION : 3.X OS : DOS WIN DATE : October 19, 1993 PAGE : 5/13 TITLE : Installing and Configuring Borland C++ DOS 5.0's and 6.0's memory manager may be configured with the switches DEVICE=EMM386.EXE X=E000-EC00 Quarterdeck's manager may be configured with the switches DEVICE=QEMM386.EXE EXCLUDE=C000-CFFF Both of these lines will prevent the manager from allowing other programs to allocate the memory in the ranges specified. If you need to do this, your software documentation will list the ranges that would need to be excluded. BOOTING CLEAN ============== **NOTE**: If you are using a DOS compiler, then you only have to follow the procedures for Booting Clean for DOS. If you are using a Windows compiler or are going to use a DOS compiler under Windows, you will want to follow both the procedures for Booting Clean for DOS and for Windows. FOR DOS ========= The first thing you want to do is create a bootable floppy. The reason for creating a bootable floppy is because you need to edit your config.sys and autoexec.bat. If anything were to go wrong, you could always go back to your old configuration by booting without using your bootable floppy. To create a bootable floppy, put a floppy disk in drive A and at the dos prompt type: format /s a: Next copy over your config.sys and autoexec.bat files. These files are usually located in your C root directory. At the Dos prompt type: copy config.sys a: copy autoexec.bat a: After you have done this go to your A drive, by typing a:, PRODUCT : Borland C++ NUMBER : 1010 VERSION : 3.X OS : DOS WIN DATE : October 19, 1993 PAGE : 6/13 TITLE : Installing and Configuring Borland C++ and edit your config.sys and autoexec.bat. You should remark out, by typing rem at the beginning of a line, all lines in your autoexec.bat EXCEPT your path and prompt statements. For example: PATH C:\DOS;C:\BORLANDC\BIN PROMPT $P$G MOUSE should become: PATH C:\DOS;C:\BORLANDC\BIN PROMPT $P$G REM MOUSE In your config.sys you should remark out all lines EXCEPT your files and buffers statements which should be set to at least 30. For example: FILES=30 BUFFERS=30 DOS=HIGH should become FILES=30 BUFFERS=30 REM DOS=HIGH **WARNING**: Do not remark out: If you are using any kind of disk compression, Stacker or Doublespace for example, you must leave these device drivers in. If you have any SCSI drivers you must leave them in also. When you are ready to clean boot, put your bootable floppy in your A drive and reboot by pressing ctrl+alt+delete. If Borland/Turbo C++ will run after Booting Clean, then the problem is probably either 1) the use of memory by other software leaves less than 1MB of extended memory free for Borland/Turbo C++ 2) conflicting use of memory by Borland/Turbo C++ and other software The most common problem is allocating memory to a disk PRODUCT : Borland C++ NUMBER : 1010 VERSION : 3.X OS : DOS WIN DATE : October 19, 1993 PAGE : 7/13 TITLE : Installing and Configuring Borland C++ cache such that less than 1MB remains available. Examine your CONFIG.SYS file for any disk caches such as: DEVICE=C:\DOS\SMARTDRV.SYS 1024 512 The above allocates 1024KB for the disk cache (the 512 is only used if Windows is running). Other devices which may be using up memory are RAM drivers, such as: DEVICE=C:\DOS\RAMDRIVE.SYS 1024 /E This allocates 1024KB for the RAM drive. If you are not sure what is conflicting with Borland/Turbo C++, the easiest way to find out is to start with a Clean Boot and unremark a few lines at a time, testing to see when Borland/Turbo C++ will no longer run. FOR WINDOWS ============= If you are having difficulties running any part of the product under Microsoft Windows, then there are some additional steps you must take to do a clean boot. First you should make sure you do NOT remark out the line in your config.sys file that loads the himem.sys device driver. Also, the statements in the win.ini file in your Windows directory that look like this: load=something run=something should be made to look like this: load= something run= something The space after the = remarks out the "something" so that it will not be automatically loaded or run when starting up Windows. In your system.ini file, also in your Windows directory, you SHOULD have the line: PRODUCT : Borland C++ NUMBER : 1010 VERSION : 3.X OS : DOS WIN DATE : October 19, 1993 PAGE : 8/13 TITLE : Installing and Configuring Borland C++ shell=progman.exe WITHOUT a space after the =. **NOTE**: Before you try to clean boot, start Windows up and make sure your STARTUP FOLDER is empty. If things are still not working after you clean boot, try running Windows in standard mode by typing: win /s to start Windows. When you are ready to clean boot, put your bootable floppy in your A drive and reboot. COMMON ERROR MESSAGES ====================== "APPLICATION LOAD AND EXECUTE ERROR FFE0 OR 0001" You will usually get this error if you do not have enough extended(XMS) memory (see Insufficient Available Extended Memory in the Configuration Problems section). If you have XMS but not enough is free, you can try to do a clean boot (see section on Booting Clean) in an attempt to free up some more XMS. "MACHINE NOT IN DATABASE" If you get this error, you will want to do a clean boot (see section on Booting Clean) and then run DPMIINST.EXE. This is located in the bin directory of borlandc(tc). "EXCEPTION 13 (0D)" or "GENERAL PROTECTION FAULT" To alleviate this error you should first try a clean boot (see section on Booting Clean) and then running DPMIINST.EXE in your bin directory. If this doesn't alleviate the error, you may want to get Technical Information Documents 731 and 649, both of which will help you to get rid of this error. The last thing to check is your BIOS date. It should be 1990 or later, 1989 is borderline. PRODUCT : Borland C++ NUMBER : 1010 VERSION : 3.X OS : DOS WIN DATE : October 19, 1993 PAGE : 9/13 TITLE : Installing and Configuring Borland C++ "DOS ERROR CODE 14" (BORLAND C++ ICON PROBLEM) First click once on the borlandc icon. Then check the Program Manager's File|Properties menu and make sure that the command line specifies BC.PIF and not BC.EXE. "A20 LINE ALREADY ENABLED" (WHILE RUNNING DPMIINST.EXE) You will get this error if you do not remark out the line DOS=HIGH in your config.sys. You will only have to remark this out while you are running DPMIINST.EXE. After you have executed this, you can unremark DOS=HIGH. The best thing to do is a clean boot (see section on Booting Clean) and then run DPMIINST.EXE again. "CAN'T LOAD(FIND) WINDEBUG.DLL" This problem occurs if your are running Turbo Debugger 3.0 under Windows 3.1. There are three things you can do to resolve this: 1) upgrade to Turbo Debugger (Borland C++, Turbo C++ for Windows) 3.1 2) go back to Windows 3.0 3) get a temporary fix, TDWIN.ZIP, from our BBS until you can upgrade "CAN'T LOAD KEYBOARD.DLL" If you are running Turbo Debugger for Windows and get this error then you will need to run this with a -wd option. Example: win tdw -wd "CANNOT FIND UNZIP.EXE" This error can occur if you copied between disks sizes (see number 3 in the Installation Problems section). You can also get this error because of a conflict with some low-level CPU and disk caches. Try invoking your CMOS setup and turning off any CPU and disk caches. If this does not resolve the conflict, the problem can normally be resolved by booting your computer using DOS 3.31 or DOS 4.01 and then running the install routine. Once the product is installed, you can return to your original system configuration. TURBO DEBUGGER(TURBO PROFILER) FOR WINDOWS- VIDEO,SCREEN PROBLEMS PRODUCT : Borland C++ NUMBER : 1010 VERSION : 3.X OS : DOS WIN DATE : October 19, 1993 PAGE : 10/13 TITLE : Installing and Configuring Borland C++ Technical Information Document number 1037 explains how to alleviate this error. If your Video card supports SVGA, you will want to download TDSVGA.ZIP from our BBS. If you have already done this and have followed the directions on how to solve this problem, but are still having a video problem, you will want to make sure you only have one copy of the TDW.INI file. It should be in your Windows directory. If you also have one in your Borlandc(TCWIN)/bin directory delete it or move it to your Windows directory if you do not already have one there. If you are still having problems after you have done that, you will need to download TDWGUI.ZIP. TDWGUI.ZIP will run TDW in a simulated window on the screen. No video mode switching is required. TD386- PROBLEMS If your are having problems running TD386 here are some things you can try: -because TD386 will not work with any memory manager you should try doing a clean boot ( see section on Booting Clean) -TD386 needs at least 1MB possibly 2MB XMS free in order to run(see Insufficient Available Extended Memory in the Configuration Problems section) -if your have 16MB or more on your machine you need to get tdg16m.zip from our BBS -if have a scsi driver place disk386.sys before tdh386.sys in your config.sys (disk386.sys should come with your SCSI adapter or machine) -try turning off any CPU and disk caching in your CMOS setup -if none of these suggestions work, try using TD286 PRODUCT : Borland C++ NUMBER : 1010 VERSION : 3.X OS : DOS WIN DATE : October 19, 1993 PAGE : 11/13 TITLE : Installing and Configuring Borland C++ "ERROR IN PKUNZIP.EXE" If you get this error using Turbo C++ (TC) 3.0,then you can try: -doing a clean boot (see section on Booting Clean) -if you do a clean boot and still get this error but it gives you the option to continue and lets you do so then everything should be alright. PKUNZIP.EXE will sometimes incorrectly report this error because of synchronization problems. TURBO C++ VISUAL EDITION "UNHANDLED EXCEPTION ERROR" WHEN USING PROTOGEN If you have any problems when following the "Getting Started" with Protogen, you should get pvupdate.zip from our BBS. MINIMUM SYSTEM REQUIREMENTS ============================= ***NOTE***: If you are using any kind of disk compression,Stacker or Doublespace for example, then you will need twice as much as is listed below. BORLAND C++ 3.1 & APPLICATION FRAMEWORKS (BC) -80286 -DOS 3.31 -1MB extended memory(XMS), 2MB XMS for Windows -52-55 MB hard disk space to install TURBO C++ 3.1 FOR WINDOWS VISUAL EDITION (TCW) -80286 -WINDOWS 3.0 -DOS 3.0 -2MB XMS -26-30MB hard disk space to install TURBO C++ 3.1 FOR WINDOWS (TCW) -80286 PRODUCT : Borland C++ NUMBER : 1010 VERSION : 3.X OS : DOS WIN DATE : October 19, 1993 PAGE : 12/13 TITLE : Installing and Configuring Borland C++ -WINDOWS 3.0 -DOS 3.0 -2MB XMS -20-25MB hard disk space to instal TURBO C++ 3.0 DOS (TC) -80286 -DOS 3.31 -1MB XMS -12-15MB hard disk space to install ***NOTE***:The amount of hard disk space for the install has a range because the install program uses a temporary swap space while installing that it deletes when it is done installing. In order to find out how to tell the amount of extended memory your computer has free, see Insufficient Available Extended Memory in the Configuration Problems section. To check the amount of hard disk space your computer has free use the Dos chkdsk command. Below is an example of what will be printed to your screen and the line that you should check. Volume DRAGON created 07-08-1993 1:57p Volume Serial Number is 1AD9-8166 212058112 bytes total disk space 139264 bytes in 34 directories 16318464 bytes in 437 user files 195600384 bytes available on disk <===== look at this line 4096 bytes in each allocation unit 51772 total allocation units on disk 47754 available allocation units on disk 655360 total bytes memory 507936 bytes free If you have any other problems or do not understand something outlined in this document, please call Borland PRODUCT : Borland C++ NUMBER : 1010 VERSION : 3.X OS : DOS WIN DATE : October 19, 1993 PAGE : 13/13 TITLE : Installing and Configuring Borland C++ Technical Support. DISCLAIMER: You have the right to use this technical information subject to the terms of the No-Nonsense License Statement that you received with the Borland product to which this information pertains.