Mail Archives: djgpp/1994/12/03/18:23:17
>
> The problem with the slowdown in this case is a bug I thought I would let
> the list know about. If you use "NOEMS" on the command line with EMM386
> GO32 works, but uses XMS memory allocation instead of VCPI memory
> allocation. The keep memory on exec functionality, checks for vcpi but
> does not know if valloc is using vcpi memory or xms memory.
>
> The easy fix was to subedit GCC.EXE to set the keep on spawn memory to
> 0 from 1024K.
>
> Summary: If you use EMM386 NOEMS, stubedit GCC.EXE keepmem=0 and
> compiles will run a lot faster.
I have found that this works.
Another apparent bug in go32 is that if it does not find enough conventional
memory to run (the "not enough memory to run go32" message), it forgets to
give the XMS back, so _no_ subsequent operation has XMS available. The
only way to continue is ctrl-atl-del. Given that we will be living
with go32 for some months before 2.0 emerges, is there any way to fix
this bug with a maintenance release?
Thanks!
Mike Feldman
- Raw text -