29 Sep
2010
29 Sep
'10
8:02 p.m.
Anyone else here remember fansi-console's ansi emulator.
Works great instead of ansi.sys and is a pretty good screen driver for dos.
On Wed, Sep 29, 2010 at 5:24 AM, Johnny Billquist <bqt(a)softjar.se> wrote:
Mark Tuson wrote:
Anyone else here remember fansi-console's ansi emulator.
Works great instead of ansi.sys and is a pretty good screen driver for dos.
http://www.highbeam.com/doc/1G1-11953307.html
Bill
--
d|i|g|i|t|a|l had it THEN. Don't you wish you could still buy it now!
pechter-at-gmail.com
Hi everyone, this is my first message, after
being on the mailing list for
the best part of three years :)
Though I might consider 2.11BSD, if that'll work on a machine with 24M of
core, and if the escapes will display properly, because
[24;1H[?1h=[;H[2J
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~[H
is a little bit difficult to work with when I'm wanting to edit source
code.
2.11BSD won't make a difference. You'll see the same result. This is a
problem because you are running under DOS. It is the DOS screen handler that
needs to understand whatever codes are output by the programs running inside
simh. In this case, the program inside simh thinks it is connected to a
VT100 (or xterm, or something similar), and sends escape codes based on
that. I don't know why it thinks so, but I suspect you told the system by
setting the TERM variable. Please set it to something that matches reality,
or else fix reality. :-)
Johnny