Xref: utzoo alt.msdos.programmer:767 comp.sys.ibm.pc:38822
Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!uunet!ibmpa!ironside!eclarke
From: eclarke@ironside.uucp (Eric S. Clarke)
Newsgroups: alt.msdos.programmer,comp.sys.ibm.pc
Subject: Re: Turbo C console i/o routines and non-standard video modes
Message-ID: <3056@ibmpa.UUCP>
Date: 27 Nov 89 16:13:39 GMT
References: <2090@calvin.EE.CORNELL.EDU>
Sender: news@ibmpa.UUCP
Reply-To: eclarke@ibmsupt.UUCP (Eric S. Clarke)
Distribution: na
Organization: IBM AWD Development, Palo Alto
Lines: 28

In article <2090@calvin.EE.CORNELL.EDU> richard@calvin.EE.CORNELL.EDU (Richard Brittain) writes:
>1)  Whether Borlands console i/o routines will work (cputs, cprintf etc.) in
>    a window larger than 25x80
>2)  Whether the standard i/o routines will work, assuming the display is
>    already in the required mode, or can be set using something nnansi.sys
>
>I have already established that the gettextinfo() routine does not return
>the correct screen size but I think I can fix that.  

I have used cputs, cprintf etc., in text windows of 135x43 on an EGA and 135x50
on a VGA with no problems.  I am not sure why you claim gettextinfo() doesn't 
work.  I have used it to get the info for the windows I mentioned above.  If it
wasn't working that is news to me.

I don't know if you are talking about standard DOS i/o routines or Borland's
standard i/o routines in paragraph two.  I also don't know what a nnansi.sys
is.  I can guess that nnansi.sys is a replacement ansi.sys supplied by some
VGA card maker but that is only a guess.  It would be nice to have a little 
more info.

The above statements are only my opinions.  They in no way reflect the official
opinions of IBM or of IBM AWD Development.



Eric S. Clarke                                   UUCP: uunet!ibmsupt!eclarke
1510 Page Mill Road                              COM:  415-855-4458
Palo Alto, CA 94304                              TIE:  465-4458