Hallo Lutz,
I downloaded the new Version 8.0rc1 and installed it on my Windows XP Pro system without any problem.
The documentation is correctly displayed after adapting the config-file.
But trying to run a most simple Lisp statement (+ 1 2 3) results in an error.
The log-file is as follows:
error writing "sock164": connection reset by peer
error writing "sock164": connection reset by peer
while executing
"puts $nlio $lastCommand"
(procedure "ProcessConsoleInput" line 28)
invoked from within
"ProcessConsoleInput"
(command bound to event)
Do you have any hint what went wrong?
Kind regards
Gerhard Zintl
Bring up the taskmanager and make sure that neither newlisp.exe nor newlisp-tk.exe is running. Than try to start newlisp-tk again.
If you installed as default c:newlisp then no changes for displaying the documentaion should be necessary. Only if you changed the directory to a different place (which you can) you need to make changes for the path of the help files.
You may also have an old bad configured newlisp-tk.config. Delete it and generate a new one by doing a 'Options/Save settings'
Lutz
Hallo Lutz,
I did as you proposed. New config-file created. TaskMgr showed just newlisp-tk.exe after running it. Same error message after entering '2'in newlisp-tk.
error writing "sock164": connection reset by peer
error writing "sock164": connection reset by peer
while executing
"puts $nlio $lastCommand"
(procedure "ProcessConsoleInput" line 28)
invoked from within
"ProcessConsoleInput"
(command bound to event)
V7.5.14 runs without any problem.
Hello Lutz,
I also have the problems with 8.0 RC1 with newLISP-tk.
The DLL works normal.
I have now clue whats going on here and cannot reproduce on my PCs with Win2k and XP-Home edition, so I am rolling back change by change from 7.5.14 to 8000rc1.
Please try:
http://newlisp.org/download/development/newlisp_8000rc2_win-tk-111.exe
to see if there is any difference
Lutz
RC2 is working fine again for me.
No more crashes on startup and (+ 1 2 3) working again.
Also demo.lsp.
I must have been something with RC1's newlisp.exe, since I wrapped the new tcl and tried it with an older EXE. It had work fine. Also a file-diff only shows the changes on the manual-call.
So were the rolled back changes in newLISP.EXE?
Hallo Lutz,
rc2 is working fine. Thank you very much indeed.
Gerhard Zintl
thanks for the info Hans-Peter and Gerhard, in rc3 I try to put the change back but the 'right' way, please try rc3:
http://newlisp.org/download/development/newlisp_8000rc3_win-tk-111.exe
Lutz
rc3 works on my XP-Pro laptop
RC3 is working fine on my german WIN2K and WIN_XP office systems.
I did check newlisp_8000rc1_win-tk.exe as well as newlisp-tk.exe v.111 on the following
Win98, Win2k, WinXP Pro on the US Edition, they work fine.
newlisp v8.0.0 did run well, even under the Win98 Japanese Edition.
But newlisp-tk.exe v.107 and the v.111 gave the same following error on the
Japanese Edition of Win98
-------------
Error sourcing /freewrap/newlisp-tk.tcl: bad menu entry index "*Fixedsys*"
-------------
========================================================================================
Only newlisp-tk v.095 with newLISP v7.1.4 works perfectly well on Win98 Japanese Edition
========================================================================================
And running newlisp-tk v.095 with the newlisp v8.0.0 or v7.5.0 give the same following error
------------------------------------------------
newLISP v8.0.0 Copyright (c) 2004 Lutz Mueller. All rights reserved.
>
symbol is protected in function define : (exit)
invalid function in function silent : (SYS:check-tempdir "C:/temp")
Jean-Pierre
go in to the file 'newlisp-tk.conf' and change the font spec:
set Ide(fontName) "Fixedsys")
to
set Ide(fontName) "Lucida Console"
regarding the other error: always use the newlisp-tk.exe together with newlisp.exe it was shipped with. Never mix files from different distributions because sometimes changes occur in the software affecting how both programs work together.
Lutz
Thanks Lutz
Now, newlisp_8000rc3_win-tk-111.exe with the change to the font mentioned above runs perfectly under Win98 Japanese.
Jean-Pierre