bruce@ssc-vax.UUCP (Bruce Stock) (06/01/90)
I cant seem to get Windows 3.0 to run DOS applications in a window -- not even COMMAND.COM! Yes I am in 386 enhanced mode, yes I have a PIF with windowing selected. Otherwise, W3 works fine. Here is what happens: (1) First, double click on COMMAND.PIF or on the DOS icon in Main group of Prog Manager. (2) A nice window opens up, but it is all BLACK inside. (3) A dialog box comes up saying "Sorry you cant run this application in a window OR in background mode ......"!! (4) I click on the offered OK button and dialog goes away. (5) Yet, Command.com really is running in the window, at least if I type "exit" the window closes (But the window stays BLACK all the time). Any suggestions are appreciated. See the trailer for configuration details. Regards, Bruce Stock uw-beaver!ssc-vax!bruce or bruces@atc.boeing.com -------------------------------------------------------------------------- Hardware: 386 20Mhz clone, 4MB RAM, 387 math chip, 40 MB HD, no-name VGA with Cirrus Bios, AMI bios with shadowing enabled, MS bus mouse. Software: DOS 3.3, Highmem.sys, smartdrv.sys, ramdrive.sys, dmdrvr.sys. No TSR's. No changes to Win.ini or System.ini as provided by setup.
eav@hpindda.HP.COM (Eugene Veteska) (06/06/90)
>I cant seem to get Windows 3.0 to run DOS applications in a window -- not >even COMMAND.COM! Yes I am in 386 enhanced mode, yes I have a PIF with >windowing selected. Otherwise, W3 works fine. > >Here is what happens: (1) First, double click on COMMAND.PIF >or on the DOS icon in Main group of Prog Manager. (2) A nice window opens >up, but it is all BLACK inside. (3) A dialog box comes up saying "Sorry you >cant run this application in a window OR in background mode ......"!! >(4) I click on the offered OK button and dialog goes away. (5) Yet, >Command.com really is running in the window, at least if I type "exit" >the window closes (But the window stays BLACK all the time). > >Any suggestions are appreciated. See the trailer for configuration details. I've found two ways to get around this: 1) After you click on the dialog box, select the Settings... menu from the system menu. This brings up a dialog box. From there you can select full screen. This brings up the window in full screen. Then hit Alt-Esc or Ctrl-Esc to get back to windows. Click on the DOS icon for your program and change the settings back to windowed. When you double click on the icon, it comes up in a window. 2) For some reason, if you start up windows with any windows application on the command line, command.com or DOS programs will start in a window (if that's what the PIF file says). The application started doesn't have to be the run you want to run. So if I know I will be running DOS programs, I start up windows with clipbrd, ie. win clipbrd. Has anyone else seen this? Does anyone know why starting apps on the command line would cause this behavior? Is this a bug? It seems like if you can get command.com to start in a window, you should always be able to. > >Regards, Bruce Stock uw-beaver!ssc-vax!bruce > or bruces@atc.boeing.com Eugene Veteska Hewlett Packard Information Networks Division eav@hpindda.hp.com