Re: [2/3] kernel32/heap: Fix some hacks in GlobalMemoryStatus().

[Dmitry Timoshkov]

Adam Martinson <amartinson(a)codeweavers.com> wrote:
> +/* Check the current process and all ancestors.  Some apps run sub-processes that
> + * have the IMAGE_FILE_LARGE_ADDRESS_AWARE flag set, but the parent process doesn't.
> + * (eg, Dragon NaturallySpeaking 7 setup runs Install Shield 6).
> + * If any don't have IMAGE_FILE_LARGE_ADDRESS_AWARE, return FALSE. */

How do the processes running in separate address spaces have anything to do
with that?

-- 
Dmitry.

[2/3] kernel32/heap: Fix some hacks in GlobalMemoryStatus().

[Adam Martinson]

On 05/31/2011 12:02 PM, Dmitry Timoshkov wrote:
> Adam Martinson<amartinson(a)codeweavers.com>  wrote:
> > +/* Check the current process and all ancestors.  Some apps run sub-processes that
> > + * have the IMAGE_FILE_LARGE_ADDRESS_AWARE flag set, but the parent process doesn't.
> > + * (eg, Dragon NaturallySpeaking 7 setup runs Install Shield 6).
> > + * If any don't have IMAGE_FILE_LARGE_ADDRESS_AWARE, return FALSE. */
> > How do the processes running in separate address spaces have anything to do
> > with that?

Hmm, didn't consider that.  Maybe this is only needed if the processes 
share one