Hi all,
I just updated my Retrode from 0.17g to 0.18d-beta using Flip, as I was having trouble dumping my Zero Wing (PAL) cart: the Retrode always detects it as 4Mbit, even though it's supposed to be an 8Mbit cart. Forcing the size detection didn't seem to work under 0.17g, but it did work under 0.18d-beta. Unfortunately, now the Retrode is generating USB driver errors in the Windows 7 event log every time I connect it.
I'm getting "Event ID 11, Source: Disk" errors that say:
"The driver detected a controller error on \Device\Harddisk3\DR5."
The DR# changes every time I connect the Retrode, and I get about 4 of these errors every time I plug in the Retrode, even though it seems to work fine. I tried uninstalling the driver and connecting the Retrode again, and while Windows still says that the driver was installed successfully, the error persists. Has anyone else come across such an error and know how to fix it? If not, I guess I'll start downgrading my firmware until I find the last version that doesn't generate the error anymore. Since I was previously on 0.17g, I guess I just need to try 0.18a and c before I roll back to my original firmware.
Thanks...
I also tried 0.18c, and I got the same error. I reverted to 0.17g after that, and now I can connect my Retrode again without getting errors. It's strange, but at least it works. My only guess would be that there's a new bug in the latest LUFA used in 0.18c and 0.18d, but that's merely speculation based on the changelog.
Strange; never heard about this kind of issue before. Have you tried making Windows forget the Retrode by deleting the respective entries from the registry (http://www.retrode.org/documentation/troubleshooting/)?
I'm not sure if it has a similar effect, but I used the "uninstall driver" from the Retrode properties menu before I switched firmware revisions. Uninstalling the driver caused the Retrode "disk" to disappear from the list of attached drives in My Computer.
The problem might also lie with whatever driver Windows thinks it needs to use the Retrode. When I connected the Retrode using the 0.18 branch, Windows said it was installing drivers, but when I connected the Retrode after downgrading to 0.17g, I didn't get an installation message, but the Retrode worked, anyway. I'm pretty sure when I first connected the Retrode after I got it (with 0.17g from the factory), Windows installed a driver for it, so perhaps the driver is different for 0.17g than it is for the 0.18 branch.
Strangely, XP doesn't seem to have a driver for the Retrode, despite it being a generic USB device. Windows 7 handled the Retrode automatically, but XP always opens the driver search wizard when I connect the Retrode.