About signed drivers...

A lot of the problems/issues around PPJoy have centred around driver signing (PPJoy uses test signing certificates which in turn requires Windows to be in Test Mode).

So why not simply sign PPJoy with the proper "real" certificates? Simple answer - they cost a lot of money: see http://www.verisign.com/code-signing/content-signing-certificates/microsoft-authenticode/index.html. $500 per year is downright nasty.

If enough people chip in with donations I will release a properly signed version of PPJoy, possibly as "PPJoyPro". I've been toying with the idea of a non-free PPJoyPro with some extra features (suggestions?)

Unfortunately PayPal does not allow South Africans to receive money - only send money through PayPal. Which means I need to find another way to set up a donate button or similar :-(

And comments/ideas?

New test release...

Hi all - not getting around to do a complete set of tests on the new installer (the driver code is still the same). So here it is if you want to try it:

http://drop.io/ppjoy0846testrelease

This installer will properly check for a 64 bit OS and enable test mode. Note: the drivers are still only test signed and requires the OS to be in test mode. This installer just makes the process a lot easier.

Another one bites the dust

I guess it had to happen... After transitioning my build environment to the Windows 7 DDK PPJoy will no longer support Windows 2000. The installer will refuse to install on Win2K. A word of warning: do not try to manually install the drivers on Win2K - this will cause a nasty bluescreen on reboot.

[Anybody wanting to use PPJoy on Windows 98 or 2000 should use version 0.83 or earlier.]

On a related note: I've now finished a test version of the new installer (which can automatically enable test mode) - now to test it on Win2K, XP, Vista, etc with different configurations to ensure it "does the right thing". Unfortunately this will still take while.