klothex said:
Hi Anna, thanks for your reply, I have tried every possible configuration
for
this so far, including replacing the enclosure with no changes in results.
I
tried your suggestion about scanning for hardware changes and have even
edited the registry keys where necessary to force the ESATA port to be
seen
in the services manager, but you were right, so far it has had no effect.
If
you have any other experiences with this and would like to share them, I
would be grateful for the help. Thanks in advance!
klothex:
I really don't know what else to suggest at this point. I'm aware of about 3
or 4 other persons who are using the Vantec NexStar 3 unit (I assume that's
the same model you're using) in both XP and Vista environments and with one
exception, they're all pleased with this unit. One user has reported a
problem similar to yours and there's an indication his unit may be
defective. But I'm not certain about this since this person
all-too-frequently reports non-existent problems!
As I previously indicated, assuming the enclosure & the SATA HDD are
non-defective items, we've invariably traced this non-recognition situation
to some Intel chipsets in that if the unit is connected/powered on *after*
the boot, it will not be recognized by the system until that Device Manager
command I mentioned above has been invoked. We've never experienced this
non-recognition problem when the eSATA external enclosure (regardless of
brand) was connected/powered on upon booting the system.
I should add that I've no experience with Vista's 64-bit OS, so I'm at a
loss to determine if there's some anomaly here that might be the source of
the problem.
Anna