On 16 Jun 2009 09:05:52 -0700, Patrick Scheible <
[email protected]>
wrote:
John Larkin wrote:
John Larkin wrote:
John Larkin wrote:
[piggypacking a post since I can't find the correct one]
For John Larkin:
If you want to find out how much code any EXE file has, do
the following commands:
GET FOO.EXE
CORE
It should report how many K there is. But this doesn't
give the real size when the EXE is running.
/BAH
Or just PIP FOO.EXE/L ?
John
good grief, no.
/BAH
Why not? Because it includes overlays?
Real programmers don't use overlays.
Why don't you simply do what I suggested instead of arguing.
Look up what a /L does.
/BAH
You don't make much of an effort to be helpful, do you?
You are more than annoying. A directory of the file
doesn't give you an idea of how the EXE will be mapped
in core.
I have been helpful as best as I can. I've answered your
question. Why you cannot comprehend that there is no
precise answer is beyond me. I'm beginning to think
that you are asking just to be a RPITA.
It doesn't seem like it would be that hard to give a range. The
biggest I saw was xxx, the smallest was yyy.
-- Patrick
What she keeps saying is pretty much "I have more experience than you,
so I'm right and you're wrong", but otherwise fact-free.