Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10 beta 3/9/83; site mot.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!allegra!bellcore!decvax!genrad!teddy!panda!talcott!harvard!seismo!ut-sally!oakhill!mot!edski
From: edski@mot.UUCP (Ed Skinner)
Newsgroups: net.micro.pc
Subject: TurboPascal 2.0 Patch (MSDOS)
Message-ID: <84@mot.UUCP>
Date: Tue, 15-Jan-85 17:15:03 EST
Article-I.D.: mot.84
Posted: Tue Jan 15 17:15:03 1985
Date-Received: Sun, 20-Jan-85 00:36:26 EST
Organization: Motorola Microsystems, Phoenix AZ
Lines: 18


     When TurboPascal (the compiler, or a created .COM file) begins, it takes
over the breakpoint vector.  If you want to "debug" a TurboPascal program,
such as one containing in-line machine code or "external" assembler routines,
you are out of luck:  Any breakpoint gets handled by Turbo, not by Debug.
     To prevent TurboPascal from snarfing up this vector, modify cs:be2 thru
cs:be4 to hex 90 90 90.  (This replaces a "call" instruction with three NOPs.)
     Note that reaction to ^C will be "different" (?) and that this patch
should not be used except for debugging purposes.  Production code should not
include this patch.

     Also, I am told that the September 1984 issue of PC Tech Journal contains
a patch to disable the initial "ClrScr" which occurs when a Turbo program is
started.  I think the patch is in a letter to the magazine.

     Anyone know a patch to prevent keyboard buffer purging?  I.e., to allow
type-ahead?  Folks at Borland didn't have one for this.