Path: utzoo!utgpu!water!watmath!clyde!cbosgd!ihnp4!homxb!mtuxo!mtune!lzaz!lznv!psc From: psc@lznv.ATT.COM (Paul S. R. Chisholm) Newsgroups: comp.sys.ibm.pc Subject: Re: Fun with RAM disks (was Re: Improve response time with paths) Message-ID: <1211@lznv.ATT.COM> Date: 9 Dec 87 18:04:00 GMT References: <15000048@silver> <1199@lznv.ATT.COM> <2263@techunix.BITNET> <634@astroatc.UUCP> Organization: AT&T Lines: 32 In article <634@astroatc.UUCP>, jojo@astroatc.UUCP (Jon Wesener) writes: > In article <1199@lznv.ATT.COM> psc@lznv writes: > >I do something similar with my C compiler. Most of the time, I boot > >off of the C: drive (hard disk), without a RAM disk. When I want to > >hack, I put in my "C boot floppy" and boot off of it. The CONFIG.SYS > >builds a RAM disk, specifies that C:COMMAND.COM is the command > > Why don't you get one of the ramdrive programs that don't > take up any memory (except for a small amount for the driver) until > you request it to. The one I use lets you specify the drive and > amount of memory you want whenever you want with a special program > called setram. You can also use it to deallocate the space from the > drive as well. Okay, sounds interesting. Where can I get one of these? (SETRAM, you said?) There's an advantage to "dealing with floppies": I don't need to keep *anything* on my hard disk to build the header files. I could keep just the header file archive on the hard disk . . . or I guess I could still keep it on floppy, and have the batch file build from floppy. *sigh* The *real* solution is to get an EMS board, so I can have a *big* RAM disk without losing any conventional RAM. And a bigger hard disk. And a math coprocessor, so ORBITER and Generic CADD run faster. And a laser printer. . . . > jon wesener {seismo|harvard|ihnp4}!{uwvax|cs.wisc.edu}!astroatc!jojo -Paul S. R. Chisholm, {ihnp4,cbosgd,allegra,rutgers}!mtune!lznv!psc AT&T Mail !psrchisholm, Internet psc@lznv.att.com I'm not speaking for my employer, I'm just speaking my mind.