Xref: utzoo comp.windows.x:20861 comp.sys.att:9285
Path: utzoo!attcan!uunet!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!rpi!rpi.edu!vancleef
From: vancleef@pawl23.pawl.rpi.edu (David A. Van Cleef)
Newsgroups: comp.windows.x,comp.sys.att
Subject: Re: SimulTask-386/OpenLook incompatibility
Message-ID: <DTP#TV+@rpi.edu>
Date: 10 Apr 90 19:33:59 GMT
References: <14891@s.ms.uky.edu>
Organization: /home/n/vancleef/.organization
Lines: 17
In-Reply-To: morgan@ms.uky.edu's message of 10 Apr 90 14:26:23 GMT

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)