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

[Adam Martinson]

On 06/02/2011 03:11 PM, Dmitry Timoshkov wrote:
> Adam Martinson<amartinson at codeweavers.com>  wrote:
>
>> +/* Check the current process and all ancestors that share its address space.
>> + * 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. */
> My previous question still applies.
>
Your previous quesion:
 > How do the processes running in separate address spaces have anything 
to do with that?

I thought I addressed that with this version of the patch, but if I'm 
not checking address space correctly, please tell me the correct way.  
PEB::InheritedAddressSpace doesn't work, I'm not sure what else I should 
be looking for.