Suggestions for Dual 32bit and 64bit Installation

[Hector Santos]

For all these years, I had inno scripts for 32 bit new installs and updates (already installed). 

I have 64 bit images (exe & dll files) for PARTS of the total system and the 64 images was provided as overwrites for an existing 32 bit image setup via an online update system. Now I would like to put this into a inno setup.

I am wondering the following:

1)  Should I create a separate "64 bit installation" setup?  

2)  Should I modify existing 32 bit script with types, components, etc to OFFER a 32 vs 64 bit install option? a separate "64 bit installation" setup?  

All operations will always have the 32 bit client side set of files and the 32 bit server side files too for a pure 32 bit install..  But the new option to install the 64 bit server side files is now available the update system.

I am just trying to reduce the complexity.  99.99% of the operators are not going to be switching back and forth in the 32/64 bit setups.   Either they are going to use pure 32 bit because their OS is only 32 bit, or they MAY use the 64 bit images on a 64 bit ready OS. I made it easy via an online update it and that was SUPER complex to get 32 vs 64 bit images all correct for the silly option to go back and forth via the online update.

I just don't its worth it for creation of an EXE.   At worst, there were 2nd EXE that installs the 64bit images for them plus the VS RTL 64 bit as well.

Your thoughts? Suggestions? 

Thanks

[Martijn Laan]

Take a look at the 64BitTwoArch.iss example script. See http://jrsoftware.github.io/issrc/Examples/64BitTwoArch.iss

Greetings,
Martijn

Op 21-9-2021 om 17:03 schreef Hector Santos:

--
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 on the web visit https://groups.google.com/d/msgid/innosetup/1c79f07a-24c5-4307-8613-d3b3443cfd57n%40googlegroups.com.

[santosh]

Ahh, ok, so the suggestion here is to go ahead and create a 2nd specific 64 bit  setup and use this script to launch the appropriate one?  

Does this mean the setup.exe size will be near double?

The current 32 bit setup.exe is 79mb.  With the VS RTL 64 file added plus the extra 64 bit source files added to the script, a test compiled shows a total of 90mb.  So in the combined two arch script, it would be combined the two the setup.exe will be ~160mb?

Thanks

[Gavin Lambert]

On 22/09/2021 4:47 am, santosh wrote:
> Ahh, ok, so the suggestion here is to go ahead and create a 2nd specific
> 64 bit  setup and use this script to launch the appropriate one?

No, not at all. Did you look at the example script?

[Hector Santos]

Hi, Yes I did download and studied it as best I can. I believe it requires the more recent compiler - {autopf} was not known.  I'm using Inno 5.5.3  due to legacy XP/2003 support.   When I do upgrade, I will have to maintain two setups, one current, one xp/2003, but I will stay with 5.5.3 for this production.

I think I understand the logic in the script. My platform is installed in its own directory, c:\wcat. The macros pf, pf64 or autopf are not required.  So thanks.  I got it.

I decided to go with adding 64 bit options to the components, files and  types to the existing 32 bit set.   Since the RPC server side can be 32 or 64 bit and the RPC client side only 32 bit, it should only add 64 bit images as overrides to the specific existing fixed component "wcBase\ServerFiles."  But to provide a manual 32 vs 64 bit install option I have:

[Components]
Name: "wcbase\ServerFiles"; Description: "Wildcat! Server Files"; Types: Full Custom Upgrade UpgradeDos ModemOnly InternetOnly; Flags: exclusive
Name: "wcbase\ServerFiles64"; Description: "Wildcat! Server 64 bit Files"; Types: Custom Upgrade UpgradeDos InternetOnly Install64bit Full; Flags: exclusive

Getting the function or macro to detect 64 bit OS to enable the 64 option or not is the next task to read up on.  I think it is Is64BitInstallMode() or IsWin64()? 

Thanks again.

--
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 on the web visit https://groups.google.com/d/msgid/innosetup/63f0008a-284a-9df8-1354-5e2e35f33929%40mirality.co.nz.

--

hls

[Gavin Lambert]

On 22/09/2021 5:41 pm, Hector Santos wrote:
> Hi, Yes I did download and studied it as best I can. I believe it
> requires the more recent compiler - {autopf} was not known.  I'm using
> Inno 5.5.3  due to legacy XP/2003 support.   When I do upgrade, I will
> have to maintain two setups, one current, one xp/2003, but I will stay
> with 5.5.3 for this production.

The example script is present in that version of Inno too. And of
course that version only contains content that works in that version.

[Hector Santos]

Ok, let me check ... yes, it sure does!  I've been using inno since 5.2.3 and this is my first 64 bit "CD" setup production.  I have it done (script worked out) for this release with Inno working in 32bit mode installing mixed 32/64 bit images. I don't think getting file version info of 64 bit images should be a problem.

But I added the ArchitecturesInstallIn64BitMode=x64 to see how it changes the setup and noted that I will need to work out any 32 vs 64 registry logic. In a test build, it thought it was a new install when it was not.  Going to read about this now. 

It also reminds me to look at the 32/64 or 64/32 spawning of a [RUN] process for registration and initial configuration. 

So more work, thanks.  :-)

--
You received this message because you are subscribed to a topic in the Google Groups "innosetup" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/innosetup/_bT8MmfIOCY/unsubscribe.
To unsubscribe from this group and all its topics, send an email to innosetup+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/innosetup/fb751f71-aa43-080d-1975-591f61ae7b41%40mirality.co.nz.

--

hls