Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!ub!galileo.cc.rochester.edu!rochester!pt.cs.cmu.edu!ralf
From: Ralf.Brown@B.GP.CS.CMU.EDU
Newsgroups: comp.os.msdos.desqview
Subject: Re: Memory needed in DV vs. memsize shown via LOADHI /GS
Message-ID: <285b7448@ralf>
Date: 16 Jun 91 14:23:04 GMT
Organization: Carnegie Mellon University School of Computer Science
Lines: 23
In-Reply-To: <1991Jun16.020113.28578@midway.uchicago.edu>
Originator: ralf@B.GP.CS.CMU.EDU

In article <1991Jun16.020113.28578@midway.uchicago.edu>, valley@gsbsun.uchicago.edu (Doug Dougherty) wrote:
}[LOADHI says 174K for KLONDIKE, but KLONDIKE won't run in less than ~260K]
}Why the discrepancy?  (I could understand a small discrepancy, but 100K???)
}I had been given to understand that using LOADHI /GS like this *was* the
}approved method of figuring out how much mem a program used.  (BTW,
}yes, I set the "Program....." field to KLONDIKE.EXE, so as to run it
}directly, rather than via COMMAND.COM)

KLONDIKE probably has an overly conservative memory check, i.e. the programmer
decided that it needs X amount of memory when it really only uses X-100.

}Also, as an aside, how exactly does DV load a program in a window when
}you give it a ".EXE" or ".COM" filename?  Seems I've heard something
}about it using SHELL or some such as a sort of Q&D COMMAND.COM, but,
}interestingly enough, when I did "dir sh*" in my DV directory, it came
}back with "File not found".  Whither it???

DV 1.x used SHELL.COM.	DV 2.x does the loading internally.
-- 
{backbone}!cs.cmu.edu!ralf  ARPA: RALF@CS.CMU.EDU   FIDO: Ralf Brown 1:129/53
BITnet: RALF%CS.CMU.EDU@CARNEGIE   AT&Tnet: (412)268-3053 (school)   FAX: ask
DISCLAIMER?  Did  | It isn't what we don't know that gives us trouble, it's
I claim something?| what we know that ain't so.  --Will Rogers