strel

I have updated SNM Synthesized in post #279 script to version 7 to correct some bugs I dropped in my previous update, and add cosmetic changes. Hope you enjoy.

Have you tried without /quiet? Had the system connection at that time? Interesting.

And what langpack version?

I meant the system waits for a download to continue, the language files obviously, not an intalling crash.

This doesn't probe anything more than 3.5 SP1 redist has "some slight" localization. What do you mean? FIREPROOF: Disconnect your 100 MB/s connection and type dotnetfx35.exe /lang:DEU. Installation will hang at download time. What else?

I don't think so. I think dotnetfx35.exe downloads from MS the language language files you need depending on your own system language, and installs it. This applies to the other examples you give. Even the updates-disabled one, the installer doesn't use win/ms update system, it connects directly. Where did you find the language files in the extracted .NET 3.5 SP1 redistributable? Using your method dotnetfx35.exe is a monster of 231 MB to include in your source, and needs to download language files depending on your system language while the installers obtained by this method are bellow 70 MB all the set. You can use too other unattended installers .NET installers not obtained with SNM method, there are various examples on the web, but lacks language packs, or only has it for one language or are not completely updated, or doesn't fit for win2k or win2k3. SNM handle with this issues.

For latest versions of 1.1 you have to download 1.1 and all its updates (NDP1.1sp1-KB867460-X86.exe NDP1.1sp1-KB928366-X86.exe NDP1.1sp1-KB947742-X86.exe). 1.0 is outdated and not supported by SNM nor SNM Synthesized hence. I thought that if you want latest versions of 2.0, 3.0 and 3.5 for win XP/2K3 (not for win 2K), they are embeded in .NET 3.5 SP1 full redist (.NET 2.0 SP2 and 3.0 SP2), and only needed this. EDIT: Forget what I wrote about KB953595, it's included in 3.5 SP1 full redistributable, hence in the installers obtained with SNM.

If you want latest versions of 2.0, 3.0 and 3.5, they are embeded in .NET 3.5 SP1 full redist (.NET 2.0 SP2 and 3.0 SP2), only need this. For latest versions of 1.1 you have to download 1.1 and all it's updates.

Have you used .NET 3.5 SP1 and 3.5 SP1 langpack or have you used .NET 3.5 and 3.5 langpack? Note both set of files have the same filenames.

SNM can build to you switchless full silent or only unattended installers with language packs and updates included, individual for each framework or merged; giving you a lot of flexibility for your setup, in a transparent manner.Read carefully post #279.

It's almost equal to what emzendron describes in post #235. No idea of what is happening. But be more specific.What versions did you use? Are you sure you used .NET 3.5 SP1 and 3.5 SP1 langpack? filenames are equal to that of the 3.5 versions. Did you merged frameworks? Did you uninstall previous versions before using the installers? Did you have .NET 2.0 SP1 langpack or .NET 3.0 SP1 langpack in the work folder when you build the installers?

2 ALL: I've remade solution in post #265 with cosmetic enhancements, error checkings and full compatibility with Tomcat script; and updated SNM Synthesized in post #279 to include the changes. I've made a new flavour for monitoring the installing process. Resulting installers don't change from previous version except for the new flavour, of course. 2 grx11: Thank to you for helping testing. 2 Stoner81: I don't get your results. Recheck and if you get it again, tell us, but be more specific. 2 Trolleri: Installing 1.1 and 2.0 from svcpack.inf, 3.0 and 3.5 on first logon it's OK too. Me too. MS says 3.5 SP1 is not supported for win2k and there is no other link to get 2.0 SP2.

Forget it, just a vague idea. DEP is a feature of XP that prevent programs to execute in some memory allocations reserved for the system to extra protect it from malicious software. Look in System Propierties\Advance\Performance-Settings\Data Execution Prevention. Your message happens at T13, and migrate.exe is related to Windows Media. Maybe something wrong with WMP installing from svcpack.inf.

You can make it through a theme: Unattended Guide - Themes Or through registry tweaks, search the forum or the web for the one you need.

Maybe has something to do with Data Execution Prevention.

With the last update you can build ad-hoc localized installers, selectin what versions to process and selecting the switchless default verbosity of the installers you build. You can even use switches with this installers to modify its default switchless behavior at run. For now on you can build ad-hoc nlite add-ons in an automated process. Enjoy!

Well, putting it online would violate point 13 of XP pro EULA about software transfers, but I rather meant making the script use the latest version it founds after comparing the .cab file version and the one in each user's system folder. I don't think this would violate EULA. The software would come from MS through the update system and the installers would be updated as possible, depending on the update condition. But yes, not all OS files would come from a direct download to the builder folder and maybe not all the installers would be exactly equal, depending on the update condition. Anyway, I made my own installer based on your script. Forgot to say it. Great work.

Have you considered taking muweb.dll 7.2.6001.788 directly from %SYSTEMROOT%\system32 instead of 7.2.6001.784 since there seemed to be no download link available?

You'll find this method implemented for 2K/XP/2K3 X86, all languages, all frameworks and updated in Silent .NET Maker synthesized.

No idea. Search the web, there is a lot of registry settings information. And if you don't find it and you know how to change the setting manually, use Process Monitor to try to identify the reg key this setting changes.

I hope this is what you're asking for:.NET 3.5 SP1 must be installed at first logon, not at T-13. Use: - GUIRunOnce (here too) or - RunOnceEx / RunOnceEx from CD

I've tried to recreate your results with danish langpacks but I got .NET 2.0 SP2 and .NET 3.0 SP2 danish langpacks installed correctly (on an installed XP). You are doing something different than I do. I think you could have used .NET 3.5 SP0 langpack instead of .NET 3.5 SP1 langpack, both have the same filename.

The only way I think it's possible is having installed another OS in C: when you run setup.

You can try to change the default user configuration registry settings to this the cursor pack sets, before they are applied, or even you can try to install you cursor pack via startup script after runonceex.

I think you can't.