strel

NEW VERSION RELEASED !!! All bugs I could recreate are now fixed, and some extras added. See changelog. I have not tested the behavior of SNMsynth installers/add-ons after removing VC runtimes and preinstalled them with runtime packs (in supported files list). Any info on this is welcome. If you're referring to files listed here, these files are not included in the cab file of KB958484. About the .msi cache installers renaming, seems that finally I was right. It is required, yes, I see the same thing as you with frameworks installed I changed those values in registry and KB951847 fix still worked, but now, looking for the KB951847 not working problem inserted in 20091029 version, I found that what's failing was precisely this. Curious. Later you added you were refering to x switch, but this switch is not used to extract the file partially, e switch is used instead. 7za.exe 9.07 beta is supported. Glowy & thnx4thepen I still cannot recreate this error you pointed. Check again with the new version. Enjoy

I think ricktendo is referring to 7-zip sfx modified module. Switch to russian to access to the latests version links.

Glowy There are bugs, I fixed those you mention, will be ready for next version soon. Don't use actual version except for testing purposes. I could not manage to recreate error with XPS's update.exe file not found. I tried a RunOnce install but it installs fine. It seems you're meaning that after you set the target os version through .ini file, this error don't appear but this doesn't make sense to me as thnx4thepen have the same error after setting target OS version from .ini file. atolica You better not use 20091029 except for testing, it contain serious bugs, wait for the next version, soon. What you search is Visual C 8 link in Supported File List section of the guide, I have to clarify it.

Clarifying. Thx

I don't think you take a high risk.

SNMsynth 20091029 presents important bugs, I'd recommend you to not use it except for testing purposes. Hopefully will fix all bugs for the next verion soon. thnx4thepen What method did you used to install? Did you installed 3.0 from win setup? At what time? zorro1 Thx for your help, I've found and fixed the 1.1 language bug, next version will handle it. Sp0iLedBrAt I'm not getting KB974417 in win/ms update after using an SNMsynth installer over an installed XP. Are you sure is that KB# and not KB951847?, because there's a bug with the second that I managed to fix, next version will handle it. In addition, the right files from KB974417 are applied both in my 2.0 SP2 installer and in %systemroot%\Microsoft.NET\Framework\v2.0.50727\ folder. Check this folder is removed when you remove 2.0. Glowy You said you need to set WINXP=yes in .ini file to make the script process KB971276. This sounds strange to me, I don't think it is related with target OS setting in the script, but new method for detecting host OS (which define target OS, in case .ini file setting is not defined) is being used with 20091029 SNMsynth, and though I'm confident with it, you should check it is not failing. The 2nd line after you run the script, indicates the target OS version for the installers being built. If you find any error on this let me know.

If you want to do it through nLite you have to previously build a nLite add-on, manually or automatically (with SNMsynth), or you can use one of the ready to use solutions (see them at the 3rd paragraph of SNMsynth guide). But you can do it without nLite and without building and add-on, manually, during GUI setup, through svcpack.inf method, cmdlines.txt method, or SetupParams method. But errors in Even Viewer will be generated when installing 3.0 framework from GUI setup, though they don't harm; also they will reproduce on uninstall generating 2 error dialogs. SNMsynth can avoid them, see its guide.

In the nLite process, you should get to the feature and add a command to your installer in in it. You can put your installer in $OEM$ folders to previously copy it to the HD. The command should point to the location you want to run it from.

If you used that silent installer with nLite hotfixes feature, nLite couldn't built the image without errors because it is not hotfix nor an add-on, but an installer, and it is not supported in that feature. What you have, should be used with RunOnce nLite feature. Otherwise, SNMsynth could be useful for you.

Please use attachment better for a file that long. nLite doesn't accept your file because you are trying to integrate a switchless installer and not an nLite add-on. To build an add-on you should have used T13ADDON=YES setting in the .ini file.

Kurt_Aust I forgot to finish the part for 2K hotfixes processing for 1.1 and 2.0 when I was doing changes. Will be ready for the next version. Glowy I built 3.0 SP2+3.5 SP1 merged installers with exactly the same .ini file settings and with the same files in the work folder as you. Then I proceed to install and the error didn't appear. Can you check again even repeating the process or so? geromichi & 0d14r3 Seems to be the same problem with 1.1 langpacks, I'll check it. geromichi, about uiautomationcore.dll: then your install strategy is OK, isn't it? But what did you do? What did you installed first, .NET or the update pack? YumeYao Vista/2008 dll on XP? Is that possible? Anyway, pretty heterodox!? Will see your progress and your new optimizations. I'll check that issue with msp files. Dumpy Dooby I see, OK, suppose all files to extract are zip, I'll check it to include the switch. Thx. EDIT: There's no problem with that, the script supports 7za.exe 9.07 beta. I suppose 35SP1_KB963707FIX_NOFFADDONPROPERTY.mst appears in .\TMP folder, is that right? I have not defined any timeframe limitation for the script subprocesses. Waiting for your tests. Sp0iLedBrAt Here check LDR section. Check 20SP2_KB974417FIX.mst was on .\TMP folder (See record in .\out#\processdata.txt)

Only 1 add-on.

atolica, I couldn't recreate this error in the test I made with a fresh new addon. I think is very improbable this is really failing. Check it again or give more data to recreate it.

Kurt_Aust I don't think file not found messages came from cleaning subprocess. Making tests. Glowy Thx I'll check it. atolica First, there's a typo, sorry. I meant updated VC runtimes (that ones not comming from .NET frameworks but from the updated VC runtimes sources I posted in Supported Files section) has to be installed previously to the framework version from which the same VC runtime version is removed, i.e. if you remove VC8 from any 2.0 SP# you have to install VC8 from updated sources previosly to install that 2.0 SP# framework because it is a pre-requisite. The same goes for VC9 and 3.5 SP# frameworks. Everybody I'm fixing bugs. Anyone more having problems? Anyone experiencing difficulties on uninstall not finding the cached .msi installer to proceed?

Did you missed the thread to post to? About the other post with the error not finding FF addon file, I have to say I've seen this error ago but I though it was completely solved. In fact I cannot recreate the error, using exactly the same settings in .ini file. Can I have the file list? Any other useful info to recreate this condition? Kurt_Aust The add-on error is only a TMP\ prefix I dropped in the wrong place. About the difficulties with hotfixes, when you say "not processed" I think you're meaning not installing, am I wrong? Anyway, were there any problems during building process? Have you checked a verbose output after removing ECHO OFF in the script? I have not made test yet, but a priori sounds strange to me, the way hotfixes are applied has not changed, and what is more strange is that only some of them are missing. Any extra info to help me recreate it?

New version released! It is a major update. Fixes has been atomized, and grouped, folder structure has changed to adapt to the new situation, TMP folder now hosts all temporary files. Many changes has been made in the script to support all that. It gives full support for the new regular and restricted hotfixes. It finally implements complete YumeYao's methods. Added: slimming down 3.5 SP# langpacks, removing frameworks subcomponents, and other optimizations. It solves all bugs documented, and one new important about generic fixes for langpacks not applying on some languages because of a codepage conflict between the transform and the installer. Any of you probably have experienced this simptoms but not reported it, this bug has been around many months. I've included links to many ready to use .NET releases in the guide. Testing is a growing task as there are many new paths of execution. So despite I have made a lot of tests, for sure some bugs will appear. I rely on you to help me remove them. See you later. Enjoy!

I'm just finishing, I'm writing the guide and doing some last moment checks, it will be released in the next hours sorry about the delay over expected release date.

Dumpy Dooby I've updated my answer to your logging problems. atolica MS states is KB928366 is superseded by KB953297 Raoul90 New hotfixes are: NDP1.1sp1-KB953297-X86.exe, NDP1.1sp1-KB971108-X86.exe, NDP20SP2-KB974417-x86.exe and NDP20SP2-KB971111-x86.exe

Hopefully before monday. YumeYao I'm working to include all your removing proposals.

This is not featured yet. You have to wait for the next version or do it yourself editing the .msi You can use YumeYao installers too.

1. OK, wait to see, always welcome to remove uneeded stuff. 2. Automatically and ad-hoc? ufff!, don't think so, unless .mst or .msi could be directly edited from command line or so; maybe with ad-hoc .mst files per framework version (and SP), and with one .mst per hotfix applied, but this sounds painful; but maybe there's some other way I don't know to do that. Anyway the fix the script provides do the work, it's reasonable that an hand custom made release against an automatic custom made one would be a bit more elegant. 3. KB951847 fix is never applied to 2000 installers/add-ons.

user_hidden and YumeYao Fantastic guys, I couldn't work on this in the last days. Thx a lot for the solution. Will be included in the next version, soon, I'm testing now. Kurt_Aust Thx a lot I'm going to include it in the guide. I'm not using actually any win2K so I rely on you, and you don't say anything about this hotfixes producing errors with the script nor appearing after install in win/ms update, so I guess they are correctly applied. Am I right? Alpha95 and everybody You'll find the simplified user_hidden's fix in YumeYao's post #439. Until next release, you only have to insert that value under that regkey after installing SNMsynth installer containing .NET 2.0 SP2 with NDP20SP2-KB974417-x86.exe applied. EDIT: Guide has been updated to link to KB974417 fix until next release, and to include the latest hotfixes. Anything I could have omitted, please let me know. Thx in advance.

I've added too KB953297 for 1.1 fx with a "not supported" advice as well as to KB974417. Checking...

George King A lot of thx. I've included it in the guide. Dumpy Dooby NETWUFIXES.mst (in the latest release) contains ad-hoc fixes to block some hotfixes for not to appear in win/ms update, because of its absolut nonsense (the case of langpacks for SP0 versions, not even installed) or because they are not really needed unless you use this piece of software, though ms pushed them to you as if they were required (that's the case of .NET 3.0 and .NET 3.5). I have yet to install the new hotfix to see if there is any surprises that would require an extra fix to correctly apply it, but I don't expect that. The script process this new hotfix seamlessly, so no changes needed there about it.

Silent .NET Maker synthesized.