If somebody have a solution for rebuild the rom image from SA copy (wich is different),this can be good too...

Thanks,
Janos

If you want to poke around in internal memory space including ROM you will need to know about MD 02 R/W Drive Memory
Location Command

But it's structure is confidential so you will need to work it out yourself :O) Which is fun

_________________
All went well until I plugged the drive in.

What did I told you, Janos ?

Can't you match that ROM?

What is a model of your drive and firmware?

_________________
www.datarecoveryne.com

This is not an exact case, i simply want to have in file these ROM images:
F4FYA, M6FYA, and so on, wich comes only in internal ROM.

Why?
Because i can override the internal with an external one, and i can read/write the external easily.
So, if i have ALL the known roms in image file, i need to hold only 1-2 pcb for ALL dr cases instead of one big box filled with trash maxtor pcbs....

Guru, i am affraid, you have right....

Thanks, my friend!
Janos

easier and cheaper to keep a good archive of PCB's :O)

_________________
All went well until I plugged the drive in.

Yes, agree, easier, but not so professional.

Anyway, another purpose:
I have some SABRE drive without PCB, and i have some SABRE pcb, wich are not good for the HDAs....
But if i can read out the internal rom, i can use the HDAs with the pcbs, only need to override the internal ROM....

I am sure there is plenty of ROM's stored in HDDGURU files.

_________________
www.datarecoveryne.com

Actually, i have 26.
But all are external contents, like the hddguru files...

Janos

Hello gurus,

Now i have another interesting question.
I am working on one 6Y060L042 drive wich have main SA in H2, the FW code is YAR41VW0, you must know what this is meaning.
This drive have no ALT SA at all, i have checked. (Both in ROM support, and surface.)

I am working on writing up the matching SA but for H3 and YAR41BW0 and than selfscan the drive.
I have selected the matching SA resources (head model, preamp matched), and i have the matching pcb (M6FYA with this head type and SA support).

At this point i have wrote up the main and the alt SA too!
Both readable/writable error free, but something is still missing....
Step by step:
In the first step i have created the main SA (without the calibrated, but manually selected adaptives).
It was good, readable but a little bit slowly, error free, but the pcb can't start the drive!
It shows the original rom version (not ...BWZ) and calypso.
1. What was missing for the good start?
I think this must be outside of the SA area...

The next step i have wrote up the alt SA too.
The first SS from C failed, but i have got the good and shiny adaptives.
The second try with this adaptives passed!
And after this comes the interesting point:
The drive can start up with a little bit clicking, and shows the SS from A is queued.
I have stopped the countdown and saved the main SA, and restart the drive.
But after this, the drive is only clicking crazy.
I can't start up the drive with loader for the main SA, it starts to click immediately, i can do only hotswap, but with hotswap + own adaptives the main SA is error free!
If i start the drive with ALT SA loader, i can't finish again the SS because the OPTI step starts to clicking immediately, and i don't want to destroy the heads....

2. What happened exactly?

More info:
After all, if i put back the original PCB, the drive normally starts up, and error free!

Somebody have any suggestion or info?

Thanks a lot,
Janos

Am I right in thinking that you have written ALTSA + STANDARD SA to a drive which never had an ALT SA Area?

So there are two SA copies on your test drive?

_________________
All went well until I plugged the drive in.

Sometimes is possible as I already told him, but it's not always possible to succeed in SS-C !

A drive with ALT SA is quite specific. And I would not be surprised if the drive uses set adaptives to start off in ALT SA BUT would expect to find certain things within the ALT SA area which is written during STW in the factory compared to the standard SA.

I have never tried this and will when I have some spare time :O)

_________________
All went well until I plugged the drive in.

Exactly.

A little correction:

There are tree SA copies on my test drive.

The main SA in H2, the original, + the 2 new in H3.

Janos

Hi gurus,

I have a question again:

I have one BW0 2 head 80GB drive what i want to ss.
The problem is, the H2 is almost dead, and the SS needs >1 week to done and the drive always clicking (no servo) when testing the sectors in H2.

Now i am planning to disable the H2 completely before ss.
I have removed the H2 from DISK, the defect lists are empty, i have removed the sectors form FMTI on H2, but no luck.
The ss starts, but on the first OPTI step is failed immediately with E000 sense code.

Additionally, one of the steps tries to rebuild the FMTI with H2.

Somebody have any suggestion?

Thanks,
Janos

Somebody have resources or at least loaders for NEBULA old drive?

FW: JAC61HU0

Thanks,
Janos

Here you have one.

Dobre

_________________
Murphy was an optimist

Datarecovery in Belgium, Holland, France and Germany
Datarecoverytools http://www.drtools.eu

Thank you Dobre, i will try it soon...

Janos

It is strange.

The drive works with your overlays from your loader (but not with the entire loader), but not works with own built loader:

Anyway, H3 is dead, so i don't expect too much result without MHA replacement... :S

Thank you dobre,
Janos