Jump to content

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


strel
 Share

Recommended Posts


No, the script handle .NET and its updates, this is a windows update, it's only mentioned for completeness.

But if you pretend to build an unattended windows set integrate it as you used to do; and if you're using the installers on a installed windows, then simply let update system do its job.

Link to comment
Share on other sites

No, the script handle .NET and its updates, this is a windows update, it's only mentioned for completeness.

But if you pretend to build an unattended windows set integrate it as you used to do; and if you're using the installers on a installed windows, then simply let update system do its job.

I think I can install AIO .NET from svcpack and then at first logon I can install KB961118 with "/Passive /NoRestart" switches. I'll try that later today.

Link to comment
Share on other sites

I think I can install AIO .NET from svcpack and then at first logon I can install KB961118 with "/Passive /NoRestart" switches. I'll try that later today.

I have done this at Runonce and it works great. No updates needed afterwards!

------my RunOnceEx.cmd------

cmdow @ /HID

@echo off

SET KEY=HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnceEx

REG ADD %KEY% /V TITLE /D "Installing Applications" /f

REG ADD %KEY%\005 /VE /D "Install all DotNET(s)" /f

REG ADD %KEY%\005 /V 1 /D "%systemdrive%\Temp\NETFXAIO.EXE" /f

REG ADD %KEY%\010 /VE /D "Install KB961118" /f

REG ADD %KEY%\010 /V 1 /D "%systemdrive%\Temp\KB961118.exe /q /n /z" /f

REG ADD %KEY%\055 /VE /D "Cleaning Up temp files!" /f

REG ADD %KEY%\055 /V 1 /D "%systemdrive%\Temp\cleanup.cmd" /f

EXIT

Link to comment
Share on other sites

Sorry if this question has been answered, but I don't understand all the information in this topic because I don't speak english.

I created the installers and I tried to install them using SVCPACK method, the problem is that it doesn't work and I don't know why. I added the installers this way:

[SetupHotfixesToRun]
HFSLIP.CMD
Q923789.EXE /Q:A /R:N
DNF11es.exe
DNF20SP2es.exe
DNF30SP2es.exe
DNF35SP1es.exe
IMAPI_XP_SRV2003_x86.exe /quiet /norestart
Silverlight.2.0.exe /q
SmartCard_XP_x86.exe /quiet /norestart
WindowsSearch-KB940157-XP-x86-esn /quiet /norestart
WindowsXP-KB898461-x86-ESN.exe /quiet /norestart
WindowsXP-KB905474-ENU-x86-Standalone.exe /quiet /norestart
WindowsXP-KB942288-v3-x86.exe /quiet /norestart
WindowsXP-KB950760-x86-ESN.exe /quiet /norestart
WindowsXP-KB953356-x86-ENU.exe /quiet /norestart
WindowsXP-KB956391-x86-ESN.exe /quiet /norestart
WindowsXP-KB959252-v2-x86-ESN.exe /quiet /norestart
WindowsXP-KB960715-x86-ESN.exe /quiet /norestart
WindowsXP-KB961118-x86-ESN.exe /quiet /norestart
WindowsXP-KB967715-x86-ESN.exe /quiet /norestart
CalcPlus.msi /quiet /norestart
WindowsDefender.msi /quiet /norestart
WindowsUpdateAgent30-x86.exe /wuforce /quiet /norestart
qchain.exe
MSDownloads.exe

When I excecute them after Windows installation they work perfectly. Any suggestions ???

Link to comment
Share on other sites

2 Brazillian language users for .NET 2.0 SP#

Until I release a new version, to fix KB829019 showing in win/ms update, open a console and type this command: I fixed a typo error sorry.

REG ADD "HKLM\SOFTWARE\Microsoft\DevDiv\URT\Servicing\1.1\RED\1046" /V Install /T REG_DWORD /D 00000001 /F

2 hipo_loco

Have you copied the installers to ..\i386\SVCPACK folder?

Edited by strel
Link to comment
Share on other sites

Thanks to Strel (and TC76 and all the people involved) for this useful tool.

I was trying to use only the .NET 1.1 part, and I got small pitfalls.

First, while my targets include Win2000 and Vista stations, I was building on XP64, which is seen as NT5.2 i.e. 2003 server (they share the same kernel). Even if I use WIN2K=YES in the .ini, the logic which discovers WIN2K3 according to the VER command operates, and then prevents the 1.1 installer to be built. The fix is obviously to check about the version only if there are no explicit settings in the .ini. See attached patch to this effect VerCheck.patch.txt (GNU unidiff, against the version 20090316b.)

I am guessing the setting WINXP=YES will do the job to build a 1.1 installer for Vista, but I do not have checked it yet.

Second, for bare bones W2k targets (SP4 w/o IE6, which only have 2.0 Windows Installer), the /passive and /quiet and /norestart switches are not acceptable. It took me quite more time to come with a acceptable patch :blushing: , which doubles the %VERBOSITY% stuff with a %QSWITCH% (either qb or qn). It is still not perfect :unsure:, since for example it enables the Cancel button (and I do not know what /passive does, but I guess it doesn't). Also I broadly replaced throughout the script, but an educated guess is taht .NET 2.0 might require Installer 3.x at least, thus making it moot. Anyway I attach it in case anyone is interested. VerbosityMSI2.patch.txt

Much more complex was the aim to have several 1.1 language packs (of course I am thinking about servers here, or MUI-enabled workstations). I succeded at manually building an installer which does that (by manually renaming the langpack.msi after their adminstrative installation), but I did not even try to enhance the script this way. Is there any interest?

A lot of thx for your fixes. I hadn't read your post until now, sorry. I'll review all this for the next version.

And:

- Yes, /passive don't show cancel button, at least for win installer 4.5.

- .NET 2.0 requires win installer 3.x

- The .ini file OS setting is only to define the target OS version for the installers bypassing default target that is host OS version from which they are built; so even if you change .ini file OS version setting and bypass in-script OS version checking, you cannot build installers for vista or 7 but from this versions for win2K/XP/2K3 x86.

- There's interest in having a script that cover all needs, at least mine.

Edited by strel
Link to comment
Share on other sites

Hi, I got something wrong, when i made NET 3.5 sp1 alone or pack ?

Net Framework 1.1 2.0 3.0 3.5 are installed

files in folder

_SNMsynth.ini

7za.exe

7zsd.sfx

dotnetfx.exe

dotnetfx35.exe

KB951847_FIX.mst

NDP1.1sp1-KB867460-X86.exe

NDP1.1sp1-KB928366-X86.exe

ndp20sp2-kb958481-x86.exe

ndp30sp2-kb958483-x86.exe

ndp35sp1-kb958484-x86.exe

SNMsynth.cmd

==============================

Processing .NET 3.5 SP1 installer...

Processing .NET 3.5 SP1 portion...

Processing NDP35SP1-KB958484-x86.exe...

The system cannot find the file specified.

The system cannot find the file specified.

The system cannot find the file specified.

The system cannot find the file specified.

Creating .NET 3.5 SP1 silent installer...

Done!

Press any key to quit.

=============================

something is missing after NDP35SP1-KB958484-x86.exe

Thanks

Link to comment
Share on other sites

Yes, i download all again, same error message. DNF 1, 2 ,3 ok but 3.5 error

dotnetfx35.exe 231mb

==============================

Processing .NET 3.5 SP1 installer...

Processing .NET 3.5 SP1 portion...

Processing NDP35SP1-KB958484-x86.exe...

The system cannot find the file specified.

The system cannot find the file specified.

The system cannot find the file specified.

The system cannot find the file specified.

Creating .NET 3.5 SP1 silent installer...

Creating .NET 3.5 SP1 silent nLite add-on...

Done!

Press any key to quit.

=============================

Edited by pjadec
Link to comment
Share on other sites

Yes, i download all again, same error message. DNF 1, 2 ,3 ok but 3.5 error

dotnetfx35.exe 231mb

==============================

Processing .NET 3.5 SP1 installer...

Processing .NET 3.5 SP1 portion...

Processing NDP35SP1-KB958484-x86.exe...

The system cannot find the file specified.

The system cannot find the file specified.

The system cannot find the file specified.

The system cannot find the file specified.

Creating .NET 3.5 SP1 silent installer...

Creating .NET 3.5 SP1 silent nLite add-on...

Done!

Press any key to quit.

=============================

This happen to me too. I'm using potuguse (portugal) language packs!

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...