Hello Ya'all:
Here's my two cents on this: There's two main components on a USBdrive--
thedriveitself, and the USB (or firewire) to PATA (or SATA) bridge. The
problem, as far as I can tell, is previously, like in XP, the bridge anddrivenever needed a driver from the device manufacturer -- XP had a built-in
driver for the bridge as well as thedrive. What now looks like is happening
is they have a built-in driver for the bridge, but do not have drivers for
the drives. I have a Nexstar USB to PATAdrivechassis. When I put a Seagatedrivein it, it works. When I put a Maxtor, it doesn't. My best guess is
whoever was alpha testing this at Microsoft didn't have every combination ofdriveand bridge to test, so only what was on-hand was tested, and since that
seemed to work, that's what was released.
On a similar subject is a huge oversight on the part of USB memory keys.
Originally, we heard rumors of even more advanced support for memory keys --
according to Microsoft's WHQL list -- memory keys are NOT supported. In fact,
I have a Lexar Jumpdrive -- the most common memory key ever made -- doesn't
work and not supported.
When the driver installs the bridge driver, that goes oK, but when it gets
to the "drive" portion of the driver, if you go to the driver details -- it
says "Could not start driver -- invalid switch".
I sent in an e-mail to Microsoft's support (90-days by the way on Vista),
and have had no response other than an automated acknowledgement that the
message was received.
I also contacted Lexar on the USB memory key issue, and they were completely
caught off guard.
If you thinkdriveproblems are a problem -- they are just the top of the
iceburg. Try connecting to a Mac network, or printing over an ethernet print
server -- on the Mac network, you end up logging into yourself, and most
ethernet print servers don't work - in fact, funny as it seems, when Vista
first went beta, the HP Laserjet 4si wasn't even in the device list as a
local printer.
Lance
- Show quoted text -