tporczyk@na.excelan.com (Tony Porczyk) (02/13/91)
The News Manager) Nntp-Posting-Host: na Reply-To: tporczyk@na.excelan.com (Tony Porczyk) Organization: Novell, Inc. San Jose, California References: <1991Feb12.172914.20377@oracle.com> Distribution: World Date: Wed, 13 Feb 1991 03:09:16 GMT In article <1991Feb12.172914.20377@oracle.com> schanin@oracle.com (Steven Chanin) writes: > 4DOS sounds like a pretty cool shell, but before I go out and buy >it, I was wondering if anyone knew how much conventional memory it >takes up? The reason I ask is that I'm doing Win3 development and If you specify in the 4dos.opt file (very clearly explained in the docs), 4DOS command interpreter will *swap* itself out of memory either to extended memory or to disk (as you prefer) when the applications need more room. Can't beat that. I believe it leaves about 10K or so in memory (don't remember exactly). 4DOS is really great. Could not go back to COMMAND.COM now. Tony
Jono_Moore@mindlink.UUCP (Jono Moore) (02/13/91)
In article <1991Feb12.172914.20377@oracle.com> schanin@oracle.com (Steven Chanin) writes: > 4DOS sounds like a pretty cool shell, but before I go out and buy >it, I was wondering if anyone knew how much conventional memory it >takes up? The reason I ask is that I'm doing Win3 development and Depending on how it swaps out, it takes up from around 1-4k of memory. Why not download it and try it out and see if it works? Shareware is a wonderful thing :-) -- +------------------------------------------------+--------------------------+ | cthulhu@{arkham.UUCP|arkham.wimsey.bc.ca} | He who has had has been | | {uunet|ubc-cs}!van-bc!cynic!arkham!cthulhu | but he who has not been | | jono_moore@{mindlink.UUCP|cc.sfu.ca|sfu.bitnet}| has been had. | +------------------------------------------------+--------------------------+
6600prao@ucsbuxa.ucsb.edu (Parik Rao) (02/14/91)
I seem to have 4dos take up a mere 1k or so (environment space). MSDOS takes up 35k and IO takes up 10k, and drivers and such take up another 5k. I of course have QEMM on my machine, but it doesn't directly involve 4dos. (4dos does swap to XMS in my case.) ie - I have 600k free w/ 4dos, qemm, and about 100k of drivers. -- Parik Rao, University of California Santa Barbara 6600prao@ucsbuxa.ucsb.edu
mlord@bwdls58.bnr.ca (Mark Lord) (02/14/91)
<In article <1991Feb12.172914.20377@oracle.com> schanin@oracle.com (Steven Chanin) writes: <> 4DOS sounds like a pretty cool shell, but before I go out and buy <>it, I was wondering if anyone knew how much conventional memory it <>takes up? The reason I ask is that I'm doing Win3 development and Quoting from 4DOS.DOC: 4DOS requires less than 4K of your precious RAM for its resident portion (less than 1K with XMS swapping!), and can use EMS, XMS, or disk for swapping its transient portion. -- ___Mark S. Lord__________________________________________ | ..uunet!bnrgate!mlord%bmerh724 | Climb Free Or Die (NH) | | MLORD@BNR.CA Ottawa, Ontario | Personal views only. | |________________________________|________________________|
toma@sail.LABS.TEK.COM (Tom Almy) (02/16/91)
In article <1991Feb13.030916.10963@novell.com> tporczyk@na.excelan.com (Tony Porczyk) writes: >If you specify in the 4dos.opt file (very clearly explained in the docs), >4DOS command interpreter will *swap* itself out of memory either to >extended memory or to disk (as you prefer) when the applications need more >room. Can't beat that. I believe it leaves about 10K or so in memory Better than that. If you have an XMS driver and free upper memory, then it will take *256 bytes*. Otherwise it takes about 3k. -- Tom Almy toma@sail.labs.tek.com Standard Disclaimers Apply
IO92203@MAINE.BITNET (Scott Maxell) (02/17/91)
Transient swapping in 4Dos only works if you have a hard disk... otherwise, 4Dos takes up quite a lot of memory... ============================================================================== +---------+ Scott Maxell --- IO92203 AT MAINE | | ---------------- IO92203 AT MAINE.MAINE.EDU | O | | | | "What I need is a computer that will do what I want it to do +---------+ not what I tell it to do..."
tporczyk@na.excelan.com (Tony Porczyk) (02/18/91)
The News Manager) Nntp-Posting-Host: na Reply-To: tporczyk@na.excelan.com (Tony Porczyk) Organization: Novell, Inc. San Jose, California References: <1991Feb13.030916.10963@novell.com> <5605@bwdls58.UUCP> <91047.222138IO92203@MAINE.BITNET> Date: Sun, 17 Feb 1991 20:59:14 GMT In article <91047.222138IO92203@MAINE.BITNET> IO92203@MAINE.BITNET (Scott Maxell) writes: > Transient swapping in 4Dos only works if you have a hard disk... >otherwise, 4Dos takes up quite a lot of memory... Bzzzz! Time's up. Wrong answer. Here is a quote from a 4DOS manual: Minimal Memory Usage 4DOS requires less than 4K of your precious RAM for its resident portion (less than 1K with XMS swapping!), and can use EMS, XMS, or disk for swapping its transient portion. Hope that helps to solve the mystery of transient swapping. Tony tporczyk@novell.com
Ralf.Brown@B.GP.CS.CMU.EDU (02/18/91)
In article <91047.222138IO92203@MAINE.BITNET>, IO92203@MAINE.BITNET (Scott Maxell) wrote: } Transient swapping in 4Dos only works if you have a hard disk... }otherwise, 4Dos takes up quite a lot of memory... You must have an ancient version. 4DOS will also swap to EMS or XMS. -- {backbone}!cs.cmu.edu!ralf ARPA: RALF@CS.CMU.EDU FIDO: Ralf Brown 1:129/3.1 BITnet: RALF%CS.CMU.EDU@CMUCCVMA AT&Tnet: (412)268-3053 (school) FAX: ask DISCLAIMER? Did | It isn't what we don't know that gives us trouble, it's I claim something?| what we know that ain't so. --Will Rogers
mhr@ccicpg.UUCP (MHR {who?}) (02/19/91)
In <91047.222138IO92203@MAINE.BITNET>, IO92203@MAINE.BITNET writes: > > Transient swapping in 4Dos only works if you have a hard disk... > otherwise, 4Dos takes up quite a lot of memory... > Not quite - you can also swap to EMS or XMS, if you have one (or both) of them, too. It is important to remember here that 4DOS is a COMMAND.COM _replacement_, and it only takes up about an extra 20k (I think), maximum, if the transient portion can't be swapped. I think it's worth it for the extra capabilities you get. 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. Regards. -- 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.
brad@huey.Jpl.Nasa.GOV (Brad Hines) (02/21/91)
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
mhr@ccicpg.UUCP (MHR {who?}) (02/23/91)
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.
mhr@mendip.UUCP (MHR {who?}) (03/09/91)
In <91047.222138IO92203@MAINE.BITNET>, IO92203@MAINE.BITNET writes: > > Transient swapping in 4Dos only works if you have a hard disk... > otherwise, 4Dos takes up quite a lot of memory... > Buzzzzzzzzzzzzzzzzzzzzzzzzz! Incomplete (and hence, wrong) answer. Transient swapping in 4DOS works if you have a hard disk, or EMS or XMS or a RAM disk. Read the 4DOS.DOC file (or your manual if you registered your copy), preferably before posting either questions or answers of this nature. And please, folks, if you're going to answer a question, either post the correct and complete answer or at least note that it is or may be neither. Thanks. No flames intended, just a (well, maybe not so) gentle erratum. > ============================================================================== > +---------+ Scott Maxell --- IO92203 AT MAINE > | | ---------------- IO92203 AT MAINE.MAINE.EDU > | O | > | | | "What I need is a computer that will do what I want it to do > +---------+ not what I tell it to do..." Don't we all.... -- 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.