It is not usually necessary to save an image merely to preload patches and your configuration, because these load very quickly on modern machines.
However, if you want to save an image to reduce startup time for a complex configuration (such as large application code) or to save a non-windowing image, then proceed as described in this section.
Make a copy of
C:\temp\my-configuration.lisp. When you have made any desired changes in
my-configuration.lisp you can save a new LispWorks image, as described in Create and use a save-image script.
C:\Program Files (x86)\LispWorks>lispworks-7-0-0-x86-win32.exe -build
You can now use the new
my-lispworks.exe image from the Windows Explorer, or you may choose to add a shortcut. The supplied image is not required after the configuration process has been successfully completed.
Do not try to save a new image over an image that is currently running. Instead, save an image under a unique name, and then, if necessary, replace the new image with the old one after the call to
save-image has returned.
If the LispWorks splash screen appears briefly but no image is saved, then there is some error while loading the build script. To see the error message, run the command with output redirected to a file, for example:
C:\Program Files (x86)\LispWorks>lispworks-7-0-0-x86-win32.exe -build C:\temp\save-config.lisp > C:\temp\output.txt
CL-USER 1 > (inspect 1)
To save an image which does not automatically start the GUI, use a script as described in Create and use a save-image script but pass the
:environment argument to
save-image. For example:
(save-image "my-tty-lispworks" :environment nil)
LispWorks Release Notes and Installation Guide - 2 Mar 2015