This list is certainly not complete, but may give an overview on the most commonly encountered problems.
If you have trouble using the MolArch+ program or if you think you have found a program bug, you may contact me via
e-mail (AFTER you have read the instructions on this page)
providing the following informations:
The system (LINUX distribution etc.) on which you are running MolArch+.
The MolArch+ version you are using (output of the command 'molarch+ -V').
A script file (e.g. something like 'molarch+ --spr <file>' where <file> contains a sequence of commands) or
a full command line (e.g. like 'molarch+ --<command1> --<command2> ...') which is apt to reproduce the error. If you do not know how these command lines work, read the MolArch+ - Introductory Remarks first.
A full report on the output of the above commands (preferably a LOG-file obtained from a command like 'molarch+ --<command1> --<command2> ... --quit 2&>1 > output.log';
do NOT truncate lines and/or copy-and-paste the output if long output lines are wrapped).
Any user created file used by the above commands (do NOT send MolArch+ system parameter files).
If required, informations (e.g. version number) on external programs used by the above commands (e.g. POVRAY or any VRML-viewer).
Very large or multiple files should be send as ZIP-files or any compressed TAR-archive (Do NOT send Windows RAR-archives or any other Microsoft specific file type).
A short description on why you think this is a program bug or what you have expected.
The following error messages may indicate problems with your MolArch+ installation:
"vogle X11.c couldn't open fontfile ..."
The "hershey" fonts of the "libvogle" graphics library are not properly installed (see "MolArch+ - Prerequisites").
"... no file ".molarch+.key" or "molarch+.key" found
... no file ".molarch+.ini" or "molarch+.ini" for initialization
These messages are warnings only, but if no main window of MolArch+ shows up, they most likely indicate that
the $MOLARCH variable is not properly set to point to the directory were the MolArch+ parameter files are stored (see "MolArch+ - Installation").
"COLOR DEFINITION FILE NOT FOUND"
The $MOLARCH variable is not properly set to point to the directory were the MolArch+ parameter files are stored (see "MolArch+ - Installation").
"ERROR - FAILED READING REGISTRY KEY" MolArch+ was unable to create and/or read the registry key from the ".molarch.register" file in your home directory (see "MolArch+ - Installation").
The following error messages indicate problems reading files:
"sh: TMP_FILE.pdb: Permission denied ... open: No such file or directory ... Aborted"
You don't have write permission at the current working directory from which you have evoked the "molarch+" command.
MolArch+ was unable to temporarily unzip or write files to be processed. Change to a "writable" working directory.
POVRAY - Error Messages
The following error messages indicate problems with your POVRAY configuration:
#include "colors.inc" ... Parse Error: Cannot open include file colors.inc.
You need to configure POVRAY properly to manage the include files that where contained in the POVRAY distribution. MolArch+ will use for examples the colors defined
in these files. You may have to edit your "~/.povrayrc" file adding the appropriate library path statements:
or the corresponding directory where POVRAY has been installed on your system.
#include "molatoms.inc" ... Parse Error: Cannot open include file molatoms.inc.
You need to include the $MOLARCH directory from the MolArch+ installation in your POVRAY library path by editing your "~/.povrayrc" file. Try adding the following line:
where <directory> is the same directory as indicated by the $MOLARCH environment variable.
sh: ... command not found.
You need to edit the file $MOLARCH/molshowpov.com to setup the external POVRAY ray tracing program.
VRML - Error Messages
The following error messages indicate problems with your VRML configuration:
sh: ... command not found.
You need to edit the file $MOLARCH/molshowwrl.com to setup a external program capable of viewing VRML files.