Sender: ml AT delorie DOT com Message-ID: <343901E6.349E1F0@cdata.tvnet.hu> Date: Mon, 06 Oct 1997 17:21:10 +0200 From: Molnar Laszlo MIME-Version: 1.0 To: Eli Zaretskii CC: DJGPP workers Subject: Re: cwsdpmi and upper memory References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Precedence: bulk Eli Zaretskii wrote: > Did you try the /L and /S switches to LOADHIGH? If not, please type > "help loadhigh" from the DOS prompt, read the info and try to play > with these two switches (and with "MEM /F" and "MEM /M CWSDPMI", like > the help tells you). It seems that DOS is foolishly trying to load > CWSDPMI into a region that is too small. Doesn't surprise me a bit, I think I've found something interesting. After logging to the net "mem/c" said, that ~19 kbytes of UMB memory is free. Then I started vc.com (a norton commander clone) with "lh vc". Then I exited immediately, and run "mem/c" again. And surprise!! Here is the diff of the result of the two "mem/c" commands: --- f1 Mon Oct 6 14:55:08 1997 (before "lh vc") +++ f2 Mon Oct 6 14:55:20 1997 (after exiting "vc") @@ -11,3 +11,3 @@ SETVER 592 (1K) 0 (0K) 592 (1K) - COMMAND 3,136 (3K) 0 (0K) 3,136 (3K) + COMMAND 22,320 (22K) 0 (0K) 22,320 (22K) WCED 15,872 (16K) 0 (0K) 15,872 (16K) @@ -21,3 +21,3 @@ NETX 45,168 (44K) 0 (0K) 45,168 (44K) - Free 659,120 (644K) 639,600 (625K) 19,520 (19K) + Free 639,936 (625K) 639,600 (625K) 336 (0K) @@ -28,3 +28,3 @@ Conventional 655,360 15,760 639,600 - Upper 162,800 143,280 19,520 + Upper 162,800 162,464 336 Reserved 393,216 393,216 0 @@ -32,8 +32,8 @@ ---------------- ---------- ---------- ---------- - Total memory 33,554,432 15,806,800 17,747,632 + Total memory 33,554,432 15,825,984 17,728,448 - Total under 1 MB 818,160 159,040 659,120 + Total under 1 MB 818,160 178,224 639,936 Largest executable program size 639,584 (625K) - Largest free upper memory block 19,184 (19K) + Largest free upper memory block 240 (0K) MS-DOS is resident in the high memory area. 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. Laszlo