This is an easy 'kludge' to add CompuServe B external protocol to 
GT PowerComm 12.21 and earlier versions.  (Rumor has it that GT PowerComm
12.22 may be out by late September and may include the CompuServe B
protocol internally.)  Here's a patch to be able to use the optimum
CompuServe protocol in the meantime.  NOTE:  This is not an 'official'
P&M Software patch.)

The trick is to replace GT's external Zmodem protocol with Paul Meiner's
public domain external CompuServe B protocol, CISB.COM, which is included
in this ARChive (or with a similar program such as Steve Sneed's OZBEXT).

Follow these steps:

1) Put CISB.COM in the same directory as GT1221.COM (or GT1221.0?? if you
   are running GT from a RAM disk).

2) If you are not using a 1200 baud modem edit the ZMRX.BAT and ZMTX.BAT
   files in this archive to replace '1200' with your baud rate.  Similarly,
   the parameter following the baud rate parameter in those batch files
   should reflect the number of the COM port you are using.  (COM1 as they
   are coming to you.)  You may optionally specify another directory location
   for CISB.COM as 'd:cisb 1200 1' if you wish.  See the READ.ME file for 
   CISB.COM in this ARChive for details.  

3) Replace GT's original ZMRX.BAT and ZMTX.BAT files with these new ones in
   the same directory as GT1221.COM (or GT1221.0??).

4) Use Z)modem from within GT as your transfer protocol when you want to use 
   CompuServe B.  (You will notice that GT will automatically shell to DOS
   and load CISB, assuming that CISB.COM, ZMRX.BAT, and ZMTX.BAT are 
   accessible to GT and that sufficient RAM is available.) 

5) NOTE:  When CompuServe is ready for the CISB upload or download, your
   cursor will simply 'sit' on a blank line (perhaps with a non-ASCII 
   character as the only character on the line).  It is up to you at that
   point to initiate the transfer on your end.  (Fortunately CISB will
   monitor the transfer on your screen if all proceeds correctly.)

6) NOTE:  Although GT will prompt for the filename when uploading or
   downloading from Z)modem and a valid filename is required, CompuServe
   will actually supply the filename to your default upload directory at your
   end.
7) NOTE:  When UPLOADING a file to CompuServe using this technique, CompuServe
   will not prompt you for the file description at the completion of the
   upload.  Your cursor will simply be sitting at the same blank line where
   it was when you initiated CISB.  ENTER THE FILE DESCRIPTION AT THAT POINT
   with a blank line to end.  CompuServe will then prompt you for the
   keywords as usual.  Remember that file description and keyword entry occurs
   AFTER a successful upload.  If you fail to enter the file description
   correctly, CompuServe does give you the opportunity to confirm and correct
   it before final submission.

8) As with DSZ.COM (Zmodem) and PCKERMIT.COM (Kermit), which are also external
   protocols to GT, CISB.COM (CompuServe B) must be loaded through an
   automatic shell, GT loading a secondary copy of COMMAND.COM in the process.
   This will require a total memory allocation of approximately 295K.  (Only
   approximately 130K is necessary for GT to run without external protocols
   and without being able to shell to DOS.)

9) You may set Zmodem as your CompuServe default upload protocol on GT's
   dialing directory (ALT-D).

10) Obviously, you should not makes this change if you intend to retain Zmodem
    as an option.

If you have comments I can be contacted through either Paul Meiner's BBS 
(713) 772-2090 or James Davis' BBS (713) 497-2306.  Both are dedicated to
providing support for GT PowerComm.

Bruce Aldrich
7/21/87