This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
I was wondering if the 32 bit version Java SE 7 had support for allocating more than 2GB of memory assuming the /3GB boot.ini flag is used. In other words, does Java SE 7 have IMAGE_FILE_LARGE_ADDRESS_AWARE set? On Oracle's site it says that as of Java SE 6 it is not supported but nothing about 7.
It looks like the dumpbin utility from MS Windows SDK should be able to display it (source - I guess the "Application can handle large (>2GB) addresses" line in the output indicates the IMAGE_FILE_LARGE_ADDRESS_AWARE flag is set). However, that would assume you have access to the SDK. There might be other tools that would display information from the EXE header, I've found this tool (paid, but has a trial period) that might perhaps be able to do it (I didn't try myself).
I would doubt it, though. It's quite nonstandard thing, and given that you can install 64-bit OS and use 64-bit Java instead, I'd guess it would have very low priority to be implemented.
I’ve looked at a lot of different solutions, and in my humble opinion Aspose is the way to go. Here’s the link: http://aspose.com
subject: Support for more than 2GB of memory (via the /3GB boot.ini flag) in 32 bit Java 7?