Thank you for your reply. I am using clisp-2.41 instead of 2.33 now, and that has fixed the compilation problem. However, when I run ltktest I get another error. Nothing appears unless I close the clisp shell, and when I click on one of the controls of the tcl program, I get an Application Error dialog with the message 'Error: error writing "stdout" broken...'. The details of the message dialog are - error writing "stdout": broken pipe error writing "stdout": broken pipe while executing "puts "(:callback \"$s\" $val)"" (procedure "callbackval" line 1) invoked from within "callbackval w7 $eggs" invoked from within ".w2.w3.w7 invoke" ("uplevel" body line 1) invoked from within "uplevel #0 [list $w invoke]" (procedure "tk::ButtonUp" line 24) invoked from within "tk::ButtonUp .w2.w3.w7" (command bound to event) Peter Herth <herth@peter-herth.de> wrote: Update your CLISP, this is a known bug in older versions of it. Peter On 1/27/07, Scott Brown wrote:

Hi,

when I try to compile ltk on clisp I get the following error message:

Compiling file F:\ltk-0.90\ltk.lisp ... ERROR in WITH-LTK-HANDLERS in lines 427..429 : Constant NIL cannot be bound. ** - Continuable Error LET*: NIL is a constant, may not be used as a variable

How can I fix this?

Send instant messages to your online friends http://au.messenger.yahoo.com _______________________________________________ ltk-user site list ltk-user@common-lisp.net http://common-lisp.net/mailman/listinfo/ltk-user

_______________________________________________ ltk-user site list ltk-user@common-lisp.net http://common-lisp.net/mailman/listinfo/ltk-user Send instant messages to your online friends http://au.messenger.yahoo.com

From what other users reported, your problem can come from a program running in the background, like a tray program. Try to disable all of

I have tried disabling some of the processes in the task manager, but I haven't had any luck so far. Is there a specific program or type of program which has been found to cause problems with LTK on Windows? Scott Peter Herth <herth@peter-herth.de> wrote: It looks as if you are running windows. Unfortunately, there have been several reports like yours from windows users who run LTK. But I have never been able to reproduce this behaviour (I do not have a windows box but whenever I ran LTK on a windows machine it worked for me). those to find out which one may be the culprit. If you find it, please tell the list, so we can create an issue list. Peter _______________________________________________ ltk-user site list ltk-user@common-lisp.net http://common-lisp.net/mailman/listinfo/ltk-user Send instant messages to your online friends http://au.messenger.yahoo.com