Highrez

Where and how do you specify if you want to build DEBUG or RELEASE
I am looking at both the provided MAKEFILE and sources...

Thank you

Contents of the MAKEFILE
!INCLUDE $(NTMAKEENV)\makefile.def

Contents of the Sources
TARGETNAME=hwinterface # your program name (it'll compile to "hello.exe ...

Thank you to everyone for helping.
I am now able to build the driver (.sys) file.

You need
Win 7 x64 VM
VS 2010 installed
DDK Toolkit
WDK Toolkit

Select from toolkit Build Environment, Windows 7 , x86 or x64 Checked Build Environment
At the command prompt, change the directory where your .c and ...

What do I need to compile hwinterfacedrv.c
Trying to compile HWInterfaceDrv project. Too many errors, I lost count

Seeing the same error with 2019..

Since hwinterface.sys is the driver...
InpOut32.dll and InpOutx64.dll is the Dynamic link library.

Where is the x64 driver?

If I can get a hold of hwinterfacedrv.c and recompile as x64, would that be the x64 driver? or would I need to make additional changes to hwinterfacedrv.c

Thank you again all.
Ultimately, we may have to hire a consultant with Win Device driver experience.

Thank you all for all the great replies.

Earlier it was mentioned: ( see in bold)
You absolutely can not load a 32bit driver on 764bit OS;'s.
You can load a 32bit DLL that talks to a 64bit driver - and that is what MY port of InpOut32.dll is, a 32bit DLL that contains both x86 and x64 drivers ...

Thank you SO MUCH Phil.

I had noticed, your sample is using
_stprintf_s(szFileName, MAX_PATH, _T("\\\\.\\%s"), bX64 ? DRIVERNAMEx64 : DRIVERNAMEi386);

either DRIVERNAMEx64 ("inpoutx64\0") or DRIVERNAMEi386 ("inpout32\0")
I am assuming these are the sys files located in root path \\\\.\\

I am able to locate both ...

THANK YOU very much Phil.
I will keep you updated.

I have a 32 bit app, loading a 32 bit InpOut32.dll running just fine on a Win 7 and Win 10 x86.
The same (Running the 32 bit app (process) loading a 32 bit InpOut32.dll) does not work on Win 11 or Win 10 x64.
I was told, I should have NO ISSUES, loading and running a 32bit driver on a 64bit OS as ...

Both Win 10 x86, Win 10 x64 or Win 11..

I can compile and run the InpOut sample test code.
I do not think it is working.,. No matter what BYTE I write, no matter what port I write to, It always reads back 256 0xFF which I believe is the error code