I bought a URF to connect my Xino Basic Arduino to my PC, as I was advised.

When I try to install it, I get the Found New Hardware dialog, and point it to the unzipped driver file (usb_cdc_driver_cc1111.inf) but Windows says it was unable to locate a driver for this device.



Part of the driver .inf file says this:

;------------------------------------------------------------------------------
; 32-bit section for Windows 2000/2003/XP/Vista
;------------------------------------------------------------------------------

so I don't see any reason why it wouldn't install in Win2k.

Has anyone successfully used a URF with Windows 2000? It seems like it should work but I'm guessing no one's actually tested the supplied drivers with Win2k.

All the inf file does is tell Windows to use the standard (windows) CDC USB driver. It should work for Windows 2K but I doubt if it has been tested on that platform.

An interesting paragraph is here
www.obddiag.net/drivers.html

Yes. The fact that Windows 2000 says it can't find a driver for this device makes me wonder if the VID and PID values in the .inf actually match the one I've got, which has (c) 2012 IOT Research printed on it. The buginess is something I'll have to deal with if I actually get it to work at all.

I tried downloading USBView from www.ftdichip.com/Support/Utilities.htm to check the VID and PID but it doesn't work. It's supposed to support Windows 2000, but I just get an error saying it's not a valid Win32 application. I'm beginning to suspect a conspiracy to sell more copies of Windows 7 and 8

All URFs have the same VID/PID - this is 0x0451 and 0x16A6

Thanks for the information, CisecoDev. I took the driver from the link you gave and modified it by substituting the VID and PID you gave, just to see what would happen. Windows 2000 accepted it, and apart from having to tell it where to find usbser.sys, it installed the driver.

It didn't actually work, unfortunately; the Arduino IDE could see a COM port, and tried to upload a sketch, but I got an error at th end:

Binary sketch size: 1,128 bytes (of a 30,720 byte maximum)
avrdude: stk500_getsync(): not in sync: resp=0x00

Not too surprising since it wasn't a driver for the URF, but it makes me wonder why the official driver isn't accepted by Windows as being for the URF, when I can get it to accept that one just by changing the VID and PID to match.

(duplicate post)

Okay, my mistake on that last bit. After trying various other hacks of the .INF, and getting the same avrdude error, I looked up the error code and found this:

www.arduino.cc/cgi-bin/yabb2/YaBB.pl?num=1248528012/all

Yep, I'd left the Arduino IDE set to the wrong kind of board

Oh well. The last thing I tried works, and is the cleanest solution; I took the "Arduino UNO.inf" from the drivers folder in the Arduino software (as per the Getting Started w/ Arduino on Windows instructions), and substituted the VID and PID for the URF, then changed the strings to show the manufacturer as Ciseco / IOT Research.

I still had to tell Windows where to look for usbser.sys but it works fine I now have the Xino Basic board set as an Arduino Uno in the IDE.

Here's the modified file, in case anyone else has trouble with the official URF drivers:


I've still no clear idea what's wrong with the drivers, as supplied, but maybe the problem isn't just limited to Windows 2000? I wondered about the NTx86 references in the INF. I'm running Windows 2000 on an Athlon 1800+. Would that be identified as NTx86? The working INF just refers to "nt".