mooms

Please, fix the issue with IE integration order before releasing 1.4.1.29, so we can test it before the incoming patch Tuesday.

Yes, see second rule. Filenames for Windows 7: IE9-Windows6.1-KB2898785-x64.msu IE9-Windows6.1-KB2898785-x86.msu IE10-Windows6.1-KB2898785-x64.msu IE10-Windows6.1-KB2898785-x86.msu IE11-Windows6.1-KB2898785-x64.msu IE11-Windows6.1-KB2898785-x86.msu If you were thinking about KB2898785 for IE10 in Windows 8 & for IE11 in Windows 8.1 there is no problem, they are regular Windows updates. IE10 is part of Windows 8, IE11 part of Windows 8.1, so their updates don't need any particular order or prerequisites as far as I know. (like IE6 for XP, IE7 for Vista, and IE8 for 7). Edit: To be more idiot proof, maybe you can also add a warning if Win Toolkit detect mixed versions of IE files, like we see here. (only a concerns for Windows 7 so far).

Yes. Its is much simpler for everyone. If I remember Ricaneaga have made a similar request recently. Edit: yes, see here.

I suspect the only mandatory thing is IE main cab first then all the others cab/msu related after it, with no particular order. You should code something base on these three rules: First rule: - If filename [*.exe] starts with the string ie (case insensitive) then it is IE Setup: + Extract it to a temp folder and delete the file named [*support*.cab]. + Add all others msu/cab in temp folder to integration list with respect to the second rule. Second rule: - If filename [*.cab][*.msu] starts with the string ie (case insensitive) then it is IE main cab or language pack or hyphenation or spelling pack or IE update. + Move the main IE cab after all other updates. + Move all others after the main IE cab. These two rules should do the trick for IE9/10/11(12?) and it will be much simpler to maintain. You could visually representing that in Win Toolkit GUI by creating an IE group at the bottom of integration list.

That's showed in my image. My way (I use cab versions of IE11): - IE main cab, then MSU/cab addons, then IE update(s). I rename the files with Z+number in front to achieve this in 1.4.1.27. (see image). The same with IEsetup.exe: - The cabs/MSU of the extracted IEsetup.exe (IE-Win7.CAB first then others msu/cab*), then IE update(s). * Minus IE_SUPPORT_*.CAB that is not needed in integration.

@Lego: If you move IE and all the related updates/addons to the end of the integration process, you should not worry about prerequisites. That's the smartest and simplest way , because months after months, more and more updates will be superseded and because of this the list of prerequisites will be constantly changing. Win Toolkit 1.4.1.27 does not recognize IE11 cabs and let me integrate them at the end: that works beautifully ! Because an image worth thousand words:

You have to understand that QFE/LDR hotfixes are not meant to be used in general usage (that's the purpose of GDR). Their purpose are to fix particular bug(s), and they are only distributed by MS by express demand of a customer (generally a sys admin, not the average Joe). They are not meant to be blindly installed/integrated as you are doing ! QFE/LDR hotfixes are not as much tested as GDR, and they can do more harm than good (new bugs, regressions, etc...) if not carefully and wisely used. Even GDR updates are sometimes buggy and must be removed for Windows Update.... Also, as Lego as stated, they are many in your list that are superseded, and it is very time consuming to maintain an up-to-date list of all KB. The names are pretty self explanatory: GDR means General Distribution Release LDR means Limited Distribution Release. QFE, the ancient name of LDR, means Quick Fix Engineering. If you really want as much update as possible, use this (and only this): http://forums.mydigitallife.info/threads/44645-Windows-Hotfix-Downloader-5-1

I don't see any advantages to integrate as much as possible, only inconveniences

Lol, more than 700 updates, that's insane ! also, your'e integrating IE9, IE10, and IE11, no wonder it doesn't works ! dareckibmw is right, follow his instructions and you will have a perfectly up-to-date (with the least bloat possible) Windows 7 image.

Seems a faulty USB pen drive.

Hi Lego, Tested beta 5 with Home Premium X86 French: Integration was OK, but I had two errors with RunOnce installer: error1: It is the Root Update installer by Microsoft that can be downloaded here: http://www.download.windowsupdate.com/msdownload/update/v3/static/trustedr/en/rootsupd.exe Works fine with Win Toolkit 1.4.1.27 or if launched manually (without any switches). Command line options ( "/Q" is not needed to launch it silently) Error 2 (it seems the switch "/S" was not passed to the setup) This is an AIO switchless installer made with my maker. Again, works fine in Win Toolkit 1.4.1.27 or if launching "manually" (tested the installer in the same virtual machine). Also, I have found that the silent installer of Flash Player (made with my maker) only installed the plugin version, not ActiveX one. This one is weird because the Active X version is supposed to be installed before the Plugin version. Again, works fine in Win Toolkit 1.4.1.27 or if manually launched. . There is a problem with the new Runonce installer, in particular with switches not passed to the setups. The last two problems have in common to be 7-zip SFX installer, but nearly all installers you can see in the last image are similar and as you can see they have been installed. Others programs and updates installed fine. New function with "Drivers" folder seems to work, but as it is a virtual machine I can't really say. Log have been uploaded to you after the completion. Logs and last session on my disk: WinToolkit141-29Beta_5.zip

Voici un script batch qui va télécharger Thunderbird dans la langue et la version de votre choix, puis modifier l'installateur pour le rendre silencieux. Il peut aussi créer un AddOn RVMi/nLite. Mode d'emploi: Extraire le contenu de l'archive dans un dossier Lancer Thunderbird_SFX_Maker.cmd ou downloader.cmd Vous pouvez aussi ouvrir Thunderbird_SFX_Maker.cmd avec notepad et modifier certaines variables pour éviter une ou plusieurs questions (voir fichier readme). Les fichiers sfx sont créés dans le dossier output Les fichiers d'installation originaux sont téléchargés dans le dossier download Thunderbird_SFX_Maker_5.5.zip SHA1: D6D00BDE18357D992BFA8E8C0182D0A80093AC17 Taille: 2,93 Mo

Here is a script that will download Thunderbird in the language/version of your choice and create a switchless installer (and nLite/RVMi AddOn if you still use it). How-to use: Extract the content of the archive in a work folder. Simply run Thunderbid_SFX_Maker.cmd You can also edit the file to skip one or more question. See the included Readme file Thunderbird_SFX_Maker_5.4.zip SHA1: 3af6498fc4505e75b409eb9b6cf4cbb3209532fb Size: 1.69 MB

This tutorial is more than 6 years old, no wonder some links are dead ! @ricktendo: If you don't want/don't have time to update it, I can if you wish. The 7zsd linked is the first post is a very old version, get latest stable version here: 7zSD A cmd file is a text file with the extension changed, so you just have to create a new text file and paste the content, save it then change the file extension (*.txt to *.cmd) About the content of the cmd file: this cd Bin..\7za a -mx=9 "..\Program.7z" *cd ..can be simplified to this: 7za a "Program.7z" ".\Bin\*" -mx=9So your cmd file look like this: upx --ultra-brute 7zsd.sfx 7za a "Program.7z" ".\Bin\*" -mx=9copy /b 7zsd.sfx + Config.txt + Program.7z Program_Name.exedel Program.7zThe first line upx --ultra-brute 7zsd.sfx is optional, (UPX is an executable compressor, this commands is used to compress 7zsd.sfx) so your cmd file should only have these 3 lines for beginning: 7za a "Program.7z" ".\Bin\*" -mx=9copy /b 7zsd.sfx + Config.txt + Program.7z Program_Name.exedel Program.7zAlso, all the steps that involve Resource Hacker are optionals, you should first familiarize yourself with these things, then you can change the icon, etc.... Two SFX maker (if you prefer using a GUI): http://sourceforge.net/projects/sfx-maker/ http://www.isoft-online.com/

I have two requests, in order of importance: 1. Make the list of executed apps inside an text file instead of inside the registry to allow easier editing. Ideally in the root of the installed apps folder, so it can be easily edited after (no need to mount the wim file), in case of mistake/new versions/etc.... 2. Allow translation for the RunOnce installer. Again a specifically named text file seems a good idea. There is only a few sentences to translate, so it can be embedded in the exe I suppose. I can help, at least for French translation. I also support the requests of RicaNeaga.

Version 2.5 finale. Lien dans le 1er post. Distribuée sous forme d'un exécutable et d'un fichier batch. Quoi de neuf depuis la version 2.2:

Version 2.5 final released as and exe and as a batch.(if you want to know how it's done, or change some parameters) Link in the first post. What's new since version 2.2:

It's worse than that Kel, we must select again the theme in WinRAR options, simply opening it don't do anything. In Windows 7, UAC is triggered when WinRAR install a theme, but not when changing it, kinda weird. Renaming the original installer is needed to be executed silently by the SFX. also respecting the old 8.3 convention is a good idea for XP. The renaming was also made by older versions, but the final name or the SFX was static. The naming we talk here is for the SFX and the AddOn (and ENTRIES_WinRAR.ini inside it). It took me a certain time to properly extract the version and lang values. (I'm a beginner in the "art" of batching). x86 are named this way: wrarVVVL.exe x64 are named this way: winrar-x64-VVVL.exe We have two variables: VVV is the version number, in (almost*) all versions it is three numbers without dots. example WinRAR 5.01 is named 501, so I had to add the dot for correct naming. (*some versions in version 5.00 and earlier had only 2 numbers for the version, in this case the renaming will fail, but it is only cosmetic. Versions 5.01 are all properly named so nothing to worry about.) L is the language, between 0 (if English) and 6 letters. The maker will take up to 7 characters. The maker will parse the two values and make like this: V.VV-L (notice the dot) I could have used the entire original name of the installer and rename the final SFX after it, maybe with SFX_ at the beginning, it would have been much simpler to do, but I think it is more elegant as it is now (and parsing the values is necessary to populate correctly the file ENTRIES_WinRAR.ini ). You can change how the SFX & AddOn are named (like removing the "-" between the two variables) if you open the batch, search for these strings: %VRS%-%LNG% and remove the "-" between the two variables. You can replace by anything you want. (but don't mess with variables unless you know what you are doing) All the content of the binary folder, except empty folders, is compressed and added to the SFX, the maker is designed this way. In case of a single x86 installer, only version and lang values are in the name of the SFX & AddOn. In case of a single x64 installer, "x64" is also added because of its incompatibility with Windows 32 bits. In case of both x86 & x64 installers, "AIO" is also added to reflect this. In case of mixed language/version number in the AIO version, the higher version number is used, and the 32 bits language value is used. If you put more than one x86 and/or one x64 version in the binary folder, only the first of each will be installed, because the renaming is done on the first matching name the batch will found. If your installers are already renamed rar32.exe and/ or rar64.exe, the batch file will fall back to the "old way", SFX and AddOn will have generic names like in v2.3 and earlier. (no variables used except the date in ENTRIES_WinRAR.ini) If the installer have some exotic names (or are really missing), the maker will exit with a text file popping up. (try it, it is really cool, I'd "stolen" the idea from vmanda's Firefox maker :pirate: many thanks to him :thumbsup: ) It should be possible to install the correct version accordingly to the language of the OS, but this suppose to rename each installer with correct LCID, and it will exponentially complicate the batch file and/or the sfx config. It is way beyond the scope of this maker, and if someone will really need to do this, he must have the skills to do it itself. I've realized when answering you that I forgotten to take care of the case of the English version, where the L value is missing. It is now corrected with test3 (if L value is missing, it is set to "en") WinRAR_SFX_Maker-v2.5_test3.7z edit: link removed.

v2.5_test2: What's new: WinRAR_SFX_Maker-v2.5_test2.7z edit: see below for new version

You should search on the website of the app. A Google search can help sometimes. You can also try Universal Silent Switch Finder. You can easily test the switch(es) by making a shortcut and adding the switch(es) at the end of the path. Example on Windows 7:

@ianymaty: I see what you mean, theme is applied but the icon is the default one until you have selected the theme again in WinRAR. After investigation wth RegShot, it appears the icon is a per user setting, with full path (we need variables), of the user folder, so it is unusable for a generic installer. Example on Windows XP, with an user named "xp" and the theme "sscom_winrar_48x_v2" Windows Registry Editor Version 5.00[HKEY_CURRENT_USER\Software\WinRAR\Interface\Themes]"Activepath"="sscom_winrar_48x_v2"[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\WinRAR archiver]"DisplayIcon"="C:\\Documents and Settings\\xp\\Application Data\\WinRAR\\Themes\\sscom_winrar_48x_v2\\Setup.ico"[HKEY_CURRENT_USER\Software\Classes\WinRAR\DefaultIcon]@="C:\\Documents and Settings\\xp\\Application Data\\WinRAR\\Themes\\sscom_winrar_48x_v2\\RAR.ico"[HKEY_CURRENT_USER\Software\Classes\WinRAR.REV\DefaultIcon]@="C:\\Documents and Settings\\xp\\Application Data\\WinRAR\\Themes\\sscom_winrar_48x_v2\\REV.ico"[HKEY_CURRENT_USER\Software\Classes\WinRAR.ZIP\DefaultIcon]@="C:\\Documents and Settings\\xp\\Application Data\\WinRAR\\Themes\\sscom_winrar_48x_v2\\RAR.ico" But even with this exact reg file merged by the sfx, the WinRAR icon is still the default one, so it is not something I can fix. Anyway, reg import is not a new feature: I would to know if the new features introduced in v2.5 works as intended for everyone.

I made a new version. What's new: I have tested it with multiple scenarios and I don't see any bugs, but because it is much more complex than the previous versions it needs to be tested much more, so please test it and report how it works: - If the making & install works (specify your OS/arch/lang) - If version number and language are correctly added in the name of the SFX & AddOn and in the file ENTRIES_WinRAR.ini in the AddOn, This time it's a batch file, so you can open it and see how it works. I'm open to any suggestions for improvements. P.S: don't get confused with the two similarly named folder bin and binary, you must put the setup(s)/themes/license in the binary folder as before ! (bin folder is used to store files used by the batch file) WinRAR_SFX_Maker-v2.5_test.7z edit: see below for new version

Utilisation: Lancer CCleaner_Maker.cmd et le maker va télécharger le setup slim de CCleaner et créer dans le dossier output: Un SFX qui installera CCleaner silencieusement et dans la langue du système. Un AddOn pour RVMi/nLite qui contient le même sfx (désactivé par défaut). Si vous copiez le fichier ccleaner.reg dans le dossier ccsetup, il sera automatiquement exécuté par le setup. Le fichier reg fourni désactive la vérification de màj et le monitoring système, ainsi que le partage des données avec des tiers. Vous pouvez éditer le fichier reg pour y ajouter vos propres tweaks. Si le setup Slim de CCleaner n'est pas disponible le maker téléchargera alors la version standard. Si le téléchargent n'est pas possible, il vous proposera de placer le setup dans le dossier ccsetup. Taille: 2,17 Mo SHA-1: f402fb73b79cd4becaea35fb2e54d5f5424a240f CCleaner_maker_3.9.7z

How to use: Run CCleaner_Maker.cmd and the maker will download the slim installer (or Standard if Slim is not found) of CCleaner and create a silent installer with commands to install it in the language of the operating system (and an AddOn for RVMi/nLite if you want) in the output folder: Features of the installer & AddOn: - Stock installer repacked with commands to make it silent. - AddOn compatible with nLite and RVMi. - SFX compatible with WinToolkit and RVMi. - Compatible from XP to 10 32/64 bits. - Detect your language and configure CCleaner automatically. - You can choose to keep or delete Desktop Icon (see Readme). - Automatically delete all autoupdate/autostart & data sharing "features" (can be configured) If you put the file "ccleaner.reg" in the ccsetup folder, it will be run automatically by the setup. Currently it disable the check of newer version of CCleaner and disable autostart and system monitoring. You can add any tweaks you want. Because the slim installer is available a week or two after the release of a new CCleaner version, the script will first try to download Slim, then if it's not available, it will try to download Standard version instead. You can also manually download the (slim or standard) installer and put it in ccsetup folder, when the script will ask for. Size: 2.17 MB SHA-1: ee713e98c6d5f08c1a9a7a663a1bdf8ab54243cb CCleaner_maker_3.7.1.7z

Grosse MAJ du maker: - Un AddOn pour nLite/RVMI est créé en même temps que le SFX. - Ajout du n° de version dans le nom du SFX et de l'AddOn - Gestions des erreurs