Retina Macbook Pro - USB 3.0 not working properly?

I also would like to run the firmaware upgrade of the Voyager Q by my VMWare Fusion virtual machine of Windos XP. Kuranuk, could you please be more specifc, step by step, on how to do the drivers instalation to make the drive recognizable? Thanks in advance!

I would also like some clear instructions as I have no experience with Windows and updating firmware is outside of my realm of experience in the PC world. Thanks in advance from me too.

Isn't it ironic they have a firmware update for just WIndow's/PC when OWC is a Mac primarily selling company?! Their website address is macsales! Lately i'm pretty dissapointed in their customer service too, don't think i'll be ordering from them much more

Someone explained to me that firmware updates are somehow more suited to a Windows kind of app. I dunno never had much problem with OWC their service communication has been consistent and I've always gotten to the problem in the end. I think it pays to try not get too emotional about tech issues. Do you have a better Mac oriented supplier in mind? If so please let me know. Cheers.

Hi Kuranuk, I have been travelling, and just returned, still not done the firmware upgrade. I don't have Virtual PC type app. just "Wine" and wondered if you could give any more details about your successful USB 3 firmware upgrade? Thanks in advance. STU

Well after using a rMBP since September, I bought a G-Tech 3.0 about a month ago or so, and it's really fast. Much faster than FW 800. So as maybe the newer units aren't haveing the problem, or maybe it depends on what drive you buy.

Oh yeah, anything recent will have the USB 3.0 firmware upgrade. I bought my Voyager Q's before the mid 2012 roll out of new MBP's & MB Air's. The upgrader app is an .exe app and I don't know anything much about running PC's or their aps. I wish OWC would write a Mac firmware updater! Anyone got any suggestions? 😮

This discussion is really old - there were some problems with USB 3.0 when the 2012 models first came out but those problems have been 'fixed' for quite awhile now, with firmware and software updates.

Haven't heard of anyone - recently - having USB 3.0 problems: I'd be surprised if they're still out there.

Clinton

clintonfrombirmingham wrote:

This discussion is really old - there were some problems with USB 3.0 when the 2012 models first came out but those problems have been 'fixed' for quite awhile now, with firmware and software updates.

Haven't heard of anyone - recently - having USB 3.0 problems: I'd be surprised if they're still out there.

Clinton

Yeah, I think I just said that, clintonfrombirmingham. But I'm struggling with the firmware update package that I got from OWC. It is a Windows .exe updater, and I couldn't Winewrap it to run on my MacBook Pro. So I was asking for suggestions. Your comment added nothing to the discussion, so why bother? I'm looking for "help" — not smug brush offs thanks.

If anyone has any suggestions, thanks in advance.

FYI: Here's the contents of the updater:

1.png

Content.dll

DeviceAccess.dll

DeviceManagement.dll

DriverInstaller_Isis_Core_Log.txt

DriverInstaller.exe

Drivers

i386

DPInst.xml

DpInst32.exe

PlxUsb.cat

PlxUsb.inf

PlxUsb.sys

FirmwareUpdater_Isis_Core_Log.txt

FirmwareUpdater.exe

FirmwareUpdaterSupport

Branding

Branding.xml

DefaultLogo.bmp

image_0525_3100.bmp

image_0525_3101.bmp

image_0525_3102.bmp

image_0525_3110.bmp

image_0525_3111.bmp

Product.ico

Firmware

SSI.bat

U3100_Firmware.pfw

U3100_Firmware.pfw.bak

U3100_Release_D120713_Voyager.pfw

U3100_Release_D120713.pfw

U3101_Firmware.pfw

U3102_Firmware.pfw

U3110_Firmware.pfw

U3110_Patch.pfp

U3111_Firmware.pfw

UpdateInfo.xml

Voyager.bat

U3100_Firmware.pfw

Flashes.xml

Storage.dll

Thumbs.db

Utils_ISIS.dll

XML.dll

So you're having problems installing an OWC firmware update for a USB 3.0 device? I didn't mean to sound smug at all and I apologize if I seemed to be so... but it's not really clear if you're having trouble with a USB 3.0 device or not.

Clinton

clintonfrombirmingham wrote:

So you're having problems installing an OWC firmware update for a USB 3.0 device?

Did you read the whole discussion? I was in on this discussion months ago. I contacted OWC first, found out about, chased up and finally received the USB 3.0 firmware updater. I then posted a link to it, since then I travelled overseas on a job, and now I'm back, and yes I am struggling with the PC aspects of the FW Updater (as I've mentioned a few times).

Yeah - I've been following this discussion for awhile now - I thought that your problem was solved, though. Sorry.

Have you contacted OWC again? I know that with my Crucial SSD firmware updates, I just download an .iso image, burn it to CD, and boot with it (the CD is actually named "WIndows") and apply the firmware update. The link you've given is to a zip file that says "32-bit XP only" so I don't really see how you're going to install it using a Mac (running Parallels and XP may do it - or not). If I were you, I'd contact OWC and explain that you need a MAC-oriented firmware update package. Even though you've already contacted OWC, I'd try again - surely this update isn't for XP users only? Or maybe it is...

Clinton

We do not have an OS X updater at this time. We rely upon the manufacturers of the chipsets for firmware updates to their chipsets and as such the OS specific variants as well. As of now they have only released an updater compatible with Windows.

Sincerely,

OWC Chris

Technical Customer Service Representative

Other World Computing, Inc. (OWC)

OWC.net, Inc.

Hi Kuranuk, I have followed your description as well as I can, I have VMWare Fusion running Windows XP 32-bit, but when I try to run the firmware updater, I get error messages. I have found the Device Manager folder, but I don't understand "compmgmt.msc" and how I get to manually install the drivers for the "Upgrade Device" bridge etc... Are you able to give me some clear steps? Much appreciate it. Cheers, STUART

I just registered so that I can offer thanks to STUPENDOUS! for the firmware update link. I could not find this on OWC's web site. I just got a new Macbook AIr, with USB3, and my Voyager Q would not work properly with it. Other USB3 devices were fine so long as the cable was not long. The firmware update fixed it. To make the update run as it is designed to run, do it on a machine running Windows XP natively. I didn't have one, and did it by trial and error using VirtualBox.

The USB device ID and serial number changes during the update process, rather like a USB modem can. This will confuse software such as VirtualBox (and VMware, I assume), since VirtualBox etc. will not claim the 'new' device until told to.

I used a Windows XP 32-bit VM running in VirtualBox to apply the update. Here is what I did - of course I'm working from memory here, since the update is now done, and I can't double-check everything. YMMV, don't blame me if yours goes wrong.

1. I attached my Voyager Q (with a spare disk in the slot, otherwise nothing happens) using USB2 on an older Macbook Pro, which does not have USB3.
2. I set VirtualBox to route the "OEM USB3-to-Sata bridge device" to the Windows XP VM, and started the VM.
3. After letting XP recognise and install the drive, I started the firmware updater, and it triggered the first USB device ID change. The 'new' device was not claimed by VirtualBox. The firmware updater timed out and failed.
4. Leaving the Voyager Q on so that the device ID did not change back yet, I shut Windows XP down, and set VirtualBox to route the new unrecognized USB device to the XP VM. It only showed the USB ID string as 'Unknown device 0525:8000 [FFFF]', no 'friendly' name. In theory, I should have been able to do this without closing the VM, but I didn't try.
5. Then I turned the Voyager Q off to return it to normal, and started Windows XP in the VM again.
6. I turned the Voyager Q back on again after XP had settled down, and restarted the firmware updater.
7. After the device ID change, the device was reattached to the VM, and XP came up with a 'new hardware found' dialog; I told it not to search but rather to use the driver in the i386 drivers folder that was included with the firmware updater (in 'USB 3 Voy Firmware update (xp 32-bit only)\Drivers\PlxUsb\i386')
8. The firmware updater had timed out again while I was doing this, so I turned the Voyager Q off, restarted Windows XP (again, this may not have been needed, but better safe than sorry), turned the Voyager Q on again, and restared the firmware updater.
9. The first stage of the firmware updater now worked, and the device ID changed back - but with a different serial number, so I had to tell VirtualBox to claim it again! I repeated steps 4, 5 and 6, except that this time it had the same USB3-toSata 'friendly name' as it had at first, but the serial number change was noticed by VirtualBox otherwise this step wouldn't have been needed.
10. This time the firmware updater said it had completed successfully!

Fortunately the updater is very resilient to failure, and did not brick the Voyager Q. This was a real danger, and as I said, it might happen to you if you try this. Don't blame me if so. Have fun!