[Tomcat76]

I guess I should update the info in the main thread. DNF30.exe force-installs this program (the original in .NET 3.0 or the updated version) from a batch file, which probably explains why you don't get that error message when you install .NET 3.0 normally.

[darafat]

hi there,
eheh again me
anyway i use to install the net frameworks only because i need to use the visual studio...
now visual studio 2008 pro as been released and it needs the net framework 3.5 beta 2....
i tryed to use the microsoft net 3.5 downloader because i couldn t find the net framework 3.5 beta 2 as a full installer....
now i used this with win xp without the net frameworks installed (eheh i use your 3 frameworks ) for to see wich frameworks are really needed for it. now after the download i find only the net framework 2.0 (23 mb) , dotnetfx30 (29.3 mb) and the dotnetfx35 (6.4 mb) with the lang pack (44 kb)... O.o, now their size are really strange while your:
net framework 2.0 is about 39.8 mb
net framework 3.0 is about 25.9 mb

now your script also include the hotfix and langpack, but it seems their are also included in this download (maybe yout script include also the installer for x64, in this download there are only installer for x86).

Then in this download there is not the framework 1.1 (and now i m thinking that it is useless)
But the real problem is, after installing the net 1.1 - 2.0 and the 3.0 of your script i finally run the net framework 3.5 just downloaded and an it says that it is needed the net framework 3.0 sp1 O_O (i didnt find it on the web)

Now can you explain what the hell it s happening? O.o

Anyway this post must be sticked because is really usefull, and i hope that you will contuinue you wonderfull work including the net framework 3.5 in your script

Thanks so much for this and for your great answer about the directx

p.s: here there are the images with the contents of the download:
General Folder
dotnetfx 2.0
dotnetfx 3.0
dotnetfx 3.5

This post has been edited by darafat: 11 August 2007 - 10:27 AM

[bigfatroundguy]

Tomcat76, I understand that the 7zS.sfx file has been compressed using UPX. I have tried to change icons of the resulting .NET installers to use the same icon as "ndpsetup" (.ico file attached) using reshack and it fails. I believe it is failing due to the fact that your 7zS.sfx file has been compressed. I have tested reshacking the 7zS.sfx file that comes with 7z and it works fine with your .NET installers - its just not compressed.

I read the 7z help file that indicates that UPX can compress 7zS.sfx files, so I tinkered with UPX - way cool! Executing UPX --help in a command window reveals all its secrets. bottomline is that you drop an sfx file into the same folder as UPX and from a command window you execute UPX --best --ultra-brute file.sfx and voila, it compresses all the pieces it can and leaves you with a compressed version of the same file written over the existing one.

so I took the standard 7zS.sfx file that comes with 7z, res-hacked it to use the icon file (attached), compressed it with UPX and used this instead - works perfectly (so I attached this too!). then out of curiosity, I compressed the standard 7zS.sfx file as it stood and it compressed to something slightly smaller that what you have currently packaged up (so I attached this too!). finally, I took the enhanced sfx files from http://unattended.so...attended.en.htm, res-hacked the uncompressed 7zS only file and compressed it as well (also attached).

So, in the end, thank you for putting together these .NET installers (I haven't tried .NET 3.0 but i'll get to it). In return, I have attached some more colorful SFX files and the .NET icon file for anyone to use.

Attached File(s)

•  Icon___SFXs.7z (163.37K)
  Number of downloads: 49

This post has been edited by bigfatroundguy: 13 August 2007 - 01:43 PM

[darafat]

eheh,
installing the visual studio 2008 i saw more fromeworks... lol

It will be a great thing to make unattended this stuff:

.NET Framework 1.1 (already included in your script)
.NET Framework 2.0 (already included in your script)
.NET Framework 3.0 (already included in your script)

Adding this stuff:

.NET Framework 3.0 Service Pack 1
.NET Framework 3.5
.NET Compact Framework 2.0
.NET Compact Framework 3.5

Eheh, i m asking too much

If it is not enought for you, you can make this stuff for x86 and x64 (priority at the x86 lol)

p.s: it was only an idea, not a request. just because i think that the net frameworks are basically for developers

[Outbreaker]

HI

How can i do if DNF3.0 gets Installed after the first login.
I have put in nLite under Unattended->RunOnce:
%SOURCE%\RunOnce\DNF3.0.exe
But it gets not Installed after the first login.

This post has been edited by Outbreaker: 22 August 2007 - 11:05 AM

[Arie]

I've used Silent .NET Maker to pack Microsoft .NET Framework 1.1, 2.0 and 3.0 to use with HFSLIP 1.6.2. I placed all three files (DNF11.exe, DNF20.exe and DNF30.exe) in my HFSVCPACK folder. The installation of Microsoft Windows XP Professional with Service Pack 2 goes fine until the T-13 mark. Microsoft .NET Framework 1.1 is installing fine, followed by 2.0, however once installing Microsoft .NET Framework 3.0 it returns an error code:

Windows Communication Foundation -- Error 1304.Error writing to file: Microsoft.Transactions.Bridge.dll. Verify that you have access to that directory.

There is already a topic regarding this error message, but it concerns the above error code when you install Microsoft .NET Framework 3.0 via RunOnceEx.

What can I do to solve this problem and have it properly install at the T-13 mark as both Microsoft .NET Framework 1.1 and 2.0 do?

[Arie]

Doing it differently now. I've used Silent .NET Maker to pack Microsoft .NET Framework 1.1 and 3.0 into only one file. I will use HFSLIP later on today to cook up a new image after which I will test it. Crossing my fingers...

[ponghy]

I bump this topic because after several days of researching and tests I've figured out that repair ability for .NET 2.0 is not working well in your .NET Maker ONLY if you slipstream the KB928365 patch, and I think it's virtually impossible to workaround this in any way.

Do the test yourself:

Try to delete the following file:
%WinDir%\Microsoft.NET\Framework\v2.0.50727\AppLaunch.exe . This file is marked with the following version string:
2.0.50727.832

Now, go to Control Panel > Add or Remove Programs and click the "Modify/Repair" button for the "Microsoft .NET 2.0 Framework" entry. The setup program appears. Select the "Repair" option and click Next. Repair process will take place. When repairing is complete, go to the previous directory:
%WinDir%\Microsoft.NET\Framework\v2.0.50727\ , and show the properties for file AppLaunch.exe. You will see that the string version is the following:
2.0.50727.42
That is, the original version shipped with .NET Framework 2.0 (not the patched one included in KB928365). The repair process restores the original version of .NET Framework files, not the patched version (with KB928365 applied).

The reason is simple: The hack you said me modifying the PackageCode value in the Registry is necessary in order to Setup can work with the original database of .NET Framework 2, since performing and administrative install of the product modifies the PackageCode in the administrative image. Due to this, Setup always use the original database to repair missing or damaged files.

Now, I see why RyanVM removes the repair ability (source cache feature) of .NET Framework 2, not only for freeing space.

I hope this post will be useful for you.

Regards.

This post has been edited by ponghy: 09 September 2007 - 05:23 AM

[AgiHammerklau]

Did you have SFC en- or disabled ?
Agi

[ponghy]

AgiHammerklau: I have SFC enabled, but this is not meant for .NET Framework 2. The repair process restores the original files of .NET 2 with or without SFC enabled. And this works in that way because the database contained in the CSetupMM subdirectory (the source cache feature) is the original database of .NET 2.0, not the patched one by KB928365. Setup extracts files from this MSI (database) file when repairing.

Currently I'm working on modifying the PackageCode of the product stored on the Registry to match with the stored in the patched version of the MSI file. If both Package Codes don't match, a severe error will occur when uninstalling or repairing.

This post has been edited by ponghy: 10 September 2007 - 05:29 PM

[BaTLeZone]

WOW this is great. Worked perfectly.

[sadam]

First - newbie alert! Thats me. Please be patient.
Second - sorry for my bad english - it isn't my native.

Subject: DNF30 is absent.

Description:
I am SNM user. I am HFSLIP user. I am nLite user. I'm slipstreaming XP Pro SP2 Corp. Own hands integrated SP2. From SNM I'm using DNF11_20 and DNF30. I put that into HFSLIP. DNF30 into HFGUIRUNONCE folder. I integrate all my after SP2 hotfixes with HFSLIP too. I run HFSLIP to have SOURCESS folder. For nLite. In nLite I make exclusions, registry settings and unattended install. I burn the CD (physically) and I'm installing that on other, clear machine. Connected to net. To my local lan.

The system installs without any error messages and works. I'm going to WindowsUpdate. It says me, that I haven't the Net Framework 3.0.

I'm going to my machine. OK lets move DNF30 from HFSLIP to nLite. I'm copying the all HFSLIP folder structure in second place. I move DNF30 out, delete SOURCESS folder, run HFSLIP, copy SOURCESS to nLite and include there the moved out DNF30. Burn, install and go to WindowsUpdate. Now I have the Net Framework 3.0. On my work machine I'm looking to my first HFSLIP SOURCESS folder. There isn't DNF30.EXE. DNF30 is absent.

OK, OK it is. As a command to run, in HFSGUI.CMD (name of the file is near the oryginal - now I am in my work, and I dont' remember correct - there is only one CMD file like).

Question to experienced users HFLIP and SNM: Is the absence normal?

Some other details: HFSLIP 1.6.2, SNM downloaded from that thread (first, main post) 2 days ago (problem - in ZIP I don't see the version number - in CMD, INI and readme), nLite 1.3.5.

[zxfiles]

Anyone know how to incorporate the 2.0 Service Pack (NETCFSetupv2.msi)? I can't seem to get it to merge. Any help would be greatly appreciated.

[Sonic]

NETCFSetupv2.msi is for Compact Framework if I remember, it isn't necessary for regular pc ... and it's different from .NET Framework 1.1 SP1 or 2.0 ...

[DarkShadows]

The first post in the thread only lists:

Quote

- any msxml6-KB*.exe or msxml6*.msi (to update version in .NET 3.0)

Am I wrong, or shouldn't SNM also support the following?

msxml4-KB936181.exe (released in August 2007)

[DarkShadows]

Then again, perhaps not. According to this KB article, MSXML 6.0 is added with .Net Framework 3.0. One would think that the earlier DNF versions might use an earlier version of msxml, but apparently not.

BTW, your script simply rocks!

[DarkShadows]

I'm wondering if someone can help me out here. I'm using the default SNM.ini file. I downloaded everything to a folder path with no spaces. Below is a Tree report of my folder listing. I have no search indexers running or search engines installed. I have ensured I have nothing else accessing these files, by closing all non-essential processes in Task Manager. I have only a copy of Windows Explorer open, when I click on the SNM.cmd file.

M:\SLIPSTREAM\DOTNET\SMN
|	SNM.cmd
|   _SNM.ini
|   _SNM - Backup.ini
|   7za.exe
|   7zS.sfx
|   dotnetfx.exe
|   dotnetfx2.exe
|   dotnetfx3.exe
|   hidcon.exe
|   msistub.exe
|   msxml6-KB933579.exe
|   NDP1.1sp1-KB867460.exe
|   NDP1.1sp1-KB886903.exe
|   NDP1.1sp1-KB928366.exe
|   NDP20-KB928365.exe
|   NetFX30-KB932471.exe
|   readme.txt
|   xpsepsc.exe
|   
+---DNF2
|   \---DNF20
|	   \---Win
|		   \---Microsoft.NET
|			   \---Framework
|				   \---URTInstallPath
|					   \---ASP.NETWebAdminFiles
\---OUT1
		DNF11.exe  (11,300KB)
		DNF20.exe  (39,004KB)
		DNF30.exe  (21,969KB)

As you can see in the attached screen grab, SNM.cmd cannot access one of the files above, apparently for .Net 3.0. When I install the resulting DNF30.exe, Windows Update still reports that I require KB933579. So I'm assuming that is the file that does not get slipstreamed into the installer correctly.

I have tried re-downloading all the files, ensuring each was for Windows XP SP2 (x86). I have run this script several times and each time it chokes on the same file. Am I do something wrong, or is the script in a race condition?

Any help is appreciated, Thanks!

Attached File(s)

•  Errors.png (11.42K)
  Number of downloads: 64

This post has been edited by DarkShadows: 04 October 2007 - 05:57 PM

[Arie]

Delete the file, or simply move it, download it again and run the script once more and see if that does the trick. Oh, and before retrying, also reboot your machine.

[Floppy]

Hey
I have 2 KB's giving me a hard time.(KB934238 and KB933579) (Norwegian XP)
Have read through this forum I fond this:
KB934238

Tomcat76, on Jun 18 2007, 06:34 PM, said:

Alright. These are clearly updates for .NET 3.0. I will update the SNM script for this when I have the time. It shouldn't be too hard to add support for them.

Iam using the SNM script. an the folder looks like this;

What amI missing?

Chester, on Jun 24 2007, 10:44 AM, said:

I confirmed KB934238 and language file were able to be integrated.
Thanks!!

Can you pls. tell me how you did this?

Attached File(s)

•  HFSLIP.txt (5.6K)
  Number of downloads: 28

This post has been edited by Floppy: 13 October 2007 - 04:38 AM

[Tomcat76]

sadam, on Sep 14 2007, 03:21 PM, said:

Question to experienced users HFLIP and SNM: Is the absence normal?

It is normal if you don't put it in nLite's "keep list". You may find this utility useful if you want to use nLite after HFSLIP. It must be run before running nLite, though.

DarkShadows, on Oct 5 2007, 01:56 AM, said:

As you can see in the attached screen grab, SNM.cmd cannot access one of the files above, apparently for .Net 3.0.

What I wonder about is the title that's showing in the title bar. Is this a modified version of Silent .NET Maker?

Not that it's important at this stage, but the XPS update named as xpsepsc.exe is not supported. You should keep at least "xpsepsc-x86-en-us" in the name.

Floppy, on Oct 13 2007, 12:35 PM, said:

I have 2 KB's giving me a hard time.(KB934238 and KB933579)

I see two problems.

1) You are including both msxml6_x86.msi and msxml6-KB933579-enu-x86.exe. Silent .NET Maker only takes one and it uses the MSI because it's faster, but the file named "msxml6_x86.msi" is old so you should remove it. Silent .NET Maker will then use msxml6-KB933579-enu-x86.exe. If you want, you can use msxml6.msi from inside msxml6-KB933579-enu-x86.exe to make things faster but it's not required. This should solve the KB933579 problem.

2) Your KB934238 problem is probably due to the absence of the KB934238 update for the main .NET 3.0 package. You only have the KB934238 update for your language pack.