OT: broken/useless ansi - console driver??

[Fairlight]

>From inside the gravity well of a singularity, John Esak shouted:
> working "ansi" termcap with the product. What the hell does ANSI stand for
> anyway, not much obviously, since the first thing they did years ago was

For those that actually don't know (I -know- John is being both rhetorical
and making an excellent point):  American National Standards Institute

And can you imagine what would happen if, say, safety equipment
manufacturers started selling "MyCompanyANSI Compliant" hard hats, work
boots, etc., etc.?  The lawsuits would know no end.

> around an emulation written for an "at386". C'mon, has any of you used a 386
> in the past 15 years!!  Sort of backward looking and dumb in my opinion...
> and I'm leaving the "humble" out on purpose. :-)

Actually, since that puts it at a 1990 threshhold, the vast majority would
probably say, "Yes."  We had a 386sx-16 in service here until about 1995,
running first Windows 3.1, and later linux.

Back to SCO...  Didn't ODT 2.0 (and SCO 3.2.4.x) ship with a default of
at386 as the default console terminal type?  I seem to recall having to
deal with that.  I thought "scoansi" came about wit 5.0.x.  If my memory is
even halfway accurate, sounds like they've come full circle.

BTW--that text-file-busy and core dump swap situation sounds -really-
nasty.  I don't envy you.  Jay's explanation was actually quite good.

mark->
-- 
There is no "I" in TEAM.
This would be the primary reason I've chosen not to join one.