Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!thunder.mcrcim.mcgill.edu!snorkelwacker.mit.edu!usc!elroy.jpl.nasa.gov!jpl-devvax!huey!brad
From: brad@huey.Jpl.Nasa.GOV (Brad Hines)
Newsgroups: comp.os.msdos.apps
Subject: Re: How much space does 4DOS take?
Message-ID: <11518@jpl-devvax.JPL.NASA.GOV>
Date: 20 Feb 91 20:15:49 GMT
References: <1991Feb13.030916.10963@novell.com> <5605@bwdls58.UUCP> <91047.222138IO92203@MAINE.BITNET> <18764@ccicpg.UUCP>
Sender: news@jpl-devvax.JPL.NASA.GOV
Reply-To: brad@huey.Jpl.Nasa.GOV
Organization: JPL Spatial Interferometry Group
Lines: 20

In article <18764@ccicpg.UUCP>, mhr@ccicpg.UUCP (MHR {who?}) writes:
In <91047.222138IO92203@MAINE.BITNET>, IO92203@MAINE.BITNET writes:
>My only problem with 4DOS has been that it doesn't quite agree with
>Windows 3.0/386 - for some reason I have more problems running the
>latter than under DOS 3.3.  Still, I have found a way around that, since
>I do not use Windows for everything yet.


I initially had this problem, too.  The problem turned out to be that the
Windows DOS box runs command.com, which causes problems.  If you create a file
4DOS.PIF that runs 4DOS (and if you have your 4DSHELL environment variable set
properly), and use that in place of the original Windows DOS box, everything
works great.

-- A happy registered user

-- 
Brad Hines
Internet: brad@huey.jpl.nasa.gov
Jet Propulsion Lab, Pasadena, California