OT: broken/useless ansi - console driver??

[John Esak]

>  I disagree.
> >| His explanation that it is merely the Unixware  something or
> another doesn't
> >| quite address the situation... which as I see it is this.
> >|
> ...
> >No, on the console, you just use the at386-ie termcap.
> >You need to make two modifications: stty flush= '', and change
> >GZ to octal 275.
> >If you add PV, it gives you color.
> >
> >I never played with turning the cursor off and on, but if CF and CN are
> >missing, just copy in the civis and cvvis values from the terminfo file.
>
> This sounds like something the average OpenServer user or even consultant
> would figure out immediately.
>
> One of the major strong points of SCO Xenix->OpenServer has always been
> backwards compatibility with few surprises.
>
> Bill

My point exactly. Few surprises... For years, ansi and later (regrettfully)
scoansi was supplied as the base termcap for use with OpenServer. Aside from
the small (documented!!) changes that happened from 5.05 to 5.06, there was
relatively nothing one had to do to run an ansi emulation into SCO. In fact,
I never bought into the actual "scoansi" termcap and just kept using ansi
without problem, for yes, 17 years.  My complaint with OS-6 is that it does
NOT work at all using ansi as the selected termcap. You must fiddle with the
at386-ei termcap to get anywhere... and yes, I'm capable of making any
changes required to termcap or termio. I did after all purchase the little
brown termcap booklet from O'Reilly in 1984 sometime and devoured it pretty
comcompletely. I've built dozens of termcaps, including many of the ones
sent out with filePro. As far as I can remember, JP made some changes to one
of *my* existing filePro termcaps, and for a long time it got released as
the "as modified by JP Radley" ansi termcap.  Termcap design is no big deal.
It is the fact that I should have to go do this kind of stupid fiddling with
their newly released stuff. If that is what they wanted, they, SCO, should
have done the modifications... *and* they should have released a fully
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
turn it into "scoansi". Now, we are told... oh but his is Unixware's way of
doing things. What crap. I'd rather point toward ANSI thn something based
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. :-)

John