U40 driver install in XP

firtha · Joined: 23 Dec 2003 Posts: 2 Location: Calgary, Canada

I received the USB ICD, and have (attempted to) install the USB driver on XP Home. All goes well, except the I get the message "Installation Failed".

The ICD seems to work fine even without the successful install, execpt that every time I attach the ICD to my PC, I get the 'Found new hardware', and the install dialog box again.

PCWH appears to work OK in all instances, so this is more of a pain than a show stopper, but I'd like to get the install to stop bugging me.

Anyone else seen this? Got a fix?

TIA...

wa822 · Joined: 17 Dec 2003 Posts: 4 Location: London UK

I also had a problem with the USB driver.
Luckily XP offers the facility to roll back to the last system restore point and try again. Restore points are automatically created at the start of installations. Just doing the install in a slightly different way can solve these problems. The dialogue boxes always make more sense second time around.
I'm sorry this is not very scientific, but it worked for me, and I did not have to reinstall the OS Smile

regards
_________________
Andrew White

firtha · Joined: 23 Dec 2003 Posts: 2 Location: Calgary, Canada

This is the weirdest thing... Since posting the original message, I bought and tried to install a Belkin USB to serial adaptor... with no success.

I tried the install of the U40 today... and it worked! So, armed with confidence, I tried the Belkin USB adaptor again (I was ready to take it back to the store...) AND IT WORKED!.

After that, XP found my scanner, which had disappeared when I tried to install the U40, and successfully reinstalled it.

The only thing I did was unplug my digital camera USB cable (there was no camera attached)

Weird? I guess the answer is: Keep trying! I have never had much success with USB... I guess I'm a magnet for trouble.

Thanks for your response, and to all who read my plea for help.

john cutler · Joined: 06 Sep 2003 Posts: 82 Location: Hot Tub, California

The only problem I've had is that when running my target while debugging, both the ICDS and the newer ICDU-40 take 100% of the CPU. After a short while, the fan on my laptop comes on. Unfortunately, this is also true of MPLAB using ICD2 under similar circumstances.

I know the host program is polling the ICD to monitor conditions while debugging, but is it really necessary to use 100% of the CPU's power while doing so?