Conv. Memory used by PB3.5 IDE

[Denny Moore]

Why would PB's IDE use different amounts of
conventional memory on two different computers?
Below is a comparison of the Dos MEM command
before and after loading PB5.3.

Computer ONE Pentium, Windows 98
At Dos prompt, nothing loaded, C:>Mem
Memory Type Total Used Free
---------------- -------- -------- --------
Conventional 640K 72K 568K
Load PB, Dos Shell, C:>Mem
Memory Type Total Used Free
---------------- -------- -------- --------
Conventional 640K 510K 130K
Size of IDE: 438K

Computer TWO Pentium III, Windows 98SE
At Dos prompt, nothing loaded, C:>Mem
Memory Type Total Used Free
---------------- -------- -------- --------
Conventional 632K 36K 596K
Load PB, Dos Shell, C:>Mem
Memory Type Total Used Free
---------------- -------- -------- --------
Conventional 632K 523K 109K
Size of IDE: 487K

Computer Two: 487K
Computer One: 438K

IDE Difference: 49K

Net Difference in free space: 21K

Oh yeah, computer One's Pb.exe, Pbc.exe, Pbconfig.pb, etc.
were transferred directly to computer Two via diskette.
There was not a new install on Two.

Why would second computer PB ide use 49kb of memory than the first?

Losing the net 21k for debug hurts!

Denny Moore


------------------

[keith shelton]

This looks like a difference in the way win98 and win98se run a
dos box. On my laptop I get 438kb for PB in a dos box. If I run
PB with a short cut I get 431kb for PB. This I think is because
I am not starting a dos box and then envoking the compiler.
YMYV
Keith Shelton
there is no spool


------------------

[Buck Huffman]

I think Keith is on to something there, if you run a dos program
from windows, it won't start a copy of command.com for that
session. in fact, if you don't include a shell= line in your
config.sys, you can actually run dos progs without any copy of
command.com in running(as of windows 95 M$ included the code for
command.com in with win.com). So an extra copy of command.com
could be using some of that memory. also the first machine might
have "LocalLoadHigh=On" set in the system.ini file, causing
command.com to load high. also, differences in the environment
settings can cause differences in memory useage in a dos box.

But none of this seems to account for an entire 41k of mem, I
would be interested in finding out more about this myself.
Please update this post if you find out more.


------------------