superfury1

Tried installing it (confirming to install it when it complains about x64 arch of my device). It started spouting weird errors when installing. Then, running setupc.exe, it also spouted errors and didn't work at all (couldn't even add the device).

Can you sign the latest version in bug #33 (I have the bugfix mentioned there)? I tried self-signing it myself(using various methods), but Windows 10 x64 doesn't seem to like it (only when running with driver signing signature enforcing disabled, which needs to be done on every boot of Windows 10 x64). It's a x64-specific bug issue in the source code that's causing detection issues using the documented method from the source code example. There's still another weird bug that shows when wiring the...

Can you sign the latest version in bug #33 (I have the bugfix mentioned there)? I tried self-signing it myself(using various methods), but Windows 10 x64 doesn't seem to like it (only when running with driver signing signature enforcing disabled, which needs to be done on every boot of Windows 10 x64). It's a x64-specific bug issue in the source code that's causing detection issues using the documented method from the source code example. There's still another weird bug that shows when wiring the...

Can you sign the latest version in bug #33 (I have the bugfix mentioned there)? I tried self-signing it myself(using various methods), but Windows 10 x64 doesn't seem to like it (only when running with driver signing signature enforcing disabled, which needs to be done on every boot of Windows 10 x64). It's a x64-specific bug issue in the source code that's causing detection issues using the documented method from the source code example. There's still another weird bug that shows when wiring the...

Can anyone create a proper signed version with this bugfix? It's kind of a hassle to have to keep booting into safe mode every time I want to test or use the OUT1/OUT2 extended functionality, because that requires the detection to work (which requires the above bugfix on 64-bit builds (32-bit builds work fine tho, but my OS is 64-bit Windows 10, which doesn't allow it with secure boot etc.)).

OUT1/OUT2 custom output is unstable or not driving at all

I've managed to confirm the bugfix working as it should (with the proper result when using the bottom RtlCopyMemory patch (replacing "+ sizeof(PULONG)" with " + sizeof(ULONG)")) when using badly/unsigned drivers compiled from the latest source code on sourceforge (3.0.0). Although I can't load said drivers without driver signing protection disabled in Windows 10 x64 because I can't get it to sign the drivers properly for Windows to accept it as a valid driver to load (even when setting my own signature...

IOCTL_SERIAL_GET_MODEM_CONTROL signature bug