Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!peregrine!ccicpg!mhr
From: mhr@ccicpg.UUCP (MHR {who?})
Newsgroups: comp.os.msdos.apps
Subject: Re: How much space does 4DOS take?
Message-ID: <19502@ccicpg.UUCP>
Date: 22 Feb 91 18:27:05 GMT
References: <91047.222138IO92203@MAINE.BITNET> <18764@ccicpg.UUCP> <11518@jpl-devvax.JPL.NASA.GOV>
Organization: ICL North America
Lines: 29

In <11518@jpl-devvax.JPL.NASA.GOV>, brad@huey.Jpl.Nasa.GOV writes:
} In article <18764@ccicpg.UUCP>, mhr@ccicpg.UUCP (MHR {who?}) 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.
} 
At a guess, I'd say that I must have expressed the problem inadequately.
I never had any trouble per se running either 4DOS or DOS 3.3 from
inside Windows.  The problem I kept seeing was that when I started up
Windows under 4DOS, I would get flaky performance results when running
_any_ Windows application, including our network comm program, and
invariably I wound up getting bounced out of Windows all the way back to
4DOS.  When I stopped using 4DOS and brought back COMMAND.COM, that
seemed to smooth out the situation.

Thanks anyway.

-- 
Mark A. Hull-Richter    UUCP:  ccicpg!mhr       In all things, restraint,
ICL North America                               especially with respect
9801 Muirlands Blvd                             to posting articles and
Irvine, CA  92713       (714)458-7282x4539      doubly so for flames.