simplest way to make maxtor detect as ATHENA etc?

[drc]

For demonstration purposes, what would be the simplest way to cause a functioning maxtor drive detect only as ATHENA or whatever family name it has? I was under the impression that a corrupted header in the g-list or p-list would cause this behavior, but I have been having trouble inducing it on purpose on a drive I have here by writing random bytes over the TAP_LD1 and TAP_LO1 bytes in these modules.

[harddrivespecialist]

Just hit it very hard! It would be the simplest way.

[BlackST]

Nooo... Simply put some trash in the copies of g list... Or on 1f - Disk. Easy to recover after the lesson.

[Doomer]

but I have been having trouble inducing it on purpose on a drive I have here by writing random bytes over the TAP_LD1 and TAP_LO1 bytes in these modules.

There are two copies of critical modules on Maxtor drives

[BlackST]

In fact I said COPIES, plural...

[drc]

I think part of the problem is that the disk I was using (a 94610U6) is not properly supported... Looking at the module list I'm not convinced that it was mapping them out properly.

[BlackST]

Can you post pics of label and pcb? Thanks.

[drc]

I won't be back at work until Tuesday, but sure.

What concerned me is that when I opened the saved modules in a hex editor, it looked like there were headers for other modules later on in the files.

[hddguy]

Are you using ISA PC3000?

[drc]

no, salvation data hd doctor.

here's a pic of the label and a fuzzy one of the pcb... all I had here to take pictures with was a customer's flatbed scanner so the pcb one isn't so great.

Attachments