ahn@cbnewsh.att.com (john.k.ahn) (08/21/90)
Greetings, After banging my head against the wall, I decided to ask for help. Here are two of my configurations: Setup 1: AT&T 6386/25 with 150Mb Micropolis ESDI Drive 8 Mb of memory all configured as extended (except 640K) AT&T 329D monitor and VDC 600 Video Card (Basically, a VGA) AT&T 320 Mouse MS-DOS 4.01 2 Mb smartdrv and 2Mb ramdrive Windows 3.0 running in enhanced mode Setup 2: Same as above but AT&T 6386/SX with 100Mb Conner IDE Drive 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. Even more strange, I can run them OK on some 6386/25 (identically configured), but I have these problems with some others. I was never able to run them on 6386/SX. All programs run OK on all machines if I run them full-screen. Can anybody help???!!! Thanks in advance. J. Ahn jahn@homxc.ATT.COM As usual, AT&T has nothing to do with any of above statements.
bwb@sei.cmu.edu (Bruce Benson) (08/24/90)
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