Path: utzoo!utgpu!watserv1!watdragon!tiger!swklassen
From: swklassen@tiger.waterloo.edu (Steven W. Klassen)
Newsgroups: comp.sys.atari.st
Subject: Re: Resettable RAM Disk
Message-ID: <20554@watdragon.waterloo.edu>
Date: 5 Feb 90 18:10:43 GMT
References: <908@watserv1.waterloo.edu> <510001@hpbbi4.HP.COM> <26558@cup.portal.com>
Sender: daemon@watdragon.waterloo.edu
Reply-To: swklassen@tiger.waterloo.edu (Steven W. Klassen)
Distribution: na
Organization: U. of Waterloo, Ontario
Lines: 26

In article <26558@cup.portal.com> buggs@cup.portal.com (William Edward JuneJr) writes:
>
>I thought MWC *ONLY* works with its ram disk?!
>Seemed like I tried the CodeHead one and it didn't work.
>But then that profile file is a killer to edit too, well, to me it is!

I don't believe there is anything magic about the MWC ram disk.  I have
not used any other since getting MWC (since I like the ability to take
a 'snapshot' of the ramdisk and its contents and save it as an executable
file) but I believe it will work with any ram disk.  (It will also work
without using a ram disk - thinks are just slower.)  You shouldn't even
have to tell profile about it unless you want it to be used automatically
for temporary files.  In that case, you need to set up the environment
variable TMPDIR to whatever you called your ramdisk.  (My ramdisk is
drive 'h:' and contains a single directory 'tmp'.  Hence I set the
variable TMPDIR to 'h:\tmp'.)

I use the ram disk all the time with non-MWC stuff (especially when
downloading, uudecoding, and unarcing stuff from USENET.  By doing
all the intermediate steps in the ramdisk I help avoid fragmenting
the hard drive.).


Steven W. Klassen                       +-----------------------------+
Computer Science Major                  | Support the poor...buy fur! |
University of Waterloo                  +-----------------------------+