{ "disks": { "1": { "dirs": [ { "path": "/", "files": [ { "name": "INSTALL EXE", "size": 44182, "date": "1990-10-29", "time": "2:01" }, { "name": "README", "size": 18227, "date": "1990-10-29", "time": "2:01" }, { "name": "README COM", "size": 4217, "date": "1990-10-29", "time": "2:01" }, { "name": "TD ZIP", "size": 257496, "date": "1990-10-29", "time": "2:01" }, { "name": "TD286 ZIP", "size": 282622, "date": "1990-10-29", "time": "2:01" }, { "name": "TDEXMPL ZIP", "size": 76036, "date": "1990-10-29", "time": "2:01" }, { "name": "TDUTIL ZIP", "size": 269268, "date": "1990-10-29", "time": "2:01" }, { "name": "TFEXMPL1 ZIP", "size": 34761, "date": "1990-10-29", "time": "2:01" }, { "name": "TFEXMPL3 ZIP", "size": 28873, "date": "1990-10-29", "time": "2:01" }, { "name": "TFUTIL2 ZIP", "size": 13196, "date": "1990-10-29", "time": "2:01" }, { "name": "UNZIP EXE", "size": 23044, "date": "1990-10-29", "time": "2:01" } ] } ], "volume": "TURBO DEBUG" } }, "desc_file": "README", "desc_text": " WELCOME TO TURBO DEBUGGER 2.01\r\n ------------------------------\r\n\r\n This README file contains important information about Turbo\r\n Debugger Version 2.01. For the latest information about Turbo\r\n Debugger 2.01, the accompanying programs, and the manual, read\r\n this file in its entirety.\r\n\r\n\r\nTABLE OF CONTENTS\r\n-----------------\r\n1. How to Get Help\r\n2. Installation\r\n3. Notes and Restrictions\r\n4. About Turbo Debugger 2.01\r\n5. Files on the Disks\r\n\r\n\r\n1. HOW TO GET HELP\r\n-------------------\r\n\r\n If you have any problems, please read this file, HELPME!.DOC,\r\n MANUAL.DOC, and the Turbo Debugger User's Guide first. If you still\r\n have questions and need assistance, help is available from the\r\n following sources:\r\n\r\n 1. Type GO BOR on the CompuServe bulletin board system for\r\n instant access to the Borland forums with their libraries of\r\n technical information and answers to common questions.\r\n\r\n If you are not a member of CompuServe, see the enclosed\r\n special offer, and write for full details on how to receive\r\n a free IntroPak containing a $15 credit toward your first\r\n month's online charges.\r\n\r\n 2. Check with your local software dealer or users' group.\r\n\r\n 3. Write to us at the following address:\r\n\r\n Borland International\r\n Turbo Debugger Technical Support\r\n 1800 Green Hills Road\r\n P.O. Box 660001\r\n Scotts Valley, CA 95066-0001\r\n\r\n Please remember to include your serial number or we will be\r\n unable to process your letter.\r\n\r\n 4. If you have an urgent problem that cannot wait and you have\r\n sent in the license agreement, you may call the Borland\r\n Technical Support Department at (408) 438-5300 Monday through\r\n Friday between the hours of 6 a.m. and 5 p.m. Pacific Time.\r\n Please have the following information ready before calling:\r\n\r\n a. Product name and serial number on your original\r\n distribution disk. Please have your serial number ready\r\n or we will be unable to process your call.\r\n\r\n b. Product version number. The version number is displayed\r\n when running Turbo Debugger and pressing the \r\n keys to bring up the System menu and choosing the\r\n About... option.\r\n\r\n c. Computer brand, model, and the brands and model numbers\r\n of any additional hardware.\r\n\r\n d. Operating system and version number. (The version number\r\n can be determined by typing VER at the DOS prompt.)\r\n\r\n e. Contents of your AUTOEXEC.BAT and CONFIG.SYS files.\r\n\r\n\r\n2. INSTALLATION\r\n----------------\r\n\r\n You should read the rest of this README file to get further\r\n information about this release before you do the installation.\r\n\r\n The Turbo Debugger/INSTALLATION disk contains a program called\r\n INSTALL.EXE that will assist you with the installation of Turbo\r\n Debugger 2.01.\r\n\r\n To start the installation, change your current drive to the one\r\n that has the install program on it and type INSTALL. You will be\r\n given instructions in a box at the bottom of the screen for each\r\n prompt. For example, if you are installing from drive A:,\r\n you type\r\n\r\n A: \r\n INSTALL \r\n\r\n If you have difficulty reading the text displayed by the INSTALL\r\n program, use the /B command-line parameter to force it to use\r\n black and white colors:\r\n\r\n a:install /B - Forces INSTALL into BW80 mode\r\n\r\n Specifying the /B parameter may be necessary if you are using an\r\n LCD screen or a system that has a color graphics adapter and a\r\n monochrome or composite monitor.\r\n\r\n Notes for installation:\r\n\r\n INSTALL copies all Turbo Debugger files onto your hard disk\r\n and puts them into subdirectories. The default subdirectories\r\n are\r\n\r\n Turbo Debugger Directory: C:\\TD\r\n Examples Subdirectory: C:\\TD\r\n\r\n By default, all files from the distribution disks are placed in\r\n the Turbo Debugger Directory. If you would rather separate the\r\n example programs into their own subdirectory, edit the default\r\n example files path before selecting START INSTALLATION.\r\n\r\n The Turbo Debugger distribution disks contain several files\r\n with a .ZIP file extension: TD.ZIP, TDUTIL.ZIP, TDEXMPL.ZIP,\r\n etc. These files contain one or more other files that have been\r\n compressed and placed inside an archive. You can de-archive\r\n them by using the UNZIP.EXE utility. For example,\r\n\r\n unzip /o tdexmpl\r\n\r\n unpacks all the files stored in the TDEXMPL.ZIP archive into the\r\n current directory.\r\n\r\n INSTALL gives you a choice of copying the .ZIP files intact or\r\n de-archiving and copying all the individual files onto your hard\r\n disk during the installation process.\r\n\r\n\r\n3. NOTES AND RESTRICTIONS\r\n--------------------------\r\no You need to set the files directive in your CONFIG.SYS file to\r\n at least FILES = 10, preferably FILES = 20. If you have trouble\r\n doing the File|DOS Shell command or if TD can't find your source\r\n modules, make sure the FILES directive is in your CONFIG.SYS.\r\n\r\no FNxxxx variants of floating-point instructions are not\r\n supported in the built-in assembler in the CPU window.\r\n\r\no The Fxxxx instructions do not generate an FWAIT in Turbo\r\n Debugger. You must manually code an FWAIT before floating-point\r\n instructions if needed.\r\n\r\no A single Ctrl-Break inside a DOS function call waiting for\r\n console input will not interrupt DOS and return control to Turbo\r\n Debugger. You can either press Ctrl-Break once and then end the\r\n console input function by pressing Enter, or press Ctrl-Break\r\n twice. You will then interrupt DOS and Turbo Debugger will bring\r\n up a CPU Viewer showing code inside DOS. At this point, you can\r\n look around inside your program, but you might not be able to\r\n use F7 or F8 to trace or step inside DOS. You should use only F9\r\n at this point, possibly after setting a breakpoint inside your\r\n program.\r\n\r\no If you are using TD386, make sure that you use the -e option if\r\n you have loaded any TSRs or device drivers that are using\r\n extended memory allocated using the VDISK method. The value to\r\n indicate after the -e is the total amount (in Kbytes) of\r\n extended memory at the bottom of the extended memory area that\r\n is being used by other applications before loading TD386. If you\r\n do not use this option, TD386 may overwrite extended memory that\r\n is being used by the other applications. For example, if a\r\n disk-caching program that uses extended memory is loaded and you\r\n do not use the -e option, the program may write incorrect\r\n information to your hard disk.\r\n\r\n NOTE: If your programs use the INT 0x15, function 0x88 method\r\n to allocate memory, DO NOT count this memory, as TD386 will\r\n automatically leave that memory alone.\r\n\r\no TDINST contains two new options in the Display dialog box.\r\n 'Floating precision' allows you to set the floating-point\r\n precision for variables entered in the Evaluate/Modify dialog\r\n box and Watches window. 'Range inspect' lets you set the\r\n default range for the number of elements to show in inspectors.\r\n\r\no You can set the way display updating is performed using either\r\n command line options (-do, -dp, -ds) or TDINST (selecting\r\n Display from its main menu shows the Display Options dialog\r\n box). For both methods, user screen updating now defaults to\r\n Swap. You might want to select Flip for faster operation;\r\n however, this option can cause display problems in some\r\n circumstances (usually involving memory-resident programs'\r\n assuming the active display page has not changed). If you set\r\n user screen updating to Flip and the File|Dos shell command\r\n causes display problems, changing back to Swap should solve the\r\n problem.\r\n\r\no In version 2.01, TDINST contains two new options in the\r\n Miscellaneous Options dialog box.\r\n\r\n - Full Trace History enables you to set whether Turbo Debugger\r\n begins with full Backtrace capability. This option defaults\r\n to OFF because saving Backtrace information slows execution\r\n of the program. If the Full Trace History option is off,\r\n you can't use Run|Backtrace in Turbo Debugger until you turn\r\n this option on, by choosing the Full History option on the\r\n local menu of the Execution History window.\r\n\r\n - Link Speed now has a setting for 19200 baud. New command\r\n line options controlling baud rate in TD and TDREMOTE are:\r\n -rs1 9600 baud (unchanged from version 2.0)\r\n -rs2 19200 baud (new)\r\n -rs3 38400 baud (previously -rs2)\r\n -rs4 115000 baud (default, previously -rs3)\r\n\r\no In version 2.01, the default setting for the NMI intercept is\r\n OFF. If you are using a hardware debugging board, you might need\r\n to turn this option on. Use caution, however, as several types\r\n of machines have incompatibilities that might cause mysterious\r\n crashes, possibly causing loss of data in memory or on disk. If\r\n you are using a Tandy 1000, we strongly recommended that you\r\n leave the NMI intercept off.\r\n\r\no For those of you using TD286.EXE, note that you may have to run\r\n TD286INS.EXE so that TD286 recognizes your machine\r\n configuration. In doing so, a file may be generated which has a\r\n .db extension. It is necessary that we have this file in order\r\n to make TD286 a better product. You may, if you wish, upload\r\n this file to our BBS (Bulletin Board Service) here at Borland.\r\n When doing so you should call (408) 438-5300 and give our\r\n representatives your serial number so that they may allow you to\r\n upload your file. They will help you with any questions you\r\n have regarding the use of our BBS. You can use TD286 with\r\n programs that are VCPI compliant, such as 386MAX, CEMM, & QEMM.\r\n However, to do so, there MUST be at least 640K of available EMS\r\n provided by these programs. You can determine how much free EMS\r\n is available by using TDMEM.\r\n\r\no If you are using TD386, and you are receiving a \"not enough\r\n memory to load symbol table\" message, you need to enable EMS\r\n emulation for TD386. To do this, use the -F option. For\r\n instance, to set up EMS for TD386 at segment 0D000h, invoke\r\n TD386 with \"-FD000\".\r\n\r\no If you are using an HP-Vectra, and you get an Unexpected Interrupt\r\n 06 when trying to run TD386, you need to set an option in the\r\n CMOS setup. By default the Vectra series uses a protected mode\r\n instruction as part of the HP-HIL. To work around this, contact\r\n Hewlett Packard for instruction on disabling this function.\r\n\r\no If an Exception 06 occurs after running for awhile in TD386,\r\n your code has probably been overwritten. An Exception 6 is\r\n generated by the 80386 when an illegal opcode is encountered.\r\n Common causes of this problem are using uninitialized pointers,\r\n etc.\r\n\r\no Exception 06, Exception 13, and Unexpected Interrupt 0D can also\r\n occur if you are using an old mouse driver, network driver, or\r\n other device driver. If you get these errors in TD386, try\r\n removing device drivers one at a time, starting with your mouse\r\n driver, then your network driver, and so on until you identify\r\n the offending driver. If an upgrade is available for the driver,\r\n see if installing it corrects the problem. The last resort is to\r\n remove the driver entirely, if possible.\r\n\r\no If stepping through your program seems extremely slow there are\r\n two common causes.\r\n\r\n - If you are using a PS/2 mouse driver, either remove the\r\n mouse driver or use a non-PS/2 mouse driver. Alternatively,\r\n you can disable the use of the mouse through the -p-\r\n command line option for TD.\r\n\r\n - Otherwise, slow execution is usually due to excessive disk\r\n swapping. Try using the \"-y##\" command line option (changes\r\n the size of your overlay pool) and experiment with higher\r\n or lower ## values.\r\n\r\no If you have a problem with TDCONVRT, you can get the latest\r\n version either from CompuServe, forum BPROGB section 7, or by\r\n calling the Borland Support BBS at (408)439-9181 and downloading\r\n TDCONVRT.ZIP. You will need the serial number from your Turbo\r\n Debugger installation diskette.\r\n\r\no If you get a \"Cannot run TD386: Processor is already in V8086\r\n mode\" error message when trying to load TD386, then you are\r\n using a program which uses the virtual mode of the 80386 (such\r\n as QEMM). At this time, it is not possible to use these\r\n programs and TD386 at the same time. If you need to use these\r\n memory managers, try using TD286 instead of TD386.\r\n\r\no If you're having problems with the mouse cursor disappearing or\r\n behaving erratically, you probably need an updated version of your\r\n mouse driver. Because Turbo Debugger 2.01 demands more from the\r\n mouse driver than most previous programs, you might not experience\r\n a problem with your current driver until you use Turbo Debugger 2.01.\r\n\r\n At this time, the current major mouse driver revisions are:\r\n\r\n Logitech 4.10\r\n Genius 9.03\r\n Microsoft 7.04\r\n\r\n Contact the manufacturer of your mouse for information about\r\n obtaining a newer version.\r\n\r\n\r\n4. ABOUT TURBO DEBUGGER 2.01\r\n-----------------------------\r\no Version 2.01 of Turbo Debugger has been designed to support the\r\n C++ language of Turbo C++. Earlier versions of Turbo C, Turbo\r\n Pascal, and TASM are still compatible with the new Turbo\r\n Debugger 2.01 as follows:\r\n\r\n TASM 1.0 (or later)\r\n Turbo C 2.0\r\n Turbo Pascal 5.0 (or later)\r\n\r\no The Utilities and Hardware Debugging appendices from the Turbo\r\n Debugger User's Guide have been incorporated into the\r\n MANUAL.DOC file on the Turbo Debugger disks.\r\n\r\no The file HELPME!.DOC on the distribution disks has more\r\n information about using the new mouse capabilities of Turbo\r\n Debugger 2.01.\r\n\r\no By default, TD286 will use all of your extended memory. If you\r\n are debugging programs which use extended memory you can\r\n specify the amount of extended memory that TD286 is allowed to\r\n use by creating a file in the root directory of your current\r\n drive, called CONFIG.286. This file can contain the following\r\n command:\r\n\r\n MEGS=#\r\n {Where # = the amount of extended memory TD286 is allowed to use}\r\n\r\n Also note p. 254 of the Turbo Debugger User Manual states that TD286.EXE\r\n uses all the same command-line options as TD.EXE. This holds with some\r\n exceptions. The -sm# option is not used by TD286.EXE since it runs in\r\n protected mode and automatically defines the necessary space for your\r\n programs spare symbol table. The -r options are not used since it\r\n is not necessary to perform remote debugging and the -y<#> options since\r\n TD286 does not use overlays.\r\n\r\n5. FILES ON THE DISKS\r\n----------------------\r\n\r\n TURBO DEBUGGER/INSTALLATION\r\n ---------------------------\r\n INSTALL EXE - Turbo Debugger installation program\r\n README COM - Program to display README file\r\n UNZIP EXE - Program to unpack archive programs\r\n TD ZIP - Packed file containing the Turbo Debugger program\r\n TD EXE - Turbo Debugger Program\r\n HELPME! DOC - Lists answers to common questions about TD\r\n MANUAL DOC - Explains corrections to the user's guide\r\n README - This file\r\n\r\n\r\n TURBO DEBUGGER/UTILITIES\r\n ------------------------\r\n TDUTIL ZIP - Packed help and utility programs\r\n TD386 EXE - 80386 virtual debugging\r\n TDCONVRT EXE - Converts CodeView information to Turbo Debugger format\r\n TDH386 SYS - Device driver for TD386.EXE and the 80386 debug registers\r\n TDMAP EXE - Extracts debug information from .MAP files\r\n TDNMI COM - TSR to clear NMI every half second\r\n TDPACK EXE - Compresses debug information\r\n TDREMOTE EXE - Remote debugging kernel\r\n TDRF EXE - Remote file transfer utility\r\n TDSTRIP EXE - Strips debug information off executable files\r\n TDUMP EXE - Dumps executable and object file information\r\n TDINST EXE - Custom configuration program\r\n TDHELP TDH - Turbo Debugger help file\r\n TDMEM EXE - Displays the contents of memory\r\n TDDEV EXE - Displays any device drivers that are loaded\r\n\r\n TDEXMPL ZIP - Packed file that contains Turbo Debugger examples\r\n TCDEMO C - Turbo C Program To Demonstrate Debugger Features\r\n TCDEMO EXE - Executable File For Turbo C Program\r\n TCDEMOB C - Turbo C Program To Demonstrate Debugger Features\r\n TCDEMOB EXE - Executable File For Turbo C Program\r\n TPDEMO PAS - Turbo Pascal Program To Demonstrate Debugger Features\r\n TPDEMO EXE - Executable File For Turbo Pascal Program\r\n TPDEMOB PAS - Turbo Pascal Program To Demonstrate Debugger Features\r\n TPDEMOB EXE - Executable File For Turbo Pascal Program\r\n\r\n TFUTIL2 ZIP - Packed Turbo Profiler utility\r\n TF386 EXE - Utility For 80386 virtual profiling\r\n\r\n\r\n TURBO DEBUGGER/TD286\r\n --------------------\r\n TD286 ZIP - Archive containing the Protected Mode Turbo Debugger\r\n TD286 EXE - Protected Mode Turbo Debugger program\r\n TD286INS EXE - Kernel Configuration Program for Installing TD286.EXE\r\n\r\n TFEXMPL1 ZIP - Archive containing Turbo Profiler examples\r\n PLOST C\r\n PLOST EXE\r\n PLOSTPAS PAS\r\n PLOSTPAS EXE\r\n PTOLL C\r\n PTOLL EXE\r\n PTOLLPAS PAS\r\n PTOLLPAS EXE\r\n CALLTEST C\r\n CALLTEST EXE\r\n OVRDEMO PAS\r\n OVRDEMO1 PAS\r\n OVRDEMO2 PAS\r\n OVRDEMO EXE\r\n OVRDEMO OVR\r\n\r\n TFEXMPL3 ZIP - Archive containing Turbo Profiler examples\r\n PRIME0PA PAS\r\n PRIME0PA EXE\r\n PRIME1PA PAS\r\n PRIME1PA EXE\r\n PRIME2PA PAS\r\n PRIME2PA EXE\r\n PRIME3PA PAS\r\n PRIME3PA EXE\r\n PRIME4PA PAS\r\n PRIME4PA EXE\r\n PRIME5PA PAS\r\n PRIME5PA EXE\r\n PRIME6PA PAS\r\n PRIME6PA EXE\r\n\r\n\r\n NOTE: If you have the 3.5\" version of Turbo Debugger, the disk\r\n layout is as follows.\r\n The TURBO DEBUGGER/INSTALLATION disk is combined with\r\n the TURBO DEBUGGER/UTILITIES disk.\r\n\r\n The TURBO PROFILER/INSTALLATION disk is combined with\r\n the TURBO DEBUGGER/TD286 disk." }