Path: utzoo!utgpu!jarvis.csri.toronto.edu!clyde.concordia.ca!uunet!mcsun!hp4nl!hpuamsa!frank
From: frank@hpuamsa.UUCP (Frank Slootweg CRC)
Newsgroups: comp.sys.ibm.pc
Subject: Re: DESQVIEW 386 W/ 600K APPLICATIONS
Message-ID: <7310002@hpuamsa.UUCP>
Date: 2 Jan 90 16:16:02 GMT
References: <213400081@s.cs.uiuc.edu>
Organization: HP NL
Lines: 37


  I only have used DESQview a little bit. I could get 562128 bytes free
in a (full screen) COMMAND.COM DESQview "window".

  With Windows/386 I can get 578096 bytes free in a *full screen*
COMMAND.COM "window" ("Windows beats DESview by over 15K!" :-)).
  To this you can add the resident size of COMMAND.COM (nearly 4K (I
think) see "map[mem]", "mi" etc.) if you start your application directly
from a PIF file (instead of *via* COMMAND.COM).

  The Windows/386 test was done on a *2* MB HP Vectra QS/16  with :

- 636 K (*not* 640) of Base/Convential memory (our (HP) machines have a
  4K extended BIOS)
- BUFFERS=8
- FILES=20
- *no* drivers
- *no* TSRs
- WIN.INI: windowmemsize=420 (or down to 385)
- WIN.INI: emmsize=0 (because windowmemsize!=640)

  The DESQview test was done on the same system (perhaps with 640 K Base
Memory). I think that DESQview *claimed* that it could give more but it
did not. The numbers from the Memory Status command (*before* opening the
"window") were (last two rows) :

615 608 572
912 688 560

  I only have the numbers here (not the system or manual). I think the
"572" is the important number. So DESQview only "lied" a "little" :-).

  Hope this helps.

Frank "I like|hate *both*!" :-) Slootweg
Hewlett-Packard, HP-UX Support, Dutch Customer Response Center.
                 ^^^^^--*not* MS-DOS :-)