JP1 Remotes

Posted: **Fri Feb 23, 2007 10:41 pm**

ElizabethD wrote:There seem to be two versions of driver .inf files, 2004 and 2005. 2005 has fixes like unlclemiltie mentioned, plus one more: how the service starts. M$ says PnP devices have to have value 3 (demand), not 2 (auto start) for .AddService which is in the 2004 file, but I think service startup mode is not relevant, since Nils doesn't even get to trigger it. Also unclemiltie is onto something about encryption, but I know nothing about it.
.

I only know of the 2004 version which sounds like what unclemiltie described.

I went through all the group and local polices and templates and changed a few just for the heck of it with no luck.

I have also change the unsigned driver option to each option. Ironically none of the options made a difference.

Just for the heck of it I also temporarily removed all the oem##.inf files

Posted: **Sat Feb 24, 2007 1:34 am**

Assuming from context all of this is about the delcom driver, the 2004 inf is paired with driver version 1.x.x (1.something) and the 2005 inf is paired with driver version 3.1.something. The 2004 driver doesn't work for me under Windows Vista, but the 2005 driver does (as long as I run IR with admin rights). Without admin rights both drivers give me a privileged operation error.

For some reason finally under Vista I am able to have both my JP1 USB cable and my JP1.2 cable VIA USB->Serial adapter plugged in at the same time and they both work (this didn't work for me under XP).

Posted: **Sat Feb 24, 2007 7:08 am**

The driver that I have is Version: 1.00.5001.6 ReleaseDate: 01/23/2004.

If there is really a 2005 version I would love to have it. The one I have is the latest on Delcoms site and going through this with them they did not offer a 2005 version. I even asked if the had a later or could update it.

Please post it or e-mail it to me.

Thanks

Posted: **Sat Feb 24, 2007 8:12 am**

I found the 2005 drivers. Thanks.

It would not install either so there is something weird going on with XP installer

If it helps anyone figure this out for me here is the install log entries for the attempt to find the driver. The only thing that is clear to me is that it is definitely finding the Delcom device.

Code: Select all

[2007/02/24 09:05:22 1672.3 Driver Install]
#-019 Searching for hardware ID(s): usb\vid_0fc5&pid_1222&rev_000<,usb\vid_0fc5&pid_1222
#-018 Searching for compatible ID(s): usb\class_00&subclass_00&prot_00,usb\class_00&subclass_00,usb\class_00
#-198 Command line processed: C:\WINDOWS\system32\services.exe
#-166 Device install function: DIF_SELECTBESTCOMPATDRV.
#W059 Selecting best compatible driver failed. Error 0xe0000228: There are no compatible drivers for this device.
#W157 Default installer failed. Error 0xe0000228: There are no compatible drivers for this device.
[2007/02/24 09:05:24 824.2]
#-199 Executing "C:\WINDOWS\system32\rundll32.exe" with command line: rundll32.exe newdev.dll,ClientSideInstall \\.\pipe\PNP_Device_Install_Pipe_0.{B93A5921-3BF3-4660-8D4D-35F0D21E7E9F}
#I060 Set selected driver.
#-019 Searching for hardware ID(s): usb\vid_0fc5&pid_1222&rev_000<,usb\vid_0fc5&pid_1222
#-018 Searching for compatible ID(s): usb\class_00&subclass_00&prot_00,usb\class_00&subclass_00,usb\class_00
#-166 Device install function: DIF_SELECTBESTCOMPATDRV.
#W059 Selecting best compatible driver failed. Error 0xe0000228: There are no compatible drivers for this device.
#W157 Default installer failed. Error 0xe0000228: There are no compatible drivers for this device.
#I060 Set selected driver.
#-019 Searching for hardware ID(s): usb\vid_0fc5&pid_1222&rev_000<,usb\vid_0fc5&pid_1222
#-018 Searching for compatible ID(s): usb\class_00&subclass_00&prot_00,usb\class_00&subclass_00,usb\class_00
#-019 Searching for hardware ID(s): usb\vid_0fc5&pid_1222&rev_000<,usb\vid_0fc5&pid_1222
#-018 Searching for compatible ID(s): usb\class_00&subclass_00&prot_00,usb\class_00&subclass_00,usb\class_00
#-166 Device install function: DIF_SELECTBESTCOMPATDRV.
#W059 Selecting best compatible driver failed. Error 0xe0000228: There are no compatible drivers for this device.
#W157 Default installer failed. Error 0xe0000228: There are no compatible drivers for this device.
#I060 Set selected driver.
#-166 Device install function: DIF_INSTALLDEVICE.
#I125 Installing NULL driver for "USB\VID_0FC5&PID_1222\6050".
#I121 Device install of "USB\VID_0FC5&PID_1222\6050" finished successfully.

Posted: **Sat Feb 24, 2007 12:18 pm**

Did you do the have disk thing with it? I found that the newer driver would not be found unless i forced it to try and install that one.

Posted: **Sat Feb 24, 2007 12:26 pm**

cywelchjr wrote:Did you do the have disk thing with it? I found that the newer driver would not be found unless i forced it to try and install that one.

Yes, I forced to look in a specific location rather than automatic with no luck.

Is there another way to force a driver to load?

Posted: **Sat Feb 24, 2007 12:31 pm**

Yes, tell it that you will choose from a list, then click on "have disk" and point to the inf file you want it to use. It was the ONLY way I was able to get the newer driver to install.

Posted: **Sat Feb 24, 2007 1:14 pm**

When I do that no matter what type of device I select and do the have disk all I get when I select the inf file is "The specified location does not contain information about your hardware".

Posted: **Sat Feb 24, 2007 1:21 pm**

Nils, sorry, I got the 2005 inf file from Delcom or diygadget site, can't remember which.
I just uploaded Microsoft API file, don't understand a word of it
https://www.hifi-remote.com/forums/dload ... le_id=4266
taken from
http://search.microsoft.com/results.asp ... s+device.+

The solution for somebody on similar thing
http://www.mcse.ms/message1258926.html
Application was re-writing Windows DevicePath but
had registry entry type as REG_SZ instead of REG_EXPAND_SZ.

Something about need for DEVICEPATH key ???
http://help.lockergnome.com/windows/fin ... 38690.html

Windows fights you doesn't it?

Posted: **Sat Feb 24, 2007 1:31 pm**

Nils, just unzip and run the .exe file. Make it narrow so you can see it. Then start the blasted installer again. FileMon monitors what files used -
https://www.hifi-remote.com/forums/dload ... le_id=4267
perhaps it'll tell you where it's going

Third button from the left - capture - stops the log
Then right click on file to see entire properties
4th from the left controls autoscroll.

Posted: **Sat Feb 24, 2007 1:52 pm**

ProcessMonitor will show all registry items used. Also unzip and just run .exe on the side and watch it
https://www.hifi-remote.com/forums/dload ... le_id=4268
Once again first figure out when and how to freeze the display. I hope it'll hint at something.

Posted: **Sat Feb 24, 2007 2:27 pm**

Interesting. I am beginning to think it may be a rundll32.exe problem but still need to read more entries. it is finding and opening the usbiods.inf file but never accessing the .sys file.

Posted: **Sat Feb 24, 2007 6:51 pm**

The only thing I see out of the ordinary is a BUFFER OVERFLOW every so often during the running of rundll32.exe and services.exe while it is trying to locate and install the driver.

I restored both exe's from i386 and it did not help

Posted: **Tue Feb 27, 2007 4:56 pm**

With the help of ElizabethD and Unclemiltie I got my USB driver working.

I was doing my best not to reinstall XP to solve the problem and gave up on making the .inf install work so I attacked building a Delcom.reg file to install all the registry entries needed to make it work. After running some process tracking (thanks Liz) to see what was going on and acquiring some registry entries from a working driver system (Thanks Bill), and stealing a co-workers system to create some more entries I got it to work.

I know this hits a few people once in a while so if anyone needs the reg file and the instructions please PM me and I will e-mail it.

I don't want to just post it since it takes a little care and engineering to make it work without killing your system. Messing with the registry can be kind of dangerous.

Posted: **Tue Feb 27, 2007 8:04 pm**

congrats!

now back to your real past-time, programming your remotes!

JP1 Remotes

USB Driver issues

Delcom USB Driver