Path: utzoo!utgpu!news-server.csri.toronto.edu!clyde.concordia.ca!uunet!samsung!usc!apple!oliveb!amdahl!rtech!cpsc6a!crs
From: crs@cpsc6a.att.com (Chris "I'm Outta Here!" Seaman)
Newsgroups: comp.sys.amiga.hardware
Subject: Re: A2091 - question re: which FastFileSystem file to use?
Summary: Sorry, but nope.
Keywords: A2091 FastFileSystem
Message-ID: <2432@cpsc6a.att.com>
Date: 13 Apr 90 21:54:18 GMT
References: <1990Apr11.032032.12598@uncecs.edu> <10790@cbmvax.commodore.com> <10817@cbmvax.commodore.com>
Organization: AT&T (CPSC), Oakland, CA
Lines: 48

steveb@cbmvax.commodore.com (Steve Beats) writes:
< 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)

OK, for the record, I did NOT purchase a pre-formatted 2091/Quantum P40S
combo.  I purchased a 2091, and a Quantum P105S SEPARATELY.  The version
of FastFileSystem on my 2091 install disk has the following characteristics:

Size:    12248
Date:    5/8/89
Time:    09:33:20

Typing the file in hex mode shows the following:

"V36.03 (5/9/89)"

I have (several times) tried 'Update File System', as well as 'Delete File
System' and 'Add File System'.  I still have the problem with location 0.
The value that is there is NOT 'GDOS'.  When printed as a long, it shows
184549384.  When printed as a string, the middle two bytes are null, and
the outer two bytes are non-ascii.  Note that this value is the same whether
I boot from my unmodified Workbench 1.3.2 disk, my hard disk, or the
2091 install disk.  Also note that the copy of FastFileSystem on my 2091
matches the copy on my Workbench 1.3.2 disk identically, which was in use
on my 2090A for several months, and never bothered location 0.

I appreciate all the help that has been given, but there is definitely
something else causing this problem.

Chris

-- 
Chris (Insert phrase here) Seaman |   o\  /o                See
crs@cpsc6a.att.com <or>           |     ||     "Attack of the Killer Smiley"!
...!att!cpsc6a!crs                |  \vvvvvv/           Coming Soon
                                  |   \____/      to a newsgroup near you!