Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!zaphod.mps.ohio-state.edu!mips!decwrl!fernwood!uupsi!rodan.acs.syr.edu!ldstern From: ldstern@rodan.acs.syr.edu (Larry Stern) Newsgroups: comp.sys.ibm.pc.misc Subject: Re: Command.com in ramdisk Message-ID: <1991Apr15.233724.13987@rodan.acs.syr.edu> Date: 15 Apr 91 23:37:24 GMT References: <1991Apr12.192526.23566@rodan.acs.syr.edu> <1991Apr14.022004.9023@news.iastate.edu> Organization: Syracuse University, Syracuse, NY Lines: 20 In article <1991Apr14.022004.9023@news.iastate.edu> jdwhite@iastate.edu (White Jason David) writes: >In article cs352a41@cs.iastate.edu (Adam Goldberg) writes: >[...] >>Admittedly, this isn't a great speed-up, but I haven't any easy way to use >>my upper 384K for anything else. Speaking of which, anyone have any ideas >>what I could do (for free) to utilize my 384K better than a Ramdisk? >>-- > >Yes, set it up as a disk cache. You'll love the difference in access time. >This is, of course, assuming you have a hard disk. > >Jason White // jdwhite@iastate.edu // "Get bent!" - Bart Simpson What is the best way (or configuration) to set up the 'upper' 384K as a cache? And does DOS have a way or is a PD program better? -- Larry Stern LDSTERN@RODAN.ACS.SYR.EDU