Xref: utzoo comp.binaries.ibm.pc.d:13829 comp.windows.ms:11584
Path: utzoo!utgpu!cunews!bnrgate!bwdls58!mlord
From: mlord@bwdls58.bnr.ca (Mark Lord)
Newsgroups: comp.binaries.ibm.pc.d,comp.windows.ms
Subject: Re: 4DOS 3.02 and MS Windows 3.0
Keywords: 4DOS Windows problems
Message-ID: <6444@bwdls58.bnr.ca>
Date: 12 Apr 91 14:56:11 GMT
References: <18059@sdcc6.ucsd.edu>
Sender: mlord@bwdls58.bnr.ca
Reply-To: mlord@bwdls58.bnr.ca (Mark Lord)
Followup-To: comp.windows.ms
Organization: Bell-Northern Research, Ottawa, Canada
Lines: 27

In article <18059@sdcc6.ucsd.edu> hartung@crl.ucsd.edu (Jeff Hartung) writes:
<
<... When windows starts up with 4DOS installed
<as the shell, the setup program will not run properly.  Any attempt to search
<the disk for applications to install will result in an unexpected application
<error, and possible a crash.  The solution seems to be that COMMAND.COM should
<be loaded as the primary shell if you intend to run Windows, and 4DOS can be
<run as a subshell if you exit Windows, or from Windows by adding the 4DOS PIF
<file to your Main group.

The windows "setup" problem may be due to something else.  I had this problem
at one time and managed to get rid of it.  And I still use 4DOS for *all* 
shells.

Give this a try if you are still having problems:

alias WIN c:\windows\win

Followups to comp.windows.ms

-- 
MLORD@BNR.CA  Ottawa, Ontario *** Personal views only ***
begin 644 NOTSHARE.COM ; Free MS-DOS utility - use instead of SHARE.EXE
MZQ.0@/P/=`J`_!9T!2[_+H``L/_/+HX&+`"T2<TAO@,!OX0`N1(`C,B.P/.DS
<^K@A-<TAB1Z``(P&@@"ZA`"X(27-(?NZE@#-)P#-5
``
end