Driver for USB interface from filebug.com?

Forum for the discussion of JP1 Interfaces, hardware hacks, etc.

Moderator: Moderators

Post Reply
todd_i
Posts: 34
Joined: Wed Sep 24, 2003 12:43 pm
Location: West Michigan

Driver for USB interface from filebug.com?

Post by todd_i »

I bought a usb interface from filebug.com a little over a year ago. I haven't used it in several months, but when I tried tonight I found that the interface/driver was not correctly installed.

I tried to go to the filebug.com site and download the proper driver files, but I only get an error message when I go there (some junk about accessing the site by IP address).

Is the driver for that interface available for download anywhere?
underquark
Expert
Posts: 874
Joined: Mon Jun 20, 2005 4:58 am
Location: UK

Post by underquark »

Since the cables are similar (I assume), does the driver from this site work? They also sell cables and kits and have good instructions.

http://www.diygadget.com/download.php
The Robman
Site Owner
Posts: 21886
Joined: Fri Aug 01, 2003 9:37 am
Location: Chicago, IL
Contact:

Post by The Robman »

Tom (at Filebug) has dropped out of the JP1 business and has let his domain name expire.
Rob
www.hifi-remote.com
Please don't PM me with remote questions, post them in the forums so all the experts can help!
todd_i
Posts: 34
Joined: Wed Sep 24, 2003 12:43 pm
Location: West Michigan

Post by todd_i »

I tried the driver from diygadget.com. But, I still get an error saying "Windows was unable to locate a driver for this device."

Does anyone around here have a copy of the older driver?
whompus
Posts: 540
Joined: Wed Apr 27, 2005 1:43 am

Post by whompus »

You will get that error if you are letting windows do an automatic install for the drivers.

You will need to select the option to search for the driver yourself, then point windows to wherever you have unzip the driver to. You will get an error that say something about not passing windows compatibility just click continue anyway.
todd_i
Posts: 34
Joined: Wed Sep 24, 2003 12:43 pm
Location: West Michigan

Post by todd_i »

I got that error when selecting the location manually.

When I hook it to my PowerBook (running MacOS X 10.4.3) I get some more info:

Composite device: "USB IO Controller"
Device vendor/product ID: 0x0FC5 / 0x1222
Device version number: 0x0009
Manufacturer String: "Delcom Engineering"
Serial Number String: "3148"
whompus
Posts: 540
Joined: Wed Apr 27, 2005 1:43 am

Post by whompus »

From looking at the info your power book gives you about it. Then looking at the info in the driver. I see this string in the driver.

[Delcom]
%String2%=USBIODS.Dev,USB\VID_0FC5&PID_1222.

That says you have basicly the same cable as diygadgets.

If you just plug the cable to the remote and then to the usb on the windows computer do you get a new hardware found prompt?

If you do and can not install the driver you may need to remove a bad driver that is present on the system. To do this. Go to the windows/inf folder and delete usbiods.inf (only that file if windows98 or me) look for 2 more files that windows2000 or xp made. One will be called oem#.inf and the other will be oem#.pnf. The # represents a number that will not be the same on other systems. In my case the # is 15 in yours it will most likely be another number. To tell which are the right ones open the oem#.inf in notepad and at the top of the inf it will say Installation inf for the Delcom USB IO Driver. After deleting them reboot the computer then plug the cable into the remote then into the usb connector on the computer. It should install then. You will still want to not let windows do it automatic.
todd_i
Posts: 34
Joined: Wed Sep 24, 2003 12:43 pm
Location: West Michigan

Post by todd_i »

Thanks for the tips, whompus. I located the usbiods files, and oem* files with the Delcom information (oem8, in my case), and removed them. Unfortunately, that still didn't get it to recognize the drivers as valid for my device.

After a lot of googling, and lots of frustration (incuding a windows BSOD on one driver install attempt), I finally got it to load. Some search results pointed to usb.inf and usb.pnf being involved. I deleted them, and the behavior changed (but still didn't work). I deleted just the pnf file, and it still didn't work.

Then, I dug out my Win2K install CD, and got the original usb.in_ file, expanded it (expand usb.in_ usb.inf) and plugged that file in. Finally, it took the driver, and IR was able to communicate with the remote! (I'm really not a fan of Windows at this point... I guess experiences like this is why I'm primarily a Linux and MacOS user. )


So, at the end of this all, I can now fully control my MythTV DVR, using the FusionHDTV IR receiver, with my URC-6131 remote.
whompus
Posts: 540
Joined: Wed Apr 27, 2005 1:43 am

Post by whompus »

Your welcome. Glade to hear you got it sorted.

For others that run into problems with the usb cable this thread may be of use.

I think the driver is the basic same as it has been for like 7 years or so.
todd_i
Posts: 34
Joined: Wed Sep 24, 2003 12:43 pm
Location: West Michigan

Post by todd_i »

One more note, to aid in the searchability.. Another windows error message I got was the following:

The installation failed because a function driver was not specified for this device instance


I think this was related to whatever was wrong / corrupted in the usb.inf and usb.pnf files. Once I deleted the PNF file, and replaced usb.inf with the original, this error went away & the driver installed.

Files deleted: oem?.inf, oem?.pnf, usb.pnf, usbiods.inf, usbiods.pnf, and usbiods.sys (from /winnt/system32/)

Files replaced: usb.inf (extracted from original win2k media with the command "extract usb.in_ usb.inf").
Post Reply