Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!zaphod.mps.ohio-state.edu!uwm.edu!uwvax!daffy!rt6.cs.wisc.edu!pochron
From: pochron@rt6.cs.wisc.edu (David Pochron)
Newsgroups: comp.sys.amiga.programmer
Subject: Re: ramdrive repacking
Summary: Concerning RRamDisk
Keywords: Ram disk
Message-ID: <1991Feb8.184424.10170@daffy.cs.wisc.edu>
Date: 8 Feb 91 18:44:24 GMT
References: <88002@tut.cis.ohio-state.edu> <11795@helios.TAMU.EDU>
Sender: news@daffy.cs.wisc.edu (The News)
Organization: U of Wisconsin CS Dept
Lines: 23

In article <11795@helios.TAMU.EDU> cmw1725@tamsun.tamu.edu (Christopher Walton) writes:
>I would suggest to just use RRamdisk from The Other Guys.
>It works nicely, and better than the ramdrive.device drives..

The only problem with RRamDisk is it is nearly useless to all us Amiga owners
who have a combination of 16 and 32 bit memory and want the ram disk only in
16 bit memory.  Although the preallocated, fixed space of CBM's ramdrive.dev
is limiting, I can at least re-order the memory lists when I boot and make sure
it is in 16 bit memory.  With a 3000, this isn't necessary of course.

Also, VD0: is very useful if you have 16/32 bit mem combos, since it does
things very cleverly and allocates out of the C00000 memory first if it
finds it.

If they would add an extra flag bit to the mountlist entry that would force
the device to alloc out of memory in the last MemList field, I could use it.
(I *would* use it!)

-- 

       -- David M. Pochron   | "Life's a blit,
                             |  and then you VBI."
pochron@garfield.cs.wisc.edu |