Node:Problems Getting Started, Previous:Password Problems, Up:Installation Problems

Problems Getting Started

Question:

I get the message "Failed to locate bootfile".

The message "Failed to locate bootfile" means that SICStus cannot find either spds.sav or sprt.sav, depending on whether you are executing a development system or a runtime system. If you are running a runtime system, you may want to read the chapter "Runtime Systems" in the User's Manual. If you want to execute runtime systems on machines that do not have SICStus installed (a.k.a. target machines), read the sections "Runtime Systems on Target Machines".

If you get this message running a Development System, your installation is probably inconsistent. Reinstall SICStus and try again.

Question:

^D doesn't seem to bring me back a level down after break.

The manual assumes that ^D is the EOF character. Under Windows, however, it's ^Z (except when running under Emacs). In most contexts, the term end_of_file terminated by a full stop (.) can be typed instead of the EOF character.

Question:

spld fails with the message:

'rc' is not recognized as an internal or external command,
operable program or batch file.
! Could not generate .res file for data resources. at spld.pl line 745.

Question:

splfr fails with the message:

'cl' is not recognized as an internal or external command,
operable program or batch file.
! Could not compile spa011160.c: No such file or directory

You need to include Microsoft Visual Studio (or at least its C compiler and linker) in your PATH environment variable. The easiest way is to run vcvars32.bat from the Visual Studio distribution. To do it manually (Windows NT/2000/XP):

C:\> set PATH=location of Microsoft Visual Studio;%PATH%