Handling OEM Installations

[jkrasky]

Hello,

I now have our setup done for the next release of our application. This represents a complete migration away from InstallShield to InstallAware. So far, I am very happy with what I'm seeing. We have been able to implement functionality that we were never able to get working with InstallShield.

I have one last problem to get around. We have an OEM arrangement with a company where we change the splash screen for the OEM. This involves distributing a XML file and a BMP file for the splash screen that is installed only when those OEM customers install. With InstallShield, I was able to maintain two seperate *.ism files (their installer files) with different file configurations and build different setups for each maintaining the same package code in each. I could probably try that with InstallAware but I'm concerned it's going to mess up patching.

Another thought I had was to use a ZIP utility to make a self extracting ZIP which then ran the setup using a custom command line parameter to include an additional feature that installed the extra files needed for the OEM. However, it would be really nice to be able to handle this through the installer and not need this step.

Do you have any experience with people handling OEM situations with InstallAware? What is the best way to handle this? Again, the problem is at install I have no way of determining if someone is one OEM or another to select the right stuff to install unless I do it with the UI and people will select the wrong options.

Any suggestions would be great. Thanks!

[garyk]

I see nobody responded to the original question. Can somebody from Install Aware address this issue?

I have a very similar problem. We sell to OEMs. I use Uncompressed installations. I customize the paths, TITLE, and other strings by reading them from different INI files that I put in the Data folder for each vendor. But I want to use different HTML pages for each vendor, on the installer screens that display such pages. The problem is that all the content (HTML GIF, etc) must be compiled into the resource file. And the build in browser will not open any URL outside the resource file. At the moment I have to compile a different build for each vendor.

Does anybody know if there is a way around this limitation? Does Install Aware plan to fix this hindrance?

[MichaelNesmith]

You can always copy files in to $SUPPORTDIR$ using Call DLL Function and CopyFileA in kernel32.dll to customize the necessary bits at runtime.

[garyk]

It work
Wow. I am soooo pleased.
Thanks.

[jkrasky]

Hello garyk,

I'm hoping I can get some more information from you about how you're doing this saying its working for you.

The problem I can't get around is determining which files to copy based on which OEM. I have no idea when setup is launched if the copy is a non-branded or a branded copy. I could use a user interface dialog but that seems extremely error prone.

How are you making this distinction?

Thanks!

[garyk]

Very importantly, I use "uncompressed layout" which gives me a lot of control over the installer.
Lets say I use image1.gif.
I put a default image1.gif under Support Files and build the installer.

Then for each OEM I put another image1.gif file under Release\\Uncompressed\\Data. (refered by $DATADIR$)

Then the first thing I do in the installer script is to delete image1.gif from $SUPPORTDIR$ and copy $DATADIR$\\image1.gif to $SUPPORTDIR$\\image1.gif

So in essance I have only 1 installer, and distribute it with different gif files.
Aurica.
Of course u must use uncompressed for this.

See the File Attached:

<a>IA.JPG

File Attached:

IA.JPG