..:: PCSX2 Forums ::..

@zoomHYPERIONzoom: can you post your ScpDriver.log and ScpService.log

@Scarlet.Crush many many thanks!

Your solution is the simplest and most transparent I have come across...and hopefully I can get it working so I can then exclaim it to be the most effective as well! Sheesh I will be glad to be done with that MiJ wierdness.

In any case ..I have finally managed to get your package installed and my Sixaxis controller successfully working via USB. Bluetooth expectedly does not work when I disconnect the cable (as my device ID is not amongst those listed) - Also, my bluetooth adapter is able to scan for and see other bluetooth devices (such as my phone)...so I guess the BT driver was not successfully installed (Also have host: disconnected in SCPMonitor).

I have attached my log files.

I have an integrated bluetooth device in my laptop with Device ID: USB\VID_0A5C&PID_21E1

Can you please add this ID? Is the absence of this device ID in your .inf and .cat files the only thing preventing installation of the bluetooth drivers?

---

@Scarlet.Crush

Oh!...also...follow up question..does your solution also work for the PS3 keypad add-on as well? A PS3 controller with the keypad add-on, both connected via bluetooth and utilized with JoyToKey and perhaps AutoHotKey would make for an outstanding HTPC/Gaming rig controller.

(02-15-2013, 09:51 PM)Donty Wrote: [ -> ]I have attached my log files.

I omitted the SCPDriver log file..attached.

(02-15-2013, 09:51 PM)Donty Wrote: [ -> ]@Scarlet.Crush many many thanks!

Your solution is the simplest and most transparent I have come across...and hopefully I can get it working so I can then exclaim it to be the most effective as well! Sheesh I will be glad to be done with that MiJ wierdness.

In any case ..I have finally managed to get your package installed and my Sixaxis controller successfully working via USB. Bluetooth expectedly does not work when I disconnect the cable (as my device ID is not amongst those listed) - Also, my bluetooth adapter is able to scan for and see other bluetooth devices (such as my phone)...so I guess the BT driver was not successfully installed (Also have host: disconnected in SCPMonitor).

I have attached my log files.

I have an integrated bluetooth device in my laptop with Device ID: USB\VID_0A5C&PID_21E1

Can you please add this ID? Is the absence of this device ID in your .inf and .cat files the only thing preventing installation of the bluetooth drivers?

---

@Scarlet.Crush

Oh!...also...follow up question..does your solution also work for the PS3 keypad add-on as well? A PS3 controller with the keypad add-on, both connected via bluetooth and utilized with JoyToKey and perhaps AutoHotKey would make for an outstanding HTPC/Gaming rig controller.

Yeah, the missing ID in the inf is the only thing preventing it from installing. If you're savvy enough, you can add your ID alongside the others in the proper .inf file and try reinstalling. The correct inf is the one with Bth in the name.

(02-15-2013, 01:56 PM)zoomHYPERIONzoom Wrote: [ -> ]Interesting, but the bluetooth still won't work with my official DS3 controller.

Did you try with the updated .inf file that Scarlet.Crush posted? It should show up as "Bluetooth DS3 Device" near the bottom in the device manager if the driver has been installed properly.

Also, try to find the Hardware Id of the knockoff controller. I'd imagine if it tries to mimic an official DS3, there might be a chance the driver will work with it.

@Donty: added your hardware id, see Post #301

The drivers don't currently support the PS3 keypad, sorry.

(02-15-2013, 10:25 PM)Ashnal Wrote: [ -> ]Yeah, the missing ID in the inf is the only thing preventing it from installing. If you're savvy enough, you can add your ID alongside the others in the proper .inf file and try reinstalling. The correct inf is the one with Bth in the name.

Didn't you end up with a BSOD issue after attempting to only change the .inf file? There is also a .cat file that Scarlet has been updating as well...I believe it is a catalog file that is utilized for the trust dialog boxes during SC's driver install..i'm guessing that this file needs to be re-signed/encrypted whenever one of the files it catalogs are changed??

@Donty: Yes, the .cat file is created from the .inf file and contains hashes for the drivers in the amd64 and i386 folders. The .cat file is then signed with the certificate which is displayed during installation.

The drivers in the amd64 and i386 folders are also signed, ScpVBus.sys is signed with my certificate, the other dlls are signed by Microsoft (redistributables from WinDDK).

Altering the .inf file manually will not cause a BSOD or stop the drivers from working properly. The BSOD on shutdown Ashnal is seeing is most likely a non-standard / proprietry command that his specific on-board dongle requires to shutdown properly.

If your dongle installed without the need for custom drivers and works correctly with the Windows Bluetooth stack before installing the SCP drivers this won't happen.

I would like to keep track of which Dongles (hardware ids) work correctly and maintain the .inf file so that it is not required to be modified manually, and people can trust that the drivers have not been modified. All the binaries supplied in the download are signed as well.

(02-16-2013, 12:17 AM)Scarlet.Crush Wrote: [ -> ]I would like to keep track of which Dongles (hardware ids) work correctly and maintain the .inf file so that it is not required to be modified manually, and people can trust that the drivers have not been modified. All the binaries supplied in the download are signed as well.

Worked flawlessly with my integrated BT. This is by far the best solution for getting the PS3 controllers playing nicely with windows.

I especially like the disconnect macro (L1+L2+PS = disconnect) and pressing PS again seamlessly reconnects the controller.

Thanks for taking the time and effort to share you work with us SC, you've no doubt made a bunch of people happy and grateful.

I have a feeling that your solution is going to become mighty popular once its ready for wide release.

Outstanding.

(02-16-2013, 12:17 AM)Scarlet.Crush Wrote: [ -> ]@Donty: Yes, the .cat file is created from the .inf file and contains hashes for the drivers in the amd64 and i386 folders. The .cat file is then signed with the certificate which is displayed during installation.

The drivers in the amd64 and i386 folders are also signed, ScpVBus.sys is signed with my certificate, the other dlls are signed by Microsoft (redistributables from WinDDK).

Altering the .inf file manually will not cause a BSOD or stop the drivers from working properly. The BSOD on shutdown Ashnal is seeing is most likely a non-standard / proprietry command that his specific on-board dongle requires to shutdown properly.

If your dongle installed without the need for custom drivers and works correctly with the Windows Bluetooth stack before installing the SCP drivers this won't happen.

I would like to keep track of which Dongles (hardware ids) work correctly and maintain the .inf file so that it is not required to be modified manually, and people can trust that the drivers have not been modified. All the binaries supplied in the download are signed as well.

It *might* be. I will say that for the longest while I had the MIJ drivers installed on the internal dongle and never had this bluescreen issue, I didn't have it when no driver was installed for them at all as well. I'll have to see if it still persists if I disable the device before shutdown.

(02-15-2013, 02:49 PM)Scarlet.Crush Wrote: [ -> ]@zoomHYPERIONzoom: can you post your ScpDriver.log and ScpService.log

Thank you for being so accommodating, Scarlet. I reinstalled the update but still not working with my BT.

I didn't use an "elevated command prompt" to make the C:\Program Files\Scarlet.Crush Productions\ folder. Does it matter?

I'm using my official DS3 controller. See below for the requested logs:

ScpDriver.log:

SCP Bluetooth Driver Installer 0.7.0.96 [2/17/2013 7:12:03 PM]

Detected - Microsoft Windows 7 Home Premium Service Pack 1 (6.1.7601.65536 AMD64)
Selected WIN7 configuration.

INFO - ENTER: DriverPackageInstallW
INFO - Looking for Model Section [SCProductions.NTamd64]...
INFO - Installing INF file 'C:\Program Files\Scarlet.Crush Productions\bin\System\ScpVBus.inf' (Plug and Play).
INFO - Looking for Model Section [SCProductions.NTamd64]...
INFO - Installing devices with Id "root\ScpVBus" using INF "C:\Windows\System32\DriverStore\FileRepository\scpvbus.inf_amd64_neutral_a38dc2f185de5e56\scpvbus.inf".
INFO - Will force install because driver is not better and force flag is set.
INFO - ENTER UpdateDriverForPlugAndPlayDevices...
SUCCESS - RETURN UpdateDriverForPlugAndPlayDevices.
INFO - Installation was successful.
SUCCESS - Install completed
INFO - RETURN: DriverPackageInstallW (0x0)
INFO - ENTER: DriverPackagePreinstallW
SUCCESS - .\System\BthWinUsb.inf is preinstalled.
INFO - RETURN: DriverPackagePreinstallW (0x0)
INFO - ENTER: DriverPackagePreinstallW
SUCCESS - .\System\Ds3WinUsb.inf is preinstalled.
INFO - RETURN: DriverPackagePreinstallW (0x0)
INFO - SCP DS3 Service Started.

Pre-Install Succeeded.

-- Pre-Install Summary --
SCP DS3 Service
Bus Driver
DS3 USB Driver
Bluetooth Driver

INFO - ENTER: DriverPackageInstallW
INFO - Looking for Model Section [SCProductions.NTamd64]...
INFO - Installing INF file 'C:\Program Files\Scarlet.Crush Productions\bin\System\ScpVBus.inf' (Plug and Play).
INFO - Looking for Model Section [SCProductions.NTamd64]...
INFO - Installing devices with Id "root\ScpVBus" using INF "C:\Windows\System32\DriverStore\FileRepository\scpvbus.inf_amd64_neutral_a38dc2f185de5e56\scpvbus.inf".
INFO - Will force install because driver is not better and force flag is set.
INFO - ENTER UpdateDriverForPlugAndPlayDevices...
SUCCESS - RETURN UpdateDriverForPlugAndPlayDevices.
INFO - Installation was successful.
SUCCESS - Install completed
INFO - RETURN: DriverPackageInstallW (0x0)
INFO - ENTER: DriverPackageInstallW
INFO - Looking for Model Section [SCProductions.NTamd64]...
INFO - No matching devices found in INF "C:\Program Files\Scarlet.Crush Productions\bin\System\BthWinUsb.inf" on the Machine.
INFO - RETURN: DriverPackageInstallW (0xE000020B)
INFO - ENTER: DriverPackageInstallW
INFO - Looking for Model Section [SCProductions.NTamd64]...
INFO - Installing INF file 'C:\Program Files\Scarlet.Crush Productions\bin\System\Ds3WinUsb.inf' (Plug and Play).
INFO - Looking for Model Section [SCProductions.NTamd64]...
INFO - Installing devices with Id "USB\VID_054C&PID_0268&REV_0100" using INF "C:\Windows\System32\DriverStore\FileRepository\ds3winusb.inf_amd64_neutral_f7204b7a132528eb\ds3winusb.inf".
INFO - ENTER UpdateDriverForPlugAndPlayDevices...
SUCCESS - RETURN UpdateDriverForPlugAndPlayDevices.
INFO - Installation was successful.
INFO - Phantom Device with Hardware/Compatible Id 'USB\VID_054C&PID_0268&REV_0100' already has 'C:\Windows\System32\DriverStore\FileRepository\ds3winusb.inf_amd64_neutral_f7204b7a132528eb\ds3winusb.inf' installed on it.
SUCCESS - Install completed
INFO - RETURN: DriverPackageInstallW (0x0)

Install Succeeded. [Reboot Required]

-- Install Summary --
Bus Driver
DS3 USB Driver

ScpService.log:

2/17/2013 7:30:54 PM.363 ++ C:\Program Files\Scarlet.Crush Productions\bin\ScpService.exe 0.7.0.96
2/17/2013 7:30:54 PM.379 ++ C:\Program Files\Scarlet.Crush Productions\bin\ScpControl.dll 0.7.0.96
2/17/2013 7:30:57 PM.848 ++ Microsoft Windows 7 Home Premium Service Pack 1 (6.1.7601.65536 AMD64)
2/17/2013 7:30:58 PM.248 -- USB Device : HID_Worker_Thread Starting
2/17/2013 7:30:58 PM.258 -- Controller : UDP_Worker_Thread Starting
2/17/2013 7:40:17 PM.278 -- Received : Status Request [127.0.0.1:49158]