benners

It will be a while before I create a translation file, I want to get the GUI layout done first. WRT Windows Live, do you mean the messenger or other parts. I have tried again on a VM with an English version and I see and ARP entry for Windows Live Messenger, the size is 40.41MB, there are also 2 other entries for sign in assistant and upload tool, but they are made by their installers.

Thanks jinkazama, As I say it is only just starting off. I am looking at adding a few more things. 1. Patched files tab for files edited using the mess.be patch 2. A Tweaks tab that has various registry tweaks that can be applied to the msi or made into a reg file. These will be normal things like removing the minimize balloon tip that occurs when MSN is 1st run. 3. A tweaks tab for passport specific tweaks like disabling MSN today or showing time stamps in the conversation window. 4. A selection of icons found on the net that can be used for the sfx. 5. Extra gfx for the gui 6. Maybe translate it to different languages, This makes designing the GUI a bit of a ballache Cheers.

You can try yourself if you have the time here

WLM Creator (Windows Live Messenger 9 Creator) enables you to create a single switchless SFX that installs Windows Live Messenger 9 onto you PC. It can be used for everyday installs or as part of an unattended setup. The method used is based on the work of Shark007 and elajua and the original thread can be found here., so a big thanks to him and Shark for explaining how best to accomplish this.. To create the SFX successfully you need to have already downloaded and installed Windows Live Messenger 9 previously on your PC, this will ensure that the setup files will be located where expected. Using the program you can specify options for the SFX such as: title; icon; display level and compressions level. You can also include files that have been patched with A-Patch or MessPatch (Not available at time of writing) to add features or remove annoyances and choose from a selection of tweaks that will be applied to Windows Live Messenger 9 after installation. The help file is extracted when the program is run and pressing F1 while the program is running will open it. Change Log (Build 15) Updated - A-Patch to latest version. Download (2.80MB) Clicky

I just tried in three unattended installations and effectively, the uninstall entry is missing. I don't know why is this happening, though. I don't find this much important, but it is nice to solve all wrinkles. The way I did it was to delete the ARPSYSTEMCOMPONENT property in the Property table

If you want to know the exact language specific updates needed you can install office and sp3 then goto the Office update site, select Office Update in the left had column under updates and once your system is checked there will be a list of the required ones. You can also use this program to integrate the SP and the updates for you. There is also a help file with the latest update links for your version with the program. When you click the link just select your language from the web page.

Are people still interested in doing this. I ask because I am working on the Office Integrator and the next release will have the ability to do this. The process is this: select the fileformatconvertors.exe select the SP1 select the hotfixes press create The end result is an single MSI that has the lot integrated, there is also a reg file created that adds the entries to keep MU happy, I am trying to find a way to integrate this as well.

I know he is very busy at the moment, the forum problems are known to him but he hasn't the time to fix them. I'll IM\PM him and direct him to your post. PM sent on siginet forums.

Its probably the InfoPath problem, you can find some info here you can also find the Integrator that takes care of integration and the InfoPath problem here

It's probably because of this line REG ADD %KEY%\66 try changing it to REG ADD %KEY%\066

Some of the the installers are tricky. Innounp is not perfect and does not give a perfect representation of what the author used to create the installer. You can use Pascal code to offer options and do things like create variables and if an installer uses it there will be a file I think it is called compiled.bin. This will query user settings such as the users temp dir or the dir the user wants to install the program to such as {code_GetUserTempDir} etc but I don't know if you can decompile the code. The files with the numbers are a way to install the package for multi language installs or 32 and 64 bit versions of files, they probably track in the script to the language section or may have something like Lang:EN or Lang DE you can delete any languages you aren't gonna use and the files as well. Some scripts take a while to edit to remove the errors, I normally use discretion and delete the items causing the errors, an example would be a min OS version or remove the variables like {code_GetUserTempDir} as I know where they are bieng installed and in what language. The Architecture things are for the installers to tell it what 64bit Architecture the setup is allowed to run\install on and if blank it will run on any processor that can understand its 32bit code. Another thing some installers do is run the program exe after installation has finished to continue with the setup options. Kaspersky used to do it with the msi installer and not sure if Outpost runs the main exe once with a few switches to create profiles or extries, it's been a while since I messed with it.

It is an easy way, however when I create installers I like to make them as clean as possible, using this method if you don't delete the useless reg entries and temp files that are created during the install and by other processes running on the machine they are installed on the target machine, not a biggie just a bit messy. Some programs also install files to the users app data which is fine if it is intended for personal use but if you share with others or install on other machines some of the files may not be found. Another thing is if you want to register the program for a completely automated install I have seen some programs, one I can think of is FlashFXP, that generate random codes from various info from the system\user or machine and the registration code. Apart from the above I think InstallRight is a useful app and I personally use it when I want to try and create an Inno Installer from other installer types or to test the differences between my versions and newer ones as they are released.

Or Compression=lzma/ultra64 SolidCompression=yes in [setup] section of .iss file and use Inno to compile. I tried the Ultra64 but got an "Out of memory" msg when compiling with ISTool, never bothered looking into the prob just reset to previous values. I have 2GB of mem so it should be enough

Using ISTool Options - Compiler there are settings there for compression. I normally use Compression=lzma InternalCompressLevel=ultra SolidCompression=true

Inno Unpacker to extract the setup and ISTool to rebuild it. ISTool also needs Inno Setup to compile the script. It isn't often that a new Grabit is released so if you are unsure how to use the tools is would be easier to create a sfx with WinRAR and add a command to run after extraction to import the reg file. Some people can't be assed spending the time to learn stuff but there are a lot of setups that use Inno and you can always create your own to repack different installers. The installers do not always repack straight away as sometimes the script may need altering. I have attached the one I use for Grabit, it adds the files from the Grabit dir and registry info so you don't need to do a full update on every install, it should be just how you left it. Grabit.iss

Here are a couple of suggestions :- 1. Create a sfx of the Grabit dir, you can delete the articles and temp folders, export the Grabit info from the registry and import the reg file using the sfx. 2. Edit the Grabit original Inno setup and delete both entries under the InstallRun section 3. Create your own Inno setup that does what #1 does.

I am trying to add some registry keys to an msi and have problems with the keys being deleted. I am adding the keys to the Registry table and using a component that installs keys in the same hive. I have also tried creating a new feature and components as described here but again the keys are deleted. Does anybody know why this is happening or what I can do to make sure the keys stick. I have successfully added the keys to another table in the msi called Registry2 and they work so I think it may be a sequence thing but I would like to know why my keys are being removed in the first place. Cheers.

I extracted the files with v.20 which is specified as beta Here in the forum for innounpacker.

It's basically the same with v4 and Inno, You will need all the files in the program dir and 3 from sys32. I have attached the one I made as a reference. It is a version I use that adds the reg entries for IE protection and file changes for Firefox. you will need to edit it for your own needs. Spywareblaster.7z

If you can edit the script then you can manually add the program group name. I use ISTool and you can go to the program group tab under options and type it in, manually you could add the code below to the [setup] portion DefaultGroupName=ConvertX2DVD

This is what I use in my AutoIt script. C:\Program Files\Mozilla Thunderbird\uninstall\helper.exe /SetAsDefaultAppGlobal

No problem, if you want I can send you my script if it would help.

Hi mara, You could always use the ChainedInstall sections to add the fileformatconvertors and the subsequent hotfixes. I built my own slipstreamer for a friend who wanted extra features that weren't available in yours or Siginets' and to change a few that are, I have a tab where extra exe or msi files can be added to these Chained sections and they run after the office setup that way people can add there own MUI or the convertors without you editing your script each time. Hope this helps

I don't know if this works for all Installshield apps but most extract to a temp folder and install via an msi file, you can use these extracted files and pass parameters to the msi, this is provided that you know what they are. Programs like Orca (free) and InstallShield Studio etc (paid) can open the msi and you can try and figure out the parameters buy following the dialog boxes. Acronis Home works like this and it can be run and the serial entered by using acronis.msi PIDKEY=BLAH-BLAH-BLAH-BLAH-BLAH /qn The problem is knowing what the parameters are. You could try passing the arguments to the exe as some installers then pass them to the msi file after extraction.

This has worked for me so far [-HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\MyComputer\NameSpace\{FC9FB64A-1EB2-4CCF-AF5E-1A497A9B5C2D}]