morgan@ms.uky.edu (Wes Morgan) (04/10/90)
I recently acquired an AT&T 6386 with OpenLook. After installing
Simul-Task 386, I can execute DOS applications with no problem....
until I go into OpenLook. While in OpenLook, the DOS application's
window <or command-level DOS window> echoes neither my input nor
any output. The sequence of events is as follows:
<from an xterm> $ dos
<new window> DOS is in full screen mode
on virtual terminal 02
<window goes to full screen> prints BIOS message, VP/ix message,
MS-DOS boot message, and Simul-Task
welcome message
<window returns to previous size> no update, just a blank screen
with the cursor at the proper
place (at the prompt which followed
all the above dos output on full
screen)
Could some OpenLook/Simul-Task guru explain this and/or offer a fix?
Wes
--
| Wes Morgan, not speaking for | {any major site}!ukma!ukecc!morgan |
| the University of Kentucky's | morgan@engr.uky.edu |
| Engineering Computing Center | morgan%engr.uky.edu@UKCC.BITNET |
Lint is the compiler's only means of dampening the programmer's ego.vancleef@pawl23.pawl.rpi.edu (David A. Van Cleef) (04/11/90)
In article <14891@s.ms.uky.edu> morgan@ms.uky.edu (Wes Morgan) writes:
I recently acquired an AT&T 6386 with OpenLook. After installing
Simul-Task 386, I can execute DOS applications with no problem....
until I go into OpenLook. While in OpenLook, the DOS application's
window <or command-level DOS window> echoes neither my input nor
any output. The sequence of events is as follows:
[sequence deleted]
Could some OpenLook/Simul-Task guru explain this and/or offer a fix?
What you need is Simul-Task 2.0U. It's available from the AT&T NSSC
(1-800-922-0354) as fix #0079 on 5.25" media, #0080 on 3.5".
--Dave Van Cleef
--(Working for the NSSC, but hardly ever reflecting their opinions)