🚀 go-pugleaf

In article <14015@reed.UUCP> minar@reed.bitnet (Nelson Minar) writes:
>...
>My problem is a simple one.  In Turbo C 2.0, I turn on EGA mode with the
>standard function call.  Then I use printf() to put text on the screen
>(things like logical color number and its composition).  The problem is, I
>need to position the text on the screen so it lines up properly. What I have
>been doing is using gotoxy() to move the cursor over, and then printf() to
>stick the text on the screen.
>
>Unfortunately, gotoxy() seems to be leaving behind a cursor, namely an ugly
>white underbar.
>...

Along similar lines, I recently rewrote the dos.c module of STEVIE to use
the Turbo-C text library for FAST output, and discovered that the library 
routines are HARDCODED for a 25-line screen!!  

This includes the gotoxy(), insline(), delline() etc..

The hardcoding is in an internal routine which initializes the default
text window data structure used by these routines.  If it is patched 
(in two places), then all of the other routines look like they ought to
work just fine.  The trick is.. 

HOW does one patch a routine in the Turbo-C 2.0 libraries?  Without source code?
Hmmm.. just need a good binary editor, I guess.
Perhaps I'll give Borland Tech Support a call and ask about this..

Meanwhile, I further altered STEVIE to correctly determine the number of lines
available, and it uses the TURBOC stuff if the screen has 25 lines, and it uses
the ANSI escapes for any other size (30, 40, 50, 60 lines..).  Works fine.
-- 
 ______Mark S. Lord______________________ ______________________________
|    ..uunet!bnrgate!carrsc!mlord        | These are only MY opinions.  |
| or:  bnr-rsc!mlord@bnrgate             | I charge for official views. |
|________________________________________|______________________________|