GC>> msged.exe                  133364    258632   51% Deflated
GC>> ^^^^^^^ this one locks up my 486/66

PE> Ok, to debug this one I need to know which line of code it is failing 
PE> on, and the only way I know how to do that is if you have access to a 
PE> C compiler (Borland, Microsoft, almost anything will do).  The first 
PE> thing to do is see if it works on a stand-alone DOS machine, with one 
PE> area (only) defined.  Then see if it is just under desqview that it 
PE> fails.

GC> The above works outside Desqview.  

Ok.

GC> Inside Desqview it loads, scans all 
GC> the areas and freezes at the scan window.  It looks like this;

Ok, sounds like the desqview-specific problem which Matthew recently posted
a debug for.  Let me know if that patch works for you too.

GC> I can close the window using Desqview.  I think I've got a couple of 
GC> compilers (Borland and MS C++) lying around here somewhere, tho I can't 
GC> figure out why since I don't have a clue what to do with them.

I can guide you through that, but there's no point when Matthew has likely
already nailed down the exact line of code.

GC>> msged.ico                     230       874   26% Deflated
GC>> msged32.exe                145607    278601   52% Deflated
GC>> ^^^^^  this one will work....

PE> This one works but takes up all available memory?

GC> Exactly, every byte.

Get hold of DOS4GW (it's available for FREQ from me and others) and tell me
whether running msged32 via dos4gw causes it to use up all memory.

BFN.  Paul.
@EOT:

---