Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!cs.utexas.edu!uunet!ucscc.ucsc.edu!gorn!filbo From: filbo@gorn.santa-cruz.ca.us (Bela Lubkin) Newsgroups: comp.lang.pascal Subject: Re: Turbo 3.0 - Monochrome/CGA support Message-ID: <40.filbo@gorn.santa-cruz.ca.us> Date: 29 Sep 89 04:21:39 GMT References: <1794@draken.nada.kth.se> Organization: R Pentomino Lines: 27 X-Claimer: I >am< R Pentomino! In article <1794@draken.nada.kth.se> Rickard Jonsson writes: >My question is - does setting up the >compiler with TINST affect the way my program is executed on different >machines? Yes, in Turbo 3.0 it does. Make sure the compiler is installed for "default". >the problem which appears on the monochrome systems is that my windowing >with Window() does not work at all, although some text comes out right. I half-remember some sort of interaction between the Window and TextMode procedures. Calling TextMode with no arguments puts the monitor in text mode but, on mono systems, stores some wrong values into some of the runtime library's internal variables. I >think< you must call TextMode(7) on mono systems. Also, I think I remember a function whose name is NOT GetTextMode, but has that effect. The proper thing to do is to call GetTextMode at the beginning of the program, store its return into a variable, and always use TextMode(OrigTextMode). GetTextMode may not exist (and certainly has a different name), in which case you should query the BIOS. And TextMode(7) might also be wrong; be sure to experiment. Finally, Window doesn't work right for 1-line windows; be sure you're not creating one of those. Bela Lubkin * * filbo@gorn.santa-cruz.ca.us CIS: 73047,1112 @ * * ...ucbvax!ucscc!gorn!filbo ^^^ REALLY slow [months] R Pentomino * Filbo @ Pyrzqxgl (408) 476-4633 & XBBS (408) 476-4945