Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!uunet!cpqhou!scotts From: scotts@cpqhou.UUCP (Scott Shaffer) Newsgroups: comp.sys.ibm.pc Subject: Re: window386 in dos4.0 ??? Keywords: incompatable dos4 and win386 Message-ID: <542@cpqhou.UUCP> Date: 22 Feb 90 06:00:00 GMT References: <754@eedsp.eedsp.gatech.edu> <1779@uklirb.informatik.uni-kl.de> <6889@tekgvs.LABS.TEK.COM> Lines: 33 In article <6889@tekgvs.LABS.TEK.COM>, toma@tekgvs.LABS.TEK.COM (Tom Almy) writes: > In article <1779@uklirb.informatik.uni-kl.de> gerten@uklirb.UUCP (Rainer Gerten) writes: > >In <754@eedsp.eedsp.gatech.edu> wchung@eedsp.gatech.edu (W. Chung) writes: > >> Is it true that you can not run window386 version 2.? in > >>with dos4.0. > >Windows 386, Version 2.03 and 2.10 don't work with DOS 4.01, but > >Version 2.11 does. > > Well I have Windows 386 version 2.11 and DOS 4.01, and whenever I try to run > a DOS application Windows insists on reading drive A: so that I must always > have a floppy inserted. This is a bad problem which didn't occur with DOS 3.3 > (I upgraded -- a mistake?) nor does it occur with my copy of Windows 286 > version 2.11. > > Anybody know what's happening? > Well, it seems the problem lies in Windows deciding where COMMAND.COM is on init. One possible fix is to edit the COMMANDE.PIF, COMMANDF.PIF and COMMANDW.PIF and change the entry for "Initial Directory:" from blank to "C:\" or whatever is appropriate. Also, if you continue to have the problem with a DOS app, edit (or create) a PIF file for it and be sure to completely specify its path in the "Initial Directory:" box. I know this fixes the problem (I think its does), but I couldn't tell you exactly what is going on. +==========================================================================+ | Scott Shaffer | Compaq Computer Corporation @ Houston TX | | Systems Engr | (These opinions do not necessarily reflect those of my| | | employer, friends or any living person.) | +==========================================================================+