🚀 go-pugleaf

Not having a very good year so far ...

4000/060.  4Gb HD

Yesterday, writing a 3Mb w-p file, I got a block error.	 Mig crashed,
wouldn't reboot unless that partition was disabled, so couldn't run eg
DiskSalv or Quarterback. (It crashed if I tried to mount the partition
later).

Eventually I managed to "Cancel" the bootup-time requester which says
something like "Block error in WORK:  Retry/Cancel", after which it
booted with WORK mounted OK; so I ran Quarterback which sorted it out.

1st question:
That requester shows for much less than a second, and the mouse isn't
available *until* it shows.  I needed a 12-year-old shootemup expert, but
in the absence of such a being it took me about twenty tries before I
succeeded in catching it. Does anyone know how to slow the thing down?
I suppose it's still in ROM at that stage, so perhaps I've just got to
struggle, but .... ?

Today I tried again, and got a block failure again, though this time it
didn't wreck anything except the file itself :-)

It said "Block No 1089826", same as yesterday.

I want to put this in as a Bad Block, but HDToolBox doesn't care about
block numbers, it wants Cylinder, Head, Sector OR Bytes from Index.

2nd question:
I hate admitting such dismal ignorance, but please, someone, how do I
work out the figures that HDToolBox wants?

FWIW, the mountlist which I keep for emergencies tells me that the drive
has 945 blocks per track, 1 surface (eh?).  Does that help?

1089826/945 = 1153, which is a feasible track or cyl number for this
partition, with remainder 241 -- is that the sector?
Is that how to do it?  What about the other stuff that HDTB wants?

And why can't these people use the same terminology?  Is a block the same
thing as a sector?  I can't find anywhere where it says so.

I tried running HDToolBox's "Verify Data on Drive", hoping that it would
pick the duff block up for me, but it found no problems.

For the time being I've renamed the broken (and unreadable) file to
BADBLOCK and left it sitting there, which is a temporary cure, but it's
a tad wasteful at 3Mb :-)

Any advice will be very welcome.

DaveB