Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!elroy.jpl.nasa.gov!sdd.hp.com!news.cs.indiana.edu!ux1.cso.uiuc.edu!midway!clout!chinet!chaz From: chaz@chinet.chi.il.us (Charlie Kestner) Newsgroups: comp.os.msdos.desqview Subject: Re: Memory needed in DV vs. memsize shown via LOADHI /GS Keywords: desqview qemm loadhi memory Message-ID: <1991Jun18.002923.12045@chinet.chi.il.us> Date: 18 Jun 91 00:29:23 GMT References: <1991Jun16.020113.28578@midway.uchicago.edu> Organization: Chinet - Chicago Public Access UNIX Lines: 27 In article <1991Jun16.020113.28578@midway.uchicago.edu> valley@gsbsun.uchicago.edu (Doug Dougherty) writes: >I just setup a DV window for playing the game Klondike (A really nice >solotaire game; much better than the one that comes with WIN3, BTW) > >To try to figure out how much memory to allocate to the DV window, I ran >KL in Big DOS window using LOADHI /GS. I ran the game (played a full game) >and LOADHI came back saying it required about 174K (0K resident) So I >figured I'd leave a bit of slack and set the window size in DV (on the >first page of Add/Change a Program) to 190. But when I ran it, it came >back with "Klondike: Program too big to fit in memory". Well, some >number of tries later, I determined that the magic number is somewhere >between 250 & 275K (I.e., it works with it set to 275 [which is where I >am leaving it] but fails at 250K) > >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) [additional stuff whacked out...] It displays graphics information? Perhaps your answer lies in your examining the section of the Desqview manual (Changing A Program's Information) that refers to allocating screen memory. In that section, it mentions that Desqview will need more memory when it must manage graphics pages.