PCI to Parallel Port card using Parallelput

[JoshOohAh]

What is it you are trying to achieve?
Get Parallelput to work with a pci to parallel port controller card. I had to build a traffic intersection for a school project for my computer engineering class. I just bought this because I wanted to test the code at home so I can work on it.


What is the problem you are having?
First time I run it i get the error : Unable to find I/O port device driver. DLPortIO.sys device driver must be correctly installed
Second time I run the exact same script I get: Unable to find I/O port address [4]


Describe what you have tried to solve this problem
Went to device manager and tried updating drivers


Please specify what version of Turing you are using
4.1.1.a for Windows

[chrisbrown]

Run the dlportio_install.exe file found in the Support folder of your Turing directory.

[JoshOohAh]

chrisbrown @ Sun Jun 12, 2011 5:07 pm wrote:

Run the dlportio_install.exe file found in the Support folder of your Turing directory.

]

Thanks for the help but however it wont work because I am on a 64 bit O.S it says to request for a 64-bit version?

[chrisbrown]

Ah.

OK so in the Binaries Only zip file from here, I extracted x64/inpoutx64.dll to Turing/Support/bin and renamed it to dlportio.dll.

This results in the following error:
Parallel port initialization failed. Unable to open required DLL at [path].

Now, I don't have a parallel port on this machine, but it is Win7/64 bit. So I don't know whether the DLL is incompatible or the missing hardware is preventing it from "opening."

If you want to give it a try, it's supposed to be drop-in compatible with the regular dlportio:

Quote:

From Version 1.0.0.7, I have added, simple compatibility with DLPortIO that should allow LCDSmartie to use this DLL as a drop in replacement for DLPortIO in x64 windows. To do this, download just the binaries only package (below) then take the 32bit DLL (in the \Win32 folder), rename it to DLPortIO.DLL and copy it to your LCDSmartie folder. Read the DLPortIO.TXT file included in the ZIP for more information.

*Note: I tried both win32/ and x64/ versions; win32/ gave the same error message that you have now.

[JoshOohAh]

chrisbrown @ Sun Jun 12, 2011 9:51 pm wrote:

Ah.

OK so in the Binaries Only zip file from here, I extracted x64/inpoutx64.dll to Turing/Support/bin and renamed it to dlportio.dll.

This results in the following error:
Parallel port initialization failed. Unable to open required DLL at [path].

Now, I don't have a parallel port on this machine, but it is Win7/64 bit. So I don't know whether the DLL is incompatible or the missing hardware is preventing it from "opening."

If you want to give it a try, it's supposed to be drop-in compatible with the regular dlportio:

Quote:

From Version 1.0.0.7, I have added, simple compatibility with DLPortIO that should allow LCDSmartie to use this DLL as a drop in replacement for DLPortIO in x64 windows. To do this, download just the binaries only package (below) then take the 32bit DLL (in the \Win32 folder), rename it to DLPortIO.DLL and copy it to your LCDSmartie folder. Read the DLPortIO.TXT file included in the ZIP for more information.

*Note: I tried both win32/ and x64/ versions; win32/ gave the same error message that you have now.

So in essence... I'm screwed?

[Tony]

Old, no-longer-supported language with old, no-longer-supported hardware, via a new operating system who's architecture did not exist when either of the former technologies were developed?

Yeah, in essence this is unlikely to work.

You could write in some abstraction that would display some debug information instead of setting parallel port's pins. That will allow you to still interact with code in some ways (provided that timing delays allow for something meaningful).

[JoshOohAh]

Tony @ Mon Jun 13, 2011 2:46 pm wrote:

Old, no-longer-supported language with old, no-longer-supported hardware, via a new operating system who's architecture did not exist when either of the former technologies were developed?

Yeah, in essence this is unlikely to work.

You could write in some abstraction that would display some debug information instead of setting parallel port's pins. That will allow you to still interact with code in some ways (provided that timing delays allow for something meaningful).

I think I'll just find some old machine from one of my buddies or something.

Thanks for the help though