it seems i am forced to replace a harddisk within a Vulcan harddisk system.
It seems the drive from Seagate has been patched with special information
within the track zero for use with the Vulcan controller by the people at
Applied engineering. The regular software itself won´t accept any other
drive from Seagate ( remark from software after attempt to write new partition:
"i don´t recognize this disk" ) from general market.
So the conclusion is that the guys at AE must have marked up the track 0
of the drives used in their system in special way that the controller would
recognize only drives with that patched track zero.
If anybody has replaced such a drive within tha last years with another harddisk
( not from another Vulcan system ) i would appreciate information on that exchange.
Otherwise i will be forced to enter after more then 30 years again back to
that "handy tools" like Locksmith, Copy II+ 9.1, and Merlin as well as the old
disassemblers ( probably first starting by searching that good old container
with the ORCA set of manuals and program related to the assembler there....
and after that all collected together start picking up the track zero from the
availiable drive and starting to analyze and debug that disk.
As for quite a lot parts of that age my drive has a damaged bad block in the
beginning of the disk and therefor refuses the updates, change or repartitioning....
and doing a low level format would be a very bad idea because that would delete
the precious information from the track 0 and the next track used by the AE engineers
containing the information required for smooth work with the firmware in the controller....
At the other hand just plugging in another IDE drive with 40 MB or 100 MB or even 200 MB
freshly just low-level formatted and not partitioned or formatted by anything else
doesn´t work... ( see reply from software mentioned above )......due to missing infos from patched track
ao unless the information patched by the guys from AE to the disk isn´t also patched with updated data
(according to the actual drive => amount of tracks, amount of sectors, amount of sectors i.e. blocks,
translationtable to VTOC and to proDOS as well as the initial proDOS heading of that drive and a kind of AE-ID byte ) to the replacement drive the controller won´t ccoperate and accept the drive for working,
partitioning and formatting....
any kind of information from cracks who entered that task -
or former employees from AE who have documentation to this topic are welcome ......
i even guess that the guys at AE had a disk within the company containing taht initial formatting programm that permitted just to enter the drive data with cylinders, heads and amount of sectors and the formatting programm
then writting this "special track" to the disk ready for use with the controller....
it might be a great deed to the public, after stopping the support of the Vulcan Harddisk system and releasing
the material to the public at the "Applied Engineering Repository" at http://ae.applearchives.com/
to release there the documents or the image of that disk to enable the Users of a Vulcan Harddisk System
and thereby granting them the chance to replace a drive, if that turned bad by age or damage....