Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 11 Sep 1995 10:12:48 -0700 (MST)
From:      Terry Lambert <>
To: (David Anderson)
Subject:   Re: cons25 and vt100
Message-ID:  <>
In-Reply-To: <> from "David Anderson" at Sep 11, 95 02:31:56 am

Next in thread | Previous in thread | Raw E-Mail | Index | Archive | Help
> I tried that.. There were some problems..
> Local console:
> 1- All stuff that was supposed to be bold, was blue.

8-).  Direct mapping of the mono attribute bits to the CGA attribute

What's "bold" on a color screen?

> 2- The screen would constanly become garbled. I would be typing something 
>    at the commandline and suddenly the cursor would just jump to the 
>    other side of the screen. 

What video card do you have; sounds like a non-linear VGA memory map?

> 3- When the system boots up, everything is white on a red background. Not 
>    necessarily a problem, but it looks strange. 

Another attribute mapping.

I'd say PCVT was under the impression that your card was a mono card; does
it emulate one?  This could cause it to mis-probe the card.  You may want
to look at the dmesg output for boot and see what probe messages it puts
out to you.  Then contact the author for advice.

> Remote systems:
> 1- When I do either a setenv TERM vt220(or even vt100), and run pine, the 
> screen turns to black text on a white background. 

I've seen this even on the default console.

It looks like a clear screen is clearing with the attribute set.  This is
the way SCO consoles work, and is probably a requirement for compatability.

> The thing is, I don't really want vt100/220 all the time. I just want it 
> for those times when I'm working on the remote systems. 

Screen is your best bet, then.  Or X.

					Terry Lambert
Any opinions in this posting are my own and not those of my present
or previous employers.

Want to link to this message? Use this URL: <>