[net.micro.pc] ANSI console driver braindamage

mo@seismo.UUCP (Mike O'Dell) (05/31/84)

We have an IBM PC-XT which we are trying to use with some screen control
software running on the PC.  Believing it would make life simpler,
we load the ANSI console driver; however, our experience is that
this driver's interpretation of and ANSI X3.64 escapce sequences is
unconventional, if not plain wrong.  Does anyone out there have
any experience with this beast they can share with us?  Alternatively,
does anyone know what control characters the normal driver honors??

	Thanks,
	-Mike O'Dell

	seismo!mo
	mo@lbl-csam

matt@oddjob.UChicago.UUCP (Matt Crawford) (06/01/84)

I have tried using the ANSI driver and am completely unhappy with it.
As far as I can tell, it correctly interprets those few escape sequences
that are listed in the appendix, BUT:

	In ANSI, it no longer understands CR, LF, ...

	There is a separate `cursor' location for characters written to the
	ANSI screen port, so cursor motion under ANSI followed by plain 
	"PRINT"s (in basic) don't do what you want.

___________________________________________________
Matt			ARPA: crawford@anl-mcs.arpa
Crawford		UUCP: ihnp4!oddjob!matt

geller@rlgvax.UUCP (David Geller) (06/03/84)

The manual DOS 2.0 manual clearly states that output to the screen under
the control of the ANSI driver should be done with direct console
output functions. These are DOS functions 2,6, and 7. You may also use
something like LATTICE's cprintf routines. These go directly to the
console. It is possible that the print routine you were referring to did
not send stuff directly to the console port. As to the problem with CR and
LF - you may be right. As it is the doc seems as brain damaged as the
driver.

					David P. Geller
					Computer Consoles, Inc.
	{seismo}!rlgvax!geller		Office Systems Group
					11490 Commerce Park Drive
					Reston, VA  22091

					703-648-3483