Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!snorkelwacker!mit-eddie!uw-beaver!uw-june!dylan
From: dylan@cs.washington.edu (Dylan McNamee)
Newsgroups: comp.sys.amiga
Subject: Re: The A-590/2091 FFS problem
Keywords: Location 0
Message-ID: <12541@june.cs.washington.edu>
Date: 13 Jul 90 16:02:01 GMT
References: -2085@gould.doc.ic.ac.uk= -6600012@okcusr.UUCP= -1449@nyx.UUCP= -38440@sequent.UUCP=
Reply-To: dylan@june.cs.washington.edu (Dylan McNamee)
Organization: University of Washington, Computer Science, Seattle
Lines: 29

In article -38440@sequent.UUCP= cseaman@sequent.UUCP (Chris "I'm Outta Here, Man!" Seaman) writes:
=bscott@nyx.UUCP (Ben Scott) writes:
=- bn@okcusr.UUCP writes:
=- There's a simple clean fix for this.  Go in through HD_Toolbox, to "Partition
=- Drive", then click on "Advanced Options" and you'll see a box labeled "Add/
=- Update Filesystems" -click this and then change the version number of the FFS
=- from 0 to 1.  
=
=Sorry, but this doesn't fix anything.  I have had this problem since the
=day I installed my 2091, and NONE of the suggested fixes have done anything.
=Believe me, I REALLY wish this was the case. Unfortunately, it isn't.  In fact,

My experience agrees with Chris's;  changing the version number did 
nothing at all.  I still have to run my (56 byte!) clearZero C program.

=If anyone has any other ideas, I am willing to try anything.  However, I
=have tried the 'change the version to 1', 'manually force the filesystem
=to be updated', 'install the filesystem from another Workbench disk' tricks
=more times than I care to mention.  So please, DON'T suggest I do these
=things again.  THEY DON'T FIX THE PROBLEM!

Ok, so what's going on here?  Either some people have 'mutant' 2091's
that respond to the filesystem version change, or the helpful people
that have suggested the "simple clean fix" aren't running the same 
system.  (Mine is a stock 2500/30.)

=Chris (Insert phrase here) Seaman |    /--\

dylan 				-dylan@cs.washington.edu