Re: Assistance requested......

[Rubywand <rubywand@swbell.net>]

remove the ZZ to reply writes ...

>>A friend/colleague has an Apple II GS that is the love of his
life.  It has a Vulcan hard disk drive.

Apparently, he was in the Apple Utilities and somehow managed to
rename the hard disk while a book was resting on his keyboard,
and thus renamed his drive something like 00000000000000.

He went back and tried to rename his drive to the old name, and
now that hardware cannot be recognized.

He has totally lost access to that drive.

Prodos does not even recognize that there is any hardware
installed in Slot 7. He can still access his two floppy drives,
and can boot ProDos from there, but he is unable to access or
locate his hard drive.

The install disk that came with his Vulcan hard drive cannot 
seem to locate the hardware either.

I told him I would post a plea for help. IN the meantime, he is
going to physically remove the hard drive, operate the system,
then try and re-install the hard drive to see if the hardware
recognises it. ....
<<

     It's an interesting hard drive problem (especially since 
it's not _my_ hard drive!) Not ever having messed with a Vulcan 
puts kind of a crimp in coming up with useful suggestions.

     If the problem is that ProDOS and/or GS/OS does not like 
the new name, one try might be to use a block editing utility 
(e.g. Zap or Block Warden from ProSel, Block Work, etc.). If the 
hard disk can be accessed by Slot and Drive from the utility, 
you should be able to modify the volume name in the main 
directory block.

     Vulcan's Install disk program probably expects to find a 
nicely formatted volume with a standard ProDOS or HFS name. Most 
likely, your friend has already tried doing repairs under 
whatever other utils come with Vulcan or which have been 
developed by Vulcan users. If not, it's another possible way to 
go.

     There are a few disk-fix utilities to try. ProSel-16 
includes some. Another fixer is called "Salvation".

     If the big problem is that the GS simply refuses to connect 
with the interface + drive-- i.e. there is no Vulcan Slot and 
Drive accessible under any software--  then, maybe, attaching 
the drive to a IIe or some other Apple II which is less picky 
would help.

     If the problem is that the interface refuses to tell the GS 
that it is connected to a valid volume because it does not like 
its name-- which, by the way, would cause one to wonder that it 
permitted writing such a name-- then, your friend may have to 
find a way to connect the HD via a different interface to 
salvage his data.


Rubywand