Hi Steffen,
But back to the question: HOW DOES FREECOM KNOW THAT THE CURRENT STANDARD
OUTPUT IS THE DEVICE DRIVEN BY THE BIOS? Is it save / useful to use BIOS
functions. Or how can FreeCOM ensure the human sitting on the other side
of the line is seeing the results.
The only reliable way is
On Thu, 5 Aug 2004, Bart Oldeman wrote:
Hello Bart,
But back to the question: HOW DOES FREECOM KNOW THAT THE CURRENT STANDARD
OUTPUT IS THE DEVICE DRIVEN BY THE BIOS? Is it save / useful to use BIOS
functions. Or how can FreeCOM ensure the human sitting on the other side
of the line is seeing the
Well, this is embarrassing.
I downgraded to 0.91o and it is no faster. I could have sworn it got
slower when I upgraded to 0.91r... But maybe I am just crazy and it
was never as fast as I remember.
I apologize for the false alarm.
- Pat
On Thu, 5 Aug 2004, Steffen Kaiser wrote:
a) you cannot detect an ANSI driver across the line **), and
b) you do not know for sure what CTTY is in place, except the
shell itself has invoked it ***).
True. And now my opinion is that you can only assume that a VT100-style
terminal is in place