Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!cs.utexas.edu!uunet!isis!nyx!bscott
From: bscott@nyx.UUCP (Ben Scott)
Newsgroups: comp.sys.amiga
Subject: Re: The A-590/2091 FFS problem
Summary: Does too does too!
Keywords: Location 0
Message-ID: <1581@nyx.UUCP>
Date: 14 Jul 90 00:26:49 GMT
References: <2085@gould.doc.ic.ac.uk> <6600012@okcusr.UUCP> <1449@nyx.UUCP> <38440@sequent.UUCP>
Reply-To: bscott@nyx.UUCP (Ben Scott)
Organization: Public Access Unix - University of Denver
Lines: 42

In article <38440@sequent.UUCP> cseaman@sequent.UUCP (Chris "I'm Outta Here, Man!" Seaman) writes:
>bscott@nyx.UUCP (Ben Scott) 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
[...]
>who).  Suffice it to say that I am still forced to manually poke a 0L into
>address 0 on every reboot, or MANY programs fail miserably.
 
Does too does too!  At least it worked like a charm on my A-590.  My explanation
of the actual cause may or may not have been accurate but the fix DOES work for
me and everyone I've heard about (until now).

>Believe me, I REALLY wish this was the case. Unfortunately, it isn't.  In fact,
>the version of FFS that I use with the 2091 is IDENTICAL to the version I
>used on my 2090a, which never caused any problems.  Whatever the problem is,
>it is not in the filesystem.

You may have hit on the problem... I mean, the only thing I can think of is 
that it is NOT the 2091 that's doing this to your location zero.  Check every
other program in your startup (even the normal C: commands) and see if it's
one of them.  If you really are running version 1 of the 1.3.2 FFS, then I think
it's unlikely that it's trashing location zero.
 
And what do you mean by "many" programs failing?  I never found any that 
actually died - most just exhibited that weird "gdos" string showing up or 
reported errors after they finished doing their jobs.  At any rate a program
affected by a trashed location zero is itself buggy, usually because of trying
to use an uninitialized pointer.  

.                           <<<<Infinite K>>>>

--
.---------------------------------------------------------------------------.
|Ben Scott, professional goof-off and consultant at The Raster Image, Denver|
|Amiga UUCP node domain: bscott@vila.denver.co.us Else: bscott@nyx.cs.du.edu|
|FIDO point address 1:104/421.2, or call the Arvada 68K BBS at (303)424-9831|
|"Don't embarrass us..."  "Have I ever?" - Buckaroo Banzai  | *AMIGA POWER* |
`---------------------------------------------------------------------------'