OT: broken/useless ansi - console driver??

[Jean-Pierre A. Radley]

John Esak propounded (on Mon, Oct 24, 2005 at 02:14:08PM -0400):
| > In that group, termcap_5.0.04D4 is from Nov 1, 2000.
| >
| > --
| > JP
| 
| In regards to filePro, this was an error on my part. Apologies. There is an
| entry in the distributed termcap file... something I have not replaced since
| the first beta testing of 5.0, probably in early 2000 or even late 1999.
| Afte having lots of troulbe with the install clobbering not only my
| personalized termcap file, but my edits, printers and other things as well.
| I took to not replacing my configuration files with the new ones, but doing
| the type of install that touched nothing, or did the installs since then by
| hand. So, in regards filePro, I spoke without looking at the latest termcap
| from them, which as you say could be 5 years old now.
| 
| I might be testing all this illegally. If this is the case, my apologies
| again. I have been running this SCO 6.0 as a guest operating system using
| Virtual PC. If I have to stay with at386-ie, so be it. It all seems to work,
| but not all of it. Under FacetWin using ansi... EVERYTHING works. In
| contrast to this, using the real console (in NJ not near me), the ansi
| termcap still does not work anything close to how it should... nothing to do
| with filePro at all... using scoadmin it shows wrong graphics, etc. My point
| is simply that they should not have taken away the ability to run things as
| they were, only to move on to at386-ie. Yes, I know some things in the old
| ansi's and "soansi's" did not work... but they never bothered me. Adapting
| to the new thing should have been made painless. Like I say, it is just an
| opninion.

If you log in via telnet or ssh, FacetWin, or Anzio, or using a scoterm
in X Window, scoansi should be your default TERM, and ansi will work too.

-- 
JP