Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!swrinde!ucsd!sdcc6!crl!hartung
From: hartung@crl.ucsd.edu (Jeff Hartung)
Newsgroups: comp.binaries.ibm.pc.d
Subject: 4DOS 3.02 and MS Windows 3.0
Summary: Some incompatibility problems
Keywords: 4DOS Windows problems
Message-ID: <18059@sdcc6.ucsd.edu>
Date: 7 Apr 91 18:09:05 GMT
Sender: news@sdcc6.ucsd.edu
Followup-To: comp.binaries.ibm.pc.d
Organization: University of California, San Diego
Lines: 27

Just a brief note on something I noticed, but have not seen reported yet.
I've been trying out J.P. Software's 4DOS (version 3.02) and have been
generally VERY pleased with its vast improvements over COMMAND.COM.  However,
there are some problems I have noticed which have not been mentioned, as far
as I know, in this newsgroup so far.  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.

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.

Hope this isn't old news to everyone, but I've seen no mention of this.


-- 
 --Jeff Hartung--  	
 Disclaimer: My opinions only, etc., etc., BLAH! BLAH! BLAH!...
 InterNet - hartung@crl.ucsd.edu    or    ps299bx@igrad1.ucsd.edu
 UUCP - ucsd!crl.ucsd.edu!hartung	 BITNET - hartung@ucsd