[Caspean]

Ok I'm getting really confused. I did a search to find what exactly is contained in .net 3.5 redistributable. And there is basically no documentation I can find on it. According to fenyo it contains all of 2.0 and 3.0. Which would make sense because I don't see a link provided to download 2.0, only hotfixes and service packs.

fenyo, on Jan 5 2009, 01:49 PM, said:

Caspean, on Jan 5 2009, 07:39 PM, said:

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

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 ?

So can someone clarify that 3.5 redistributable contains all of 2.0 and 3.0 and not just the service packs?

strel, on Jan 5 2009, 02:50 PM, said:

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

So I take this to say that .NET 3.5 SP1 full redistributable does not contain the .net 2.0 or .net 3.0? This is confusing because if it only contains the service packs why is it so huge? Those service packs are like 16MB aren't they?

If I look at 3.5 redistributable and break it down based on the same grammar syntax then you are saying that it does not contain full installs for 2.0 and 3.0, but only the service packs for them. If that's the case where do I get 2.0 from?

If someone who does a FULL synthesis could please share the actual _SNMsynth.ini and directory contents this would help shed some light on this for me.

I don't understand how I can download both the 3.5 redistributable and 3.5 SP1 redistributable and have them in the same directory without modifying at least one file name.

Thanks,
C

This post has been edited by Caspean: 05 January 2009 - 02:34 PM

[strel]

2.0 SP#, 3.0 SP# and 3.5 SP# are not SPs are full frameworks versions (each one) updated to this SP# (of its own). You probably are trying to build updated installers for XP. Download 3.5 SP1 redistributable and updates for 2.0 SP2, 3.0 SP2 and 3.5 SP1, you don't need 3.5 redistributable (2.0 SP1, 3.0 SP1 and 3.5) unless you want any of the versions outdated. You don't need need NetFx20SP1_x86.exe because you have one 2.0 in .NET 3.5 SP1 redistributable. OK?
It's easy believe me.

[Caspean]

I want to start by saying thank you. I know it can be very frustrating trying to explain something to someone of a different native langauge, made even harder when the material is of a technical nature. Again, thanks for not getting to frustrated with me.

strel, on Jan 5 2009, 03:58 PM, said:

2.0 SP#, 3.0 SP# and 3.5 SP# are not SPs are full frameworks versions (each one) updated to this SP# (of its own). You probably are trying to build updated installers for XP. Download 3.5 SP1 redistributable and updates for 2.0 SP2, 3.0 SP2 and 3.5 SP1, you don't need 3.5 redistributable (2.0 SP1, 3.0 SP1 and 3.5) unless you want any of the versions outdated. You don't need need NetFx20SP1_x86.exe because you have one 2.0 in .NET 3.5 SP1 redistributable. OK?
It's easy believe me.

So can I also download .net 1.1 redistributable and its two hotfixes (NDP1.1sp1-KB928366-X86.exe and NDP1.1sp1-KB947742-X86.exe hotfix) and synthesize/integrate into a single installer in one shot? This was my assumption several post ago and nobody said it was correct, so I'm worried it is not correct.

Caspean, on Jan 5 2009, 02:12 PM, said:

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

.NET 1.1 Redistributable Package (dotnetfx.exe) for windows 2000, XP, x86 only.
NDP1.1sp1-KB867460-X86.exe hotfix for 2000/XP only.
NDP1.1sp1-KB928366-X86.exe hotfix for 2000/XP only .
.NET 3.5 SP1 full redistributable (dotnetfx35.exe -- note it's the same filename as 3.5 but this is 231 MB), contains .NET 2.0 SP2, .NET 3.0 SP2 and .NET 3.5 SP1. For XP/2003 only.
NDP20SP2-KB958481-x86.exe, NDP30SP2-KB958483-x86.exe and NDP35SP1-KB958484-x86.exe hotfixes for XP/2003 only.

Is this correct?

Thanks Again,
C
EDIT:

My directory now contains:
7-zip.chm
7za.exe
7zSD.sfx
copying.txt
dotnetfx.exe
dotnetfx35.exe
license.txt
NDP1.1sp1-KB867460-X86.exe
NDP1.1sp1-KB928366-X86.exe
NDP20SP2-KB958481-x86.exe
NDP30SP2-KB958483-x86.exe
NDP35SP1-KB958484-x86.exe
readme.txt
SNMsynth.cmd
SNMsynth_loud.cmd
_SNMsynth.ini

I have attached my _SNMsynth.ini file. Now I get this:

Processing .NET 1.1 installer...
Processing NDP1.1sp1-KB867460-X86.exe...
Processing NDP1.1sp1-KB928366-X86.exe...

Processing .NET 3.5 SP1 installer...
Processing .NET 2.0 SP2 portion...
Processing NDP20SP2-KB958481-x86.exe...
Processing .NET 3.0 SP2 portion...
Processing NDP30SP2-KB958483-x86.exe...
Processing .NET 3.5 SP1 portion...
Processing NDP35SP1-KB958484-x86.exe...


Creating merged .NET 1.1, .NET 2.0 SP2, .NET 3.0 SP2, .NET 3.5 SP1 installer...

Done!

Press any key to quit...

I'm going to assume I did this correctly and test the install of it now.

C

Attached File(s)

•  _SNMsynth.ini (2.05K)
  Number of downloads: 110

This post has been edited by Caspean: 05 January 2009 - 03:46 PM

[strel]

Yes, correctly for updated complete set of .NET frameworks for XP or 2003. This merged installer should be used on first logon.

[Caspean]

Thank you very much for your help and your patience.

I've tested it as a standalone on a couple systems and it seems to work perfectly. I'll now use HFSLIP and test it in the HFGUIRUNONCE folder to see if it I can successfully integrate it into my XP disc.

Thanks again,

ss3

[fenyo]

strel, on Jan 4 2009, 04:12 PM, said:

I should add that the file fenyo was prompted to download by MS Update when 3.0 SP2 language is installed from admin install (aka SNM installers),

Not just with admin install.
If i install the original pack (not admin install), it's showed size 10MB, but MS Update offers me 3.0 Langpack again! So it seems it's not just an admin-install problem.

strel, on Jan 4 2009, 04:12 PM, said:

wasn't the same 3.0 SP2 language standalone, as stated before, but 3.0 SP0 language standalone

strel, on Jan 4 2009, 04:12 PM, said:

This happened only under hungarian XP, not under english XP (with .NET hungarian languages), to make things even more strange.

I think this is because English XP doesn't need any language packs at all, so if an installed langpack is corrupted, it won't offer any, because it doesn't need one.

strel, on Jan 4 2009, 04:12 PM, said:

So what's happening? I think 3.0 SP2 hungarian language files for XP/2003 may be corrupted, causing installing though administrative install (aka SNM installlers), not to complete correctly

As i mentioned above, the standalone 3.0 SP2 Langpack install (not admin install; and i've installed xpsepsclangpack manually) does the same(MS Update problem) with installed size 10MB.

strel, on Jan 4 2009, 04:12 PM, said:

Any ideas?

You've said, that the 4 lacking file actually does not get into the system. What happens, if we just copy these files from an other language to hungarian Admin install? I think i'll try it...

[strel]

These 4 are not present in many other langpacks with the same structure, and don't generate problems. I don't think they are culprit of anything.

[fenyo]

strel, on Jan 6 2009, 11:06 AM, said:

These 4 are not present in many other langpacks with the same structure, and don't generate problems. I don't think they are culprit of anything.

Ok.
Then we have to tell M$ to repair their package.
(but i'm afraid it can take months...)

[strel]

.NET 3.0 SP2 language (for some languages)

There's problems when installing 3.0 SP2 from .NET 3.5 SP1 redistributable under some XP x86 localized versions:
- If you install english version (dotnetfx35.exe /lang:ENU), windows/ms update prompts you to download 3.0 SP0 langpack standalone.
- If you install some language to the english version windows/ms update prompts you to download the same 3.0 SP0 langpack standalone KB928416:
---> when installing dotnetfx35.exe normally, the installer downloads the language files, if you're connected, obviously
---> or when you install it from .NET 3.5 SP1 langpack standalone
---> or when you install it from a 3.0 SP2 language administrative install (aka SNM installers) generated from standalone langpack
In all install scenarios of 3.0 SP2 under hungarian XP are the same.

So, what's happening?

I think there's a problem with 3.0 SP2 framework under some XP X86 (maybe 2003 too).
It doesn't matter how you install it (with or without language), windows/ms update prompts you to download 3.0 SP0 langpack standalone.

And if you're going to use SNMSynth 3.0 SP2 installers under some localized XP (and maybe 2003, this has to be checked) and you want to get freed of win/ms update prompting to install 3.0 SP0 standalone language KB928416, I recommend you to use the method described in the "Obtain a Clean or Customized DataStore.edb File" section of this guide.

EDIT: I recommend to use the latests version the script that fixes this issue.

At least until MS fix all this.[/b]

Thx 4 your help fenyo.
Anymore ideas?

This post has been edited by strel: 16 March 2009 - 09:04 AM

[fenyo]

strel, on Jan 6 2009, 03:21 PM, said:

Thx 4 your help fenyo.

No, it is I who should thank you!

BTW, your summary is good.

And i've written a mail to the hungarian M$ group about this problem.

[simurqq]

strel, thank you very much for such a great topic!!! CMD and BAT scripts are my favourites when it comes to simplicity of install and complexity of the processes wrapped into just a few bits

But I have to admit that the synthesis of several .NET packs was NOT that simple for me at a first glance into the .INI file.

1- I'm a bit confused with batch instructions since my only experience with .NET is version 2.0 installed manually on my XP SP3 to use nLite. Could you please explain me the process in more detail, therefore?

Quote

It supports the following files:
.NET 1.1 Redistributable Package (dotnetfx.exe) for windows 2000, XP, x86 only.
Any NDP1.1*.exe, Sxxxxxx.msp and Mxxxxxx.msp hotfixes for .NET 1.1, specifically:
- NDP1.1sp1-KB867460-X86.exe hotfix for 2000/XP only.
- NDP1.1sp1-KB928366-X86.exe hotfix for 2000/XP only .

QUESTION 1: When you say "specifically", does that mean I need only the above-listed 2 (two) hotfixes/SP or .MSP files either?

2- I have downloaded this file: .NET 2.0 SP1 package (NetFx20SP1_x86.exe). But later in your post I found that:

Quote

.NET 3.5 full redistributable package (dotnetfx35.exe -- note it's the same filename as 3.5 SP1 but this is 197MB), contains .NET 2.0 SP1, .NET 3.0 SP1 and .NET 3.5. For XP/2003 only.
.NET 3.5 SP1 full redistributable (dotnetfx35.exe -- note it's the same filename as 3.5 but this is 231 MB), contains .NET 2.0 SP2, .NET 3.0 SP2 and .NET 3.5 SP1. For XP/2003 only.

QUESTION 2: Which one of "dotnetfx35.exe" should I download, if I want to make a full .NET pack with v1.1, 2.0, 3.0 & 3.5 with ALL hotfixes and updates?!? I assume that I cannot keep both "dotnetfx35.exe" files in the same folder since they contain identical names and, therefore, I need only one of them. This assumption leads to another question ->
QUESTION 3: If .NET 3.5 SP1 full redistributable contains .NET 2.0 SP2 (which is only ~9Mb compared to .NET 2.0 SP1 (NetFx20SP1_x86.exe) weighing almost ~24Mb), does that mean that I don't need .NET 2.0 SP1 anymore? What I understand from "SPx" is that it is the service pack only but NOT the full .NET pack v2.0 plus specific service pack. Am I right?!?

3- The following is an excerpt from my edited "_SNMsynth.ini" in the first run:

; -----  PROCESS MAIN PACKAGES
; These settings request processing of .NET 1.1 (dotnetfx.exe), .NET 2.0 SP1 (NetFx20SP1_x86.exe) and each one of .NET 2.0 SP1/SP2,
; .NET 3.0 SP1/SP2 and .NET 3.5/3.5 SP1 inside any of the dotnetfx35.exe (3.5/3.5 SP1 respectively). DNF2 can not be processed
; simultaneously from both NetFx20SP1_x86.exe and any of dotnetfx35.exe. None of dotnetfx35.exe is compatible with 2K.

PROCESS_DNF1=YES
PROCESS_DNF2=YES
PROCESS_DNF35_DNF2=
PROCESS_DNF35_DNF3=
PROCESS_DNF35_DNF35=

In this configuration I've managed to get rid of the error message I encountered first by running "SNMsynth.cmd" (which prompted with "choose what file is .NET 2.0 SP# going to be processed from"). However, I could only integrate .NET 1.1 and .NET 2.0 together.

Then (after reading your notes in .INI file), I've deleted the compiled file (DNFxxx.exe) from the OUT folder and restarted CMD with INI file re-configured as follows:

PROCESS_DNF1=YES
PROCESS_DNF2=
PROCESS_DNF35_DNF2=YES
PROCESS_DNF35_DNF3=YES
PROCESS_DNF35_DNF35=YES

QUESTION 4: Is this the right configuration to get a FULL .NET pack with all updates and hotfixes for XP SP3? I know, it depends on files I have put into the Work Folder. So, here is the list in alphabetical order:

dotnetfx.exe
dotnetfx35.exe (231Mb)
NDP1.1sp1-KB867460-X86.exe
NDP1.1sp1-KB928366-X86.exe
NDP20SP2-KB958481-x86.exe
NDP20SP2-KB958481-x86.exe
NDP35SP1-KB958484-x86.exe
NetFx20SP1_x86.exe

QUESTION 5 (Final): I also assume there is no way to make a full switchless installer in the first run only. If true, how many runs are required (can you post your .INI configurations for such specific runs in respective order)?!?

Thank you very much for your patience and support!!!

Rustam

This post has been edited by simurqq: 06 January 2009 - 03:24 PM

[strel]

I've got to review the guide, you're not the first to say it to me.

A1: This means the script can handle updates of this types for 1.1, specifically of the types MS make available to us for 1.1 nowadays, all are in the list.

A2 & A3: There's no SPs standalone, in every case it is the complete framework updated to that SP#. The script only admits one dotnetfx35.exe. Choose your update condition. If you use NetFx20SP1_x86.exe and any dotnetfx35.exe , you have to choose which of the 2.0 SP# versions contained in these packets you are going to process, the script cannot be fed with two different steps (SP#) of the same framework #.# , even not with the same step (SP#) of the same framework #.# from 2 different files.

A4: To get FULL merged installer, apart of feeding the process with the correct frameworks you want (this is matching correct packets in the work folder with the settings in .ini file that triggers the process of the frameworks contained in it that you want), you have to set MERGE_FRAMEWORKS=full in the .ini file. Configuring the setting this way only build the full installer you want if you fed the process correctly, if not the merged installer would be partial only.
In your list you repeat:
NDP20SP2-KB958481-x86.exe
NDP20SP2-KB958481-x86.exe ----> You need NDP30SP2-KB958483-x86.exe

and:
dotnetfx35.exe (231Mb)
...
NetFx20SP1_x86.exe ---->Last version of 2.0 is 2.0 SP2 contained in dotnetfx35 (231 MB). You can delete this file or empty PROCESS_DNF2 not to feed the process with it.

The script deletes automatically files generated in an incomplete or wrong, building process.

A5: You can make full single switchless installer in one run. Another uncommon results like merged 1.1+2.0 + merged 3.0+3.5 needs 2 runs. Don't know of any combination requiring 3 runs.

Is that Azerbajan, isn't it? Good luck.

This post has been edited by strel: 23 March 2009 - 09:53 AM

[RickSteele]

Check it out [for XP (x64)]
http://www.ryanvm.ne...opic.php?t=6419
works very well

[strel]

Updated.
Enjoy.

[thophi]

@strel: Thanks for this great tool

But I have a problem. After installing the complete package wsus still want´s to install kb932471, but can´t do this (error). This patch should be included in the latest 3.5er SP-releases. Anyone knows how to fix this?

[strel]

Can you give me details?
- Your SNMsynth.ini settigns.
- The merged installer filename you get.
- What windows version are you installing on and language?
- What files did you put in the work folder?
- What method did you use to install?

You're updating through WSUS, is there any chance you could try to update from windows/ms update through the internet to validate results? Ask your netadmin in case it's not you.

This post has been edited by strel: 09 January 2009 - 05:59 AM

[strel]

From MSDN forums, it's very explanatory with the condition:
FAILURE: Update for .NET Framework 3.0: x86 (KB932471)

Aaron Stebner points one possible cause, but this was posted one year before the last one in the previous link:
.NET Framework 3.0 hotfix (KB932471) will fail to install if .NET Framework 3.5 beta 2 is installed

Here is offered a possible workaround:
Dot Net 3 SP1 & KB932471 problem - Makave234

Tell us your experiencies with this, please.

This post has been edited by strel: 09 January 2009 - 07:51 AM

[fenyo]

fenyo, on Jan 6 2009, 04:30 PM, said:

i've written a mail to the hungarian M$ group about this problem.

I've received a reply from Microsoft Hungary Ltd, they told me they forwarded my problem to their center.

[strel]

Good news for hungarian speakers. Thank U.

[Inki]

FYI, everything appeared to go smoothly, when I used the latest (20090107) script to create a passive, merged installer for .NET 1.1 and 2.0 SP1 + all hotfixes, and then applied that at T-13 with HFSLIP to create a fresh Windows 2000 installation.