Re: Manually compile InnoSetup as 64-bit?

[Eivind Bakkestuen]

AFAIK: Only if you are prepared to do significant work to implement and test your solution.

On Tue, Mar 4, 2025 at 2:23 AM Jonah Janzen <jonah....@gmail.com> wrote:

Hi there,

I need to build an installer with some relatively large files, and I'd prefer not to use DiskSpanning, and keep everything as a single file.

Is it possible to compile InnoSetup from source as a 64-bit application, to avoid the 2GB file size limit?

Thanks!

--
You received this message because you are subscribed to the Google Groups "innosetup" group.
To unsubscribe from this group and stop receiving emails from it, send an email to innosetup+...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/innosetup/37873469-efef-459a-a2a0-007be51a16d7n%40googlegroups.com.

[Martijn Laan]

Hi,

Op 3-3-2025 om 17:20 schreef Jonah Janzen:

Is it possible to compile InnoSetup from source as a 64-bit application, to avoid the 2GB file size limit?

In 6.5.2 the limit will be raised to almost 4 GB when disk spanning is not enabled. (The limit was not related to Inno Setup being a 64-bit application or not.)

There is still a limit of 4 GB because Windows cannot handle larger executables.

Also, disk spanning is still recommended for large executables due to slow startup times imposed by Windows, especially when the executables are digitally signed.

Additionally in 6.5.2: With disk spanning is enabled, the new maximum disk slice size is effectively unlimited (9223 PB instead of 2 GB). The default disk slice size will not change (2 GB).

Details may change between now and 6.5.2's release. I don't know then it will release.

Greetings,
Martijn

[Dan Breyen]

As of today, In the current help I see that DiskSpanning has been extended.  Does this mean that it's available in 6.5.1, and we don't need 6.5.2?

[Setup]: DiskSpanning

Valid values:yes or no

Default value:no

Description:

If set to yes, the disk spanning feature will be enabled. Instead of storing all the compressed file data inside Setup.exe, the compiler will split it into multiple Setup-*.bin files -- known as "slices" -- suitable for copying onto separate CD-ROMs or DVD-ROMs. Each generated slice contains a number in its name which indicates the disk onto which it should be copied. (For example, Setup-2.bin should be placed on disk 2.) The generated Setup.exe always goes on disk 1 along with the Setup-1*.bin file.

The size of each slice and the number of slices to create for each disk are determined by the values of the DiskSliceSize and SlicesPerDisk [Setup] section directives, respectively. Other disk spanning-related directives that you may want to tweak include DiskClusterSize and ReserveBytes.

Note that it is required that you set this directive to yes if the compressed size of your installation exceeds 4,200,000,000 bytes, even if you don't intend to place the installation onto multiple disks. (The installation will still function correctly if all the Setup-*.bin files are placed on the same disk.)

THANKS!

[Martijn Laan]

Hi,

Op 10-9-2025 om 16:55 schreef Dan Breyen:

As of today, In the current help I see that DiskSpanning has been extended.  Does this mean that it's available in 6.5.1, and we don't need 6.5.2?

The following is part of 6.5.2:

"The size limit of 2 GB for a single Setup.exe and for disk slices has been removed.

• The maximum size for a single Setup.exe without disk spanning has increased from almost 2 GB to nearly 4 GB, which is near the maximum Windows supports.
  However, disk spanning is still recommended for large executables due to slow startup times imposed by Windows, especially when the executables are digitally signed.
• With disk spanning enabled, the maximum disk slice size has been increased from almost 2 GB to effectively unlimited (9223 PB).
• The default disk slice size is still 2100000000, which is almost 2 GB. To update, you can simply set [Setup] section directive DiskSliceSize to max."

Greetings,
Martijn Laan