Contents |
[edit] ZWDA - General Mouse - How to load the filter driver on Windows 7 64 bit
I will load the general mouse filter driver on Windows 7 x64. I'll be using a Logitech VX Nano. I you are afraid to break your computer, you can use a virtual machine (I use VMware).
Warning: you should read this page entirely before trying the procedure. If you only have one mouse, be sure to know how to use windows with the keyboard because the device will be stopped during a part of the tutorial (because Windows won't load the driver)
[edit] Part 1 - Is your driver configured for your device?
Try to load the driver following Part 2.
If the device is recognized, go on with the procedure.
If Windows tells you that the folder does not contain driver for your device, you will need to edit the inf file. See Step 1 of this page.
[edit] Part 2 - Load the driver
I'll try to load the driver normally.
Success! But is it really?
Restart as required.
Open the device manager. You will notice that your hardware has a little yellow exclamation mark on its icon.
Showing details presents you the famous Code 52 error.
This happens because the driver is not digitally signed.
[edit] Part 3 - Get into test mode, sign the driver, and load it again
[edit] Reboot into test mode
- Download the Driver Signature Enforcement Overrider.
- Start it.
- Read and accept the license.
- Select Enable Test Mode and Validate.
- Reboot.
[edit] Sign the driver
You will notice that some text appear in the bottom right part of your wallpaper, confirming that you are in Test Mode.
Get back to the Device Manager. You will notice that the situation didn't improve at all.
We need to sign the driver file ourselves. Open the DSEO again, and select Sign a System File.
Enter the full path of the driver file in the system (not the one in the ZWDA package).
Success! Restart your computer again.
[edit] Part 4 - Check that the driver is loaded
Go again in the Device Manager. This time the driver should be loaded.
Also, you can check that the driver is completely loaded by seeing a symbolic link to the control device, using WinObj.
That's it.
If you run into any problem, post a message in the message boards.

