From:	Charles Sandmann <sandmann AT new-orleans DOT NeoSoft DOT com>
Subject:	Re: `Not enough memory to run GO32' ?
To:	A DOT APPLEYARD AT fs1 DOT mt DOT umist DOT ac DOT uk (ANTHONY APPLEYARD)
Date:	Fri, 11 Nov 1994 11:18:58 -0600 (CST)
Cc:	djgpp AT sun DOT soe DOT clarkson DOT edu

>   Could GO32 be revised so it could run more than one Gnu C program at once?
> I.e. if Gnu C program X calls Gnu C program Y, the (copy of GO32 that called
> X) would also call Y. If Y is on an .EXE file that on examination proves to
> start with its own copy of GO32.EXE, then X's copy of GO32 would ignore the
> GO32.EXE part of Y.EXE and load the rest of it and run it.
>   There would also seem to be a case for thoroughly searching and going over
> GO32 to reduce its bulk as far as possible. 78810 bytes seems rather a lot.

GO32 is completely eliminated in V2.0.  The free DPMI which is provided will
provide this multiple use functionality (so the 53K is only needed once).
Any further work on GO32 is really wasted effort.  With each V2 program
needing as little as 5K to run, this is not a problem you will see in the 
V2 release (hopefully 1Q95).

BTW, V2 has been running for almost a year now, so it isn't vaporware.  
It just needs a lot of work to completely rewrite functions and make
improvements.  For example, I just got the debuggers running this month.
Many signals are still missing (those based on HW interrupts).

Be a bit patient.  The new stub (2048 bytes) is worth waiting for.  It
is a work of art (thanks to DJ and Morten Welinder).

- Raw text -