https://bugs.winehq.org/show_bug.cgi?id=44931
--- Comment #6 from Anastasius Focht focht@gmx.net --- Hello Zebediah,
--- quote --- (For the record, this sort of problem is known. I think the oldest bug tracking something like it is 19494.) --- quote ---
well, the original reason bug 19494 was created for is invalid. The conclusion drawn from the error message has nothing to do with virtual memory/pagefile etc. I've put an update in that ticket and resolved it.
But yes, an improvement could be to allow tweaking certain pagefile/physmem values via registry settings to get rid of some hacks in 'GlobalMemoryStatus()' It doesn't necessarily need to be accessible via user interface though (as shown in http://www.tacktech.com/display.cfm?ttid=303) .. that would be luxury.
Regards