bitmonster

I suggest you reread the "Terms of Use" at SourceForge. SF only hosts projects with OSI-approved licenses. If you don't intend to license it under one of these licenses or don't intend to publish the sources from the beginning, you should not register a project there. All at SourceForge is about open source in the first degree and not binaries.

Sorry to insist, but why? This is no fair use of SourceForge's services.

Sorry to ask, but where can I find the source code?

what is a /Dnetfxsp1 switch?/D defines the working directory where START should execute the msiexec. "netfxsp1" is the directory where the SFX will unpack the .NET-stuff. The SFX will also create directories for langpack, HighMat and so on. And this way every directory will be handled separately.

Yes, you are right. Actually the script is not installing the stuff itself, but creating an SFX-file that can be used to do all the installs when it's executed. This way it compresses much better than individual archives and can easily be extended to include even more stuff. No, the code is complete. EOF means "End Of File" and is a predefined label in the batch interpreter. This goto-statement is comparable to an exit-statement, but because I use a subroutine-like block, this special trick is needed.

Not directly. You can't integrate it to the installpoint of .NET (as far is I know) but you can create an own installpoint for it and pack both into one sfx. Here is a version that I use to also include JViewer and HighMAT into the same SFX so they all compress better. Just put your langpack.exe in the same folder as described in my guide and create this batch file as make.bat: If you want to also include JViewer and/or HighMAT just copy JViewer.exe and/or Q831240.exe to the folder and the batch will automatically include them to the netfxsp1.exe.

The approach posted from Kaspin should do the trick: http://www.msfn.org/board/index.php?showtopic=25118 It will only install the Control Panel and SmartGART through RunOnceEx if an ATI card has already been installed through Windows-Setup. Similar approaches I use to install tools that are only needed if some special hardware is present. For me it works fine.

Hmm, actually it should be the other way round. An msiexec.exe from SP1 should run on both SP1 and SP2. But the msiexec.exe from SP2 only runs on SP2.

Yes!

OK, I made some more tests on an XP-SP2-install and everything runs fine so far. Would be nice if XP-SP1-users could test this out. Here is a small guide how to create your own: Get the .NET framework v1.1 re-distributable package and put it in some folder. Get the .NET framework v1.1 SP1 update and put it in the same folder as above. Get 7-Zip and install it. Open up the folder where 7-zip has installed itself to and grab the 7za.exe and 7zS.sfx files and copy them to your folder. You can deinstall 7-Zip now if you want. Get the UPX-package (Win32 console version), unpack it and copy the upx.exe to your folder Get the StartX-package, grab the StartX.exe out of the archive (you find it in the 'Release' folder) and move it to your folder. Make a new batch-file in your folder, name it make.bat and paste the following text into it: Now you should have the following files in your folder: 7za.exe 7zS.sfx dotnetfx.exe make.bat NDP1.1sp1-KB867460-X86.exe upx.exe StartX.exe Start the make.bat and wait 2 minutes. At the end you should have a netfxsp1.exe in your folder with a size of about 11.3 MB. You can run this standalone file through svcpack.inf or any other batch without any commandline switches. But if you use a batch instead of svcpack.inf you should use the start-command:

Sure. I currently test it on an unattended svcpack.inf install. If everything runs fine, I will post an updated guide.

OK, the impression that the installation takes longer was bulls***. They both seem to take quite long. I just tried the last idea with the 'bridge-exe' and it also seems to work fine. The resulting .exe is 60kB bigger, but I like the idea to use the most up-to-date msiexec that the system can use.

The approach to use msiexec.exe from an XP-SP1 seems to work. I just tested such package on an SP2 XP-machine. But the installation seems to take much longer. I will test it more extensively tomorrow. Another solution might be to use a 'bridge-exe' to fire up the msiexec of the system where the package currently get's started.

@koszopal I tried it with the german langpack and the 7z-method downsized the file from 1.37 MB to 670 kB. Here is the batch I used: Simply put your langpack.exe and this batch-file in the same folder as described for the .NET-SP1-method. After you have run this batch, you should have a 'langpack-new.exe' in your folder.

There is no -y switch. Just call it without parameters.

The netfxsp1.exe mentioned above runs from CD (simply because it unpacks itself first to the user-temp-folder before executing msiexec).

Didn't understand what you ask really. If you need a languagepack, you can simply install it directly after the netfxsp1.exe. As far as I know a languagepack cannot be 'slipstreamed' into a .NET-Adminsitrative-Install-Point. But as the resulting netfxsp1.exe runs like charm from svcpack.inf there is no problem to install the languagepack directly afterwards. But there are also localized-builds of the .NET-1.1-package, so it might be a good idea to use them instead of the default english one. But I haven't got any problems with the english-packages, even when I install a german-languagepack afterwards. Anyhow you can change the language at the microsoft-links I posted above and get the right one for you. The batch should work with every version. It might be possible to create a 7z-languagepack-installer to save some bytes. Hmm, will see if this would bring any benefit.

Attention! This guide is outdated! Look on page 24 to see the new one! The 7z-Method is the most space-saving method I know of, so I don't think you can beat it with something else. It will also run from everywhere. Here is a small guide how to create your own (might be usefull, if you want to use localized builds of .NET): 1. Get the .NET framework v1.1 re-distributable package and put it in some folder. 2. Get the .NET framework v1.1 SP1 update and put it in the same folder as above. 3. Get 7-Zip and install it. 4. Get the UPX-package (Win32 console version), unpack it and copy the upx.exe to your folder 5. Open up the folder where 7-zip has installed itself to and grab the 7za.exe and 7zS.sfx files and copy them to your folder. 6. Now you need to make a batch-file in your folder, name it make.bat and paste the following text into it: Now you should have the following files in your folder: 7za.exe 7zS.sfx dotnetfx.exe make.bat NDP1.1sp1-KB867460-X86.exe upx.exe Start the make.bat and wait 2 minutes. At the end you should have a netfxsp1.exe in your folder with a size of about 11.3 MB. The machine where you make this should have XP-SP2 installed, if you want to use the package on a XP-SP2-CD.

@j4ever The TabletPC-way will also work, as far is I understand it. Because it will install .NET as a windows component, it will already be installed when RuneOnceEx executes the ATI-install. So his suggestion is also helpful (but complicated).

@j4ever You can simply wait till RyanVM releases the new 7zip-SFX-installer for .NET 1.1 with SP1. It will run without your problems from svcpack.inf. Ryan already has the file, so I expect he will release it tomorrow. If not I will write a step-by-step guide to let you create your own.

I've tested the 7zip-installer a dozen times on a real-machine from svcpack.inf now and it works flawless. You don't need to call it through RunOnce. The automatically created temp-folder is removed for sure after the installation and I can't find any other straying files/folders. The batch or svcpack.inf will definitely be interrupted till the installer finished its job (i've tested it with a call to a cmd-window). I have a .NET-languagepack directly after the .NET-install, that would give an error if .NET is not installed right, so this should work for every language. This SFX is really easy to use, as you don't need any commandline-switches to start it. I've contacted RyanVM so he will possibly host the ready-made package (if he hasn't made his own till now ).

OK, I have a working version for svcpack.inf and normal batch-operation. The 7z-SFX-Installer does interrupt execution till netfx.msi has completed it's installation, so it does not have the drawback of the RAR-SFX. It will also make the archive a bit smaller. You have to include msiexec.exe in the package, because the 7z-SFX can only call programs in the folder it has unpacked. I've used the "7zs.sfx" module and downsized it with UPX also. My config-file looks like this: You only need to include the resulting netfxsp1.exe in the svcpack.inf and everything works smoothly. The tempfiles will also be removed automatically. If someone has the webspace to host the file, I can supply a ready-made version (11.3 MB).

@Coolsights2000 Basically the SFX works, but there is one problem, that you might not notice, because you don't need a NET-Languagepack. The NET-SP1 installer will give control back to svcpack.inf directly after the unpacking has happened and the actual installer runs in his one process. So next the LanguagePack starts and can't find a NET-install, because the installer hasn't finished it's job now. There might also arise problems with qchain.exe if something like this happens. BTW: What does the "!-" in "Setup=netfx.msi /qb!-" do? I haven't got this working through svcpack.inf till now. Unpacking works, but how can I call the the netfx.msi? Because it's now not in in the folder that is defined through svcpack.inf (CatalogSubDir), we will have to supply the path. But till now every path I supply doesn't work.

Good idea, I will try it. Currently I have modified the the skript to: ;The comment below contains SFX script commands Path=%systemroot%\temp\dotnet SavePath Setup=cmd /C start /wait netfx.msi /qb Silent=1 Overwrite=1 but this will popup a command window. My experiments have shown, that netfx.msi itself will not block, so there might be the same problem if I start it directly from svcpack.inf. But I will try it out.

There seems to be one problem with this approach. The SFX will not block the execution of a script, till it completes its installation. So if you use this in svcpack.inf, things will go unpredictable. Is there any chance to make this a "blocking SFX"?