Because Vista 64 has increased driver security, I would have to reboot, press F8 to enter boot menu and select Disable Signed Driver Requirement because the usbhost driver is not digitally signed :( BUT the psp type b would install successfully and then it would work fine if ran during that session..but it will NEVER work booting straight into windows until now!
Since a signed driver must have a way to be tested during development some research on the windows sdk and driver sdk was done by me and all
But today i busted some donkey put on my thinking cap and abused google to find the answer!
So what do wee have to do?
First reboot press F8 to enter boot menu and select Disable Signed Driver Requirement
Now that wee are in the sandbox so to say wee can successfully create and install an unsigned driver, but then replace the file with a signed one.
First wee must tell windows wee are testing drivers.
bcdedit.exe /set TESTSIGNING ON
Prior to RTM, this had fixed the problem, but now that command is not as powerful and only works for one session when in Disable Signed Driver Mode.
Now that wee have done that, wee must create a certificate.
makecert.exe -$ individual -r -pe -ss "PSP Certificate Store" -n CN="PSP Driver" "PSP Driver.cer"
If that went well, lets install the certificate in the appropriate place
certmgr.exe /add "PSP Driver.cer" /s /r localMachine root
Now that the certificate is installed, lets tell our driver.sys files that that certificate is to be used
signtool.exe sign /v /s "PSP Certificate Store" /n "PSP Driver" libusb0.sys
signtool.exe sign /v /s "PSP Certificate Store" /n "PSP Driver" libusb0_x64.sys
As long as there is not an error wee can verify the link between driver file and certificate.
signtool.exe verify /pa /v libusb0.sys
signtool.exe verify /pa /v libusb0_x64.sys
|
WOOHOO..wee just signed a driver with a temporary certificate that will expire in 2034 or so :P
Now if you have already installed the usbhost drivers rename libusb0_x64.sys to libusb0.sys and overwrite the file in c:\windows\system32\drivers and reboot to test it out.
If you have never installed the USBhost PSP Type B driver then copy both the libusb0.sys and libusb0_x64.sys to the folder with the usbhost drivers and overwrite the old ones, connect your psp via usb, enable remotejoy/remotejoylite and tell windows that you want to choose the driver for this device and point to your usb drivers folder at this time. Test by starting remotejoylite.exe and see if you have a display!
Once it is all done you can reboot and try again in regular mode. If it works, pat your self on the back for following directions real well :D
If you fell you have screwed up and want to restart, Uninstall the PSP Type B while it is connected in device manager, delete the libusb0.sys from c:\windows\system32 and remove the PSP Certificate Store in your registry here HKEY_CURRENT_USER\Software\Microsoft\SystemCertificates
I have all the necesary windows sdk utilities packed up in a .rar with a simple batch file that does all of the certificate stuff for you that i will upload if anyone is interested and there is no bad juju from doing so.
Hollar back and let me know if you are using remotejoy and vista64
p.s. video capture is PERFECT and everything is SOOO much faster in remotejoylite 0.15 and vista 64bit!
http://www.mediafire.com/download.php?2uqignhm3ag
Download and extract that.
Make sure you reboot and press F8 then select DISABLE SIGNED DRIVER REQUIREMENT!
After reboot, double click 1 - Create and install certificate and modify sys file.bat and it will create a certificate, install it, and leave libusb0.sys and libus0_x64.sys.
If you have already installed and have remote joy working then just delete libusb0.sys and rename libusb0_x64.sys to libusb0.sys and copy that file to c:\windows\system32\drivers and overwrite the current.
If you havent installed the drivers, copy BOTH .sys files into Original usbhostfs_pc+drivers_x64 and replace. Then enable remotejoy on psp, and when asked for drivers point it to the above mentioned folder. Now test your remote joy. If it works, reboot and it should work in normal operating windows. :)