Direct memory access in nt and higher -- port95nt.exe

[wildWolverine]

I've got a code that directly interfaces with the parallel port on my computer. It works fine on win 95 and win 98. However, it does not work on nt, 2000, or xp. I discovered that changes in the os make direct interaction w/ the hardware impossible, unless you have a special driver. Thus, I d/l a driver -- port95nt.exe (a freeware version of driverlinx). However, after installing the driver, my program still doesn't work. Has anyone used port95nt.exe? If so, do I need to make any changes to my source code so that it knows the new driver/dll is there?

any and all help is much appreciated...

 

[gonzo_for_civ]

I haven't used it myself but I wonder if the site you got it from has a support section on it?

You would figure that if anything special is required to get it working it would be mentioned in a readme or FAQ.

 

[wildWolverine]

Unfortunately, while Keithly provides said code, it is explicitly "unsupported." Also a downside, most people had this problem (at least, most of the sort of people who would recognize this problem) had it about 4 years ago, when NT and 2000 came around (the first two os's that don't allow direct access to memory addresses -- everything is virtual) -- therefore, all the discussions I can find about this topic are ~1997/8...

 

[Comraddict]

there must be workaround, but it is know fact that NT doesn't allow direct access to any of hardware.

 

[wildWolverine]

Hence why I need a driver to allow me to do so...