Got a jvc film camera with this drive built in for dr. To be clear: the drive works
perfectly in the camera, but the customer has erased some photos.

All my systems have the same type of ide or sata frames built in. I put the hdd
to test in a bay to slide it into the appropriate frame in the test system I want
to use.

Usually when connecting this drive with a pc the pc hangs at drive(s) detection.
Deepspar freezes
pc3k no detection
data compass no detection - freezes
Ninja - no drive detected
Atola - detects the drive but reports a defect pcb

But a mainboard Asus P5PE-VM is able to recognise the drive and even gives
access to partition and data and I could do the DR.

What causes the problem, that only a simple and cheap mainboard is able
to have access where all expensive tools fail?

+++

Could you not have used the drive in the camera and mounted it as a USB device for recovery?

_________________
All went well until I plugged the drive in.

All interfaces are equal, but some interfaces are "MORE EQUAL" than other.... It happens more often than we think.

Maybe your adapter is bad

_________________
SAN, NAS, RAID, Server, and HDD Data Recovery.

used 4 different adapters = of different manufacturers

Only one of them worked at all - but only on this mainboard.


+++

Another think one should always consider, is the possibility of an non-standard sector and/or block size, which will crash most (nearly all) systems. I have seen this a few times. 512 byte sectors is not always used. Especially in proprietary devices/systems.

_________________
http://pcrecoveryllc.com

this drive has 512 bytes per sector

_________________
SAN, NAS, RAID, Server, and HDD Data Recovery.

I had a HS031GA -30GB Nexus on PC3k UDMA working fine last week.

_________________
All went well until I plugged the drive in.

but for the copy I changed the UDMA from 66 to 33 and worked ok

_________________
All went well until I plugged the drive in.

Are you sure, the ss != 512?
Not was only logical remapping, like Linux does?

Janos