Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!uwm.edu!csd4.csd.uwm.edu!bionet!agate!ucbvax!UREGINA1.BITNET!GORRIEDE
From: GORRIEDE@UREGINA1.BITNET (Dennis Robert Gorrie)
Newsgroups: comp.sys.amiga.tech
Subject: Re: Hard Disk Problems... VERY LONG...
Message-ID: <8909121615.AA06969@jade.berkeley.edu>
Date: 12 Sep 89 16:11:21 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Lines: 37


OK.  In the devsetup file, I changed BlockRead to NoBlockRead, and things
seem to be working, ALMOST...

Do you (or anyone, especialy Steve Tibbet, who wrote FEdX) have experience
FEdX??  It does not seem to be creating proper .hdft format files for the
format program.

I start the format program.  It goes through pattern tests 0 to 6.
Then :
       'Beginning final format'
       'Error - 26h - Invalid field in parameter list'
       'Program aborted - Device error'
       'CLTD format failed return code 100'

In the format file the next thing is an errors list of the errors I entered, in
Cyl, Head, Offset Format.  For the heads, when I entered the errors, I entered
them with head numbers 0 to 6, like the errors sheet I recieved.

I am thinking that this is the cause of the 'Invalid field in parameter list'
error.  Should I number the heads 1 to 7?  Or, should I be using BLOCK format
for entering the errors?

I ran another format, WITH 0 pattern tests, and I CLEARED all of the errors
list.  THAT TIME, the format completed successfully.

SO, it seems the formater will complete OK if I don't enter the errors list,
but it bombs if I do enter the errors list.
SO  it is still next to useless , as far as reliability goes.

Any ideas?   Should the heads be numbered 0 to 6 or 1 to 7 in the errors list?
Also, is the ADAPTIVE BUFFERS flag crucial in  my devsetup?   Should I remove
it altogether from my DEVSETUP?

      Thanks for all of your help

                           Dennis Gorrie  GORRIEDE AT UREGINA1.BITNET