1) I have tried every damn configuration available such as bcdedit edits to that "dseo13b.exe" program and followed every instruction to a T and cannot get windows 7 64bit to automatically allow unsigned drivers such as those provided to use my ps3 controller.
Tried this: http://www.passsy.de/2009/12/26/ps3-con ... essing-f8/
Tried this: http://www.ngohq.com/home.php?page=File ... _cat_id=34

I will save everyone the time and say it is all bullshit, nothing works but F8.



2) I almost thought I bricked my PS3 controller using this because for some odd reason, my controller would no longer connect or scan for bluetooth connections. I would press the PS button, and all the lights would come on. I would press the button again, all the lights would go off. If I held the button, the controller would blink like it would when it was scanning (but it was not scanning). Luckily there was a reset button the controller which fixed this problem.

3) I followed all instructions many times to a T and am having issues connecting over bluetooth. I have V2.0 EDR bluetooth dongles which I ordered off ebay, I have connected my LG phone to it prior to using this software for my PS3 controller to confirm the dongles work.
When I plug the controller in via USB, everything is perfectly fine. All controller inputs work, vibration works, the motion sensors work, etc.
When I click "Pairing", two dialogues pop up "Dualshock 3" which I click "OK", then "bluetooth dongle" which I click "OK" again.
While my controller is plugged in, the leds light up in order from 1-4 and they keep repeating that pattern. Once I unplug my controller from its usb cord after pairing, the controllers LED position will freeze. For example, say if I unplug it while it is illuminating LED 1 & 2 (in its cyclical pattern of 1-4), it will leave LED's 1 & 2 illuminated and render the controller useless until I hold the PS button for about 10 seconds to turn off the controller.
Once I push the PS, all of the LEDs flash at the same time like it is scanning to connect, the problem is.... it never connects. It will keep flashing for 10 minutes or more(maybe?) if I let it try.
Anyway to fix this?

I am having a similar issue. I disabled driver signing via bcdedit, back when version .200 was out. Now with the latest drivers it doesnt work any more. Though i can still load the driver via f8 on boot. I'm not sure if its the driver or microsoft. I know microsoft sees driver signing diabling as huge security risk, and am wondering if they did an update to disable it completely. Does any one have any insight on this? Maybe an easy way to sign the driver or updated instructions on how to permanently disable driver signing, as the testmode on and ddisable_integrity_checks via bcdedit no longer works.

If you have a WIDCOMM-Licensed Adapter, I have a theory in development, right here:
http://www.motioninjoy.com/forums/viewt ... lit=#p1272

In terms of the driver signature:
I can't override it either on Win7 x64 Pro... when I try something like that, Windows accuses me to have stolen software, which I have not.



Yeah right.
All they see is that huge hole in their pockets and a great opportunity to control who may and who mustn't release new products.

I figured out my driver signing issues. They happened after i installed the latest drivers, without everyhing connected to the pc. I simply did a complete unitstall and reinstall of the drivers, with a reboot in between making sure all the products were connected at the time of install, and I also turned off driver signing rebooted and turned it back on. I did the driver signing reboot before i did the drivers.