[net.micro.pc] CTTY Problems

helly%AEROSPACE@sri-unix.UUCP (09/29/83)

From:  helly at AEROSPACE (John Helly)

I have fiddled with the CTTY command of DOS 2.0 with some strange
results.  While I have been able to use other ASCII terminals as the
console to DOS, whenever I invoke an application program (VDTE,
Wordstar, LOTUS, etc.)  display reverts to the system console and the
system accepts commands from neither keyboard.

The command sequence I use to set up the initial reconfiguration is:

	mode com1:1200,e,7,1
        ctty com1

This works fine as long as you converse only with DOS.  I suspect that
applications are somehow resetting the mode to use the system display.

Does anyone know how to overcome this or better understand what's
happening?

--john helly

BRACKENRIDGE%USC-ISIB@sri-unix.UUCP (10/06/83)

From:  Billy <BRACKENRIDGE@USC-ISIB>

Programs can use DOS calls or IBMPC BIOS calls or directly write
to the screen using the MOV instruction. DOS calls are the slowest.

In order to make a competitive product most software developers use
the BIOS calls or write directly to the screen. VDTE as a case in point
could not keep up with 9600 baud terminal lines if it were using the DOS
calls.

Only the DOS calls can be diverted to the ANSI standard terminal supported
by DOS 2.0. This is part of the reason for the slowness of the calls.


-------