A specialized DOS application I must use includes DESQview (v2.0).  In a
VDM session under OS/2 WARP v3.0 it runs and executes one set of specifi-
cations without problem; but when I try to execute a second set the pro-
gram displays DESQview error messages calling for more "system" memory.
Although the application copy of DESQview has no means for changing
"system" memory, I contrived to patch in higher values.  It turns out
that a "system memory" setting of 90 or higher (along with "common
memory" increased to 50) eliminates the error messages; but it also
turns out that this does not eliminate the underlying problem.  I still
cannot run a second set of specifications without interruption.
The program now just kicks me out of DESQview, back to the application
main menu with a couple of protesting beeps but without going through the
error message rigmarole.  Some gain, but not yet the whole enchilada.
(In case you wondered, a setting of 110 produces the same result, but
with THREE beeps.)
The folk at Quarterdeck were shocked by the high memory value settings I
used; but told me I would have to seek help from the developer of the
program in which DESQview was incorporated.  That developer is no help.
Are there other settings that need to be changed to overcome this prob-
lem?  If it's a conflict between DESQview and OS/2 (not unlikely), any
ideas about what it is and how it might be eliminated--either in DESQ-
view settings or in OS/2 settings?  Any suggestions, ideas, clues or
wild guesses will be appreciated. 
Jack P.
--- FLAME v1.0
---------------