Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 GARFIELD 20/11/84; site garfield.UUCP
Path: utzoo!utcsrgv!garfield!derek2
From: derek2@garfield.UUCP (Derek S Keeping)
Newsgroups: net.micro.pc
Subject: Re: ANSI.SYS & emulation
Message-ID: <2427@garfield.UUCP>
Date: Thu, 31-Jan-85 15:17:29 EST
Article-I.D.: garfield.2427
Posted: Thu Jan 31 15:17:29 1985
Date-Received: Thu, 31-Jan-85 16:20:04 EST
References: <24700097@uiucdcs.UUCP> <24700099@uiucdcs.UUCP>
Reply-To: derek2@garfield.UUCP (Derek S Keeping)
Followup-To: net.micro.pc
Distribution: net
Organization: Memorial U. of Nfld. C.S. Dept., St. John's
Lines: 23
Keywords: ansi basic bios
Summary: Using ANSI.SYS with basic


	Hello.
    
	I tried opening con: as a device and found it still bypassed ANSI.SYS
	This was on a old motherboard PC with DOS 2.0 so it may work with 2.1
	or whatever.

	The problem which has been mentioned before is that Basic does its own
	I/O. (at least as far as the screen is concerned.) The way I finally
	got around this was to write a small routine that took a string and
	displayed it using a DOS function call. That way ANSI.SYS got a chance
	to process the string.

	This is not to say that this is a great way to do this. From what I have
	read, BIOS is terribly slow for displaying things on the screen.
	Perhaps that's why it was bypassed for Basic.

	Also as I recall, the Basic compiler did not fix the problem. It also
	does its own screen handling. (Again this applies to the version I
	used.)

          Derek S. Keeping.
          {allegra,inph4,utcsrgv}!garfield!derek2