On this page, you'll find suggestions for solving problems, organized into the following categories:
Program does not start or crashes unexpectedly
Most problems are related to corrupted configuration files.You can find this out very easily by starting pyilper with the default configuration and a new instance:
python -m pyilper2 --clean --instance temp
This creates a new default configuration for the instance temp, which does not affect your current configuration.
If this does not help, you need to check the error messages pyILPER writes to standard error. Run the program from the command line:
python -m pyilper2
Watch for messages displayed on the console. There are two types of error messages to distinguish between:
It is known that older versions of display drivers crash pyILPER at startup if the program tries to run the internal web browser. Try to start pyILPER with:
python -m pyilper2 --use-system-browser
This option instructs pyILPER to use the system default web browser instead of the integrated PySide6 browser.
In any other case, issue an error report on GitHub
Error message: Cannot change to working directory
The application did not succeed in changing the working directory to the configured file path. Check the path and permissions.
Error message: Your configuration files are of the pyILPER version: XXX that is newer than the version you are running. The program might crash or misbehave. Do you want to continue?
You probably downgraded pyILPER to an older version. The current configuration files might contain data that are not compatible with the running version. To avoid problems, you should reset the configuration files. See the section above.
If the loop terminates with an error message when it starts or remains in the “waiting for connections” state, the cause are incorrect or incomplete interface configurations. Please read the instructions for the interfaces below.
The status light for the PIL-Box interface stays "yellow"
The serial device you specified in the interface settings does not exist. Please check at the operating system level whether the device specified in the configuration is active.
The connection to the PIL-Box is terminated with an error message
Errors like baudrate mismatch or cannot reset device indicate access issues with the interface. It is possible that another process is already using it.
A timeout error indicates that the connected device is either not a Pil-Box or that the connected Pil-Box is taking too long to become operational.
The loop does not start with the error message TCP/IP: cannot bind to port
The port number you specified as In Port is probably used by another program.
I started all my Virtual HP-IL over TCP/IP programs, but the status of the interfaces stays "yellow"
That's normal. Generate some network traffic, for example, by performing a RESTORE IO on the HP-71. That's what establishes the network connections.
Generating network traffic results in a HP-IL loop timeout
There is something wrong with the configuration of the TCP/IP interfaces in pyILPER or the other Virtual HP/IL over TCP/IP programs. See the Virtual HP-IL Example for a working configuration, and carefully check the TCP/IP connection parameters of all programs that are components of the TCP/IP loop.
Error messages related to log file processing
Log files are created in the pyILPER working directory. They are named after the corresponding tab and end with “.log.” Please check the disk space and access permissions for the log file and the pyILPER working directory.
Error messages related to reading or writing configuration files
The locations of the configuration files are:
| Platform | Directory |
|---|---|
| LINUX | $HOME/.config/pyilper2 |
| Windows | %HOMEDRIVE%%HOMEPATH%\pyilper2_config |
| Mac OS X | $HOME/Library/Application Support/pyilper2 |
| Other | $HOME |
Please check the disk space and access permissions for the files in the directory mentioned above.
The HP-71 keyboard does not work
If you use the PIL-Box interface, you must check the Enable IDY frames option. In addition, the program PILTERM must be run. See the documentation about the terminal for details.
The display of the REVERSI game is partially incorrect
Set the print line length to infinity with PWIDTH INF.
The File Management Controls are disabled
You need to install the required version of the LIFUTILS. In addition, the Device enabled option must be unchecked or the loop must be stopped. This is a safety measure to prevent HP-IL and LIFUTILS operations from being performed simultaneously on a LIF image file.
Error message: File cannot be read
The first 256 bytes of the file could not be read. Either the file permissions prevent reading or the file is too short.
Error message: File is not a LIF1 file.
The LIF identifier 0x800 at offset 0 is missing. This can happen, for example, if the file was created using an HP-41. You can repair the header of this file. Be sure to make a backup copy first.
Error message: The LIF image file has an invalid layout information. Fix the header and try again.
The file was likely initialized by an HP-71 with IL-module revision 1a. Repair the header of this file. Be sure to make a backup copy first.
Error message: LIF image file has an unsupported layout.
The layout information found in the LIF header of the file does not match the supported layouts shown in the table of the documentation for the Drive.
Error message: Expected LIF image file type XXXX for this drive type.
The currently selected drive type only supports LIF image file layouts of type XXXX. Use the drive type HDRIVE1 instead.
Error message of the Pack function: corrupted medium: overlapping files.
In the directory of the LIF image file are at least two files that use the same disk sector. The file cannot be packed. You can use the LIFSTAT program of the LIFUTILS to examine the LIF image file and extract the undamaged files.
There is no print output from V41 or an HP-41 connected to a PIL-Box and/or the function keys of the printer tab do not work.
Always place the tab of the HP82162A termal printer directly after the Interface tab, to which the HP-41 controller is connected. If an HP-41 controller is connected to a PIL-Box, make sure that the Enable IDY Frames option is set.
The status light of the plotter stays red
You need to install the required version of the LIFUTILS that contains the backend program to run the plotter.
Graphic elements are malformed or missing
If you use PRINT to output data to the plotter than it's probably the print line width setting that inserts CR/LF into longer lines. Set either the line length to infinity with PWIDTH INF or use the OUTPUT command instead of PRINT.