Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!zaphod.mps.ohio-state.edu!wuarchive!udel!rochester!pt.cs.cmu.edu!sei!bwb
From: bwb@sei.cmu.edu (Bruce Benson)
Newsgroups: comp.windows.ms
Subject: Re: Using MS-DOS Shell in Win3
Keywords: Windows, DOS Shell
Message-ID: <8336@fy.sei.cmu.edu>
Date: 24 Aug 90 14:33:48 GMT
References: <1990Aug21.140925.14210@cbnewsh.att.com>
Reply-To: bwb@sei.cmu.edu (Bruce Benson)
Organization: Software Engineering Institute, Pittsburgh, PA
Lines: 26

In article <1990Aug21.140925.14210@cbnewsh.att.com> ahn@cbnewsh.att.com (john.k.ahn) writes:
>Greetings,
>
>After banging my head against the wall, I decided to ask for help.
>
>With these, I cannot run the DOS Shell or some other old DOS Apps
>(such as Norton Utilities 4.5) in a window.  Actually, these do run,
>but I can't see a thing.  It seems everything is written black on black.
>The programs seem to respond to keyboard input; DOS shell terminates
>when I type "exit" and NI terminates when I press the escape key.

I often have this same problem when using 4dos as my command shell.  The
DOS shell comes up and takes input, but nothing is seen on the screen.  This
only happens some of the times, but I've found a curious work around.  When
the problem occurs, I leave windows, invoke 4dos (which is now a 
secondary shell to the 4dos I booted up with) and immediately exit. Restarting
windows, the dos shell works fine.  Restarting windows without entering
and exiting 4dos finds the problem still existing. (I assume something
gets reset when invoking the secondary shell.)

For what it's worth ....

* Bruce Benson                   + Internet  - bwb@sei.cmu.edu +       +
* Software Engineering Institute + Compuserv - 76226,3407      +    >--|>
* Carnegie Mellon University     + Voice     - 412 268 8469    +       +
* Pittsburgh PA 15213-3890       +                             +  US Air Force