Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!csd4.csd.uwm.edu!bionet!agate!stew.ssl.berkeley.edu!johnf From: johnf@stew.ssl.berkeley.edu (John Flanagan) Newsgroups: comp.sys.amiga Subject: Re: VD0 help Message-ID: <1989Aug31.142939.17009@agate.uucp> Date: 31 Aug 89 14:29:39 GMT References: <4450@shlump.nac.dec.com> Sender: usenet@agate.uucp (USENET Administrator;;;;ZU44) Distribution: na Organization: University of California, Berkeley Lines: 27 In article <4450@shlump.nac.dec.com> balzer@frambo.enet.dec.com (Christian Balzer) writes: >In article <20932@sequent.UUCP>, dmose@sequent.UUCP (Dan Mosedale) writes... >[Lots of trouble with the new asdg.vdisk.device deleted] >The new VD0: works like a charm (after installing the new CRD and DRD >utilities) on my 5 MB A2500 type system at home. It fails however >miserably on my 1 MB A500 here in the office, showing the described >symptoms (unable to load device). >Now the only "real" difference between the systems as far as VD0: is >concerned, is the lack of "real" FAST memory in the A500. >So if your system doesn't contain FAST memory besides memory at >$C80000, the new VD0: will fail. >And yes, I tried to set the BuffMemType to CHIP mem (3), but no go. >- You don't need to have any FAST memory. I installed VD0: on my 1 Meg A500 the other night, and it works just fine. I have a Super Agnus, and set the BufMemType to 3. Guess it's time to send in my check. John Flanagan Space Sciences Laboratory johnf@sag4.ssl.berkeley.edu University of California, Berkeley (...!ucbvax!sag4.ssl!johnf) Berkeley, CA 94720 Manners Maketh Man. (415) 642-7635