Hi, michael3, and thanks for your question.
These are the steps you'll need to take to get CLISP working on Windows XP.
1. Download the CLISP program. You need the Win32 version - this is
the technical name for Windows 95/98/2000/XP. You can get this from
http://unc.dl.sourceforge.net/sourceforge/clisp/clisp-2.33.1-win32.zip
in zip format. Choose to save it to disk, and save it somewhere you
can find it later (such as your desktop).
2. Decompress it. To do this, double-click on the zip file and drag
the 'clisp-2.33.1' folder inside it to the base level of your hard
disk (C:\).
3. Install it. Do this by going into the newly-created 'clisp-2.33.1'
directory, and double-click on 'install.bat'. Answer 'y' to the first
question, and 'y' to the second and third if you want shortcuts to be
created on your desktop.
4. Make a directory where you will store all the files you want to run
in CLISP. For example, create a folder called 'programs' in the
'clisp-2.33.1' folder on your hard disk.
5. Start the command prompt by going to Start > Programs > Accessories
> Command Prompt
6. Type 'cd \clisp-2.33.1\programs\'.
7. To start lisp, type (including the quotes, all on one line):
c:\clisp-2.33.1\full\lisp -B "C:\clisp-2.33.1\" -M
"C:\clisp-2.33.1\full\lispinit.mem"
You should then get the lisp prompt.
To load a program in your programs folder, type (including the brackets):
(load "yourprogram.list")
To exit from lisp, type '(exit)'.
Note that the commands above depend on you creating the directories in
the places I have specified. If you are comfortable with file paths,
feel free to move them around, but remember to edit the paths in the
commands. You can find out about file paths at
http://www.lvsonline.com/dirs/index.shtml.
As for editors, you can start off with the simple 'notepad' program
that comes with windows. It's in Start > Programs > Accessories >
Notepad.
You can also use editors such as CodeMagic
(http://www.appzgamezwarez.com/CodeMagic_1_1_RC2.exe) or possibly
Visual Lisp (http://xarch.tu-graz.ac.at/autocad/lsp_tools/visual-lisp.html).
The following links may also be useful:
http://www.cecs.missouri.edu/~skubic/375/clisp.htm
http://commonmusic.sourceforge.net/doc/install.html#clisp.bat
There are also several other editors that will work with lisp listed
on http://www.hotscripts.com/Tools_and_Utilities/Script_and_Text_Editors/.
I hope this was of use to you. If you have any questions, please do
not hesitate to request a clarification. Good luck!
-- wildeeo |
Request for Answer Clarification by
michael3-ga
on
05 Jul 2004 08:34 PDT
Hi Wildeeo, thanks for the reply.
This works up to step 7, but in response to the command line you gave,
the system replies:
module 'syscalls' requires package POSIX
and returns to the > prompt.
Also, how do I get that long string passed to the command line without
typing it in each time? The install procedure automatically sets up a
shortcut on the desktop which points to
C:\clisp-2.33.1\lisp.exe -B "C:/clisp-2.33.1/" -M
"C:\clisp-2.33.1\/base/lispinit.mem"
That seems to be wrong, as the file lisp.exe can't then be found. It
appears at least to be missing the \full\ part of the path. Adding
that back in then causes the shortcut to open a Command Line window,
and then immediately close it again. If it is doing anything in
between, it's too quick to see. Is the /base/ part correct? Forward
slashes seem unusual for a Windows path!
The shortcut's properties show that it's starting in
"C:\Documents and Settings\Family\"
I assume that doesn't make any difference?
|
Clarification of Answer by
wildeeo-ga
on
05 Jul 2004 12:18 PDT
Hi,
To get clisp running, try replacing '\full\' in the paths above with
'\base\'. This will load an alternative version of the program, which
will hopefully run.
The shortcut can be modified to make clisp run more easily (even if it
is broken by default).
You're right in saying that forward slashes aren't normal for Windows
paths - it's probably a remenant of the original Unix code. To fix it,
you need to change a couple of things:
- You need to set the path to the exe file correctly. Set it to the
path to the program above. (On my machine, I would set it to
'c:\clisp-2.33.1\base\lisp -B "C:\clisp-2.33.1\" -M
"C:\clisp-2.33.1\base\lispinit.mem"').
- CLISP will look for any programs you tell it to load in the
directory it's started in, so set the starting path to the directory
you will keep your programs in.
Hope that helps.
-- wildeeo
|
Request for Answer Clarification by
michael3-ga
on
05 Jul 2004 14:02 PDT
I've changed the command line to
C:\clisp-2.33.1\base\lisp.exe -B "C:\clisp-2.33.1\" -M
"C:\clisp-2.33.1\base\lispinit.mem"
That starts CLISP, which immediately then generates the message:
WARNING: No initialization file specified.
Please try C:\clisp-2.33.1\base\lisp.exe -M lispinit.mem
*** - PARSE-NAMESTRING: syntax error in filename "C:\\clisp-2.33.1\"
-M C:\\clisp-2.33.1\\base\\lispinit.mem\\" at position 15
1. Break>
Running a shortcut which points to the command suggested
(C:\clisp-2.33.1\base\lisp.exe -M lispinit.mem) starts CLISP with no
errors. So should I use C:\clisp-2.33.1\base\lisp.exe -M lispinit.mem
rather than the command you gave me? I don't understand what the
differences actually do.
|
Clarification of Answer by
wildeeo-ga
on
05 Jul 2004 14:52 PDT
Hi, michael3
In my command line, I use the '-B "C:\..."' section to specify the
base directory of CLISP. From what I've read, this is unusally
unnecessary, and I mostly included this out of a general fear that
computers won't be able to find anything unless you give them explicit
directions to it. :-)
Likewise, the '-M "C:\clisp-2.33.1\base\lispinit.mem"' bit is
specifying the complete path to the lispinit.mem file, which CLISP
needs to start, whereas the program's suggestion of '-M lispinit.mem'
is assuming the program can find it, which it apparently can.
If the program starts and works properly with the
'C:\clisp-2.33.1\base\lisp.exe -M lispinit.mem' command, then use that
one. If it doesn't, then I'll suggest an alternative command to use.
Hope this was of help.
-- wildeeo
|
,
0 Comments
)