Millisecond Forums

Inquisit 3.0.6.0 crashes when changing Parallel Port Number

https://forums.millisecond.com/Topic18038.aspx

By ITS DOM - 1/5/2016

Problem signature:
  Problem Event Name:APPCRASH
  Application Name:Inquisit.exe
  Application Version:3.0.6.0
Application Timestamp:4ef024b1
  Fault Module Name:Inquisit.exe
  Fault Module Version:3.0.6.0
Fault Module Timestamp:4ef024b1
  Exception Code:c0000005
  Exception Offset:00043180
  OS Version:6.1.7601.2.1.0.256.4
  Locale ID:3081
  Additional Information 1:0a9e
  Additional Information 2:0a9e372d3b4ad19135b953a78882e789
  Additional Information 3:0a9e
  Additional Information 4:0a9e372d3b4ad19135b953a78882e789
Read our privacy statement online:
 
http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409
If the online privacy statement is not available, please read our privacy statement offline:
  C:\Windows\system32\en-US\erofflps.txt
By Dave - 1/5/2016

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!
By ITS DOM - 1/5/2016

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).

https://www.millisecond.com/forums/uploads/images/18639b95-1a60-4e37-b059-1bd3.png
By Dave - 1/5/2016

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.