nsus_cif@uhura.cc.rochester.edu (Nicholas Leon Susch) (10/03/90)
A quick and simple question: Do you have to have a certain amount of
memory to run a dos application in a window? I have a 386-25 and 2 Megs
of memory and when I try to run a dos application it will only work in
full screen mode (yes I am running in 386 "Enhanced" mode). Thanks for
any answers. (and sorry if this has already been asked).
--
"And when I have understanding | /\/ick Susch - University of Rochester
of computers, I will be the | nsus_cif@uhura.cc.rochester.edu
supreme being!" | nsus_cif@uordbv.bitnet
- Evil (from "Time Bandits") | ... !rochester!ur-cc!nsus_ciftony@softway.sw.oz.au (Tony McGrath) (10/04/90)
In <9718@ur-cc.UUCP> nsus_cif@uhura.cc.rochester.edu (Nicholas Leon Susch) writes: >A quick and simple question: Do you have to have a certain amount of >memory to run a dos application in a window? I have a 386-25 and 2 Megs >of memory and when I try to run a dos application it will only work in >full screen mode (yes I am running in 386 "Enhanced" mode). Thanks for >any answers. (and sorry if this has already been asked). Windows 3 uses a default PIF for the DOS command line. Unless you create a specific windowed version for COMMAND.COM you will always get a full screen COMMAND.COM. You can do this simply using the PIF Editor to create a COMMAND.PIF and then changing the command to be invoked by the Program Manager when you click the DOS icon to be that new COMMAND.PIF. Similarly, if you are creating a PIF for a standalone DOS application you must use the Extended 386 options to set up a windowed mode. However, this can only work if you are really using Windows in Enhanced mode. In Real or Standard mode you will always get a full screen. By default all DOS application PIFs use full screen mode. Be aware that if you start up a DOS appication directly, rather than its PIF, then the PIF will be ignored and the application will start in full screen mode regardless. You must execute the PIF to get windowed mode. Also note that if your DOS application needs to use the mouse then you must load a mouse driver in your CONFIG.SYS or AUTOEXEC.BAT before you start Windows. The mouse, however, will only work with the DOS application when that application is running in full screen mode. Tony McGrath Senior Consultant Softway Pty. Ltd.
jolly@voyager.ece.cmu.edu (John Lee) (11/27/90)
This is a question that has been asked before - I would be grateful if somebody could forward the answer. I would like to run a DOS session (just text, if that matters) in a window, akin to "xterm" under X. If I create a simple ".pif" file, the window will pop up, but a dialog box will come up saying something like "Cannot run application in window. App will restart when run in full screen mode". The application runs fine in full screen mode. And, if I pause the session, I can open it again as a window. Can somebody send me a simple list of items to check off in the ".pif" editor, and other hints (ie; touch up to *.ini). I have a 386sx clone (Austin), 4 meg ram, and am running in 386 enhanced mode. John.
jbf@ariel.ucs.unimelb.edu.au (John Brendan Fitzpatrick) (01/11/91)
I do not think this is a frequently asked question: I get an "unreoverable application error" message whenever I try run a non-win application in a window in 386 enh mode. It always happens if I try to start the appl in a window. If I start the appl in full screen mode and switch to a window the same thing will happen after I try something not too fancy (eg. view a table in Paradox 3.5). All the non-win appl that I have work perfectly in full screen mode though. The same occurs when I try to run a plain DOS shell as well. I have tried altering my pifs, but have had no luck as yet. Or might the problem be hardware related? I have an Osborne 386SX (16Mhz), 4 meg ram, standard VGA, running Banyan Vines 3.1 over Ethernet. Any help would be appreciated. --JBF@ariel.its.unimelb.edu.au
whkr@ciba-geigy.ch (Hans Kraft) (01/14/91)
On my PC I use an elder Logitech mouse and I had some troubles with getting windows started. As a new mouse driver was not available (weekend) I loaded the newest Microsoft mouse driver - and I got exactly the same messages as you did. Especially the DOS shell window (pure command.com) did not work. The problem disappeared with the new Logitech driver. Clearly, you need not to load any mouse driver for windows - but other applications like it. Hope this helps. Hans Kraft (Giovanni Forza)