Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
If your 3rd party Wired Xbox controller is not being fully detected by windows and you have tried the drivers etc. and still no working result. Then the following may help.
1: * Download the Microsoft Xbox Accessories Driver from Microsoft.
* Download and Install WinZip.
2: * Unpack the Microsoft Xbox Accessories Pack Execution File to a temporary Location Using WinZip (Should be able to right click on the file and click extract to…)
3: * Now Open Device manager (Right Click on Computer in Start Menu and Click Manage, Device manager will be on the left under System Tools)
4: * Now Plug in your control and wait for it to appear in device manager (normally under the Universal Serial Bus Controllers, Mind you it might be under human Interface devices)
* Right Click on the control and click Properties and click the Details Tab.
* In the properties dropdown box select Hardware ids.
5: * Now Two sets of numbers would appear we are after the set that does not contain the REV, but if that is the only one you have it should be fine to select it.
* Once you click on the appropriate id copy the number to clip board (Hold down the CTRL button then tap the C button while doing so.)
6: * Now go to the folder where you unpacked the Microsoft Accessories Pack And follow this path “Xbox360\setup64\files\driver\win7\” now setup64 might be setup86 depending on your system setup and there is a choice between operating systems either vista or win 7 so pick the appropriate folder.
7: * Now this is the driver path and you should see a file called xusb21.inf open this file with notepad
* Now you should see somewhere near the top of this document “Supports the following Devices” and under that heading Wired common controller and next to it a hardware id.
We want to search this entire file for that id and replace it with the one we copied from our control.
* Click Edit in the Menu and go down and click replace, Type in the Hardware id next to Wired Common Controller in the Find what box it should start with USB\VID.
* In the Replace with box Hold CTRL and tap P this should paste the hardware ID that we copied from our control.
* Once you have entered these details click Replace all, once done close and save the document.
8: * Now go back to the properties of your control from device manager
* In the Driver Tab Click update Driver, Click Browse My Computer for Driver Software
* In the Search for Driver Software in This location Enter the path where the xusb21.inf file is then click next.
9: The Driver should now install with no problems, what we did by changing the ids was tell windows that this software is for our hardware device and to use it.
You don’t create a new document your modifying the original document 'xusb21.inf' if notepad is not letting you save it then it would be a user permissions problem. So check the file properties and make sure the read-only attribute is not on, and open the document 'xusb21.inf' as administrator that might help also. But i stress you’re not create a new or copy of the file 'xusb21.inf' you’re just modifying the original file.
Well did you try the common fixups (uninstall drivers/reinstall drivers, cheak game control settings) And is it only with hotline miami or all games? if it's only hotline miami and you've tried the common fixups then i can only suggest using xpadder software to emulate keyboard and mouse inputs when you use your control.
and such
Just a recap i mentioned the wrong file name it dose not end in .ini it's .inf my bad it was mentioned in another comment just double check to see if that was the problem. otherwise it could be the operating system your using or the software to open the file. I only say this because it sounds like your opening a binary file. The xusb21.inf file should be plan text when displayed in windows notepad. (This is my experiance when using english oriantaed language settings in a 64bit windows 7 environment).
So just double cheack to see if something your running or doing differs and let us know maybe someone has had the problem and discovered it's answer.