SB8 Tips and Tricks: Hybrid 32-bit / 64-bit Installation

[NewsArchive]

-- Hybrid 32-bit / 64-bit Installation

This example demonstrates how to install different versions of a file based
on the Windows Operating System "bitness" (32/64-bit) from the same
setup.exe.

http://www.lindersoft.com/projects/Hybrid3264Demo.zip

There are multiple options available to handle the scenario. We'll use the
"Set Feature State..." script function in this example.

1. Set Installer Type to "Windows 32/64-bit (Hybrid)" in General
Information -> Generator Settings (see Hybrid1.png). If the installer is
running on a 32-bit OS, the installer is running in 32-bit mode (installs to
the 32-bit folders, uses the 32-bit Windows registry, registers 32-bit OCX,
etc.). If the installer is executed on a 64-bit Windows OS, the installer
is running in real 64-bit mode (installs to the 64-bit folders, uses the
64-bit Windows registry, registers 64-bit OCX, etc.).

2. Create two new 32bit and 64bit Features in the "Features" Visualizer.
Disable (uncheck) the "Install By Default" option (see Hybrid2.png).

3. In the "Files and Folders" Visualizer, add your 32-bit specific files to
the 32bit Feature folder tree and the 64-bit specific files to the 64-bit
Feature folder tree (see Hybrid3.png).

4. In the Script Editor, detect the "bitness" of the Windows Operating
System ("Get System Info -> WOW64 Status" script function). If the setup is
running on a x64 operating system, enable the 64-bit Feature ("Set Feature
State" script function). If it is running on a x86 operating system, enable
the 32-bit Feature (see Hybrid4.png).

On Windows 64-bit, the setup installs the 64-bit components and on Windows
32-bit it installs the 32-bit components (see Hybrid5.png and Hybrid6.png).

That's it :-)

--
Friedrich Linder
Lindersoft
www.lindersoft.com
+1.954.252.3910

--Helping You Build Better Installations
--SetupBuilder "point. click. ship"
--Create Windows 8 ready installations in minutes
--Official Comodo Code Signing and SSL Certificate Partner

[NewsArchive]

Norton doesn't like it . <G>

See Attached

Lynn Howard

[NewsArchive]

Send it to Norton in your bug report <g>

--

Russ Eggen
RADFusion International, LLC

[NewsArchive]

Lynn,

> Norton doesn't like it . <G>

That means one of your last virus definition update introduced a bug. I
would suggest you report it to your anti-virus vendor (they will most likely
request your .exe). Otherwise, sooner or later, all your compiled installs
will be blocked!!!!!

Friedrich

[NewsArchive]

Hi Friedrich,

This error was when I compiled and tested your hybrid project. I didn't run
it just Tested it.

My apps compile and test fine

Lynn Howard

[NewsArchive]

fwiw, kaspersky thought it was groovy.

Jeff Slarve
www.jssoftware.com
www.twitter.com/jslarve
I'll search help files & Google for you.

[NewsArchive]

He's a a cooler guy than Norton. Now Macafee is something else.

AVG didn't flinch at all.

Lynn

[NewsArchive]

Lynn,

> This error was when I compiled and tested your hybrid project. I
> didn't run it just Tested it.
>
> My apps compile and test fine

Yes, I understood that. But it has absolutely nothing to do with the demo
project per-se. It just means that your virus definition update is buggy.
Sooner or later, the same might happen with all your other setup projects!
You should report this to your virus definition update vendor so they can
fix it and make sure that your compiled setups will not be flagged by the
heuristic detection.

BTW, sometimes, a simple re-compile can help because this always generates a
different binary contents.

Friedrich

[NewsArchive]

BTW, here is a Google VirusTotal analysis for "Hybrid_32_64_Demo.exe"

https://www.virustotal.com/en/file/971f52cd8abce2214ce36d3c8159e73e0817833af1bb11804c 33d06aeecf8df3/analysis/1372748672/

Norton / Symantec definition update 2013-07-02

File name: Hybrid_32_64_Demo.exe
File type: Win32 EXE
Detection ratio: 0 / 47
Analysis date: 2013-07-02 07:04:32 UTC

Just a quick note. Lynn compiled the project and (of course) it has <5
users (because he never uploaded it) and was released <1 week ago (because
he compiled it yesterday). So the buggy SONAR heuristic "protection"
flagged his own private .exe.

Friedrich

[NewsArchive]

To exclude items (folders) from SONAR scanning and to work around the
Symantec "bug", you can do this:

Settings > AntiVirus > Scans & Risks Tab > scroll down and you will see
Items to Exclude from Auto-Protect and SONAR Detection. Click on the
Configure(+) Select Add, add the item and OK. Note you can click on the
folder to browse to the item you desire to add.

BTW, the "Hybrid_32_64_Demo.sb8" compiles the output into the current
project folder (and not into the per-user Documents folder).

Friedrich

[NewsArchive]

Thanks Friedrich.

I plan to do away with Norton in a few days when the evaluation period ends.

Lynn