Go to Control Panel > System > Device Manager. Flightsticks, arcade joysticks and gamepads are treated the same.įull instructions for installing a gameport joystick in XP:įirst, make sure XP knows you have a gameport. XP has to be told what kind of joystick to expect at the gameport using the Game Controllers item in Control Panel. Windows XP will not automatically detect DB-15 gameport joysticks. The same is basically true for your DOS games, with the differences that a) DOS simply choses not to involve itself at all with the game port, and b) the games bring their own driver that is set up with reasonable defaults, and relies on the user having installed their gameport hardware correctly. This is the likely reason modern OSes will not by default support it, since a misconfigured or autoprobing driver could potentially cause a severe hardware crash (eg if some other legacy hardware uses some of the I/O resources that a multi-port gameport card would use). Actually, there seems to be no easy way even for a configured driver to ascertain whether it is reading from an installed game port or reading garbage data off the bus in its absence.
#USB VIBRATION JOYSTICK DRIVER WINDOWS XP PC#
Hence, the OS, if it supports the game port hardware at all (Post-XP Windows by default will not work with the standard PC implementation!), needs to be manually configured for the type and number of joysticks connected.Īlso, the legacy (standard) type of game port is non-autodetectable hardware in itself. The standard PC implementation of such a port (basically a bunch of 555 timers that are tuned by the variable resistors in the joystick) cannot even reliably detect if anything AT ALL is connected to it, a game port with nothing connected will just present nonsensical data to software.
The DA-15 Joystick port (BTW, not to be confused with the AUI ethernet connector, which is also a DA-15 with additional locking hardware!) has no standardized provision to detect what is connected to it.