The head brand is the same.
The pcb maybe compatible if both have rom or both not have.
If only one have, in this case this have some factory workaround for some problem wich can be (maybe) unique.

The pcb swap is not soo dangerous on this model.
Try it...

q2: depending on the healty of the drive, some hour....

Janos

Thanks Janos!

Both pcb has ext. ROM.
I was afraid of that maybe PCB swap will burns out something.

Q2: SS from the ALT SA is shorter then from MAIN SA?

ss from alt only prepares the main for real ss.
This is shorter of course.

I started a 'blind' SS from ALT SA with HDRepair2.0. It halted after about half hour.
I jumpered back to master, but nothing happened.
Now again in safe mode after boot it is in BSY state and in ALT SA.
How can I check why and where stopped the process?

The hddrepair dont have the proper knowledge to start a good ss.
This situation can be anything.
You need real tools to get information about the fault, if it is at all...

Janos

ALTSA test on drive is 20min only then normal selfscan starts . You need to modify selfscan script to start SS from ALTSA .

There are only two kinds of pcb on these drive :

1> c5-c1 with rom .
2> c8-c1

so it wont be hard finding donor pcb for the drive .

Question C. (SA in ALT SA) again.

Is it possible to build an SA (to reach LBA) in the ALT SA?
If I replace all modules in ALT SA with the MAIN modules and
maybe modify the 97h,96h,98h modules (ROM+OVL) in case of DM+8,
will it work like a MAIN SA?
I assume that both SA has the same size (number of UBA sectors).
Same mods+same entry point(boot) ->same functions...or not..

If not , what is the MAIN reason of it? (maybe CHS adressing)

ALT-SA is servo written in factory (hard coded push pin setup) MAIN SA is self servo write (drive does it )

ALT-SA is like the boot sector for initial process

_________________
All went well until I plugged the drive in.

The complete solution : buy a STW