Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

CLISP 1999-01-08 on Windows 95

1 view
Skip to first unread message

Wayne Rogers

unread,
Jun 20, 1999, 3:00:00 AM6/20/99
to
WINDOWS 95 version 4.00.950 with 32 MB ram
VC 5 compiler version 12.00.8168

I am having a problem getting CLISP to run on my win 95 machine. I first
tried to use the binaries from the ftp.cons.org ftp site for win32
binaries. Everytime I ran the lisp.exe I got an error 0x8
(ERROR_NOT_ENOUGH_MEMORY). I tried all the suggestions for arguments,
like -m 10MB -M lispinit.mem. Didn't make any difference.

So I downloaded the source and followed the instructions
built cccp no problem
built ffcall no problems
when running nmake on the makefile (Makefile.msvc5)
nmake stops on the line that compiles spvw.i.c ; It complains with
error messages 'int ' no members defined using this type


Suggestions anyone?

Thanks for your assistance
Wayne


Steve Gonedes

unread,
Jun 20, 1999, 3:00:00 AM6/20/99
to

Wayne Rogers <way...@erols.com> writes:

< WINDOWS 95 version 4.00.950 with 32 MB ram
< VC 5 compiler version 12.00.8168
<
< I am having a problem getting CLISP to run on my win 95 machine. I first
< tried to use the binaries from the ftp.cons.org ftp site for win32
< binaries. Everytime I ran the lisp.exe I got an error 0x8
< (ERROR_NOT_ENOUGH_MEMORY). I tried all the suggestions for arguments,
< like -m 10MB -M lispinit.mem. Didn't make any difference.


Have you tried setting the SHELL environment variable in your
autoexec.bat? This may work if CLISP is running in a shell. Using the
following will ensure your shell has 8 megs of memory.

set SHELL=c:\command.com /e:8192

Ideally windows would allow for dynamic memory allocation, and stack
allocation bigger than 100k without raising an operating system
exception. I mean, why not make alloca just fail rather than terminate
the program with an uncatchable exception? I dunno, and don't I want
to either.

Wayne Rogers

unread,
Jun 20, 1999, 3:00:00 AM6/20/99
to Steve Gonedes
Actually, I had tried that. I went Start,Run and entered "command /e:8192"
Then when the shell came up I tried "lisp -m 10MB -M lispinit.mem"

Got the same error.

F. Xavier Noria

unread,
Jun 22, 1999, 3:00:00 AM6/22/99
to
On Sun, 20 Jun 1999 15:34:45 -0400, Wayne Rogers <way...@erols.com> wrote:

: I am having a problem getting CLISP to run on my win 95 machine. I first


: tried to use the binaries from the ftp.cons.org ftp site for win32
: binaries. Everytime I ran the lisp.exe I got an error 0x8
: (ERROR_NOT_ENOUGH_MEMORY). I tried all the suggestions for arguments,
: like -m 10MB -M lispinit.mem. Didn't make any difference.

:
: So I downloaded the source and followed the instructions


: built cccp no problem
: built ffcall no problems
: when running nmake on the makefile (Makefile.msvc5)
: nmake stops on the line that compiles spvw.i.c ; It complains with
: error messages 'int ' no members defined using this type
:
:
: Suggestions anyone?

I downloaded the binaries for Win98 from

http://clisp.cons.org/~haible/clisp/binaries/win98/

just some days ago and everything works fine. You could check

http://clisp.cons.org/~haible/clisp/binaries/win95/

-- Xavier

F. Xavier Noria

unread,
Jun 22, 1999, 3:00:00 AM6/22/99
to
On Sun, 20 Jun 1999 15:34:45 -0400, Wayne Rogers <way...@erols.com> wrote:

: I am having a problem getting CLISP to run on my win 95 machine. I first
: tried to use the binaries from the ftp.cons.org ftp site for win32
: binaries. Everytime I ran the lisp.exe I got an error 0x8
: (ERROR_NOT_ENOUGH_MEMORY). I tried all the suggestions for arguments,
: like -m 10MB -M lispinit.mem. Didn't make any difference.

Have you executed SAVEINITMEM?

F. Xavier Noria

unread,
Jun 22, 1999, 3:00:00 AM6/22/99
to
On Tue, 22 Jun 1999 18:14:49 GMT, f...@retemail.es (F. Xavier Noria) wrote:

: Have you executed SAVEINITMEM?

Hmmm... I meant if you are able to execute commands from
the command line as in

lisp -q -x "(list foo bar)"

to follow the instructions of the readme file.

-- Xavier

Wayne Rogers

unread,
Jun 23, 1999, 3:00:00 AM6/23/99
to
I tried the 1999-01-08 binaries, I believe. I was able to run the more recent
binaries at work on my NT box without any problems. At home for the WIN95, I
went all the way back to the 1997-09-17 binaries and it runs like a champ on
95. I just thought if anybody was familiar enough with the C source I might be
able to make the necessary fixes in my copy of the latest source code.

Thanks for the suggestions though,
Wayne

F. Xavier Noria wrote:

> :

Wayne Rogers

unread,
Jun 23, 1999, 3:00:00 AM6/23/99
to
Actually not a problem now as you might note in my reply to your other
message. I am using the 1997-09-17 binaries without any problems. I updated
config.lsp and compiled it, saveinitimem, all of that.

Thanks,
Wayne

Bruno Haible

unread,
Jun 25, 1999, 3:00:00 AM6/25/99
to
Wayne Rogers <way...@erols.com> wrote:
> WINDOWS 95 version 4.00.950 with 32 MB ram
> VC 5 compiler version 12.00.8168
>
> I am having a problem getting CLISP to run on my win 95 machine. I first
> tried to use the binaries from the ftp.cons.org ftp site for win32
> binaries. Everytime I ran the lisp.exe I got an error 0x8
> (ERROR_NOT_ENOUGH_MEMORY).

The newest binaries at
ftp://clisp.cons.org/pub/lisp/clisp/snapshots/clisp-win32.zip
finally fix this problem.

Bruno http://clisp.cons.org/

Wayne Rogers

unread,
Jun 26, 1999, 3:00:00 AM6/26/99
to
I've been using this one for two days, it looks fine.

Thanks,
Wayne

0 new messages