INPOUT32/X64 Works with SOME PCI cards

[phil]

OK good news.

On x64 windows, it can only load x64 drivers. That is why InpOut x64 was born. The driver should be automatically copied to the system32 folder thought when the DLL is first loaded, so I'm a little surprised you had to manually copy it across.

Thanks, I will see if I can modify the DLL sometimes over xmas but no promises

Thanks,
Phil

[phil]

I've just had confirmation that InpOut32/x64 works with the StarTech PE1XP Parallel Port card on port address 'D010'.

Thanks to Michael Tracy for letting me know.

[Kfirasulin]

inpout32.dll even work under win 8..

I recenly installed win 8 in my computer, and I also bought a PCI to Parallal card.
In order to have the inpout32.dll to work follow these steps:
1. Make sure you installed the PCI divers in the operating system (comes with the card).
2. Make sure you have the latest inpout32.dll version (which enables the support of long adress numbers).
3. Make sure that you modify your code to the new adress, in order to do that, go to the device manager, and
see what address your PCI card occupies - now modify this number in your code.
4. You are done.

[DerbyRacer]

Works OK on SIIG CyberPro Parallel Port card on Windows 7 machine with 64 bit operating system.
Using the following drivers:-
SIIG driver version 1.3.2.1
Inpout32 installer version 1.4.0.0
Inpoutx64.dll version 1.5.0.0

[cappy2112]

Well done. Don't expect the orriginal InpOut32.dll to work on an x64 machine though

Really? We are using it on Windows 10, 64-bit, and it's been working.
Well, very recently, we have started having issues with writes to the data port disappearing.
I will post a separate message about that.

[phil]

The original InpOut32 from (before my port to x64 which is in itself ancient now) from Logix4U only had a 32bit driver which does not/can not install on 64bit Windows.
My port included a 64bit (x64) driver as well as the 32bit driver - thus it works on either Windows edition.

My x64 port is now very old and I am unable to make changes to it because I do not have the ability to sign the driver these days (and am unable to get the required certs as an individual) so as far as I am concerned, its legacy and unsupported. Someone made some updates a few years ago - check this out: viewtopic.php?t=4516 but I doubt that will hglp as it expanded upon and fixed a few things but the basic read/write of bytes should be no different?!

[cappy2112]

The original InpOut32 from (before my port to x64 which is in itself ancient now) from Logix4U only had a 32bit driver which does not/can not install on 64bit Windows.
My port included a 64bit (x64) driver as well as the 32bit driver - thus it works on either Windows edition.

My x64 port is now very old and I am unable to make changes to it because I do not have the ability to sign the driver these days (and am unable to get the required certs as an individual) so as far as I am concerned, its legacy and unsupported. Someone made some updates a few years ago - check this out: viewtopic.php?t=4516 but I doubt that will hglp as it expanded upon and fixed a few things but the basic read/write of bytes should be no different?!

Which file are you calling “the driver”?
We are using the DLL only on x64 systems, it works fine.
There is no installer from what I’ve downloaded, we cou the DLL is o C:\Windows and have no problem writing to the parallel port.

I don’t know of any driver being needed

[phil]

The driver is an embedded resource file (.sys) inside the DLL (well there are two in my DLL, one for 32bit and one for 64bit) it is installed and loaded on the fly so long as the executing program has elevated (admin) permissions (that is what Installdriver.exe does - loads the DLL with elevated permissions which in turn installs the driver - which is a one-off thing to do).