PATCHES FOR IBM DOS 3.3
                         -----------------------
                                ADDENDUM
                             by Frank Fitch
                                 2-1-88

    In the process of testing these routines, I wrote EDLIN scripts
    to perform the actions called upon by DOS33.PAT.  So the patches
    for which there is a .SCR file has been tested.  [No way, I was
    going to do the FORMAT patch and add yet another beep to my life]
    
    However, before using the scripts, I would recommend that you do
    just as I did, use DEBUG's (D)ump command to verify that what is
    supposed to be there is indeed there.  Of course, if it isn't,
    don't continue with that patch.
    
    You could make the same mistake that I did.  My memory said that
    I was to change the name of FIND.EXE to temp.com.  When I asked
    DEBUG to dump the appropriate location, the 03 that was expected
    was not there.  I must have been asleep, EXE files not only can't be
    loaded directly, but they have to be loaded as a nonexecuting file
    (some extension other than .EXE or .COM, so they will be loaded at
    the proper starting address.  Sure enough, the documentation said
    FIND.TMP was the name to give FIND.EXE.

    While I was checking out COMP.COM, I noticed that the second location
    to be changed was the hiding place of all the beeps that program
    inflicts upon the user, so I put together an extra script for
    eliminating the beeps.  Would you believe that program has 8
    separate error messages terminating with beeps?
    
    Fortunately, they are caused by the 'bell' character (ASCII 7)
    being placed at the very end of the error message.  The message
    is displayed by the DOS routine that determines that it has found
    the end of the message when it encounters a '00', so my .SCRipt
    just shortens each beeping error message by 1 character by replacing
    the '07' with a '00' in front of the existing '00' end of message
    indicator.  Since the program starts its messages with a <CR><LF>,
    you could replace the beep with another character (like '@') to
    assist in finding/searching a redirection capture file of the
    results of COMPs actions on a number of files.  But it won't be
    terminated by a <CR><LF>.

    This is a list of the script files I've enclosed:

        ANSI-SC  SCR      33   | FIND-HD  SCR      18
        COMP-50  SCR      30   | OFF-ECHO SCR      30
        COMP-BEP SCR     102   | PRINT    SCR      39


    Keep in mind that making any patches to programs entails a measure
    of risk, and since only you can determine its magnitude, the
    responsibility both for the decision and any consequences must
    rest with you.

                Good luck,
                %% Frank %%