Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!ucsd!ames!uhccux!olson
From: olson@uhccux.uhcc.Hawaii.Edu (Todd Olson)
Newsgroups: comp.sys.amiga
Subject: Re: The A-590/2091 FFS problem
Summary: me too!
Message-ID: <8737@uhccux.uhcc.Hawaii.Edu>
Date: 26 Jul 90 21:21:53 GMT
References: <2085@gould.doc.ic.ac.uk> <6600012@okcusr.UUCP> <1449@nyx.UUCP> <3398@leah.Albany.Edu>
Organization: University of Hawaii
Lines: 23

In article <3398@leah.Albany.Edu>, wfh58@leah.Albany.Edu (William F. Hammond) writes:
> It seems to be the case that using the "lock" command to change the
> write protect status of dh0: (vanilla 2500/30 with A2091) will cause
> the hex value 0B000008 to be placed in the longword at location 0.
> I don't know why, and I don't know whether there are other ways to
> provoke it.  I have never seen any other non-NULL value sitting there.
>

That is the value I also have in long word zero with my 2091 installed.
I would like to have an official fix as the change the filesystem method
does NOT work.  I purchased the controller and the hard drive at different
times so there was not a debuging version of the FFS on my drive when I
purchased it.  The update file system DOES NOT WORK, I have tried booting
up with a new copy of WB1.3.2 then do a ctrl-d and it is 0B000008.

Is there a REAL fix?

 
> ----------------------------------------------------------------------
> William F. Hammond                   Dept. of Mathematics & Statistics
> 518-442-4625                         SUNYA, Albany, NY 12222
> wfh58@leah.albany.edu                wfh58@albnyvms.bitnet
> ----------------------------------------------------------------------