Help! Me too...
I updated the software included with the PicoScope3206 from what was included on the CD 5.10 to 5.13 from the web, and now I get the same error message no matter what I do. I had it working after a long struggle with the USB2.0 on my machine under Rev 5.10. I was blaming it on something else since this is a new computer, but now I am thinking the PicoScope is causing my downgrade to USB1.1 without detecting 2.0 capability.
I have had a lot of trouble with the PicoScope downgrading my entire USB to 1.1, and leaving it there. This has been forcing me to install the motherboard USB drivers and re-install them over and over to get this thing functional. I love PicoScope when it decides to run.
Please help, or at least force the darned thing to stay in USB2.0 somehow. It is confusing my poor system and causing me headaches.
Ok, now I see what you are talking about when it tests for USB2.0; once the driver is installed, I get the error for "Device can run faster" windows message (I forget the wording) meaning USB hun is in 1.1 mode, but then I get the disconnect/reconnect beeps, and then it is up at 2.0 speeds. I guess this is a result of me getting my USB drivers working properly, but...
I only have it working again under the older 5.10, but cannot get it working under the newer 5.13. For now I will stick to the 5.10 to see if this gets fixed or there is another solution that someone can hopefully suggest.
BTW this is my system:
Lots of HD space
nForce4 chip set
DFI LanPartyUT nF4 Ultra-D motherboard.
About 6 devices on the USB, all 2.0 compliant.
Yeah, I play a few games on this box too
BTW Does using the external power supply play any role in the USB not initializing correctly? Perhaps not allowing a power-cycle?