[Bug 30307] Memory Allocation severely limited when running wine executable via condor scheduler

http://bugs.winehq.org/show_bug.cgi?id=30307

--- Comment #7 from [e-mail] 2012-03-30 11:57:22 CDT ---
thanks alexandre for the reply.

that is what i was suspecting. however the key here is: how could the manner in
which the executable is invoked (in this case by a scheduler) affect what
libraries are loaded?

regarding large blocks of memory. surprised to hear that in this 'big data' day
and age. I analyze multi-GB datasets all the time, requiring they be in-memory.

i looked at the /proc/pid/maps but will try again and post.

next challenge is to provide my 32-bit program the full 2GB memory allocation
it could receive in a 64-bit windows. possible?

thanks, jason