🚀 go-pugleaf

This is a questionthat has been bothering me for
some time but I have seen no discussion of it here
or in the FAQ. How is it that in seamless sessions
I can have conflicting settings? 

To be more specific If I have 3 Apps each with
separately twiddled settings for HARDWARE_ROM_TO_RAM
DPMI_MEMORY_LIMIT etc all running in the same session
how is this all sorted out when the all have to run in a
single VDM?

Do they all run in a single VDM?

I can imagine separate memory limits on a per app basis
but something like VIDEO_MODE_RESTRICTION surely can't
be incompatible when all the apps in that session share a
windows driver. The situation is further confused by
the generic WINOS2 notebook in the command prompts folder.
What takes priority when these settings conflict with those
of an app?

One last question. Does this have anything to do with the 
fact that I cannot figure out how to start up a windows app
to run in an _existing_ full screen session? Right now it seems 
to me that the only way to have more than one app running in a
full screen session in to fire up progman full screen and take
it from there in windows mode. This seems to waste precious
RAM resources to have progman doing a poor job of something WPS
should do.

I would really like to see some discussion on this or better yet
get a pointer to some solid information. Any thoughts?

Tom