search

divyang4481 / photivo

Automatically exported from code.google.com/p/photivo
GNU General Public License v3.0
0 stars 0 forks source link

2GB limitation in 32-bit Windows: partial overcome possible #45

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
Hello,

thanks a lot for developing Photivo!

I am using it on a 32-bit Vista and I read of the 2 GB limitation issue. It 
seems that MS foresaw this problem and the allocation space can be incremented 
to 3 GB, according to this article:

http://avatechsupport.blogspot.com/2008/03/how-to-set-3gb-startup-switch-in.html

Hope it works

Cheers,
F Rainone (Switzerland)

Original issue reported on code.google.com by fabio.ra...@gmail.com on 20 Aug 2011 at 11:39

GoogleCodeExporter commented 9 years ago 
Hi,

adding the /3GB switch to your boot.ini is not enough, though. Application side 
support is needed as well. Meaning Photivo would have to use 
IMAGE_FILE_LARGE_ADDRESS_AWARE in its image header, which currently it 
doesn’t. Apparently that is possible with our MinGW/GCC toolchain, but I 
wouldn’t enable it without some heavy testing on different setups.

Unfortunately neither mike nor me have a suitable machine to test on and 32bit 
optimizations are quite a way down on the todo list. But if you or anyone else 
wants to start tinkering, don’t hesitate. I’ll be happy to answer specific 
questions. Key points imo:
a) Any problems/crashes/weird behaviours on different RAM/Windows version 
combinations with or without the /3GB switch?
b) How large is the real benefit, i.e. how much more Mpx work without crashing?

For reference:
http://msdn.microsoft.com/en-us/windows/hardware/gg487508
http://groups.google.com/group/gnu.gcc.help/browse_thread/thread/b1548cd5e7c15a8
b/05628751f5f46111
http://www.jvadillo.com/software/3gbproblem.html

cu
Brother John

Original comment by brother.john.gm@googlemail.com on 20 Aug 2011 at 1:19