Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - skyhawk71

Pages: [1]
1
I see. I should probably try messing around with it again to see if I could get it working. If push comes to shove, I might have to get my WinXP machine up and running again.

EDIT: As it turns out, I did the workaround incorrectly. I had accidentally created a sub-folder inside the root folder that was supposed to be made in regedit. The workaround now works.

2
This possible solution was posted in another thread:
Hi!

I had this problem too, looks like it is a common problem not limited to the retrode.
Following the instructions there brought me f├║rther, problem is described there:
 
http://blogs.msdn.com/b/usbcoreblog/archive/2013/11/26/why-does-my-usb-device-work-on-windows-8-0-but-fail-on-windows-8-1-with-code-43.aspx, go straight to the Workaround! You can search for the following sentence: "To apply the workaround for a specific device, add a REG_DWORD value named SkipBOSDescriptorQuery that"

(Though I am not done with flashing yet, at least no usb error and usb connection can be opened.)

edit: Flashing is now working.
This workarround worked for me. I was able to enter DFU mode and install drivers but Flip always threw an error on connecting. I suggest adding this piece of information to firmware update instructions if it is not too much of a hassle.

Using Win10 pro x64 in case that ring any bells.

Regards.

How did you find the hex and binary codes for the USB Device Descriptor? I tried the workaround a couple days ago but couldn't get it to work. I feel like I did the workaround wrong.

Pages: [1]