Re: Aargh! Goodbye HD...

[supertimer@aol.com (Supertimer)]

bguenter@rummelplatz.uni-mannheim.de (Boris Guenter) wrote:

>Hi, folks. I hate it when this happens.
>
>Jaz drives are nice for mass storage, but their habit to turn themselves
>off after 30 minutes has often annoyed me and today it was the first
>time that this &%$$% drive has actually DESTROYED some of my data.
>
>Played a game, drive turned off, re-inserted disk, saved game, game
>garbled partitioning information. I know that the data is still somewhere
>on the disk, but unavailable with classic IIgs file or disk utilities.
>
>Now the three questions are: 1) Are there any Mac utilities which are
>able to check an entire volume for lost files and can restore them to 
>another volume? 2) Are there any sector editors for SCSI volumes so that
>I may at least check the contents of the lost files? 3) Is there really
>no way to disable that $@"/&@ auto-sleep feature to prevent future
>accidents? Otherwise I will have to sell this shit device, I have enough!

Hi, you need the Tulin driver.  With the Tulin driver, any access
to the drive will safely wait until the drive is turned on again.

I know how you feel.  I have a Zip drive on the IIGS and it does
the same thing.  Since I don't have the Tulin driver yet, I have
to "goose" the drive by ejecting and reinserting the disk every
once in a while.

If anyone knows a way to open the drive to hardwire it to stay
on, I'd do it in a second!

Ok, where to get the Tulin driver.  Someone on Compuserve
sells it (a former Tulin employee).  I don't have the email address
handy.  Maybe someone else on csa2 can provide it.

PS. In the meantime, I've found that HFS volumes are more
resistant to total failure.  For example, when the drive spins
down and a write is made to a ProDOS volume, usually the
Zip disk becomes inaccessable.  When this happened to one
of my HFS disks, however, the volume could still be accessed
but the file written to was damaged and could not be deleted.
I was able to copy the files from the HFS volume to a new
disk.  I think this is because HFS file info is not stored in a
centralized block map like ProDOS file info.