Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!mnetor!seismo!lll-crg!topaz!uwvax!cameron From: cameron@rsch.wisc.edu (Andrew J Cameron III) Newsgroups: net.micro.pc Subject: Re: NANSI.SYS and Turbo Prolog & Turbo Prolog reactions request Message-ID: <2567@rsch.wisc.edu> Date: Mon, 4-Aug-86 02:39:52 EDT Article-I.D.: rsch.2567 Posted: Mon Aug 4 02:39:52 1986 Date-Received: Mon, 4-Aug-86 07:19:52 EDT References: <739@oakhill.UUCP> Distribution: na Organization: U of Wisconsin CS Dept Lines: 38 Keywords: NANSI.SYS, Turbo Prolog In article <739@oakhill.UUCP>, luis@oakhill.UUCP (Luis Basto) writes: > I started using NANSI.SYS recently and was very satisfied with its faster > screen scrolling. ... > However, there seems to be a problem when using it with Turbo Prolog. > Everything works normally except on Quit. Then the screen blanks completely > until a warm boot (Ctrl-Shift-Del) is used. Any clues as to what might be > causing this? Thanks. I experienced the same symptoms, but one should not be so quick to re-boot. Always try other things first, like and , etc. In this case however, these don't help. The remedy is a bit more obscure. Ever think of typing "mode co80" even though the screen is comatose and you get no response to the keystrokes? It worked for me. Seems Turbo_Prolog QUITs leaving the system in "Monochrome Monitor" mode or at least not a "Color Monitor" mode. (I have not gotten around to contacting Borland about this.) I use the following batch file (called "TP.BAT") as a workaround: PROLOG %1 %2 %3 %4 %5 %6 %7 %8 %9 MODE CO80 EXIT Now you would invoke Turbo_Prolog by typing "TP" instead of "PROLOG". BTW, NANSI is not the only culprit. I encountered this problem when I first started using Turbo_Prolog (FCONSOLE was loaded at the time). I tried again using a "bare" system (no CONFIG.SYS and no AUTOEXEC.BAT) and there was no problem with QUITting. Everything is fine when ANSI.SYS is loaded as well. The above batch file enables one to use FCONSOLE (and NANSI as well, I assume). -- andyiii P.S. I would be interested in anyone's reactions to Turbo_Prolog in general (actually, the more specific, the better). If I get a significant number of responses, I will summarize and re-post to the net.