[OutTrendz]

How do you a silent install for it?

[wass]

well.. extract the file and obtain these :

install.exe
netfx1.cab
netfx.msi

and use : netfx.msi /qb

[mazin]

BTW, you don't need install.exe if you run netfx.msi!

[midiboy]

Hi !

mhh, I don´t understand ....

I downloaded the German version (NDP1.1sp1-KB867460-X86.exe) from the official Microsoft page and extracted it using Winrar but I did not get any msi ...only those 3 files:

PatchExec.exe
Microsoft.WindowsInstaller.dll
Microsoft.WindowsInstaller.Package.dll

strange, huh ?
any ideas ?

Thanks,
Alex

[m4dh0]

.net 1.1 obviously needs to be installed before installing the service pack,
but try this for the service pack

NDP1.1sp1-KB867460-X86.exe /q

[prathapml]

Run PatchExec.exe with "/QB" switch, I think. See if there's an MSP file within one of those files - if so, its possible to merge the SP into the main installer.

[my2001]

Described so often before: just start your downloaded installer (here that one of Framework) and then look into your temp folder of your current logged in user account. Voilá!

And here's an overview of available command line switches:

Quote

Windows ® Installer. V 3.00.3790.2180

msiexec /Option <Erforderliche Parameter> [Optionale Parameter]Installationsoptionen
</package | /i> <Produkt.msi>
  Installiert oder konfiguriert ein Produkt.
/a <Produkt.msi>
  Administrative Installation - Installiert ein Produkt im Netzwerk.
/j<u|m> <Produkt.msi> [/t <Transformliste] [/g <Sprachkennung>]
  Kündigt ein Produkt an - m für alle Benutzer, u für den aktuellen Benutzer
</uninstall | /x> <Produkt.msi | Produktcode>
  Deinstalliert das Produkt.

Anzeigeoptionen
/quiet
  Hintergrundmodus, keine Benutzerinteraktion
/passive
  Unbeaufsichtigter Modus - Nur Statusleiste
/q[n|b|r|f]
  Legt die Benutzeroberfläche fest.
  n - Keine Benutzeroberfläche
  b - Einfache Benutzeroberfläche
  r - Reduzierte Benutzeroberfläche
  f - Vollständige Benutzeroberfläche (Standard)
/help
  Hilfeinformationen

Neustartoptionen
/norestart
  Kein Neustart nach Abschluss der Installation
/promptrestart
  Benutzereingabe, falls Neustart erforderlich ist
/forcerestart
  Computer nach Abschluss der Installation immer neu starten

Protokolllierungsoptionen
/l[i|w|e|a|r|u|c|m|o|p|v|x|+|!|*] <Protokolldatei>
  i - Statusmeldungen
  w - Nicht schwerwiegende Warnungen
  e - Alle Fehlermeldungen
  a - Ausführung von Aktionen
  r - Aktionsspezifische Einträge
  u - Benutzeranforderungen
  c - Ursprüngliche Benutzeroberflächenparameter
  m - Informationen betreffend zuwenig Arbeitsspeicher oder schwerwiegendem Abbruch
  o - Meldungen betreffend zuwenig Speicherplatz
  p - Terminaleigenschaften
  v - Ausführliche Ausgabe
  x - Zusätzliche Debuginformationen
  + - An vorhandene Protokolldatei anhängen
  ! - Jede Zeile ins Protokoll aufnehmen
  * - Alle Informationen mit Ausnahme der Optionen v und x protokollieren
/log <Protokolldatei>
  Entspricht /l* <Protokolldatei>

Aktualisierungsoptionen
/update <Update1.msp>[;Update2.msp]
  Übernimmt Update(s).
/uninstall <Patchcode-GUID>[;Update2.msp] /package <Produkt.msi | Produktcode>
  Entfernt Update(s) für ein Produkt.

Reparaturoptionen
/f[p|e|c|m|s|o|d|a|u|v] <Produkt.msi | Produktcode>
  Repariert ein Produkt.
  p - nur wenn eine Datei fehlt
  o - wenn eine Datei fehlt oder eine ältere Version installiert ist (Standard)
  e - wenn eine Datei fehlt oder eine gleiche bzw. ältere Version installiert ist
  d - wenn eine Datei fehlt oder eine andere Version installiert ist
  c - wenn eine Datei fehlt oder die Prüfsumme nicht mit dem berechneten Wert übereinstimmt
  a - Erzwingt die Neuinstallation aller Dateien
  u - Alle erforderlichen benutzerspezifischen Registrierungseinträge (Standard)
  m - Alle erforderlichen Computerspezifischen Registrierungseinträge (Standard)
  s - Alle vorhandenen Verknüpfungen (Standard)
  v - Führt von der Quelle aus und speichert das lokale Paket zwischen

Öffentliche Eigenschaften festlegen
[PROPERTY=Eigenschaftswert]


Weitere Informationen betreffend der Befehlszeilensyntax erhalten Sie im Windows ® Installer SDK.


Copyright © Microsoft Corporation. Alle Rechte vorbehalten.
Teile dieser Software basieren zum Teil auf der Arbeit der Independent JPEG Group.

[midiboy]

Hi guys,

thanks for your tips and sorry for the redundant question, my2001.

So I found something in the temp folder, but it was no msi but an msp file.

I was able to silently install it using the /quiet /norestart switches, however, I am not sure if this is actually an update to SP1 or if it replaces the original framework 1.1 installer.

The msp file is 18,3 MB in size and the NDP1.1sp1-KB867460-X86.exe is from this website

Thanks for your help !
Alex

[RyanVM]

MSP files are patches.

The question is, can an administrative install be done of .NET 1.1 followed by an SP1 update to the install point?

[XPC-001]

you dont need to extract the .NET Framework v1.1 SP1 patch
i renamed the original file NDP1.1sp1-KB867460-X86.exe to netfxsp1.exe making it shorter for me to type and it is neater in the batch

just use the /qb switch and it will silently install

ECHO Installing .NET Framework v1.1 Patch
ECHO Please wait...
start /wait %systemdrive%\install\NetFramework\netfxsp1.exe /qb

[RyanVM]

XPC-001, on Aug 31 2004, 01:48 PM, said:

you dont need to extract the .NET Framework v1.1 SP1 patch
i renamed the original file NDP1.1sp1-KB867460-X86.exe to netfxsp1.exe making it shorter for me to type and it is neater in the batch

just use the /qb switch and it will silently install

ECHO Installing .NET Framework v1.1 Patch
ECHO Please wait...
start /wait %systemdrive%\install\NetFramework\netfxsp1.exe /qb

If SP1 can be integrated into the install package, the total package should be smaller than the combined size of .NET 1.1 + the SP1 patch.

EDIT: I'm attempting it right now. Gotta re-download .NET first though (yay for being at work )

[RyanVM]

I've got a 12.2MB RAR archive with SP1 theoretically integrated. Anyone feeling brave enough to give it a shot?

Shoot me a PM if you're willing. If it works, I'll post the link in this thread for everyone to enjoy.

[prathapml]

That's cool. Could you describe what you did to merge it in?

[RyanVM]

prathapml, on Aug 31 2004, 02:28 PM, said:

That's cool. Could you describe what you did to merge it in?

Administrative install point.

[prathapml]

That's odd, it didn't work before for me......
Anyways RyanVM gave me the courage, and here's the steps (given by him):

1. First download the .NET framework v1.1 re-distributable package, and run "dotnetfx.exe" with the "/C" switch (to extract contents).
2. Then download the .NET fw v1.1 SP1 update, and run "NDP1.1sp1-KB867460-X86.exe" with the /XP" switch (to extract contents).
3. A dialog box asking you where to save the MSP (update patch) comes up, choose where you want to save it (size 18,760 KB).
4. Rename that MSP to SP1.MSP, and place the extracted contents of dotnetfx.exe (.NET framework installer) in the same directory.
5. Clean the directory so sp1.msp, data1.cab, and netfx.msi are the only files (3 files) in the directory.
6. Run the following commands (from a command prompt):

msiexec /a netfx.msi TARGETDIR="c:\netfx"
msiexec /p sp1.msp /a c:\netfx\netfx.msi

These commands created an admin-install point and patch-updated it to .NET SP1 respectively.
7. Your c:\netfx directory should have 3 items in it after this operation: 2 directories - Program Files & Win, and netfx.msi.

8. Now you can compress it to SFX (if compressed it will be just 12.2 MB, if left uncompressed it is 56.2 MB). And set it to silently extract.
9. And install your newly created ".NET Framework v1.1 slip-streamed with SP1" package during XP/win2k setup with the "/QB" switch.

This post has been edited by prathapml: 01 September 2004 - 04:32 AM

[diesel_98a]

i got the msi out of my temp file for my user acct, i started the program and then went in and retreive the msi, i have noticed it renames it self something different each time but i was able to install using the /QN.

[RyanVM]

just use the /Xp command to extract the MSP file and the /C command to extract the dotnet install files.

[prathapml]

The planned method has been posted in previous post.
Does anyone know if there is any way to check if the now installed version of .NET is really the 1.1+SP1 version?
Because the main file (mscoree.dll) in the "\Win\System" folder shows the same version, before and after the SP1 refresh (i.e., the version 1.1.4322.2032).


@RyanVM
All credits go to you for the above step-by-step description of the process.

[RyanVM]

prathapml, on Aug 31 2004, 03:15 PM, said:

The planned method has been posted in previous post.
@RyanVM
All credits go to you for the above step-by-step description of the process.


Does anyone know if there is any way to check if the now installed version of .NET is really the 1.1+SP1 version?
Because the main file (mscoree.dll) in the "\Win\System" folder shows the same version, before and after the SP1 refresh (i.e., the version  1.1.4322.2032).

The previous file versions were 1.1.4322.573

SP1 file versions are 1.1.4322.2032

[prathapml]

OK, I'll check "before" and "after" version numbers once again, I guess....
Also, the easiest way to check if the SP1-slipstreamed version is properly made/installed is to simply visit Windows Update, and check if it offers the SP1. I found that the method given by RyanVM (and posted in my post) kept windows update happy - it said I already have .NET SP1 installed - nice!

So here's your confirmations dudes. Let the slogging (for all you who HAVE to stay with the latest) begin to have .NET+SP1 together, LOL. You've got the necessary guide above.



@RyanVM
Updated my step-by-step post above to reflect your most recent post (the switches /XP and /C).