home *** CD-ROM | disk | FTP | other *** search
- ═══════ Turbo Help 2.0 Patch ═══════════════════════════════════
-
-
-
-
- █▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀█
- █ TurboHelp 2.0 Patch █▓▒░
- █▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄█▓▒░
- ░▒▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▒░
-
-
- « Developed by Christopher Antos »
-
-
- █▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀█
- █ A patch to allow multiple copies █▓▒░
- █ of THelp to reside in memory █▓▒░
- █▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄█▓▒░
- ░▒▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▒░
-
-
-
-
- ─────── Patch Explanation ──────────────────────────────────────
-
-
- Here's the scoop: Borland made a boo-boo. You can only load
- one copy of THelp in memory, and you CAN'T CHANGE HELP FILES.
- This, quite frankly, sucks, if you use more than one language or
- more than one help file (very probable, now that they have a
- help file for TASM). I made a very simple patch to my copy of
- THelp, so that I have two copies of the same version of THelp,
- BUT THEY DO NOT ACKNOWLEDGE THEMSELVES TO EACH OTHER. In other
- words, each is a distinct version, and both may be loaded at the
- same time (with different hotkeys, of course). However, if you
- try to load one of them a second time, it will recognize this
- and scold you appropriately. The patch consists merely of
- changing an 8-byte ID string in the THELP.COM file.
-
- All you need is a copy of THELP.COM (v2.0) and DEBUG.COM, which
- should have come with your copy of DOS. Simply follow the
- instructions below, and you will have yourself one THelp for
- Turbo Assembler, one THelp for Turbo C++, and the standard
- THelp. I recommend naming them THELPASM.COM (for Turbo
- Assembler), THELPCPP.COM (for Turbo C++), and THELP.COM (the
- original version). Each one distinguishes itself from the
- others. For example, if you load THELPASM and then try to load
- THELPCPP, everything will go fine and THELPCPP will install
- itself. However, if you then try to load another copy of
- THELPCPP, you won't be able to, because it will know that it is
- already installed.
-
-
-
-
- ─────── Step by Step Patch Instructions ────────────────────────
-
-
- (1) Make sure you are at the DOS prompt, and that the
- orignal THELP.COM program is in the current directory.
- Also make sure that DEBUG.COM is on the DOS PATH, or
- that it is in the current directory.
-
-
- (2) Make two extra copies of your original THELP.COM file,
- and name them THELPASM.COM and THELPCPP.COM:
-
- COPY THELP.COM THELPASM.COM
- COPY THELP.COM THELPCPP.COM
-
- You will now have a total of three copies. When you are
- finished installing this patch, you will have, in
- essense, three different versions of THelp.
-
-
- (3) Now, configure the two new THelp programs:
-
- THELPASM /Fc:\asm\tasm.tah /K0C57 /W
-
- This uses the help file C:\ASM\TASM.TAH (you should
- enter the pathname for your Turbo Assembler help file,
- here), the hotkey combination Ctrl-Alt-F11. (See the
- THelp documentation for information on selecting a
- hotkey).
-
- THELPCPP /Fc:\c\tchelp.tch /K0C58 /W
-
- This uses the help file C:\C\TCHELP.TCH (you should
- enter the pathname for your Turbo C++ help file, here),
- the hotkey combination Ctrl-Alt-F12. (See the THelp
- documentation for information on selecting a hotkey).
-
-
- (4) Now that we have the THelp programs configured and ready
- to use, we will make them able to differentiate between
- each other, by changing their 8-byte ID strings.
-
- Once you are in DEBUG, the prompt will become a minus
- sign. Type the rest of the commands (below) at this
- prompt (but don't type the comments, which begin with a
- semicolon).
-
- DEBUG
-
- L THELPASM.COM ; load THELPASM.COM
- E 1F01 "THelpAsm" ; set new ID string
- W ; save THELPASM.COM
- L THELPCPP.COM ; load THELPCPP.COM
- E 1F01 "THelpC++" ; set new ID string
- W ; save THELPCPP.COM
- Q ; quit to DOS
-
-
- (5) All done. Go grab a Sprite or a Pepsi. Then enjoy the
- full benefits of the Turbo Help facilities.
-
-
-
-
- ─────── Sit Back and Relax ─────────────────────────────────────
-
-
- Now that you can have both help files resident at once, life
- becomes a little simpler, though it still has some ruffles...
-
-
-
-
- ─────── Complaints ─────────────────────────────────────────────
-
-
- I'm really surprised by the new THelp 2.0 program. It leaves
- something to be desired, but in a couple ways it is better than
- the old one.
-
- The new THelp does not make use of EMS at all, which I find
- puzzling, if not distressing. Judging from the fact that the
- executable file size is 9912 bytes and the resident size is 25k,
- I would have to assume that it is using conventional memory as a
- buffer for the help file. WHY?? The old THelp was quite
- capable of using EMS, so I consider this a major step backward.
-
- The new THelp also is incapable of switching help files once it
- is installed. Again, the old THelp was able to. Another step
- backward, though not a very big one. Seen in another light,
- this was an advantage, because I was forced to patch THelp to
- allow two help files in memory SIMULTANEOUSLY, which is
- certainly a convenient advantage. However, my reprimand to
- Borland, International still stands, because they did not
- distribute THelp with this intention.
-
- I do like the new paged format, as opposed to the old "file
- card" format (it was often annoying to have to hit PgUp/PgDn
- with the file card format), but I do not like how the cursor
- keys work now. I find having to use the Tab key extremely
- cumbersome. A convenient, simple solution to this problem would
- be to make the cursor keys select keywords if ScrollLock is off,
- or move the cursor and scroll the window if ScrollLock is on.
-
- I like a lot of the new features in the Turbo C++ Professional
- package, but I am greatly disappointed by a lot of little
- careless oversights and numerous oddities. For example, the
- installation programs for the debugger and profiler don't
- install all the colors, or even do a good job of letting you
- pick the colors. Also, Borland completely overlooked that those
- of us with EGA/VGA can have 16 background colors, and limited us
- to 8. The debugger has a number of settings that can only be
- set from within the debugger--and cannot be saved! Worst of
- all, the debugger is S...L...O...W...! I am left thinking that
- either the program is sloppily written, or it was written in a
- high-level language (quite inappropriate for a debugger). I am
- also suprised that we can't configure the mouse pointer. Also,
- the scroll bars don't work quite right in the debugger or
- profiler, although they work fine in the IDE.
-
- Most of the complaints I have are color-related (the
- installation programs look like they were tossed together at the
- last minute--they just don't install everything!), but the major
- complaint I have is an important one. On my 16MHz PS/2 Model
- 70, Turbo Debugger traces execution maddeningly slowly.
-
-
-
-
- Christopher Antos
-
-
- ═══════ End of File ════════════════════════════════════════════
-