Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!cornell!rochester!udel!mmdf
From: wilts@cavax.ab.ca (Ed Wilts)
Newsgroups: comp.sys.amiga
Subject: Re: FFS bug/ fixed in 1.3.1
Message-ID: <22521@louie.udel.EDU>
Date: 25 Aug 89 20:49:57 GMT
Sender: mmdf@udel.EDU
Lines: 28


>    As some of you might recall I am having trouble with my HardFrame
> and an ST296N. It does not seem to want to automount the drive and
> its partitions.
>    I talked to a fellow at MicroBotics this morning and he said that
> it sounds like 'the FSS bug'. Loosly what he said is this: The older
> version of FFS (the one that came with 1.3) will not automount partitions
> with null bytes in the header block (or something like that). He said
> that Commodore just admitted to the 'feature' about 6 weeks ago. He
> also mentioned that this has been fixed in the version of FFS that
> is with 1.3.1 of the system software. Therefore. could someone from
> Commodore (or anyone else for that matter) send me a uuencoded version
> of this newer FFS. I really need it to get my drive up and running.

I believe that 1.3.1 was released to commercial developers only.  It is claimed
to fix not only the FFS bug but also SETCLOCK RESET so that people won't have
to revert to 1.2 to reset their clock.  I believe that there were some fixes to
serial.device to prevent lost data at high speeds as well.  If I recall
correctly, FastFonts was also fixed to parse the command line properly.  Maybe
CATS can tell us what the status of 1.3.1 is for us end-users? The last I heard
(rumoured) was that they were unsure how to electronically distribute these
updates - perhaps we'll have to back to our dealers and get updates again for
fixes between releases (ie between 1.3 and 1.4).

        .../Ed          (EWilts%Janus.MtRoyal.AB.CA@UncaNet.Bitnet)
Ed Wilts
Sr. Systems Analyst, Canadian Occidental Petroleum Ltd.
Calgary, Alberta, Canada                 (403) 234-1007