Xref: utzoo comp.lang.lisp:1444 comp.sys.ibm.pc:24466
Path: utzoo!utgpu!utstat!jarvis.csri.toronto.edu!mailrus!ames!pasteur!ucbvax!decwrl!decvax!tektronix!tekcrl!tekgvs!toma
From: toma@tekgvs.LABS.TEK.COM (Tom Almy)
Newsgroups: comp.lang.lisp,comp.sys.ibm.pc
Subject: Re: modest LISPs for the 386
Keywords: LISP,386
Message-ID: <4614@tekgvs.LABS.TEK.COM>
Date: 9 Feb 89 16:04:26 GMT
References: <215@rappel.Morgan.COM> <576@mipsmag.UUCP>
Reply-To: toma@tekgvs.LABS.TEK.COM (Tom Almy)
Organization: Tektronix, Inc., Beaverton,  OR.
Lines: 29

In article <576@mipsmag.UUCP> dbetz@mipsmag.UUCP (David Betz) writes:
>In article <215@rappel.Morgan.COM>, lebowitz@Morgan.COM (Mike Lebowitz) writes:
>> LISP that can use expanded (or extended) memory.  (Is XLISP able
>> to use such memory?)  
:
>No, XLISP can't use extended memory on a 386 unless you're running a
>386 version of UNIX or OS/2 or a DOS extender.

Which is not that difficult to do.
I run XLISP 2.0 compiled with Metaware High C 286, running under the
Phar Lap DOS Extender.  Since the extender is "bound" to the executable,
XLISP appears to be a standard DOS .EXE file.

Not only is more memory usable to XLISP, but it also runs faster since the
protected mode program is "SMALL" model rather than "LARGE" model. (Small
model in 80386 protected mode limits one to 4 Gigabytes.  If you need more
than you are back to segments again :-) ).

Running under an 80386 UNIX is also possible, but the XLISP user interface
(break facility) is not as sophisticated.  With OS/2 you are running in
80286 protected mode, which would not be as fast.

The only disadvantage to using the DOS Extender is that it won't work when
the 80386 is running in virtual 8086 mode, as happens with Window/386,
QEMM, or 386ToTheMAX.

Tom Almy
toma@tekgvs.LABS.TEK.COM
Standard Disclaimers Apply