[madpenguin]

Forgive me guys for not being up to speed with what you are talking about. I'm using silent .net maker for a combined .NET 1 and 2 addon pack for nlite. And yes, KB974417 is still showing up under automatic updates even tho SNM reported that it was processed. What exactly is the fix for nlite/SNM so you don't have to screw with anything after a fresh install?

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Products\DC3BF90CC0D3D2F398A9A6D1762F70F3\Patches\9E0DE89293FE9BB33898F24ED18CCF08]
"MSI3"=dword:00000001
"State"=dword:00000001
"LUAEnabled"=dword:00000000
"PatchType"=dword:00000000
"DisplayName"="KB974417"
"MoreInfoURL"="http://www.microsoft.com/"
"Uninstallable"=dword:00000000

Can I make nlite add the above reg key? Forgive me, but I'm not too good with this stuff yet....

[YumeYao]

you can save it as *.reg, and merge it into your registry.

[madpenguin]

Ok. Thanks. I assume you mean to add 'regedit' as a runonce command and point it to the above *.reg file on the installation media? I'll give it a try.

[YumeYao]

yes, it's ok as far as it's added at any time after .NET installation.

[Kurt_Aust]

As I have not yet seen the latest Windows 2000 specific patches listed in this thread, I'd best mention them:

For .Net 1.1 sp1:
dotnetfx.exe
NDP1.1sp1-KB867460-X86.exe
NDP1.1sp1-KB953297-X86.exe
NDP1.1sp1-KB971108-X86.exe Required for W2K (replaces KB947742)

For .Net 2.0 sp2:
NetFx20SP2_x86.exe
NDP20SP2-KB958481-x86.exe
NDP20SP2-KB974417-x86.exe
NDP20SP2-KB971111-x86.exe Required for W2K

[mooms]

YumeYao, on Oct 17 2009, 06:02 AM, said:

you can save it as *.reg, and merge it into your registry.

Even better: save it with the name DNF20.REG and place it in the root of the 7zip sfx archive (use 7zip split and 7zip for this)
I have used this content, thank to zorro:

REGEDIT4

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Products\DC3BF90CC0D3D2F398A9A6D1762F70F3\Patches]
"AllPatches"=hex(7):39,45,30,44,45,38,39,32,39,33,46,45,39,42,42,33,33,38,39,\
  38,46,32,34,45,44,31,38,43,43,46,30,38,00,00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Products\DC3BF90CC0D3D2F398A9A6D1762F70F3\Patches\9E0DE89293FE9BB33898F24ED18CCF08]
"MSI3"=dword:00000001
"State"=dword:00000001
"Uninstallable"=dword:00000001
"LUAEnabled"=dword:00000000
"PatchType"=dword:00000000
"Installed"="20091016"
"DisplayName"="KB974417"
"MoreInfoURL"="http://support.microsoft.com/kb/974417"

works flawless with snmsynth 20090922.

[Alpha_95]

Hi,

Could you update snmsynth 20090922 so that it takes into account the new update (NDP20SP2-KB974417-x86.exe)?
I tried this version but the update is requested by Windows so I think it did not work ....
Thank you in advance

[YumeYao]

Kurt_Aust, on Oct 18 2009, 02:51 AM, said:

As I have not yet seen the latest Windows 2000 specific patches listed in this thread, I'd best mention them:

For .Net 1.1 sp1:
dotnetfx.exe
NDP1.1sp1-KB867460-X86.exe
NDP1.1sp1-KB953297-X86.exe
NDP1.1sp1-KB971108-X86.exe Required for W2K (replaces KB947742)

For .Net 2.0 sp2:
NetFx20SP2_x86.exe
NDP20SP2-KB958481-x86.exe
NDP20SP2-KB974417-x86.exe
NDP20SP2-KB971111-x86.exe Required for W2K

good info. thanks dude.

[YumeYao]

Alpha_95, on Oct 18 2009, 03:54 PM, said:

Hi,

Could you update snmsynth 20090922 so that it takes into account the new update (NDP20SP2-KB974417-x86.exe)?
I tried this version but the update is requested by Windows so I think it did not work ....
Thank you in advance

I guess strel is busy IRL. If needed I can help update his script.

[Alpha_95]

Hi,

Could you update snmsynth 20090922 so that it takes into account the new update (NDP20SP2-KB974417-x86.exe)?
I tried this version but the update is requested by Windows so I think it did not work ....
Thank you in advance

[strel]

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.

This post has been edited by strel: 18 October 2009 - 03:44 AM

[YumeYao]

some new thoughts after I did a test on windows 2000:

1. There are some files in .NET 2.0 only needed by windows 2000, if we could remove them then the size would be smaller for XP/2k3. I decide to remove all components with condition NOT (VersionNT > 500) yet i haven't done a test yet. I'll let you know the result.

EDIT: .NET 1.1 also has such files. but I don't intend to install .NET 1.1 any longer.

2. Is it possible to create a generic mst that removes components such as KBxxxxxx.ARP.NoRemove & KBxxxxxx.ARP.Add? They cause the issue that 2000/XP SP0/XP SP1/2k3 SP0 shows KBxxxxxx for .NET entries on ARP. I decide to manually move them in my release, however.

3. For 2000, KB951847 fix is not needed. KB971111 doesn't require a fix too(WU checks gdiplus.dll version).
The only need is KB974417 fix (plus language pack fix for 2.0).
Therefore I'm going to make a new mst for .net 2.0 to avoid useless registry entries on windows 2000.

This post has been edited by YumeYao: 18 October 2009 - 08:33 AM

[strel]

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.

This post has been edited by strel: 18 October 2009 - 09:42 AM

[YumeYao]

I see. You don't apply KB951847 fix to windows 2000 in the SNM script....

[Kurt_Aust]

Well my test on Windows 2000 reveals (nLite addons, not merged):

The .Net 1.1 framework appears to be processed correctly, although one does get warnings about missing KB928366 & KB947722.


With .NET 2.0, Windows update declares that KB974417 has not been applied, also the processing order is perhaps not optimal:
NetFx20SP2_x86.exe
NDP20SP2-KB958481-x86.exe
NDP20SP2-KB971111-x86.exe Required for W2K
NDP20SP2-KB974417-x86.exe

Edit for cut & paste while half asleep.

This post has been edited by Kurt_Aust: 18 October 2009 - 11:29 PM

[YumeYao]

back from tests. Removing those components can reduce the final 7-zip size by 0.8MiB around, and doesn't harm on xp/2k3 at all.

[mooms]

If i don't want to install outdated vc++ runtimes with dotnet (like the YumeYao one) wich parameters should i change in snmsynth.ini ?

[strel]

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.

This post has been edited by strel: 22 October 2009 - 07:03 AM

[YumeYao]

@moons:
you can use my chinese installer (link or sp3only), extract it and replace language packs with yours, then repack it. Only that SNM won't slim down 3.5 LNG pack for you, if you need it and don't understand how to do it yourself, leave a post here, I'll help you with it.

@strel:
can you introduce to us what the progress is for next release. I know I have written too much on it.

This post has been edited by YumeYao: 22 October 2009 - 10:41 AM

[Raoul90]

strel, on Oct 22 2009, 03:02 PM, said:

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.

When are you planning to release it?