To:	tyuan AT beta DOT wsl DOT sinica DOT edu DOT tw
Cc:	djgpp AT sun DOT soe DOT clarkson DOT edu (djgpp list)
Subject:	Re: Why djgpp 1.12 is so slow on my 486PC
Date:	Fri, 19 Aug 94 14:18:23 +0200
From:	pieterh AT sci DOT kun DOT nl

 >I find out w/
 >	device=c:\dos\emm386.exe noems
 >in my config.sys
 >then, I can get my answer in seconds.  BUT if I remove that line
 >from config.sys then I must spend 45 minuates to get the answer.

Okay, so I'm not the only one.  I subscribed to this mailing list
precisely for this problem.  I normally don't use a memory manager
apart from HIMEM.SYS, relying on chipset features to provide UMB
space.  After upgrading from 1.11maint5 to 1.12,

   make pagetest

took 100 seconds.  That's on a DX2/66 with 8MB of RAM.  Booting a
setup with EMM386 reduced this to a more normal 15 seconds; a
Windoze DOS box turned out to be a little faster still.

That fits in nicely with Fred's notion that GO32 uses only
conventional memory in the absence of VCPI or DPMI.  That's not a
feature, that's a bug!  At least this feature was not yet present
in 1.11maint5 :^(

BTW, when GO32 is started in the XMS only setup it _does_ properly
report the available memory (5412Kb free memory, 45872Kb swap in my
case).  Only, it doesn't appear to use it (the only reason it was as
fast as 100 seconds probably is the fact that 6MB of memory lending
cache does a fine job of cushioning the swapping).

Unfortunately I know next to nothing about the innards of GO32, so,
er, basically, the question is, er,... HELP!

 - Peter Herweijer
   pieterh AT sci DOT kun DOT nl


PS. Completely unrelated, obnoxious and pretentious lecture follows:
Considering the very short time I've been on this list I've seen
an amazing number of messages from people who don't know how to
unsubscribe.

	To: listserv AT sun DOT soe DOT clarkson DOT edu
	Subject:

	DELETE djgpp

should do the job.  Note that you should not mail to the list itself.

- Raw text -