Path: utzoo!censor!becker!douglee
From: douglee@becker.UUCP (Doug Lee)
Newsgroups: comp.sys.amiga
Subject: Re: VD0 help
Message-ID: <830@becker.UUCP>
Date: 4 Sep 89 05:03:26 GMT
References: <935@wsu-cs.uucp> <11102@boulder.Colorado.EDU>
Reply-To: douglee@becker.UUCP (Doug Lee)
Distribution: na
Organization: G. T. S., Toronto, Ontario
Lines: 34

In article <11102@boulder.Colorado.EDU> rademach@tramp.Colorado.EDU (Simon Rademacher) writes:
>In article <935@wsu-cs.uucp> jal@kronos.cs.wayne.edu (Jason Leigh) writes:
>>I'm having a problem with installing the new VD0 which I hope
>>Any hints?
>I hate to say it (really) but "me too."
>
>To add a few more details--vd0 mounts ok (well, no errors) and even shows up
>in the list of devices that assign gives.  The message about not being able
>to find vd0 occurs when I try cd, ls, etc.  The computer does go looking on
>my boot disk for something (not cd, it's res'ed) but apparently can't find
>what it needs.  I do have the asdg.vdisk.device file in devs:.

>As Jason Leigh said, "Any hints?" and "Thanks in advance."

Some things to beware of, which are documented but nevertheless may have been 
overlooked. Make sure that BufMemType is correct. If you specify 5, and have 
no fast memory (fat agnus users take note), it probably won't work. HighCyl
must be an ODD number. Make sure you have as much free memory as VD0 
will use. The warning in the mountlist about not making HighCyl larger than what
you have is there for a good reason. I found the OLD VD0 didn't work well when
not able to run in a CONTIGUOUS block of memory. If you have 2 meg true fast,
1/2 meg chip and 1/2 meg $C00000 memory for example, making VD0 larger than 
just under 2 meg is probably asking for trouble. Make sure it is mounted 
BEFORE using rad:
>
>=======================================
>=          Simon Rademacher           =
>= rademach%tramp@boulder.colorado.edu =


-- 
Doug Lee
douglee@becker
416-461-5357