Loader creation is called "Off-line start resources" when you do HDD resources backup.

_________________
Digitalsupport Data Recovery
https://digitalsupport.dk

I renamed your modules.

I'm studying the LDR file, you might try to build LDR manually for other hitachi arm drives too...

I attached instructions on how to build ldr manually, but i'm not sure if is correct, in particular i'm not sure about first 200 (hex) bytes

_________________
My firmware database:
https://mega.nz/folder/O01DkBRI

I haven't test yet, i'm still doing some other checks, it seem that i was wrong about creating ldr portion regarding USAG.
After i will sure about it i will check with sediv.

_________________
My firmware database:
https://mega.nz/folder/O01DkBRI

I can't open the posted RAR instructions. However, I have had a look at the loader here:

http://www.hddoracle.com/viewtopic.php?t=2696&p=19960#p19960

_________________
A backup a day keeps DR away.

Yes, my USAGE ldr portion studing is wrong due to some bytes that in the ldr are different from USAGE module file!
It's tough for me to build USAGE portion correctly, i don't understand why pc3000 changes some bytes when creating the ldr, the only thing i understood is that inside ldr file created in pc3000 you can read since offset 200h which modules are included and in which order.


Inside USAGE module you can see all modules of service area

_________________
My firmware database:
https://mega.nz/folder/O01DkBRI

The differences between the USAG module in the loader and the corresponding USAG module in the SA are the result of adjusting the individual "offsets" of each component module when the preceding, unnecessary module (eg PSHT) is removed from the directory.

_________________
A backup a day keeps DR away.

It's not only that, some byte are also different.

_________________
My firmware database:
https://mega.nz/folder/O01DkBRI

I show you which bytes are different, maybe you will find out how those bytes have to be modified.

_________________
My firmware database:
https://mega.nz/folder/O01DkBRI

I noticed that all '04' bytes in USAGE file are swapped into '05' bytes in LDR and all '05' swapped into '04'.

_________________
My firmware database:
https://mega.nz/folder/O01DkBRI

Those bytes constitute a little-endian word, eg 0x052E -> 0x04C1.

_________________
A backup a day keeps DR away.

Thanks, i still don't understand what they mean this little-endian words and how to modify them correctly to build a proper ldr file.
I compared spildit USAGE file with my USAGE file (i posted in this thread from one of my hitachi fw resource), the are some little difference but all bytes are identical where ldr applys changes
Probably we don't need how to figure how pc3000 builds the loader, because probably difference between USAGE and LDR are always the same.
I would be able to confirm that, if drHDD can build a ldr from my fw resource and then i compare it with my USAGE.

_________________
My firmware database:
https://mega.nz/folder/O01DkBRI

AFAICT, the parameters which I have called "offsets" for each module in the USAG directory should be the PBA or sector number in the SA. This means that the locations of some of the modules in the loader's USAG directory do not match their actual locations in the SA. :?

_________________
A backup a day keeps DR away.

ISTM that when PC3K creates a loader, it grabs all the necessary modules and compacts them all into a contiguous "virtual" SA which resides in RAM. The layout of this RAM based SA bears no relationship to the physical SA on the platters. AISI, this creates a potentially dangerous situation whereby one could overwrite a physical SA module with the wrong virtual SA module.

_________________
A backup a day keeps DR away.

ISTM that the tool which was used for the SA dump incorrectly determined the size of the IDNT module as 3 sectors rather than 2 (as specified in the USAG directory). In fact the third sector of the IDNT dump is actually the first sector of the SRVP module. :?

_________________
A backup a day keeps DR away.

I don't understand why SeDiv doesn't just consult the USAG directory rather than an INI file. :?

_________________
A backup a day keeps DR away.

Because USAG might be unreadable....

Spot on answer BGman

_________________
All went well until I plugged the drive in.

Spildit,
Please contact me
Whatsapp +79176782880
email Jubtcrussia@gmail.com

HUS724040ALA640-MFAOA8G0

~~~~
I don't understand, who helped me create a LOD?