Not a valid Win32 Application

[loganlehman]

I removed the data packs associated with the application. I just went little by little, and once I got to 3.8GB it worked.

[giaviv]

Hi,

Since I was able to create a build sized 4.5 GB, I have a feeling that this has to do with the amount of files you are installing.

Would you please try creating an installer that deploys between 1 and 3 large files, totaling at around 4 GB?

Thanks!

[loganlehman]

I did that, and it failed yet again. The main files that are causing the size are files that hold terrains data for 3D environments. There are very few of them. I packaged those in ONLY, and compiled. The error happened yet again.

[giaviv]

How many files are those and how big are they?

[loganlehman]

There are 3 and two are 1GB a piece, and the other is 2.6GB

Any Ideas?

[loganlehman]

Is there any way we can persist to address this issue?

[giaviv]

Hi,

I have been looking into this - I am trying different configurations and machines to try and narrow down the problem.
I will keep you posted - thank you for your patience.

[loganlehman]

Thanks Gaiviv,

But here is something I wrote up to explain the space address on large executables:

Each process has its own virtual memory called an address space. This process maps the code that it executes and the data that the code references. A 32-bit application uses a 32-bit address space, which in using binary mathematics, shows that the cap on 32-bit applications is 4GB (or 2^32).

This identifies and explains the issue that was found, although there was more found about these address spaces:

The operating system that the application is running in has to reference its own code, and what it references as well. As a default, the 32-bit version of Windows splits the address spaces in half. So in all actuality, the maximum executable limit without support files (such as .cab or .bin files), in a 32-bit environment, is approximately 2GB.

Many applications might use Heap APIs or Heap space allocation to process its own virtual memory instead of injecting it into the address space, but in the case of an installer, this not possible. What is possible, but may not be applicable to this current case, is the option of configuring the system of the address space with the “increaseuserva BCD” runtime option to permit user address spaces up to 3GB.

[loganlehman]

Any more information on this?

[loganlehman]

I am starting to wonder our company made the right decision on purchasing InstallAware. The fact that I came up with a more viable solution on why an error occurs tends to tell me that the people who created this software do not know what they even created.

There should be more documentation on possibilities and limitations, so the customer doesn't have to create their own.

I am disappointed at the moment, and I would like to have an answer on this soon.

[giaviv]

Hi,

As you said, this is indeed a Windows limitation for 32 bit applications.