Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!gem.mps.ohio-state.edu!ginosko!uunet!nuchat!sugar!karl
From: karl@sugar.hackercorp.com (Karl Lehenbauer)
Newsgroups: comp.sys.amiga
Subject: Re: VD0: Problems
Message-ID: <4327@sugar.hackercorp.com>
Date: 10 Oct 89 00:06:06 GMT
References: <1122@nigel.udel.EDU> <15283@netnews.upenn.edu>
Reply-To: karl@sugar.hackercorp.com (Karl Lehenbauer)
Organization: Sugar Land Unix - Houston
Lines: 22

In article <15283@netnews.upenn.edu> strasser@grasp.cis.upenn.edu.UUCP (Colin Strasser) writes:
>There never WAS a resolution to this, was there?  I too have (what I think is) 
>the newest VD0: and cannot get it to operate.  It'll mount, but it won't
>recognize the device driver (DEVS:asdg.vdisk.device, I think) no matter how
>I try to finagle the mountlist entry.

I gave up on it based on problem I was having with the 512K of slow-fast
RAM on the 2000 and how rebooting overwrites part of it.  There was something
I could do to make it not happen, I believe it was to not do a FastMemFirst,
but I wanted to do one, because otherwise the thing was mallocing the first
512K of fast RAM from the DMA-slowed fast RAM, rather than the good stuff.

Anyway, I use RAD: now, but I sure did like having a RAM disk that grew on the 
fly.

Oh yeah, there was a hack in VD0 so you could only have a 2 MB VD0 unless
you had an ASDG memory board, in which case the limit was 8 or something.
(I did ultimately get one, an 8MI, which has served well.)
-- 
-- uunet!sugar!karl	"There is hopeful symbolism in the fact that 
-- 			 flags do not wave in a vacuum."  -- Arthur C. Clarke
-- Usenet access: (713) 438-5018