Path: utzoo!attcan!uunet!lll-winken!elroy.jpl.nasa.gov!usc!zaphod.mps.ohio-state.edu!think!mintaka!oliveb!amiga!cbmvax!steveb
From: steveb@cbmvax.commodore.com (Steve Beats)
Newsgroups: comp.sys.amiga.hardware
Subject: Re: A2091 - question re: which FastFileSystem file to use?
Keywords: A2091 FastFileSystem
Message-ID: <10817@cbmvax.commodore.com>
Date: 12 Apr 90 09:22:11 GMT
References: <1990Apr11.032032.12598@uncecs.edu> <10790@cbmvax.commodore.com> <3190@usceast.UUCP>
Reply-To: steveb@cbmvax (Steve Beats)
Organization: Commodore, West Chester, PA
Lines: 23

In article <3190@usceast.UUCP> yarnall@usceast.UUCP (Ken Yarnall) writes:
>Hmmm.  I looked on all of my disks (HardDrive, 1.3.2 WorkBench, and 2091
>Installation disk) and all of them have a l:FastFileSystem with size 12248,
>as you promised.  However, when I plow through HDToolbox, I find it thinks
>that the FastFileSystem has a size of 13596.  Can you say wether this is an
>old version?  Where did it come from?  Is this one stored in the 2091's boot
>roms?  I don't want to go replacing it, since apparently I can't put it back,
>unless I *know* it is outdated!

Let`s get this straight once and for all.  The 2091 location 0 bug is caused
by a debug version of the fast filing system.  That version was accidentally
installed on the pre-formatted hard drives (the ones with workbench already
on them).  It is ALSO in the RDSK file which is just an image of the Rigid-
DiskBlocks on the drive.  If you do the quick setup then you`ll get the
buggy FS installed.  You should delete the FastFileSystem that is 13596 bytes
long and replace it with the one in L: on the 1.3.2 Workbench or the A2091
installation disk.  There are NO location zero bugs in the A2091 driver!
-- 
  _________________
 / __	    __	   \	Commodore/Amiga Inc.	|       This space left
( (__'	   |__)	    )	Email:	cbmvax!steveb	|        intentionally
( ,__)teve |__)eats )	BIX:	sbeats		|           blank!
 \_________________/	PHONE:	(215) 431-9100	| 01144 482 824141 (UK phone)