Filter
Top Products
Prolifics Installation Error Messages
78 2-Tier Installation
Windows: Set the variable to win in PROL4W32.INI.
If you are running in character mode and the screen appears disorganized,
with all the text bunched together along with special characters, check the
value of
SMTERM; you probably only need to change its value, but you
may also need to create a new video file.
Filename: No such file or directory
Cause: The filename in brackets is specified as the value of the SMVIDEO, SMKEY,
SMMSGS, or some similar configuration variable in the environment or in
smvars.bin, but the file could not be found.
Action: Correct the name, and use the full pathname of the file. If you correct it in
smvars, recompile smvars with the var2bin utility.
[Variable]: Environment variable missing
Cause: Prolifics could not find an entry for the cited variable in SMVARS or in the
environment (refer to the following note). This error usually means that
you have some variables defined in your environment, but not all that are
required, and
SMVARS is not defined.
Note: Most Prolifics setup variables can be set in the environment, rather
than depending on values set in an SMVARS-defined file. If Prolifics can’t find
a required variable specification in either the environment or in the SMVARS
file, that variable will be cited as missing. Refer to the Configuration Guide
for more details.
SMVARS: Bad file format
Cause: SMVARS is set to be the name of an existing file, but it is not a binary
SMVARS file. The most common incorrect value for SMVARS in this case is
the path and name of the source SMVARS file instead of the binary SMVARS
file.
Action: Point to the binary file that has the .bin extension.
SMVARS: Environment variable missing
Cause: SMBASE (or SMVARS, if you are using one) is not set, or not set properly.
Normally, Prolifics looks for smvars.bin in the config directory under
the directory pointed to by SMBASE. If SMBASE is not set, you must have
an SMVARS variable to tell Prolifics explicitly where the SMVARS file can
be found. If SMBASE is not set properly, and Prolifics cannot find an
SMVARS variable, the above message is given.
Action: Correct (or set) the SMBASE variable specification, or determine why
setting it is not taking effect.
Windows: Check to see that SMBASE is being set in autoexec.bat and
that you have not run out of environment space.