Millisecond Forums

Could you please detail

- the port numbers involved (i.e., you changed the number from X to Y when encountering the crash),
- the port number(s) and base address(es) of the parallel port(s) involved,
- whether you changed the port number in the parallel port monitor, in a script or both,
- whether your operating system is a 32- or a 64-bit Windows edition,
- whether the crash still occurs when changing your system's locale ("Default language for non-Unicode programs") to English via the system's control panel ( http://www.eightforums.com/tutorials/29081-language-non-unicode-programs-change-windows.html )

Thanks!

Thank you so much for your quick response, Dave.

The port number change was via Tools > Parallel Port Monitor. The default Port Number is 1, as soon as I click the up arrow or type a different number manually, the software crashes. The operating system is Windows 7 Enterprise 64bit with the locale set to English (Australia).

Thanks for the additional details. The bitness of your OS (64-bit) is likely the problem. Inquisit 3 only exists as a 32-bit application and thus can only use 32-bit libraries and drivers. The solution would be to either switch to a 32-bit Windows 7 edition or to upgrade to Inquisit 4 (which does have a dedicated 64-bit build).

The only other thing you can try is using an alternative port interfacing library. To do this, download http://logix4u.net/InpOutBinaries.zip . Extract the zip and put inpout32.dll in the Inquisit program directory (i.e., where Inquisit.exe is located). To switch back to the original library, simply delete inpout32.dll from the Inquisit program directory again.

Hope this helps.

Genius, Dave. That worked like a treat. Will get the client to test it out in the lab and see how it goes. Hopefully this means I don't need to rebuild the machine with the 32bit OS or upgrade the software to the version 4.