Second, C:\Windows\system32 is indeed the correct place for 64-bit drivers on 64-bit systems. SysWow64 is for 32-bit binaries on 64-bit systems (see http://blogs.sepago.de/d/helge/2008/04/ ... ent-part-7).
The batch file didn't work for me either, but because it didn't find the input file. It seems at least on Windows 8 64-bit, running a batch file (by right-clicking and "Run as administrator") launches the batch file with the working directory set to something other than the file's directory. As the path to the driver is relative to the working directory:
Code: Select all
copy /Y IBM_ECWDRV.SYS %DRV%
Code: Select all
copy /Y %~dp0\IBM_ECWDRV.SYS %DRV%
Finally, the ReactOS guys have a proper code signing certificate that they use to sign drivers for open source projects (http://www.reactos.org/wiki/Driver_Signing). There are a few caveats though:
- That offer is only for open source projects. That might or might not be a dealbreaker for you.
- You'd need to get the interest of one of the ReactOS developer. I don't know them, so I have no idea how difficult that would be.
- Since each new driver release would have to be signed, you'd probably want to keep changes to the driver binary to a minimum.
Edit: As an additional data point, I use the software on an X200, Core 2 Duo P8400. Half multiplier, low-FSB, IDA seem to work fine as far as I can tell.