SNMsynth script builds highly customizable .NET unattended installers/nLite-RyanVM integrator addons, supporting all latest .NET framework versions, and all its hotfixes and langpacks for win 2K/XP/2K3 x86 up to date. Besides, it provides fixes to some .NET annoyances, allow removing outdated subcomponents and optimizes installers size. The building process is a 6 step process, a lot flexible and easy to set up (see Instructions section), allowing to build the installers/add-ons to your liking, giving you full control about when to install what, and how. Don't be afraid of the guide, is made to be comprehensive.

The stuff in this topic is based in the excellent Silent .NET Maker script by Tomcat76 to which it adds new features or simplify it, but the basis are the same administrative installs. We must thank Tomcat76, Oleg_Sch, Acheron, gora, mickmack, antoineL, Stephan, YumeYao, user_hidden and Yzölw for providing solutions to this method, and DarkShadows, SipTomi, CEoCEo, bruno32600, ercofra and Dumpy Dooby for fixing bugs; and all the people who helped pointing bugs, testing and making suggestions in the production of this script (you'll find their posts in this and SNM threads). I want to specially thank Aaron Stebner for his splendid blog and solutions it provided to this method.

You can have generic -ready to use- solutions if you prefer not to build custom packets.
Following are english solutions: YumeYao's 3.5 SP1 family; user_hidden's 3.5 SP1 family (mirror), 1.1 SP1 (mirror), 2.0 SP2 (mirror), 3.0 SP2+3.5 SP1 (mirror); OnePiece's 1.1 SP1; or RogueSpear's various flavors (many outdated, but worth to mention, have served as basis to some in this list).
You can have localized solutions also. Chinese: YumeYao's 3.5 SP1 family. Dutch: Raoul90's AIO and Stephan's -1.1- and -3.5 SP1 family-. French: Moom's -3.5 SP1 family- and -AIO-. German: Ganesha's 3.5 SP1 family, Sereby's AIO. Italian: OnePiece's 1.1 SP1.
You might want english x64 solutions also, like HJW's 3.5 SP1 family or radix's 3.5 SP1 family. There's even a x64 german packet: Sereby's x64 AIO


SNMsynth builds custom unattended installers with the following features:

• Optimized for each win version, compatibility among versions has practically ended with last optimizations.
• Works with custom default switchless mode out of:
  - Passive: Unzipping and installing progress bars, no cancel button.
  - Silent: No feedback, even from unzipping. To supervise the installing you have to use Task Manager or command line tasklist.
  Switches can be used to change default behavior. Even nLite/RVMI add-ons can use them, see Installing section bellow.
• Are compatible with HFSLIP when used switchless.
• Can be packaged as T-13 nLite/RyanVM integrator add-on(s). Installers can be extracted from them.
• .NET frameworks can be packaged in a flexible way. All framework versions can be merged All In One (AIO) in a installer, or subsets of them; or you can build single framework installers, with or without hotfixes and langpacks (any combination). Moreover, you can remove certain framework subcomponents, to get rid of them or to be able to install them from another updated sources without duplicating files. See SNMsynth.ini section bellow.
• Can integrate multiple languages for each framework #.# version, intended for MUI or servers.
• Avoid win/ms update to push KB928416 (3.0 SP0 langpacks) and KB829019 (2.0 SP0 PT-BR langpack) pointless updates when the right upper version langpack is installed.
• Avoid old problem when .NET 3.0 is installed at T-13 with SVCPACK.inf or T-13 nLite/RVMI add-ons, and later uninstalling (everytime) getting:
  Error 2004. Method GetFontCacheDataFolder failed. HRESULT: 0x80004005
  Error 2004. Method SHGetFolderPath failed. HRESULT: 0x80004005
  SNMsynth installers/add-ons containing 3.0 SP2 (only) framework avoid these errors, having a clean install/uninstall. I found these errors begin with the "Font Cache Service" installer/uninstaller DLL from 3.0 frameworks, which "RemoveFontCacheData" entry point, has probably a bug and it's not able to resolve CSIDL reference for font cache file folder when tries to remove previous font cache file.
  For 3.0 SP1 users problem remains, so don't install 3.0 SP1 (and hence 3.5) at T-13 unattended, because you get 2 dialogs for the errors above that pause the unattended install. Not doing this, you still get these errors dialogs when you uninstall 3.0 SP1 framework, and the font cache file is removed, but this is not harming at all.
• Slims down .NET 3.5 SP# and its langpacks to the maximum through YumeYao's method. Besides size reduction, it also means that the first step of uninstall from add/remove programs, a superfluous installer framework that is used to check for updates on original installers, is removed making uninstall quite faster, in 2 clicks (as the other frameworks/langpacks versions).
• Avoid win/ms update to push .NET 3.5 SP1 Family update KB951847 for WXP/2K3. KB951847 is an ad-hoc update (variable size depending on components included) prompted via win/ms update to complete your own installed .NET set with the parts not installed of the following set (3.5 SP1 family):
  2.0 SP2 + NDP20SP2-KB958481-x86.exe + 2.0 SP2 langpack (matching OS language)
  + 3.0 SP2 + NDP30SP2-KB958483-x86.exe + 3.0 SP2 langpack (matching OS language)
  + 3.5 SP1 + NDP35SP1-KB958484-x86.exe + 3.5 SP1 langpack (matching OS language)
  So actually doesn't add anything novel. SNMsynth installer(s)/add-on(s) let you do seamless install/remove operations of each #.# SP# framework from the above set individually, avoiding update system to push KB951847 (for the framework versions left from the set); but this is only true if installer(s)/add-on(s) including each framework version of the above set, also include its related hotfix and langpack (matching OS language), i.e. all components in each line from the above set included in the installer/add-on for that framework version.
• Can completely remove, or simply avoid to install without removing, .NET Framework Assistant 1.0 add-on for Firefox (and its companion add-on, see next link). This add-on adds ClickOnce to Firefox, and it is installed with .NET 3.5 SP1 (unless you remove it, or avoid it with a switch), that also adds it to IE (always). Some people dislikes this add-on in their FF because its installing is not advertised, and it opens a new, sometimes undesired, door for software; and even after KB963707 was issued to solve urgent problems with it, there's still some annoyances.
• Precompile assemblies. This means installing last longer but doesn't left unfinished tasks to complete later on idle time (default .NET behavior).
• Create install logs under %TEMP% folder (except when installing at T-13 or later from GUI setup, in which case it get created in %SYSTEMROOT%), with filenames with the following pattern: NETFX11install.log, NETFX11lnginstall.log, etc. thus removing old install logs on each run, and allowing easy identification. Uninstall logs keep MSIXXXXX.log random pattern under %TEMP% folder.
• Remove pointless modify and repair buttons, in addition to all subcomponents and hotfixes useless entries under "Add/Remove Programs" list (only in the list). I.e., after installing, only frameworks and langpacks will be listed but not hotfixes or subcomponents, although they'll get installed and identified by MBSA and win/ms update.
• Have descriptive filenames specifying target OS version, frameworks versions and languages, except for multilanguage described with -multi suffix for any combination of languages.
• Workaround install error 1935 for 1.1 and 3.0 (last one not documented in the article).
• Installer databases (.msi files) are quite self-contained with all fixes (.mst files) preapplied, but other work is done by install scripts outside .msi process. YumeYao's solution to remove deadlocks that avoided to install directly from .msi files (not a recommended practice) is appplied, thus ADDEPLOY property is no more needed in the install commands.
• W2K only components are automatically removed from XP/2K3 installers/add-ons, optimizing size (YumeYao's solution).
• Remove .NET 1.1 and 1.1 langpack (useless) english configuration/wizards items from Administrative Tools menu when langpack is used.
• As reference, with best compression, without removing subcomponents, and for XP, the complete set of english frameworks+hotfixes installers, extends around 45 MB; and 43.4 MB merged AIO . And around 47 MB and 45.2 MB AIO respectively, with 1 langpack and hotfixes, depending on language. Slightly higher sizes when packaged into nLite/RVMI add-on(s).

Supported Files List.

YOU DON'T NEED TO DOWNLOAD ALL THIS!. Only .NET managed software requires .NET framework(s), and among these, not every .NET software requires the same .NET #.# version. Having installed 2.0 SP# is mandatory to install 3.0 SP#, and both to install 3.5 SP#. In many cases 2.0 SP# could be enough for the average user (I only use this version), but developers usually updates his software requirements to an upper .NET #.# version; and you can still find applications requiring 1.1 to work, but only a few rare, as many 1.1 applications works on 2.0 too. So all #.# versions are needed to cover all possible scenarios, but it is quite probably you wouldn't need 1.1.
"NET #.# SP#" is not refering to a SP standalone, but to a complete framework version updated to that SP#. So choose your desired update condition for your frameworks (SP# and hotfixes).
Script can process 2.0 SP# from individual or redistributable packet, download one or choose which one to process through _SNMsynth.ini settings.

----- UPDATED FILES:

• .NET 1.1 Redistributable Package (dotnetfx.exe) for 2K/XP installers/add-ons only.
• .NET 2.0 SP2 package for 2K/XP/2K3 installers/add-ons (eventhough the donwload page states 2K is not supported).
• .NET 3.5 SP1 full redistributable (dotnetfx35.exe 231 MB), contains 2.0 SP2, 3.0 SP2 and 3.5 SP1 frameworks. 3.# frameworks are not processed for 2K installers/add-ons.

• .NET 1.1 langpacks for 2K/XP installers/add-ons only. For multilanguage installer(s)/add-on(s), add an identifier suffix of your choice to filename to allow multiple 1.1 langpacks in the work folder.
• .NET 2.0 SP2 langpacks for 2K/XP/2K3 installers/add-ons (eventhough the donwload page states 2K is not supported).
• .NET 3.5 SP1 redist langpacks (dotnetfx35langpack_x86XX.exe -- note it has the same filename as 3.5 redist langpack), contains 2.0 SP2, 3.0 SP2 and 3.5 SP1 framework langpacks. 3.# framework langpacks are not processed for 2K installers/add-ons.

• NDP1.1sp1-KB867460-X86.exe hotfix for 2K/XP installers/add-ons only. Actually this is the SP1 for 1.1 framework but it installs as any regular hotfix. It's mandatory to apply any of the 1.1 hotfixes bellow.
• NDP1.1sp1-KB953297-X86.exe hotfix for 2K/XP installers/add-ons only.
• NDP1.1sp1-KB971108-X86.exe hotfix for 2K installers/add-ons only.
• NDP20SP2-KB971111-x86.exe hotfix for 2K installers/add-ons only.
• NDP20SP2-KB974417-x86.exe for 2K/XP/2K3 installers/add-ons.
• NDP20SP2-KB958481-x86.exe, NDP30SP2-KB958483-x86.exe and NDP35SP1-KB958484-x86.exe hotfixes. .NET 3.# hotfixes only for XP/2K3 installers/add-ons.
• NDP35SP1-KB963707-x86.exe update, only for XP/2K3 installers/add-ons. It adds an uninstall button to .NET Framework Assistant 1.0 Firefox add-on. Not needed if you avoid to install this FF add-on through _SMNsynth.ini setting.
  
  Files from this group are used to build SNMsynth installers/add-ons in case following subcomponents are not removed through _SNMsynth.ini settings. They update .NET 3.0 SP# (not to build 2K installers/add-ons) annexed subcomponents (not part of the framework itself but packed together, pre-required sometimes) :
• MSXML 6.0 SP2. MSXML6 subcomponent, can be updated with this file. This let you avoid to install KB954459 later. Simply put it in the work folder. For XP/2K3 installers/add-ons only. Only one language can be used (it's not a limitation of this method) choose the one you prefer.
• KB971276 for XP and/or for XP/2K3 respectively. 2K3 file can be used to patch XP one with the most recent files from it. So for XP both files can be used (YumeYao's solution improved).
  
  RESTRICTED HOTFIXES. These hotfixes are not deployed through win/ms update or direct ms download link, but only after asking MS for them. They are not needed to stop update system prompting .NET hotfixes. It fixes uncommon errors, so up to you to use it or not. Only X86 versions of the restricted hotfixes are supported, obviously.
• .NET 1.1 restricted hotfixes.. For 2K/XP installers/add-ons only.
• .NET 2.0 SP2 restricted hotfixes. for 2K/XP/2K3 installers/add-ons.
• .NET 3.0 SP2 restricted hotfixes. for XP/2K3 installers/add-ons only.
• .NET 3.5 SP1 restricted hotfixes. for XP/2K3 installers/add-ons only.
  
  Files from this group are not used to build SNMsynth installers/add-ons, but to preinstall updated Visual C runtimes 8 and 9, and WIC when you remove pre-required outdated ones from .NET frameworks in SNMsynth installers/add-ons. See _SNMsynth.ini section bellow. Choose files that better adapts to your needs:
• Visual C++ 2005 SP1 (VC 8) runtimes.
• Visual C++ 2008 SP1 (VC 9) runtimes.
• RogueSpear's english VC8+VC9 installer.
• Code65536's runtimes pack including VC8 & VC9 among others.
• Kel's runtimes pack including VC8 & VC9 among others.
• YumeYao's WIC add-on built from hotfixes. Despite of what's said in _SNMsynth.ini this is more a more updated source than WIC component in 3.0 SP# framework and can be installed before a 3.0 SP# framework with it removed. I'll fix it for the next version
  
  Files from this group are not used in the building process, but to install them after installing SNMsynth installers/add-ons.
• In case you install 3.5 SP1, KB971314 for XP or for 2K3 respectively is required. Update system will prompt it if you don't post-install it.

----- OUTDATED FILES:

• NDP1.1sp1-KB928366-X86.exe hotfix for 2K/XP installers/add-ons only. It is superseded by NDP1.1sp1-KB953297-X86.exe above.
• NDP1.1sp1-KB947742-X86.exe hotfix for 2K installers/add-ons only. It could get installed on XP (and probably 2K3, I have not tested it) but it's not needed there. It is superseded by NDP1.1sp1-KB971108-X86.exe above.
• .NET 2.0 SP1 package (NetFx20SP1_x86.exe).
• NDP20SP1-KB947748-x86.exe hotfix for 2K installers/add-ons only.
• .NET 2.0 SP1 langPacks (NetFx20SP1_x86XX.exe).
• .NET 3.5 full redistributable package (dotnetfx35.exe 197MB), contains 2.0 SP1, 3.0 SP1 and 3.5 frameworks. 3.# frameworks are not processed for 2K installers/add-ons.
• .NET 3.5 redist langpacks (dotnetfx35langpack_x86XX.exe -- note it has the same filename as 3.5 SP1 langpack), contains 2.0 SP1, 3.0 SP1 and 3.5 framework langpacks. 3.# framework langpacks are not processed for 2K installers/add-ons.
• RESTRICTED HOTFIXES:
  - .NET 2.0 SP1 restricted hotfixes for 2K/XP/2K3 installers/add-ons.
  - .NET 3.0 SP1 restricted hotfixes for XP/2K3 installers/add-ons only.

Building Process:

• Preinstalling any 2.0 SP# framework is required to complete process for all packets supported.
• Defines a target win version for the resultant installer(s)/add-on(s), current host win version by default, applying to the process specific restrictions for this version. Another target than host OS version can be set through _SNMsynth.ini setting.
• Builds multilingual installers/add-ons for MUI or servers just dropping, in the work folder, the langpacks you need for each framework version.
• Creates installer(s)/add-on(s) in ..\yourworkfolder\OUT# , incrementing #+1 on each sequential run, not to overwrite successful results of a previous run. Besides it creates a process data file in this folder, including a list of the work folder contents, .ini file settings, and the list of .\TMP folder content after process finish; the goal of this is to check resultant files features or to debug building process.
• Removes previous .\TMP folder and any spare .\OUT# folders from a previously failed run, at the beginning of the building process.
• Installers/add-ons compression subprocesses open a separate window to show progress. This subprocesses (only, not the whole building process) can be restarted with the next lower compression ratio available by simply closing this window. Useful in case you overestimated time needed to complete compression at high ratios.

_SNMsynth.ini:

This file includes all settings for SNMsynth.cmd building process and brief explanatory comments.
Default process settings are: to build single framework passive installer(s) with host OS version as target, not removing any subcomponent, applying any hotfix and langpack present in the work folder, and allowing resultant installer/add-on containing .NET 3.5 SP1 (if processed) to keep .NET framework Assistant 1.0 Firefox add-on (and install it by default).
To get other results edit _SNMsynth.ini settings to your linking. It's easy, read comments carefully, and don't forget to match correctly the packets in the work folder with the settings that triggers its processing.

• UPX_SFX setting adds UPX compression to .sfx module gaining 50 KB. The downside is that it generates false positives on eSafe and Comodo antivirus. See it.

About settings allowing subcomponents removal:

• DNF20_VC8_RUNTIME and DNF35_VC9_RUNTIME settings allow removing outdated Visual C++ runtimes subcomponents from 2.0 SP# and 3.5 SP# frameworks respectively, to install updated ones from external files (see Suppported Files section above). Each updated VC runtime version (8 and/or 9) has to be installed previously to the framework from which the same outdated VC runtime version was removed because they are pre-required for that framework version. VC9 don't supersede VC8, both are complementary.
• DNF20_OFFICE2K3_DEBUGGER setting allow removing outdated office 2K3 (office11) crash reporting utilities (debugger) from 2.0 SP# frameworks, this subcomponent is used to update office 2K3 debugger, but it is not useful for office 2K3 SP3 (or later if any) which include a later version.
• DNF30_WIC setting allow removing outdated Windows Imaging Component from 3.0 SP# frameworks. It has to be installed before any 3.0 SP# framework. XP SP3 provides an outdated WIC version. You can get the latest files, see Supported Files List section.
• DNF30_MSXML6 and DNF30_XPS settings allow removing subcomponents pointed by their names. Not so useful because the script can process updated files for this components patching them, unless you want to externally install them externally and/or in other moment. MSXML6 must be previously installed to any 3.# SP# framework.
• DNF35_FF_ADDON setting removes completely .NET Assistant Firefox add-on (and the other hidden add-on annexed). If you not remove it, you can still use a switch to avoid installing it completely, see Installing section bellow.

Installing:

• Installing Priorities (merged installers keep them, if you merged frameworks AIO you don't have to worry about them anymore):
  - 2.0 SP# should be installed prior to 3.0 SP#, and these prior to 3.5 SP#.
  - To install 3.# SP# and 1.1 SP# frameworks without rebooting to install the other, you have to install 1.1 last.
• You can use installer(s)/add-on(s) during win setup at T-13 with SVCPACK.INF method. Though stated in the guide, you don't need to rename installer(s) to 8.3 format to use them with this method. If you use T-13 add-on(s), nLite and RVMI automates SVCPACK.INF method at T-13 to install them, what's the same.
  - The advantage of this method is that you can install .NET software compatible with SVCPACK.INF at T-13 (not all, maybe you should check it before), right after installing frameworks, and this software will pass its parameters to the Default User account.
  - The downside occurs only to 3.0 SP1 framework, for 3.0 SP2 has been avoided. In that case install/uninstall operations generate errors in the Event Viewer when installing at T-13 (SVCPACK.inf/T-13 add-on); also error dialogs appear uninstalling in every circumstance.
  - Using 3.0 SP2 framework let you avoid errors above, but if you use 3.0 SP1, to avoid them on install (not on uninstall), you can execute 1.1 and 2.0 SP# installers from SVCPACK.INF (or use T-13 nLite/RVMI add-on(s) for these versions); and 3.0 SP#, 3.5 SP# installer(s) at first logon, using RunOnceEx/RunOnceEx from CD or GUIRunOnce methods, or nLite RunOnce feature, or install them after logon.
• Installers/add-ons containing 3.5 SP1 installer/add-on that keeped .NET Assistant Firefox add-on should be installed after Firefox for it to get the add-on correctly installed. If you don't do it this way Firefox don't get ClickOnce features, but no more consequences are derived.
• You can use switches to modify the installers default installers/add-ons behavior at run. Don't use them with HFSLIP.
  Switches can modify default behavior of nLite/RVMI add-ons also, through repackaging, removing the need to build 2 different add-on(s) sets to be able to run them with another behavior. To achieve this, extract entries_xxxx.ini file, and edit it adding the required switches following the .exe filename, and changing verbosity in the decription item; and then replace it in the package. Add-ons supports .cab .zip .7z and .rar formats.
  You can use switches (- or / prefix, space separated) to set:
  -gm1 or -gm2 for showing or hiding, unzip progress bar respectively. If used, it is required the one used has to be the first switch or the command will malfunction.
  -passive or -quiet for showing or hiding install progress bars respectively.
  -noffaddon, avoids to install .NET Framework Assistant add-on for Firefox. Only works on SNMsynth installers/add-ons including 3.5 SP1 framework that keeped the FF add-on.

INSTRUCTIONS:

• Download and extract to the work folder, the packet: Click to view attachment
• Download 7-zip stand alone (if the link doesn't work retry until it works) and extract only the file 7za.exe to the work folder.
• Download UPX and extract upx.exe only to the work folder.
• Download the packets you need to build your installer(s)/add-on(s), from supported file list above to the work folder.
• Open _SNMsynth.ini and configure the building process to your liking, read the notes inside carefully.
• Run _SNMsynth.cmd.

You got it. Enjoy!

Feedback appreciated. If you know new hotfixes or you're getting errors or you're having comments, questions or suggestions, please let us know.


Solving Problems (hopufully you won't need this):

• For debugging:
  - .\OUT#\PROCESSDATA.TXT file is created on each run with building process data helpful to find problems.
  - If that file is not enough, you can create a detailed log file of the building process by:
  · Replacing @ECHO OFF line at the beginning of _SNMsynth.cmd, with @ECHO ON
  · Executing _SNMsynth.cmd > process.log 2>&1
  · Don't forget to revert line replacement.
  - You can also check the install logs.
  - You can use .NET Framework Setup Verification Tool to check .NET frameworks installation.
• In case you're experiencing problems uninstalling .NET frameworks, not so unusual with .NET (not related with this method), after all fails, you can use .NET FX Cleanup Tool. Sometimes is needed to run cleanup twice.

Changelog:

20091105
- Removed minor bug inserted on 20091029 (sometimes showing an error dialog on uninstall) with 3.0 SP2 language KB951847 FIX portion for all languages, not removing fix regvalue on uninstall in case it is the last langpack to be uninstalled among 3.5 SP1 family langpacks.
- Removed thousand separator from processdata.txt to avoid encoding glitches.
20091104c
- Fixed uninstall issues. 2 wrong lines replaced.
20091104b
- Fixed minor bug (not harming at all) putting extra .mst files for a FX version not being processed, in .\TMP folder.
20091104
- Fixed bug with new filenames in T-13 add-ons.
20091103
- Added 1.1 and 2.0 hotfixes processing for win2K part, absent in previous version.
- Fixed bug with 1.1 langpack processing inserted in previous version.
- Fixed bug with KB951847 fix not working inserted in previous version.
- Fixed host OS detection bug inserted in previous version.
- Restricted fontcachefix application to 3.0 SP2.
- Removed sensible data from proccess data file.
- Added target OS version for installers/add-ons filenames.
- Compresion subprocess restarting method, now jumps in a loop to highest compression ratio when restarting the lowest ratio setting.
- Strengthened 1.1 hotfixes superseding checkings and feedback.
20091029
- All fixes has been atomized to apply only the portion neeeded to its related framework/langpack.
- All temporary files are now created under .\TMP folder to keep better files arrengement.
- All fixes are now pre-applied, so the installer databases are quite selfcontained, avoiding some unusual problems with .mst files not getting copied to installers cache folder.
- Implemented YumeYao's methods for:
· Slimming down 3.5 SP# langpacks.
· W2K only components removal, for upper win versions installer(s)/add-on(s).
· Individually removing Visual C 8 and 9, and Office 2K3 debugger subcomponents.
· Updating, XPS with XP or 2K3 KB971276 (or both); and aplying delay to XPS install until 1st logon, to avoid potential install problems during GUI setup. I improved slightly this method.
· -Install from .msi- deadlock removal, allowing to avoid ADDEPLOY property in install command lines.
- Removed renaming of cached installers, no longer necessary.
- Added YumeYao's simplified user_hiddens's KB974417 fix.
- Added support for restricted KB971195 and KB972251.
- Replaced method for checking host OS version on building process (only), with Yzöwl's workstation service based more solid one.
- Switch added to choose to install or not .NET Assistant Firefox add-on from SNMsynth installer(s)/add-on(s) containing 3.5 SP1 framework keeping this add-on (through .ini file setting).
- Installer(s)/add-on(s) compression subprocess(es) now open separate window(s) to show progress and to allow restarting it on the fly (just this subprocess) with the next lower ratio available.
- Fixed bug applying generic langpack fixes on some languages with different codepage than fix.
- Fixed script to avoid potential problems in systems with DIRCMD setting applied, overriding it.
- Added creation of process data file in OUT# subfolder to allow feature checking or debugging for the SNMsynth installer(s)/add-on(s).
- Added option to choose adding UPX compression for .sfx module.
- Fixed bug with faulty install log cretion on %SYSTEMDRIVE% when installing from GUI setup.
- Fixed bug removing 3.0 SP# framework subcomponents entries in add/remove programs for outdated win installer versions.
- Fixed _SNMsynth.ini parsing to adapt it to .ini standard, added 7za.exe version checking and improved checking process, variable depletion and multilanguage support.
- Added .NET icon to installers and some cosmetics.
20090922
- Fixed a bug in .NETWUFIXES.mst since 20090818, applied fixes not removing correctly on uninstall, probably you unadverted it.
- Fixed a bug not applying transforms since 20090912 in certain circumstances. If you're a brazillian language user you may noticed KB829019 in WU.
20090913
- Fixed a bug applying KB963707 introduced on 20090912 SNMsynth version.
- Fixed minor issue causing "File not found" messages when removing unexistent files.
20090912
- Workaround .NET 3.0 SP2 errors installing at T-13 from SVCPACK or T-13 add-on.
- Fixed and adapted YumeYao's method for slimming .NET 3.5 SP#.
- Fixed bug removing some 2.0 hotfixes entries under A/R Programs with outdated win installer versions, since 20090826_SNMsynth.
- Needed transform files are now copied to installer folder to be avilable permissions don't allow copy them to installers cache folder.
- Added signature header to install scripts.
- Fixed minor issues.
20090826b
- Fixed buggy 1.1 italian language identifier.
20090826
- Fixed some uncommon errors with 1.1, 2.0 and 3.0 hotfixes processing.
- Part of the fix to avoid Firefox add-on install has been included in the transforms to delete it on removal.
- Added removal of pointless "..\Win" folder in 3.5/3.5 SP1 installers/add-ons.
- Now KB963707 is mandatory for 3.5 SP1 installers/add-ons if it install Firefox add-on because fixes urgent issues on it
- Replaced hotfixes extraction own method with 7-zip one for faster results.
- Fixed some minor bugs and added some cosmetics.
20090821c & b
- Fixed syntax bugs.
20090821
- Fixed hotfix checkings for 2.0 SP2 from redist package and added some cosmetics.
20090820
- Fixed bug detecting _SNMsynth.ini OS setting.
- Fixed a couple of syntax bugs and cosmetics.
20090818
- Fixed various error 1720 described here.
- Fixed multiple heading line on DNF.reg
- Added support for the latest restricted hotfixes for 2.0 and 3.0
- Added workaround for install error 1935.
- Added support to avoid install .NET Assistant Firefox add-on installing 3.5 SP1.
- Fixed bug installing 3.5 SP1 when KB963707 has been applied.
- Added workaround to avoid win/ms update pushing KB963707 update in case you don't want it.
- Added new settings and simplified existent ones in _SNMsynth.ini
- Added install log creation under %TEMP% folder.
- Added some cosmetics.
20090514
- Removed unneeded line.
20090430
- Applied fix for win/ms update to stop pushing KB829019 PT-BR (pointless 2.0 SP0 langpack) when the right upper version is installed.
- Merged all win/ms update fixes applied by this method in .mst file to allow automatic removing on uninstall, even for the cached msi itself.
- Added support for integrating multiple langpacks for each framework version.
- Added support for the installers/addons to work with win installer 2.0, for 2K non updated machines, removing cancel button for passive dialog boxes.
- Removed .exe embedded in .mst file causing AVG and eSafe false positives. It'll no longer use .exe files.
- Removed pointless modify and repair buttons under Add/Remove Programs for 2.0 SP# and 3.0 SP#.
- Precompiling assemblies is now done 1 time at the end in merged installers, for robustness of the install process.
- Fixed bug removing 3.5 SP# unused installer locale files, when path contains spaces.
- Fixed win version detection, to allow running the building process from not supported as target, host win versions.
- Added a variable emptier section to allow running the script repeatedly from the same terminal without errors.
- Fixed a bug in one warning message for 2.0 SP2 and added external MSXML process control message.
- Added some code cosmetics.
20090316b
- Fixed some syntax bugs and some lines in wrong place.
20090316
- Fixed win/ms update prompting to install KB928416 (pointless 3.0 SP0 langpack) when 3.0 SP#>=1 and its langpack are installed.
- Added support to avoid process KB958481, KB958483 and KB958484 when its related framework is being processed, not applying then KB951847 fix.
- Fixed cosmetic issue.
20090315
- Fixed bug framewok versions using KB951847_FIX.mst not finding .msi file on uninstall in some scenarios.
20090314
- Fixed a bug processing 1.1 hotfixes.
- Fixed cosmetic issue with 7za.exe absence error message.
20090313
- Added support for 2.0 SP2 framework and 2.0 SP2 framework langpack single packets.
- Added support for restricted hotfixes.
- Added a transform to avoid win/ms update (high priority) 3.5/3.5 SP1 frameworks Family Update KB951847, only for the updated last framework versions.
- Improved support for building installer(s)/add-on(s) for a different win version than current.
- Removed duplicate DNF.reg import command from the install script.
- Removed unused locale files from 3.5 SP# pool.
- Fixed bug determining win version for 2K3.
- Fixed 1.1 italian-hungarian language mismatch bug.
- Fixed installed 1.1 hotfixes not hiding bug, when coming from a merged installer/add-on integrating only 1.1.
- Fixed some cosmetic issues.
- Updated 7-zip SFX modified module to 1.2.6 version, UPX compressed.
20090111
- Added support to build nlite add-ons.
- Added changes to set all process settings from SNMsynth.ini
- Simplified MERGE_FRAMEWORKS setting.
- Fixed minor issue on absence of specific 1.1 updates.
20090107
- Added switchable installers building.
- Added support to install at T-13.
- Added assemblies precompiling at the end of the install process.
- Added UPX compression of 7-zip modified module.
- Added removal of FILEVER.VBS at the end of building process.
- Fixed full merged installer filename.
- Fixed minor cosmetic issues.
20081229
- Fixed warning generation on NDP30SP2-KB958483-x86.exe and NDP35SP1-KB958484-x86.exe absence, when appropriate.
- Added comment in a line of _SNMsynth.ini that should have been commented.
20081225
- First SNMsynth version forked from SNM.

I've made a minimum change in SNMsynth_loud, to simplify the process a bit more, results are equal.

Im assuming that this thread has replaced the other one m8? (SNM_mod8.cmd and associated files) Will get the new stuff for sure, thanks buddy!

Stoner81.

*EDIT*

Note to moderators - any chance this could be made a sticky guys its like one of the most important topics in here? Just a thought

Thank you for this new script with support for NDP20SP1-KB947748. I appreciate it very much.

Also, my thanks and appreciation to Tomcat76 for the original script.

My first impression is, that the new script works perfectly with windows 2000. I used the non-loud version to prepare a merged installer for .NET 1.1 and 2.0 SP1 and all the associated hotfixes. Although I have not yet had the opportunity to use the installer with HFSLIP to perform a complete fresh system installation, I did try it out on an already existing installation: I first fully uninstalled all .NET software and then re-installed it using the installer. Both MBSA and Windows Update were happy with the result, and I saw no issue with the installer.

Thanks for your hard work. It's so excellent and it's such helpful for an unattended windows installation.

Hi, this is my first post here, as I'm one-day old in the nLite world. I've successfully merged .NET 1.1, 2.0, 3.0, 3.5 English versions. Install is pending though.

I am interested to add language packs for Spanish and Chinese (Simplified) as the computer this is for might be used by Chinese & Spanish users. The script would only let me have ONE langpack pero dotnet installation, so I had to rename the Spanish ones.

Questions are:

1: do I really need all three languages (EN, ES, CH)? (sorry, probably off-topic here)
2: if so, how can I have all the remaining one installed?


Thanks in advance.

J

EDITED:
As far as I know you can't do that.

WXP/2K3 includes in their respective MUI CDs .NET translation packages as stated by MS, not the case for 2K. I've never tried MUI but probably only covers .NET versions included natively with the related windows version, I'm not sure.

Other people ask me to include multilanguage capacity to the script for using it with MUI, so I understand MUI uses installed .NET langpacks, contrary to what I though, since multimple .NET langpacks can be installed on a windows, but I couldn't find this around described clearly enough. Maybe someone using MUI can help.

Anyway, for this and other reasons, the script now includes multilanguage capacity.

Que vaya bien.

I create a FULL dotNet with your package and I have installed an virtual OS XP in Vmware.
After all I dont have access to internet from OS virtual.
Using the TOMCAT package all is ok and internet access is normal.

Any more have this problem?

0d

2 0d14r3
I can't reproduce your results:

I built full merged installer including .NET frameworks 1.1, 2.0 SP2, 3.0 SP2 and 3.5 SP1, plus all its hotfixes for XP, NDP1.1sp1-KB867460-X86.exe, NDP1.1sp1-KB928366-X86.exe, NDP20SP2-KB958481-x86.exe, NDP30SP2-KB958483-x86.exe and NDP35SP1-KB958484-x86.exe in english version.

I built an unattended XP SP3 set installing this full merged hotfixed english .NET installer from RunOnceEx.

I installed this set first in MS Virtual PC 2007, and then in VMware 6.0 workstation.

In both cases I had access to internet.

This is what I expected since SNMsynth doesn't change the basis of the building process of Tomcat' script. Have you installed it before GUI-mode setup ends? It should be installed on first logon. Did you find any .NET related errors in event viewer?


2 All
I've updated the scripts, with minor changes. See Changelog.

Before you modified them strel Ive had no problems at all m8!!! awesome work, I will get the new modded script (see post 9) and make them again and report back for you m8 give you some feedback for you.

Stoner81.

@ strel
I use RunOnceEX to install the full package with langpacks brazilian.
I try again and back to report.

Thanks.

0d

Great piece of work !!!
I wonder what to do with the ini-file.
It keeps asking me to choose which version of 2.0 I want.
Do I need to add NO instead of Yes to the original one or the one that comes with 3.5?
And if so do I need to do the same a bit lower for the language files?

I would like a separate file for 1.1+2.0 and for the rest (3.5).
I set MERGE to 12. Which of the 2.0 do I have to say YES to then.

What is the difference between loud and silent installation?

BTW: I am green as grass here, a total newbee

Attempt 1:
I choose NO for the 2.0 both with file as with the lang pack.
MERGE=12.
It worked and finished, but it says the 7z file in OUT is not a 7-zip file. It is only 91,5 kB!.

Attempt 2:Now I choose below settings. Also for the language. MERGE still at 12. Same result. A 91,5 kB .exe file. That of course does not work. PLEASE HELP!
PROCESS_DNF1=YES
PROCESS_DNF2=YES
PROCESS_DNF35_DNF2=NO
PROCESS_DNF35_DNF3=YES
PROCESS_DNF35_DNF35=YES

Attempt 3:
Everything at YES, only the file NetFx20SP1_x86nl.exe deleted form the work folder. Same result as attempt 1.

Attempt 4:
I will set the COMPRESSION RATIO at LOW. Until now it was MED.
Now I can see Temp.7z growing. I must say I had no look at in during the first 3 attempts.
AND IT WORKS !!!.
Now I have a 41,5Mb .exe file. that works.

Set the compression rate at LOW !!

Still 1 open question: it is not possible to have also a package for the rest? That is everything but 1.1+2.0SP2.
Or since 1.1 is the one that rewuires a reboot, is it possible to have 2.0 and all up to 3.5SP1 in 1 package and 1.1. in another?
That way 2.0+3.5 can be installed during an unattended set up of Windows.

Now I am going to test the FULL package.
Which works fine.

And to my own question: just play around with 12 FULL and YES and NO and you can combine what you want.
Question closed.

You see the script supports the processing of different packets with different versions of 2.0 built-in. The script is set for you to chose only one packet source to process 2.0. What source? the one you need based on the version of 2.0 you want, for example, if you want the more updated version of 2.0 for win2K3, then you need .NET 3.5 SP1 redistributable packet with 2.0 SP2 built-in and set the PROCESS_DNF35_DNF2=yes in the .ini file, but if at the same time NetFx20SP1_x86.exe is present in the work folder and PROCESS_DNF2=YES in the .ini file, you'll get an error.

To disable a setting in the .ini file you can empty the value or add whatever you want, it only recognize "yes", case insensitive, as working value, read notes inside .ini file.

About languages, to process the language for some framework version, you have to process it from the langpack related to the packet from which this framework version proceeds, even though the language for this version is contained too in another langpack. In the .ini file, settings to process languages only works if the correponding langpack is present in the work folder (obviously), and the framework related is being processed. So no crossed source packets of languages and frameworks are allowed to be processed, unlike Tomcat' original script, as notes inside .ini file states. Again, read it.

Differences among flavours are obvious, as described in the guide. The silent installers are absolutely silent, if you use this silent installers over and installed windows, you'll need to open Task Manager to monitor the unzipping and installing processes or you may not notice it; while loud installers shows progress bar boxes for unzipping and installing processes.

You have to match packets present in the work folder, with the setting that triggers the processing of a framework built-in it, to feed the process with a specified framework, see notes inside .ini file.

You can merge 1.1 with the 2.0 SP# you want, the process is a lot flexible. You can even use MERGE_FRAMEWORKS=fuLL to do this, not feeding the process with 3.0 and 3.5 versions. If you want 1.1 and 2.0 merged, and 3.0 and 3.5 in single installers or merged apart, you have to run the process, at least, 2 times. If you didn't feed the process with 2.0 but only with 1.1 and its langpack and set MERGE_FRAMEWORKS=12 you should get DNF11xx.EXE. If you want to merge 3.0 and 3.5, set MERGE_FRAMEWORKS=fUll and feed the process only with 3.0 and 3.5, do it disabling PROCESS_DNF35_DNF2 as dotnetfx35.exe (containing 2.0 SP#) needs to be processed. You can merge all frameworks in one installer.

You can use all resultant installers during unattended setup or over an installed windows.

One of the most useful scripts I've ever found.
Apart from custom editing the 7zip SFX program.
And, I like how you changed the program to say when it's processing different sections of the .NET 3.5 SP1 Installer.
Works like a charm.

One thing in the topic though, to someone who was just trying this, they might be confuzzled by the fact that you linked to the .NET 3.5 and the SP1 separately and download them both. That would be a huge waste of bandwidth. Just figured I'd point that out... that along with the .NET 2 Installer. I think you should remove it because they're all included in the 3.5 SP1. You might want to put something explaining that too...

Oh, I second that this topic should be pinned.

EDIT:
One problem, and extremely minor.
A file was created and not deleted: FILEVER.VBS
In the root.

Strel, THANKS.
Thorough and supportive.
I have used it and it works great. Saves a lot of space.
Next attempt: get all that 64 bit stuff out of the files. Saves a lot of Mb's.

Enjoy this evening and a Happy 2009 to you.

@strel
My excuses!!!
Your package dont have problems. My problem are random access to Internet from Vmware using dial-up connection.
Thanks for all.

0d

Hi.

It seems to me, that .NET 3.0 SP2 Language Pack integration is corrupted.
Microsoft Update Website does not see it installed.

However i see it installed in "add or remove programs",
but the install size is only 3 Mbytes.
Now i tried a fresh install in VMware, with original .NETs,
and 3.0 SP2 Language pack's size is 10 MBytes in "add or remove programs"!

So i think the script is missing something.

(i used hungarian language pack)

This script looks great, aldo i am not sure i understand it completely.

I dl'ed the 7zip stuff, and also all 3.5 net framework files (including language and hotfix).
Changed nothing in the (loud) script to and run it. Now i have three files in the OUT1 folder:
DNF20SP2nl.exe
DNF30SP2nl.exe
DNF35SP1nl.exe

Do you need all three of them for a fully working Net framework envirement ?

2 Belak51
I'll review all this in the next update, soon. About 2.0, I suppose you're meaning removing 2.0 SP1 packet, I can't, it's needed for win2K. 3.5 redistributable and 3.5 langpack (not SP1) are better candidates for removing.
Thx.

2 jweetje
64 bit stuff is removed from the installers.
Thx 2 U, happy 2009.

2 0d14r3
I supposed it.
Thx 2 U.

2 fenyo
I got the same results. But, what do you exactly mean when you say Microsoft Update don't recognize it, does it offer to you 3.5 SP1 langpack for downloading? This is not my case.
I don't know why this happens. All I can say is I don't see errors installing, and checking the building process, it ends up without errors, apparently. I'll keep searching.
Thx.

2 Jediron
Depends on the software you run. .NET is only for software that is made for using this frameworks ("managed code" in MS jargon). Not all software use .NET and not all software that use .NET, use the same #.# version. Maybe the software you use, needs only 2.0, but for ongoing updates of that software, the developer may update the code to a later .NET version. For example, paint .NET have changed its framework needs from 2.0 to 3.5 in recent versions. Up to you.
Thx.

fenyo, I found differences in installers including 3.0 SP2 magyar language, with installers in other languages (specifically with spanish and danish with which I compared). When processing magyar language these 4 files doesn't exist in the installers:

DNF30\LNG\Win\Microsoft.NET\Framework\v3.0\WCF\MUI\040E\ServiceModel.mfl
DNF30\LNG\Win\Microsoft.NET\Framework\v3.0\WCF\MUI\040E\ServiceModel.mfl.uninstall

this files exist in other languages, in its correponding folders (...\040E\... , the name of this folder depends on language used); and

DNF30\LNG\Win\Microsoft.NET\Framework\v3.0\WPF\NlsData000a.dll
DNF30\LNG\Win\Microsoft.NET\Framework\v3.0\WPF\NlsLexicons000a.dll

exceding 9 MB each one.

No! It offers me to download 3.0 SP2 Language Pack.
3.5, 2.0, 1.1 are all OK.
I've just noticed, that MU site offers it again with "original" 3.0 SP2 Language Pack installed. [link]
So i think it's a Microsoft Update bug. (it wouldn't be the first time)
You might build a workaround for this.

BTW i don't understand why the "original" Langpack 3-times bigger (as installed) than the script made one.

Whoa!

So actually just the hungarian version is corrupted.
Fine....

Edit:
I haven't find any of these files in any of the directories. (i've extracted all DNFx.EXE the script made)
Which original-installer contains these files?

Edit2:
Ok, i've found similar files:
DNF30\Win\Microsoft.NET\Framework\v3.0\WPF\NlsData0009.dll
DNF30\Win\Microsoft.NET\Framework\v3.0\WPF\NlsLexicons0009.dll
The last character differs.
But these files are not in LNG.

These files you point are not in question, they are present in spanish and danish versions too. The problem is with that I told you. You can find them in administrative installs of 3.5 SP1 langpack except for magyar.

Ouh. So these files are not corrupted, they're missing.
And you're tellin' me these files are not language-neutral?
Is there any chance that THIS contains these files?
Blaaah... I can't make an administrative install of these installer (to see if it contains the files)
...switches, switches........

I think these files are contained in the langpack for 3.5 SP1, but for some reason not extracted in the administrative install (which is the one used by this script). The update for 3.0 SP1 langpack is not for this version.

You mean THIS?
It's SP2, the main title is wrong! It says its SP1, but if you look down, you can see it's version: SP2.

I hadn't seen it. OK. I didn't know this update, but I think it is not included there, first, for size, and second, this update don't exist for spanish language but for danish. In danish I've checked these files are created in administrative install, and third, where are the MB lost among administrative install and normal install?. It's something with the hungarian 3.5 SP1 language pack.

So you're tellin' me that 3.0 SP2 LangPack alone package is good, or not?

I thought this was an update, sorry. Well no idea why microsoft is releasing another language pack for 3.0 SP2, but it should be fine. Although the script don't support it at the moment. Let me do some test.

But I really have no idea of what this last langpack is made for, and why it only exists for some languages.

hello strel! thanks for continuing (and improving) this script where TC left off ... may i ask though if output has already been tried with HFSLIP?

Nop. I don't use it. But the basis of the script are the same old admin installs. After having a quick reading on HFSLIP basis, and take a quick look to the HFSLIP script, I think resultant installers from synthesized version should work too without problems in HFSLIP.

Any of you using it can confirm it. So, please...

I realize switchless feature is intended for using installers with HFSLIP, as I suspected. For future updates, I'll keep this feature to maintain compatibility with HFSLIP, but optionally, this is, people who don't use HFSLIP will can have unique set of installers that could be switched from silent to passive.

Well, i want to install it so that NET will always work, with everything. No hassle about version, NET is there; always. Is this possible ?

Use intallers for all the frameworks in your unattended set. You can rarely use an application that needs 1.1 but if you want to be sure include all. You can use the full merged installer or individual installers, read the install rules.

So i use those three i already have and NEt 1.1 , then i have all ?

Yes, until MS releases .NET 4.0, probably during this year.

I think because it contains only 3.0 SP2 LangPack alone. You can see it's date is the same when the 2.0/3.0/3.5 Langpack released. (2008. 11. 13.)

Now i've installed a clean XP on VMware again, i've installed .NET 3.5 SP1 full redistributable (231Mbytes) without internet access. After that i tried to install .NET 3.0 SP2 Language Pack from Microsoft Update Website, but it failed!! It have throwed me error code 0x13EC.
So i installed .NET 3.5 SP1 langpack.
After that i've visited MU website, 2.0 LangPack disappeared, but 3.0 SP2 LangPack still remains!!
I've searched the whole C:\ for the 4 files you mentioned, but i found nothing.
These files are truly not exist in any of the 3.0 SP2 hungarian Language Packs.
This (the lack of these 4 files) must be the real reason why MU website offers me continually the .NET 3.0 SP2 LangPack.
So microsoft screwed up again...

I bet i can't use these files from other languages...


Anyway, i want to thank you for your excellent support! I really appreciate it.
Thank you!

These 4 files exists only in the admin install of languages other than magyar, not after intalling in the OS.

About the stand alone 3.0 SP2 langpack, to me it's a nonsense, why some languages have it and some others not? I'm not confident in any way with that packet.

Ouh. OK. Then why MU website continually offers me 3.0 SP2 Langpack? And what these 4 files need for?


Micro$oft logic.

I think continually if we don't manage the way for they to appear in the admin install of 3.5 SP2 language from 3.5 SP1 langpack.
And I don't think MS earns nothing with this. I though it was for updating stand alone 3.0 or 3.0 SP1 installations, but this doesn't explain the absence of some languages.

???
You mean we can get those files from previous LangPacks?

I could check that both dotnetfx35langpack_x86hu.exe (SP1 version) and NetFx30SP2_x86hu.exe have the same structure in patch.cab inside
..\netfx30lp\WCF_HUN.msp
..\netfx30lp\WPF1_HUN.msp
files resulting from both extractions of language packs above (3.0 SP2 portion is almost equal); patch.cab files that doesn't contain files correponding to these 2 pair of files respectively.

Moreover NetFx30SP2_x86hu.exe lacks file XPSEPSCLANGPACK-x86-hu-HU-langpack.exe. This file is installed when 3.0 SP2 language is installed from dotnetfx35langpack_x86hu.exe (SP1 version) langpack. But the install size indicated under Add/remove programs is not affected by this file, thus 3.0 SP2 language installed from NetFx30SP2_x86hu.exe shows the same install sizes, 3,8 MB and 10 MB, installing it through admin install (aka SNM installers) or directly, respectively. So NetFx30SP2_x86hu.exe, is not offering any advantage, rather the opposite.

But now this doesn't seem relevant to me since I could check there's other dotnetfx35langpack_x86XX.exe (SP1 version) langpacks that lacks the files of the first paragraph, for the 3.0 SP2 language portion, like turkish, italian, russian, chinese simplified... And installing 3.0 SP2 language from this langpacks, indicates the same install size when installed from admin install (aka SNM installers) as well as when installed directly from the langpack.

So I didn't checked all langpacks with this structure, but it seems the wrong behavior only happens with hungarian language admin install for 3.0 SP2.
Anybody want to add something?

I should add that the file fenyo was prompted to download from MS Update, when 3.0 SP2 language is installed from admin install (aka SNM installers), this is, showing 3.8 MB installed; wasn't the same 3.0 SP2 language standalone, as stated before, but 3.0 SP0 language standalone. This happened only under hungarian XP, not under english XP (with .NET hungarian languages), to make things even more strange.

EDIT: Check post #59 for updated info.

I have not yet tried the installers with HFSLIP. However, I have noticed, that Tomcat76 used the utility msistub.exe, apparently to make it work with HFSLIP and Win2k, at least at some point, and this quote is from his original readme:
Now I see, that the synthesized script does not refer to this utility, as Tomcat76's original script does, nor is the utility included.

So, I wonder if it might be correct to assume, that the script would not work with HFSLIP on Win2k, or does it include some other method to achieve the same result?

7-zip SFX modified and msistub.exe are authored by Oleg_Sch who include the function of the second in the first, so it shouldn't be a problem.

Thank you!

Hello,

I'm getting a bit confused by the instructions, I've obviously missed something or did something incorrect. Here is what I've done:

I downloaded all of the files to a working directory along with the .net packs. Here is the contents of that directory:


For my first attempt I modified the _SNMsynth.ini with the following:

And then tried both using both the SNMsynth_loud.cmd and SNMsynth.cmd and both produced this error:

I can't seem to find where to specify this parameter? Or possibly I'm misunderstanding how to use this.

Any help is appreciated,

C

Edit:

Second attempt I tried by additionally modifying the following because there are no language packs that I know of for English:

I get the same error message. I'm not really sure what I'm doing incorrectly.

I think this is because you have some unnecessary files.
For example you don't need NetFx20SP1_x86.exe when you have dotnetfx35.exe.
dotnetfx35.exe is .NET 3.5 full redistributable, which contains .NET 3.0 and .NET 2.0 too.
And what is dotnetfx35a.exe ?

Thanks for the quick response,

I get totally confused by which files I need if I want an all in one installer. The file that ends in a is the second download of the dotnetfx35a.exe is the the second file I downloaded that was named dotnetfx35.exe, I changed the name because I wasn't quite sure what to do with it.



This may sound like a stupid question but could someone just clarify for me which of the files listed above should go into a "FULL" synthesis? I'm really new at this.

Thanks,

C

Edit:

So to be clear the:
.NET 3.5 full redistributable
.NET 3.5 SP1 full redistributable

Have the same name when downloaded, so I changed the second on to dotnetfx35a.exe.

Edit 2:

I think maybe I'm just reading the list incorrectly.

I take this as saying that it contains 3.5, 2.0 SP2 (but not 2.0 or SP1), 3.0 SP2 (but not 3.0 or 3.0 SP1), and 3.5 SP1.

Should I instead read it to say:
3.5, 3.5 SP1, 2.0, 2.0 SP 1, 2.0, SP2, 3.0, 3.0 SP1, and 3.0SP2 ?

If that's the case then all I need to do a full synthesis is:


Is this correct?

Caspean, you need to feed the process with only 1 SP# of each .NET #.# version. So you have to find the correct matching of packets-in-work-folder/settings-in-.ini-file that feed the process correctly. Only packets with it's original filename can be processed. Read carefully the notes in the .ini file that explain what trigger each setting.

Thanks for the response,

I have read it several times, very carefully. I think there is a bit of a language gap is all. It's a bit difficult for me to understand. Don't get me wrong I'm not complaining, I'm just trying to clarify. I'm an Midwest born and raised US citizen, heck sometimes we can't even understand people on the east coast of our own country.

I think I added some comments to the end of the post above at the same time you were posting. They might help clarify my confusion.

Thanks,

C

Edit: If I read it the way I mention above should I also read it as


NDP1.1sp1-KB928366-X86.exe Contains NDP1.1sp1-KB867460-X86.exe (because its a later update)

and

.NET 3.5 SP1 full redistributable Contains NDP20SP2-KB958481-x86.exe, NDP30SP2-KB958483-x86.exe and NDP35SP1-KB958484-x86.exe

So really all I need for a full synthesis is:

3.5 SP1 packet=3.5 SP1+3.0 SP2+2.0 SP2, that's all. Better to include updates for this.