Skip to content
This repository has been archived by the owner on Dec 10, 2024. It is now read-only.

ScpServer installs on wrong USB interface number #84

Closed
fdavison opened this issue Dec 12, 2015 · 4 comments
Closed

ScpServer installs on wrong USB interface number #84

fdavison opened this issue Dec 12, 2015 · 4 comments
Labels

Comments

@fdavison
Copy link

ScpServer is installing on wrong USB Interface on QuadStick.

The QuadStick has four USB interfaces:
Interface 0: GamePad
Interface 1: Mouse
Interface 2: Keyboard
Interface 3: Flash Drive

All four interfaces are showing up in the Dual Shock 3 controllers list in the DriverInstaller. Selecting interface 0 and running the installer results in a different interface showing up under libusbK in the Device Manager. (In this latest run, interface 2) The interface number is not always the same with each test. In joy.cpl, the QuadStick still shows up and is functional, the XBox 360 controller is not.

The wrong interface shows up in the Ds3Controller_.....inf file:

DeviceID = "VID_16D0&PID_092B&MI_02"

so the mistake seems to be happening before that file is generated.

Logs, etc: https://www.googledrive.com/host/0B7MVckMP_1T0U2JNWG5aTE5odkU

@Jan200101
Copy link

I think that might be happening because of the naming. Interface 0 is named Quad Stick in the Installer and in the Device manager Interface 2 is too called Quad Sticks.
Try installing it on all until you get the right one and reinstall the other ones then until it gets fixed

@nefarius
Copy link
Owner

Might have identified the problem, please test and provide feedback on this release.

@nefarius nefarius added the bug label Dec 12, 2015
@fdavison
Copy link
Author

Now the correct interface 0 is displayed, and the QuadStick properly disappears from the Joy.cpl list, but there is an exception being thrown when starting the service. If I unplug the quadstick, I can start the service, but when I plug the quadstick back in, an error message pops up.

Logs: https://www.googledrive.com/host/0B7MVckMP_1T0V2E3eU9VM2trcE0/

@fdavison
Copy link
Author

It appears to be installing on the correct Interface number. I will close this issue, however I'm still having trouble with the service throwing an exception and stopping whenever the quadstick is plugged in.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

3 participants