Sender:	ml AT delorie DOT com
Message-ID:	<343B9B40.89CEE49@cdata.tvnet.hu>
Date:	Wed, 08 Oct 1997 16:40:00 +0200
From:	Molnar Laszlo <molnarl AT cdata DOT tvnet DOT hu>
MIME-Version:	1.0
To:	Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
CC:	DJGPP workers <djgpp-workers AT delorie DOT com>
Subject:	Re: cwsdpmi and upper memory
References:	<Pine DOT SUN DOT 3 DOT 91 DOT 971007143031 DOT 25685A-100000 AT is>

Eli Zaretskii wrote:
> 
> On Mon, 6 Oct 1997, Molnar Laszlo wrote:
> 
> > As you could notice, command.com is now 22kbytes instead of 3 kbytes !!!
> > Maybe it loaded its resident part into the memory? It seems that loading
> > command.com high is a bad idea. AFAIK, QEMM can load command.com high,
> > so this can be a problem with QEMM too, but I'm not sure.
> I always have COMMAND.COM loaded HIGH (with QEMM) and never had any
> problems whatsoever.

Maybe QEMM allocates enough memory for the resident part of command.com?
Or is it requires 3 kbytes too?

> I also don't see how this problem with vc and COMMAND.COM is related
> to CWSDPMI.  For all I know, it could be a bug in vc.

I thought, that when the stub wants to load cwsdpmi, command.com begins
to load some of its resident part, which eats all free UMB memory. And
then it fails for some reason.. It sounds weird I admit. And vc can be
buggy too. But this buggy vc solved my problem :-)

Laszlo

- Raw text -