We recently set up Xbox Media Center (XBMC) on the computer that’s attached to the TV. XBMC actually has nothing to do with xbox – it was a homebrew media center application for the original xbox that has since been ported to Windows/Linux/Mac/iOS.
We’re pretty close to what we feel is the “perfect” setup, but getting here was a headache and a half so I’m putting up a series of posts documenting our journey.
Part 1: Hello Xbox 360 Wireless Gaming Receiver
Part 2: Getting XBMC to work with our Xbox 360 Wireless Controller
Hello Xbox 360 Wireless Gaming Receiver
We’re currently using a wireless keyboard/mouse combo with our media PC, which is clunky and sort of a pain to use. I started looking into media center remotes. We also have a collection of wireless 360 controllers, and only very rarely use all four at once. And so my mission began.
Microsoft did at one point make a wireless 360 controller receiver for the PC, a little white dongle that plugs in to a USB port. Unfortunately, they discontinued it some time ago. You can still find the receiver bundled with a controller some places, but I had a hard time finding an OEM standalone receiver.
Fortunately, the Chinese knock-offs on eBay are still readily available. I got one for $13 including shipping, it’s a little white wireless dongle with a USB cable. Unsurprisingly, it did not include a driver disk. Equally unsurprisingly, Windows had no idea what it was when we plugged it in.
We downloaded the official Microsoft drivers for the official dongle. You can find them here: http://www.microsoft.com/hardware/en-us/downloads , click under the gaming heading.
Our media PC is running Windows XP. Everyone else seemed to have a perfectly fine time installing the drivers by hand. I guess we’re just unlucky, but the damned thing just wouldn’t install.
Turns out, we had the same problem this guy had: the dongle wasn’t identifying itself correctly, and thus Windows didn’t recognize that it belonged to the driver.
The fix involves editing the driver’s .ini file, which sounds a lot scarier than it is. Here are the steps I took:
Step 1: Find your errant dongle in the hardware manager.
- Go to your Control Panel
- Click on Hardware and Sound
- Click on Device Manager under Devices and Printers
- Scroll down the list to Other devices
- Double-click the Unknown device. If you have multiple unknown devices, you may need to use the process of elimination to figure out which one it is.
Step 2: Find out your device’s PID
- Click on the Details tab
- Look for something like this USB\VID_045E&PID_0291&REV_0107
- The bit you’re looking for is PID_0291, or whatever number is in the place of 0291
- If the number you see is 0719, you have a different problem than I did. Sorry.
Step 3: Edit the driver .ini file to reflect the actual PID
- Figure out where the driver installed itself (probably somewhere within c:/program files) and open that folder
- Open up Xusb21.inf in Notepad or your favorite text editor
- Find and replace any instances of ‘Pid_0719’ with ‘Pid_0291’ or whatever your device’s number is
- Save the file
Now if you’re lucky, you can run through the update driver dialog, point it at the folder containing xusb21.ini, and Windows will recognize the device as a Wireless Xbox 360 Receiver. Hooray! You are now halfway to tv-controller bliss.
On to the next part, getting the stupid thing to work with XBMC.
Filed under: Hacking