OK I stand corrected. The PUIS feature was indeed mentioned back in 2009, in connection with a similar problem:
Originally Posted by allen98311
Originally Posted by bfdtv
Did you open Control Panel -> Administrative Tools -> Computer Management -> Disk Management and initialize the drive?
Windows was not seeing the drive at all. I used a Fedora 11 boot disk and used fdisk to create a new dos partition table, then rebooted the computer into windows and then it was finally detected.
Update: After I turned off the computer and then turned it back on, Windows could no longer see the drive. After I then booted into Linux and then into Windows, Windows could see the drive.
Update 2: I had to disable the power-on in standby
feature of the hard disk in order for windows to recognize the drive.
I didn't even own
a Pal back in 2009!
AlexG883 brought up the above problem again just over a year ago, in posts 14427-14457. (Evidently others including LenL have also encountered this issue, so there may be more discussions that I didn't find.) But even if I'd found one of these earlier discussions (or remembered the second one), their problems weren't exactly the same as mine. Their HDDs wouldn't work in their PCs with Windows. Mine worked fine
- it only
failed when I tried to move it to an external USB enclosure, so naturally I thought the problem was related to USB or the enclosure, not the way E* originally configured these drives.
That wrinkle would have made searching the thread fruitless. There's no way I would have known to search for HDD power-related issues until after
I stumbled across the solution.
Turns out that although Windows doesn't spin up these drives, the BIOS in some PCs (apparently including mine) will, so the problem remained hidden
until I moved the drive to a less favorable setting. If you own a PC like mine, there's no need for the Linux boot that others had to use - just connect the drive directly (where it works) & use the Windows+CygWin version of HDParm (you need admin privileges but should omit the "sudo") to make the same setting. Then the HDD will work in its new home.
That's the new piece of information that made my original post worthwhile, even though the problem had been discussed before. In any case, we've now spent far more time debating whether or not I should have made that post than could possibly have been wasted by reading it.