Crashes at start of the program are often caused by a corruped configuration file. In this case the configuration file must be deleted. The location of the file is platform dependent:
| Platform | Directory |
|---|---|
| LINUX | $HOME/.config/pyilper |
| Windows | %APPDATA%\pyilper |
| Mac OS X | $HOME/Library/Application Support/pyilper |
| Other | $HOME |
The name of the configuration file is pyilpern where n is the version number of the configuration file. The version number of the file is increased every time, if the layout of the configuration file of a new pyILPR version changed. In this case pyILPER must be configured again.
If the program does not start at all you should delete the configuration file and check the file permissions of the configuration directory.
You can invoke pyILPER with the --clean option to initialize the configuration file with default values as well.
Cannot connect to PIL-Box
The application did not succeed to initialize the PIL-Box.
Check if the PIL-Box is connected to the correct port and if the baud rate
is configured according to the PIL-Box jumper setting. Check also,
if the correct port is specified in the program configuration.
Cannot create configuration path
The application did not succeed to create the directory
for the configuration file (see above). Check path and
permissions.
Cannot read configuration file>
The application could not read the configuration file. Check
file permissions. If the permissions are correct, purge the file.
Cannot write default configuration
The application did not succeed to create the configuration file.
Check path and permissions.
Cannot write to configuration file>
The application did not succeed to write to the configuration file.
Check path and permissions.
Cannot change to working directory
The application did not succeed to change the working
directory to the configured file path. Check path and permissions.
Cannot close xxx log file
The application did not succeed to close the printer or
scope log file
Cannot open xxx log file
The application did not succeed to open the printer or
scope logfile. Check path and permissions of the working directory.
Cannot write to xxx log file
The application did not succeed to write to the printer or
scope logfile. Check file an directory permissions.
PIL-Box disconnected after error (Status line message)
The application was terminated due to a runtime error. These may
be caused by various reasons. See additional error information.
File does not contain a LIF type 1 medium with valid layout
information. Using default layout.
The LIF image file does not contain a properly initialized header
with valid layout information. The default layout is used.
Warning! If the default layout does not match the current medium data corruption may occur!
Your configuration files are of pyILPER version: XXX which is newer than the version you are running. The program might crash or mishehave. Do you want to continue?
You probably downgraded pyILPER to an older version. The current configuration files might contain data which are not compatible with the running version. To avoid problems, you should reset the configuration files. See the chapter above.
Calling pyILPER from the console gives access to Python runtime errors.