Re:Driver Signing changes in Windows 10, version 1607
by xg15 on Tuesday August 02, 2016 @12:48PM
(#12211243)
Probably yes - though pragmatically, you could also check if you actually needed a kernel-mode driver for your hardware to work - especially if it's in-house only and a slightly more complicated deployment process is acceptable. Some possibilities would be:
- If you can modify the hardware, equip it with an ethernet/wifi/bluetooth module and talk to it via IP.
- if you need kernel-mode access, you could develop a linux driver instead, run it in a VM (or a raspi) and communicate with the windows PC using IP. (Admittedly, that's a bit rube goldberg-ish)
- Communicate using the good old serial interface instead and use a user-mode program/library on windows.
- If you can modify the hardware, equip it with an ethernet/wifi/bluetooth module and talk to it via IP.
- if you need kernel-mode access, you could develop a linux driver instead, run it in a VM (or a raspi) and communicate with the windows PC using IP. (Admittedly, that's a bit rube goldberg-ish)
- Communicate using the good old serial interface instead and use a user-mode program/library on windows.