Jump to content

Silent .NET Maker synthesized 20100118 - W2K/XP/2K3 x86


strel
 Share

Recommended Posts

Hello ghostdlr,

I don't think you can use this for Vista or windows 7 (from reading the first post in this thread). The supported OS are 2K, XP and 2k3. The TARGET_OS option in the .ini lets you build on an OS different than the build machine (e.g. build for install on 2K using an XP box.). Also, I suspect 64-bit would require a different installer and is not supported by .net maker.

I'm no expert: I've just used this for creating a fully patched XP install disk along with HFSLIP. The last time I used it was March 2010. Whether it can integrate any subsequent .net patches I don't know.

You know that dotnet35.exe supports silent install itself, right? (/q /norestart switches)

I hope this helps,

Clark.

Link to comment
Share on other sites


  • 1 month later...

The new list for .NET Framework 1.1 (2011-05-13)


dotNetFx.exe
NDP1.1sp1-KB867460-X86.exe
NDP1.1sp1-KB971108-X86.exe - W2K only
NDP1.1sp1-KB2416447-X86.exe (supersedes KB979906)

The new list for .NET Framework 2.0 (2011-05-13)


NetFx20SP2_x86.exe
NDP20SP2-KB958481-x86.exe
NDP20SP2-KB971111-x86.exe - W2K only
NDP20SP2-KB976576-x86.exe
NDP20SP2-KB979909-x86.exe
NDP20SP2-KB982167-x86.exe
NDP20SP2-KB2418241-x86.exe (supersedes KB976765)
NDP20SP2-KB2446704-v2-x86.exe (supersedes KB983583, KB976569, KB974417)

All of them can be processed by SNMsynth but in case of KB2446704-v2 you may have to remove the "-v2" as the filename is too long and results in a "file not found" error.

As I'm using Windows 2000 I'm not really interested in making a current list of .NET 3.5 updates. Still it would be nice if someone else made an updated list for newer Frameworks :)

Edited by tomasz86
  • Like 1
Link to comment
Share on other sites

  • 1 month later...

I do have a problem with NDP1.1sp1-KB2416447-X86.exe, it seems to be in another format.

SNMsynth cannot process it. I get the usual popup that the switches aren't correct.

Any ideas are welcome.

Cheers.

Link to comment
Share on other sites

I've just checked it and the problem with this one is not its format but filename :lol:

Rename it to NDP1.1sp1-KBz2416447-X86.exe so it will get processed AFTER the other older updates (which are KB8x or KB9x).

wPZPd.png

Link to comment
Share on other sites

I've just checked it and the problem with this one is not its format but filename :lol:

Rename it to NDP1.1sp1-KBz2416447-X86.exe so it will get processed AFTER the other older updates (which are KB8x or KB9x).

Thanks a lot! In fact I did rename the file but not in that way. Going to give it another try, I could never have known that.

Cheers.

Edit: Smooth, everything got processed and it also shows in the process data. Only thing is that the output file is smaller despite the size of the now included KB2416447.

The update probably overwrites some old files.

Edited by Escorpiom
Link to comment
Share on other sites

hi,

NDP20SP2-KB2518864-x86.EXE doen't seem to integrate with the way making iexpress cab. WU still show it.<br><br>edit: I made mistake. now it seems correct on WU.<br>

Edited by ZEUS__
Link to comment
Share on other sites

Strange because file structure is "normal", i.e. it's not different from the other updates. Do you receive any errors when processing the file in SNM?

I hope it's not connected with the KB2x filename again. I think it can be safely said that you should change filenames of the new updates in order to get them processed after the older ones.

I can't check WU now as Win2k's WU is not updated anymore and doesn't show the new .NET related updates (even though they can be installed in 2K without any problems...) but I'll try to check it later on an XP machine.

Solved I think :)

Edited by tomasz86
Link to comment
Share on other sites

Guest Robinwood

Wow ! thanks ... am gonna take print out of this tips and share it with my friends in my college... :thumbup

Link to comment
Share on other sites

  • 4 weeks later...

The new list for .NET Framework 1.1 (2011-05-13)


dotNetFx.exe
NDP1.1sp1-KB867460-X86.exe
NDP1.1sp1-KB971108-X86.exe - W2K only
NDP1.1sp1-KB2416447-X86.exe (supersedes KB979906)

The new list for .NET Framework 2.0 (2011-05-13)


NetFx20SP2_x86.exe
NDP20SP2-KB958481-x86.exe
NDP20SP2-KB971111-x86.exe - W2K only
NDP20SP2-KB976576-x86.exe
NDP20SP2-KB979909-x86.exe
NDP20SP2-KB982167-x86.exe
NDP20SP2-KB2418241-x86.exe (supersedes KB976765)
NDP20SP2-KB2446704-v2-x86.exe (supersedes KB983583, KB976569, KB974417)

All of them can be processed by SNMsynth but in case of KB2446704-v2 you may have to remove the "-v2" as the filename is too long and results in a "file not found" error.

As I'm using Windows 2000 I'm not really interested in making a current list of .NET 3.5 updates. Still it would be nice if someone else made an updated list for newer Frameworks :)

Why is NDP20SP2-KB976576-x86.exe downloading as ndp20sp2-kb976576-x86_8e8121a8bddfb2095453335c593ffa22ef8e95ec.exe? And when I Google for it, I get what I think is strange. I get pages coming up in different languages, no pages linking to Microsoft about the update.

Link to comment
Share on other sites

Why is NDP20SP2-KB976576-x86.exe downloading as ndp20sp2-kb976576-x86_8e8121a8bddfb2095453335c593ffa22ef8e95ec.exe? And when I Google for it, I get what I think is strange. I get pages coming up in different languages, no pages linking to Microsoft about the update.

The explanation is here.

You should rename it to the proper filename 'NDP20SP2-KB976576-x86.exe' after downloading. By the way, in that topic you can find the current (updated) list of updates for .NET 1.1 & 2.0.

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share

  • Recently Browsing   0 members

    • No registered users viewing this page.


×
×
  • Create New...