Edit for additional information: I am running an HP dv5-2035dx with an AMD Turion II P520 Dual Core Processor (2.30 GHz), 4GB of DDRMHz, and an Intel X25-M 80GB SSD. I assume it's just an unsupported feature, but since it seems to be software-based and not hardware-based, there should be a workaround. Right now the drives do reuse drive letters, so I assigned them permanent drive letters to make sure there was no overlap and that made no difference. I was wondering if anyone had any tips on how I might get Windows 7 to recognize both drives - i.e.ĭrivers or updates or some sort of workaround. At first I figured it was a hardware limitation (not supported by my chipset) and I just used USB most of the time, unless I had large files to transfer, but when I installed Ubuntu 11.04b2 over the weekend, it happily detected and mounted both drives via eSATA, so it's obviously not a hardware issue. If I pop the slot 1 HDD out and rescan the disks, it picks up the slot 2 HDD just fine. But when I try to use eSATA, only one drive shows up. It supports USB and eSATA and USB of course works fine, because it has built in port replication/multiplication. So I have the Thermaltake BlacX Duet, a dual HDD docking bay. More Thermaltake Blacx Windows 10 Driver videos. Thermaltake BlacX ST0005U External Hard Drive SATA Enclosure Docking Station. Windows 10 Forums Drivers and Hardware Unable to see External Hard Drive using USB. I chalked this up as either immature W10 drivers, W10 itself, or the MSI laptop I have is still immature itself. Mind you, if I plug in any kind of USB3.1 device I experience what the first poster has: it drops to 0 speed and the device turns off. Xfer speeds are superb both ways: 180mb/sec I can max out copying from the dock to the laptop and the other way. I have the same 2-bay BlacX 5G USB3.0 on the latest Windows 10 Pro + v.high end MSI laptop and while my xfers with the docking station (has 2x 8TB Seagates in it working fine) I get strange pauses and controller errors being noted in the W10 Pro event viewer from time to time (every 20 seconds it does this). Still no help from Thermaltake on this? Whats going on with the industry as this seems like a dire trend going on (and worse made considering W10 was officially released in late Jul'15 and yet all h/w vendors had more than enough time to prepare).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |