Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!csd4.csd.uwm.edu!uxc.cso.uiuc.edu!tank!uwvax!astroatc!nicmad!madnix!perry
From: perry@madnix.UUCP (Perry Kivolowitz)
Newsgroups: comp.sys.amiga
Subject: Re: VD0 help
Message-ID: <822@madnix.UUCP>
Date: 3 Sep 89 16:27:27 GMT
References: <935@wsu-cs.uucp> <20810@sequent.UUCP>
Reply-To: perry@madnix.UUCP (Perry Kivolowitz)
Distribution: na
Organization: ASDG Incorporated
Lines: 28

In article <20810@sequent.UUCP> dmose@crg3.UUCP (Dan Mosedale) 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
>>some one can help me with.  I followed the instructions in
>>properly installing VD0 but on booting up the mount command
>>results in a "Can't find device" message even though the
>>device is listed in the mountlist.
>
>I'm having the exact same problem.  I mount it (no problem here), but
>the first command which tries to reference VD0 get a 
>"Can't find device" message.  Any help would be greatly appreciated.

It is quite likely that someone changed the name of the device driver
so that it did not match the internally found name string OR the device
driver mentioned in the mountlist does not match the name of the device
driver.

The new driver provides smaller driver code but no other advantages. My
suggestion is to keep using the old driver since there's very little 
reason to disturb your already working environment.

We are offering no support at all for this software.

-- 
                        Perry Kivolowitz, ASDG Inc.
ARPA: madnix!perry@cs.wisc.edu   {uunet|ncoast}!marque!
UUCP: {harvard|rutgers|ucbvax}!uwvax!astroatc!nicmad!madnix!perry
CIS:  76004,1765 (what was that about ``giggling teenagers''?)