|
From: Wolfgang D. <wol...@da...> - 2023-03-31 15:15:25
|
Am 30.03.23 um 22:10 schrieb Wolfgang Dautermann: > I create the Windows installer since serveral versions. It does not > only contain Maxima, but several open source components (Maxima, > wxMaxima, wxWidgets, TCL/TK, Clisp, SBCL, VTK, Gnuplot) are bundeled > in one installer. And I usually update the components to the most > recent version, for a new release, so the issue might even be in one > of the sub-components. The reason might be SBCL - a Lisp-Compiler, which is included and used by Maxima: https://bugs.launchpad.net/sbcl/+bug/1971640 If that is correct, there is an easy solution: The Maxima Windows installer is compiled with two different Lisp versions; SBCL and CLISP. There is a tool included, where you can select, which Lisp version should be used by default ("Configure default Lisp for Maxima" in the start menu). There select CLISP. It is slower than SBCL, but should work on Windows 7 and it has better memory management than SBCL. Or you can select the used Lisp in the wxMaxima configuration: In the 'Maxima'-Tab enter "-l clisp" as addtional parameters for Maxima (without the quotes, of course). Or use an older Maxima version. According to the Git version control system Maxima 5.45.1 included SBCL 2.0.0, which (if the above bug report is correct) worked on Windows 7. Hope that helps. Best regards, Wolfgang |