As it happens, the author provides the source code for the driver, and at work I recently had to write a device driver, so I have all the tools necessary to compile the driver. The first thing I noticed is the source is rather old - it hasn't been updated since 2005. Even if the driver works on XP, I can guaranty the driver won't work on 64-bit Windows. I decided to take the time to update the driver and produce version 1.08. Using newer tools from Microsoft I was able to fix a few problems in the driver's source code, correct issues in the driver INF file, and recompile for both 32-bit and 64-bit Windows. This updated driver works, I've tested it on XP, 2003, Vista, and Windows 7, both 32-bit and 64-bit. I'll make this new driver available to anyone who wants a copy, including the updated source code. You can download the driver here (link updated). This 7Zip file contains the unsigned 32 and 64-bit versions, the modified source code, and the tools necessary to sign the driver if you have your own digital certificate (read on).
No discussion of the driver would be complete without mentioning 64-bit drivers. Starting with Vista, Microsoft made a change to 64-bit Windows. All device drivers must be digitally signed using a what's called a cross-certificate. These certificates cost at least $100, and quite frankly I'm not going to spend my own money for a certificate so I can sign a free driver. So if you want to run this driver on 64-bit Windows Vista, 7, or 8 then you have two choices.
- The follow website has 4 different methods of loading uncertified drivers under Windows. The intent is this is used by developers who need to test their code. So it's up to you to make these changes to your own system. http://www.raymond.cc/blog/loading-unsigned-drivers-in-windows-7-and-vista-64-bit-x64/
- You can sign the driver yourself. Assuming you have access to a valid certificate, cross certificate from Microsoft, and know how to use the signtool.exe application then you can sign your own driver.