Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!usc!cs.utexas.edu!romp!auschs!d75!woan
From: woan@nowhere (Ronald S Woan)
Newsgroups: comp.binaries.ibm.pc.d
Subject: 4DOS 3.02 and MS Windows 3.0
Message-ID: <3746@d75.UUCP>
Date: 8 Apr 91 20:57:17 GMT
References: <18059@sdcc6.ucsd.edu>
Sender: news@d75.UUCP
Reply-To: woan@cactus.org
Organization: Austin School of Hardknocks
Lines: 30

In article <18059@sdcc6.ucsd.edu> hartung@crl.ucsd.edu (Jeff Hartung) writes:
>One problem which I had been aware of is that 4DOS does not like the
>version of HIMEM.SYS required to run Windows 3.0, and will cause your
>system to crash HARD if you allow it to try to swap to extended
>memory, which it will do by default unless you tell it not to.
>Adding a swap-to-disk option (/S:D) will clear this up, and with
>Windows' SmartCache installed, the loss of speed is negligable.

Hmm.. I have been using 4DOS 3.02a with the best swapping option and
have never encountered this problem.

>The other problem was more subtle.  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.

How often do you use setup from within Windows? Anyway, I have never
had a Windows/4DOS problem and I have been using them together since
the second week after Windows 3.0 release.

Sounds like something else might be going on...
--
+-----All Views Expressed Are My Own And Are Not Necessarily Shared By------+
+------------------------------My Employer----------------------------------+
+ Ronald S. Woan                woan@cactus.org or woan@austin.vnet.ibm.com +
+ other email addresses             Prodigy: XTCR74A Compuserve: 73530,2537 +