EDIT 0B/2B DISABLE

[mhp666]

Module 0x35 seems to have no entries.
Also I do not know how with MRTLAB the translator of the SA can be regenerated.

I do not understand IIUC, ISTM

The 0x20B module does not know where it is.
I look for it in the rom and I can not find it and in the list of modules either. I find the 0x20B0, but I guess that is not it.

[fzabkar]

IIUC = if I understand correctly
ISTM = it seems to me

ROM module 0x20B

Code:

Offset(h) 00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F

0003EEE0                       52 4F 59 4C 04 00 1E 00 0B         ROYL.....
0003EEF0  02 01 00 26 D7 1A 86 30 30 30 33 30 30 30 30 00  ...&×.†00030000.
                   ^^^^^^^^^^^ 32-bit checksum

0003EF00  00 00 04 04 00 0A 12 02 01 00 18 00 03 18 90 00
0003EF10  EA F2 01 00 EA F2 01 00
          ^^^^^^^^^^^ ^^^^^^^^^^^ ABAs for copy 0 and copy 1 of mod 01

[mhp666]

IIUC = if I understand correctly
ISTM = it seems to me

I thought they were parameters of the HDD.

OK, now I understand it 0B 00 -> ox000B = 0x0B
0B 02 -> 0x020B
Thank you,

I tried to edit the module 20B, but when I try to record it (after recalculating checksum) it gives me an error, but if I do not modify it and try to record it does it well.

Tomorrow I'll see something else it's too late for me. Greetings.

[mhp666]

I finally solved the problem, by chance.

I format the SA and I record the tracks.
The hdd is not able to identify itself.
I return to record the ROM, turn off and turn on the HDD and recognized correctly.

I do the same again and the same story.
If someone wants, can I do the process again and see if something is modified in the BIOS, or is it that when recording the ROM, something else is done?

[mhp666]

By the way, module address 0x20B points to track -102 offset 0X54000 (bytes). That if I do not make a mistake, it's like a second copy of module 0x01.

Attachments

102.rar

(43.9 KiB) Downloaded 539 times

[mhp666]

If the information of the module 0x20B is copied in the module 0x0B and the module number is changed and the checksum is recalculated. It is written to the ROM and the hard drive is started. it works perfectly.

[fzabkar]

Your tests suggest module 20B should have been active, not 0B, in which case an alternative solution would be to change the flag from 04 to 06.

Module 0B

Code:

Offset(h) 00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F

00000000  52 4F 59 4C 04 00 1E 00 0B 00 01 00 F5 6E B2 86  ROYL........õn²†
00000010  30 30 30 33 30 30 30 30 00 00 00 05 05 00 0A 12  00030000........
                                           ^^^^^ active flag

Module 20B

Code:

Offset(h) 00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F

00000000  52 4F 59 4C 04 00 1E 00 0B 02 01 00 26 D7 1A 86  ROYL........&×.†
00000010  30 30 30 33 30 30 30 30 00 00 00 04 04 00 0A 12  00030000........
                                           ^^^^^ active flag

[mhp666]

Can you tell me if you do not mind some things?
microjobs and media / head: What are they?

The activation flag of the module in which offset is found? 0x04?

[fzabkar]

To understand microjogs, see the discussion of "MR Offset" in the following guide:
http://hddscan.com/doc/HDD_Tracks_and_Zones.html

Media/Head values identify the manufacturers of these parts. See SA module C5h.

Head Stack Replacement: Questions and Answers:
http://www.hddoracle.com/viewtopic.php?f=78&t=198

AIUI, the active flag is the greater of the two flag bytes at offset 0x1B. ISTM that you must have done something to change these flags.

[mhp666]

I have not touched any flags.

I did the test to overwrite the module 20B in the module 0B, but only change the module number and the checksum.

And what I have not come to understand, that I will see when I have time, is because after writing the tracks of the SA (without having touched the ROM), I have to rewrite the ROM (I have to check it again because I do not I see nothing logical unless the MRTLAB does something).

If you have any curiosity about the subject, tell me and when I reconnect, I'll send it to you.

Greetings and thank you very much for everything

[reco]

either 0B or 20B is now being activated when hdd be powered on, so contradiction will not make a difference ,I agree with that . But the addresses recorded shall nevertheless be consistent in most of the cases. Although only one of those modules is ought to be active , there is still a possibility that the other one is loaded into RAM or something which might be vital for initialization, because no matter what you have done , the aba shall be shown in module editor of ROM as long as ROM module is loaded successfully. What we are talking about is a complicated thing, a complete inspection is a good choice

[mhp666]

the aba shall be shown in module editor of ROM as long as ROM module is loaded successfully

+1