I've searched for similar problems but in the end I have to ask.

I was transferring files between drives (using Windows Explorer) and
there was some error message (I don't recall exactly) and some of
the files did not transfer. I tried again and only a few more transferred.
I tried a third time and and all subsequent efforts result in:

"D:\ is not accessible.
The file or directory is corrupt and unreadable.

The drive still appears in Windows Explorer but checking the drive properties
just shows 0 bytes used, 0 bytes free.

I can hear the drive spinning but no head activity. There is no sign of
smoke or burnt components. The data on the drive is not critical but I
would like to know:

1) is this problem is something that might be resolved by replacing the PCB?

2) if so, is this candidate donor drive compatible?

Patient (Dead) drive :
Diamond Max 10 200Gb, PATA 133
Model: 6B200P0041001
Code: BAH41BMO K, G, B, A
Sticker: B2GBA

Possible Donor drive:
Diamond Max 10 200Gb, PATA 133
Model: 6B200R0A61202

(no other info currently available)

3) If 1 is Yes and 2 is No, then which drives have compatible PCBs?

Thanks for any information you might have for me.

This really doesn't sound like a PCB problem. Maybe a firmware issue. Maybe a corrupted partition.

Check the drive in computer management to see if it shows the
unformatted size.
Sounds like a partition error to me

Thanks Steve and R for the feedback.

Computer Management sees the drive,
Status: "Healthy, Active" (if it only knew),
Capacity: 189.91 (pretty accurate, it's a 200Gb)
Free Space: 189.91 (not true)
File System: blank (not true)
Layout: Partition
Type: Basic

If I attempt to Open or Explore from the Computer Management
window:

"The system cannot find the device specified"


Fingers itching to click Format... or Delete Partition... But,
even if the data isn't "critical" but it would be nice to be
able to get this drive in good enough shape to write as
much contents as possible to another drive before doing
that.

I agree with Steve, a Partition issue. Try DR software. If possible, try imaging the drive first, as the source of the error may have been hardware-related.