Path: utzoo!mnetor!uunet!lll-winken!lll-lcc!ames!umd5!purdue!i.cc.purdue.edu!j.cc.purdue.edu!pur-ee!iuvax!bobmon
From: bobmon@iuvax.UUCP (Bobmon)
Newsgroups: comp.sys.ibm.pc
Subject: Fansi-Console (was Re: Screen Blanker WARNING!!)
Message-ID: <5857@iuvax.UUCP>
Date: 3 Feb 88 04:46:24 GMT
References: <355@scubed.UUCP> <2750@omepd> <161@mccc.UUCP> <1530@bgsuvax.UUCP> <11011@shemp.UCLA.EDU>
Reply-To: bobmon@iuvax.UUCP (Bobmon)
Distribution: na
Organization: Schizophrenics 'R' Us
Lines: 19

In article <11011@shemp.UCLA.EDU> jsin@CS.UCLA.EDU (John Sin) writes:
 - 
 - Hmmmm.  When I ftp a large file, the screen
 - will go blank, and then when ftp is done and writes on the screen to 
 - let you know, the screen will come back. I can sit across the room and 
 - ocassionally look at the screen to find out when ftp is done.
 - I use version 2.0 of fansi.

Mine may blank during transfers, but pops back (soon) when a "blocks
transmitted" display or something is updated.

 - But, I still have the problem of using the mouse-based programs,
 - whether or not I load the fconsole before loading the mouse driver.
 - Perhaps it can only detect non-graphical screen writes. Anyone know
 - how that works?

The on-disk doc. divides screen/keyboard use into hardware, ROM BIOS, and
MSDOS call approaches.  Fansi claims to replace the BIOS code, so it speeds
up console I/O which uses BIOS or MSDOS calls.  I don't think graphics is
affected.