[madpenguin]

Thanks Strel. Everything seemes to work fine with the new version. You can look at my last attachment to see what files I processed but it's basically an up-to-date 1&2 addon for nlite. I added the .7z file after 60 or so other hotfixes, no problems there as someone earlier suggested. Windows update doesn't list it as me needed it.

It appears, atleast for my needs, that your latest version works perfectly. I haven't compared file versions or gone indepth to make sure all the hotfixes were applied correctly during the windows install but for now, I'll just assume they have.

I've also noticed that firefox .NET assistant update is missing in Automatic updates. Huzzah for who ever made that one happen. Was really getting tired of looking at it.

Thanks again for all the hard work.

This post has been edited by madpenguin: 01 November 2009 - 01:51 PM

[madpenguin]

FYI, my new nlite CD worked perfect. Did a format and freash install and only have the updates I intentionally left out. The new version of SNMsynth seems to work and do what I need it to do.

Thanks much.

This post has been edited by madpenguin: 01 November 2009 - 06:00 PM

[Glowy]

strel, on Oct 31 2009, 12:39 PM, said:

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?

Weird thing is when i run it from an existing installation it runs fine.
When I use it from HFGUIRUNONCE (I'm using HFSLIP) I get the error.

[Sp0iLedBrAt]

Sp0iLedBrAt, on Oct 31 2009, 01:47 PM, said:

I compared the versions; mscordacwks.dll has 2.0.50727.3082 version, which should be at least 2.0.50727.3603.

I checked if 20SP2_KB974417FIX.mst was in the folder; affirmative.

I'm attaching PROCESSDATA.txt so you can check it out and point me to possible errors in my procedure.

Thank you for your prompt reply.

I did another one incorporating what is said above plus a few changes; the result is still the same (see post #490). I'm also attaching the log inside OUT1 from this latest experiment.

Edit: I extracted the package and verified that the necessary files (newer versions in accordance with MS's description) are indeed inside, so the question is why aren't they updated in the Microsoft.NET\Framework\v2.0.50727\ folder.

This post has been edited by Sp0iLedBrAt: 02 November 2009 - 07:14 AM

[Glowy]

There probably is something wrond in the KB971276 code.
I had to put WINXP=YES in the ini or the KB971276 updates did not get processed.
Starting up a VM installation to test if the file not found error dissapeared.
At least the file exists in the archive now (DNF30\XPS\update\update.exe)

This post has been edited by Glowy: 02 November 2009 - 08:08 AM

[strel]

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.

This post has been edited by strel: 02 November 2009 - 05:41 PM

[thnx4thepen]

strel, on Nov 2 2009, 04:05 PM, said:

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.

ok!

strel, on Nov 2 2009, 04:05 PM, said:

thnx4thepen
What method did you used to install? Did you installed 3.0 from win setup? At what time?

I simply run the installer created in a Virtual Machine (VirtualBox 2.2.2 Windows XP SP3 full updated).

I used only the "dotnetfx35.exe", the language pack and the updates.

PS when the procedure is finished I did clean the .\TMP folder

[Glowy]

When omitting the winxp=yes veriable the output is:

Quote

Checking .NET stuff to build installer(s)/addon(s) for ...

"net config work" returns "Softwareversie Windows 2002"

When I change the "TOKENS=4" in "TOKENS=3" in the OS detection part, it detects correctly, so I think it's a language issue
Because the english output is "Software version Windows 2002", there is an extra space.

This post has been edited by Glowy: 03 November 2009 - 12:39 AM

[strel]

Clarifying. Thx

[Glowy]

Building the packages went fine using winxp=yes, but in WU KB951847 and language pack for .NET 1.1 are back

[atolica]

strel

Where can I get Microsoft Visual C++ 2005 Service Pack 1 redistributable runtime package, the last version? I want to replace the net framework builtin package with the latest one using your script?

Can it be done?

Thanks

Atolica

This post has been edited by atolica: 03 November 2009 - 07:28 AM

[strel]

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.

This post has been edited by strel: 03 November 2009 - 07:54 AM

[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.

YumeYao, on Oct 31 2009, 10:11 AM, said:

...in my test of SNMsynth, KB958484 doesn't have its files updated in .NET 3.5(files are still with build number 1), but entries are present in vs_setup.msi. I think you may applies *.msp earlier than NET35SLIMDOWN.mst...

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.

Dumpy Dooby, on Oct 30 2009, 06:32 AM, said:

As of 7-zip 9.07, you must specify the type during extraction of executable files. Otherwise it will extract each individual resource and binary section...

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

This post has been edited by strel: 03 November 2009 - 05:19 PM

[thnx4thepen]

strel, on Nov 3 2009, 04:24 PM, said:

Glowy & thnx4thepen
I still cannot recreate this error you pointed. Check again with the new version.



Enjoy

ok! I try...

Thank.

[Sp0iLedBrAt]

Thumbs up from me strel, this new version definitely solved the problem for me. Thank you

[Glowy]

strel, on Nov 3 2009, 11:24 PM, said:

Glowy & thnx4thepen
I still cannot recreate this error you pointed. Check again with the new version.

OS Detection now ok.
still running XP install, will report back when it's done.

[Kurt_Aust]

Unfortunately the nLite AddOns don't work

entries_DNF20SP2.ini

[general]
builddate=Wed
description=.NET 2.0 SP2 passive installer
language=
title=.NET Framework(s)
version:
website=http://www.msfn.org/board/index.php?showtopic=127790

[EditFile]
I386\SVCPACK.INF,SetupHotfixesToRun,AddProgram

[AddProgram]
DNF20SP2.exe

Name of silent installer: 2KDNF20SP2.exe

Same problem for .Net 1.1 sp1

I'll check the other aspects shortly.

This post has been edited by Kurt_Aust: 04 November 2009 - 01:58 AM

[Glowy]

WU still complains about KB951847: Microsoft .NET Framework 3.5 Service Pack 1 en .NET Framework 3.5 Family Update x86
Langpack and OS detection fixed.
I'll try a rerun without stripping anything out of the package (currently updating VC9 externally and excluding WIC)

[strel]

Good point Kurt, forgot to include the target os in name for T13 add-ons. Fixed now.

New version released!

[Kurt_Aust]

Running the 2K versions as silent installers rather than nLite AddOns appears (as far as I can tell) to work perfectly.

Files seem to be the correct version and Windows Update is happy, I only fired up one .Net 2.0 dependant application for testing though.

For .NET 2.0, the processing order is perhaps not optimal, but works fine:
NetFx20SP2_x86.exe
NDP20SP2-KB958481-x86.exe
NDP20SP2-KB971111-x86.exe Required for W2K
NDP20SP2-KB974417-x86.exe