From: stansmith
Date: Wed, 1 Aug 2007 22:48:04 +0000 (+0000)
Subject: [WinOF] WIX - updated unattended install/uninstall for msiexec invocation; far simple...
X-Git-Url: https://openfabrics.org/gitweb/?a=commitdiff_plain;h=ca877e5db79dc05ca088b5763215df4f8029b5ab;p=~shefty%2Frdma-win.git
[WinOF] WIX - updated unattended install/uninstall for msiexec invocation; far simpler than InstallShield.
git-svn-id: svn://openib.tc.cornell.edu/gen1@750 ad392aa1-c5ef-ae45-8dd8-e69d62a5ef86
---
diff --git a/branches/WinOF/WIX/Release_notes.htm b/branches/WinOF/WIX/Release_notes.htm
index 95b8bf7a..ec12abae 100644
--- a/branches/WinOF/WIX/Release_notes.htm
+++ b/branches/WinOF/WIX/Release_notes.htm
@@ -89,7 +89,7 @@ src=openfabrics.gif>
1.0 Release Notes
-06/27/2007
+08/01/2007
@@ -107,7 +107,8 @@ InfiniBand fabric.
Binary
files from the openib-windows developers release tree http://openib.tc.cornell.edu/downloads/binaries/1.0.0.614
-are packaged into an InstallShield single file install package referred to as
+are packaged into a WIX 2.0
+(Windows Installer Xml) single file install package referred to as
the Windows OpenFabrics (WinOF) release.
The Windows OpenFabrics (WinOF) release package contains the following:
@@ -271,6 +272,11 @@ the "Found New Hardware Wizard".
packages or vendor supplied Infiniband packages, uninstall and reboot prior to
installing this version of Windows OpenFabrics.
+
For an existing Windows OpenFabrics uninstall
+ Programs-> Windows OpenFabrics-> Uninstall WinOF
+ -or-
+ Control Panel -> Add or Remove Programs-> Windows
+OpenFabrics->Remove.
openib-windows uninstall:
@@ -284,11 +290,7 @@ installing this version of Windows OpenFabrics.
System Device-> InfiniBand Fabric
-
For an existing Windows OpenFabrics uninstall
- Programs-> Windows OpenFabrics-> Uninstall WinOF
- -or-
- Control Panel -> Add or Remove Programs-> Windows
-OpenFabrics->Remove.
+
REBOOT
@@ -302,7 +304,7 @@ drivers for newly discovered PCI device.
From a login with administrator privileges, double-click the
-WinOF_arch_setup.exe file to begin the Windows OpenFabrics installation;
+WinOF_M-m_arch_setup.msi file to begin the Windows OpenFabrics installation;
where '_arch_' can be (_x64_ for Intel EMT64 systems or amd64, _x86_ for x86
compatible systems or _ia64_ for Intel IA64 systems).
@@ -344,117 +346,49 @@ built from driver source which has been WHQL'ed.
-
Install types:
-
-
Minimal
+
Install type: Custom only
- - Basics - Release Notes, Manual, Command Window
- - Tools - Subnet Management [opensm.exe, SM is installed, not
- started], Performance & Diagnostics
- - IBcore - mthca HCA driver + IB fabric driver (ibal)
-
-
-
Typical
-
-
- - Minimal install 'plus'
-
-
-
- - IPoIB - Internet Protocols over InfiniBand (aka,
- ftp/telnet/... over IB Fabric)
- - WinsockDirect - Winsock Direct Provider (Win2K3 only), service started; see
- WinOF\installsp.exe -l
- - DAPL - DAT and uDAPL support
-
-
-
Custom
-
-
- - Basics - Release Notes, Manual, Command Window
- - Tools - Subnet Management [opensm], Performance &
- Diagnostic utilities
- - IB core + IB fabric driver
- - Optional:
IPoIB
- WinsockDirect (Win2K3 only)
VNIC - Virtual Ethernet device over Infiniband
SRP - SCSI over RDMA Protocol
DAPL
- OpenSM_service_enabled - InfiniBand Subnet Management started as a Windows Service
+ - InfiniBand Core:
+ - HCA driver, IB core stack and libraries.
+ - Release Notes, Manual
+ - Subnet Management [opensm], Performance & Diagnostic tools
+
+ - Optional:
IPoIB
+ Winsock Direct (Win2K3 only)
VNIC - Virtual Ethernet device over Infiniband
SRP - SCSI over RDMA Protocol
DAPL
+ - RDMA device independent, user-mode Direct Access Transport & Direct Access
+ Provider Libraries.
OpenSM_service_started - InfiniBand Subnet Management
+ enabled and started as a Windows Service.
+
+ By default OpenSM is installed as a disabled Windows Service.
-
Unattended Install using InstallShield
-
-
+Unattended Install
-
- InstallShield is one of the oldest and most widely used application
- packaging systems.
Installers created by InstallShield recognize the
- /r
, /s
, /sms
, /f1
, and
- /f2
switches. The installer itself is invariably named
- WinOF_arch_M-m_setup.exe
.
-
To perform a silent/unattended installation, you need an InstallShield
- "answer file", customarily named setup.iss
. The WinOF
- distribution does not ship with such a file, but you can easily create one
- during a single node installation.
-
Here is how it works. Run the installer with the /r
- ("record") switch. Proceed through the dialogs and complete the
- installation. This will create a setup.iss
file and place it in
- the %WINDIR%
directory (see /f1 switch discussion below to
- alter this behavior). This file will include all of your responses to the
- InstallShield dialogs, allowing you to perform unattended installations as
- if you were giving the same answers again. Simply copy setup.iss
- to the same directory as the installer executable.
-
Once you have a setup.iss
file, run the installer with the
- /s
("silent") option. This will perform an unattended
- installation.
-
Unfortunately, the installer will fork a separate process and exit,
- meaning it will return immediately even if you run it under
- start /wait
. This makes it useless for scripting purposes. Luckily,
- there is another switch, /sms
, which will cause the installer
- to pause until the installation completes.
-
Hence, for an InstallShield application, you want to provide both the
- /s
and the /sms
switches for the unattended
- install.
-
The /f1filename
switch allows you to specify a
- fully-qualified alternate name for the setup.iss
file. Note
- that there must be no space between the /f1
- switch and the file name. This switch works both with /r
to
- create the file and with /s
to read it.
-
The /f2filename
switch specifies a log file. Once
- again, there must be no space between the switch and the
- file name.
-
WARNING: Be careful what characters you use in these
- file names, because InstallShield silently strips certain non-alphanumerics
- (like hyphens).
-Recording Mechanics (how to generate an .iss answer file):
-
- - From a login with administrator privileges bring up a Command Window
- (cmd.exe).
- - cd to where the WinOF installation file (.exe) is located, for now
- assume %TEMP% (cd %TEMP%)
- - cmd-prompt> start/wait WinOF_arch_1-0_setup.exe /r /f1%TEMP%\WinOF.iss
- The above command creates 'WinOF.iss' in the %TEMP% directory. Yes, an
- actual install is performed, be prepared.
-
-Unattended/Silent Install Mechanics (using the .iss answer file):
-
- - From a login with administrator privileges bring up a Command Window
- (cmd.exe).
- - cd to where the WinOF installation file (.exe) and silent install answer
- file (.iss) files are located, for now
- assume %TEMP% 'cd %TEMP%'
- - cmd-prompt> start/wait WinOF_arch_1-0_setup.exe /s /sms
- /f2%TEMP%\WinOF.log
- assumes .iss file is in the same directory.
- - When the cmd-prompt returns, the WinOF unattended install has completed.
- Results can be viewed in the WinOF.log file.
-
-
-
-
+
To perform a silent/unattended installation, invoke the following command
+ from a command window.
+
+ start/wait msiexec.exe /i WinOF_R1-1_x64.msi /quiet /passive /log
+ %TEMP%\WOF_install.log
+ '/log dev:path\logFilename.log' is optional.
+ msiexec.exe /? for all options.
+
+
An unattended install will install the following default install options:
+
+ - Infiniband Core - HCA driver, IB core stack and libraries,
+ Documentation
+ - IPoIB - Internet Protocols over InfiniBand
+ - WSD - (Win2k3 only, not installed on XP) Win Sock Direct
+ - DAPL - uDAT & DAPL
+
+
+Should WSD not be a desirable unattended install option (Win2K3 only),
+currently you would install unattended then execute the command 'installsp -r'
+on each node to remove WSD.
See Unattended
Installations for further references.
@@ -477,27 +411,30 @@ reference.
Uninstall
-To uninstall a WinOF package
+To uninstall a WinOF package from a single node
- Programs-> Windows OpenFabrics-> Uninstall WinOF
- - Control Panel-> Add Remove Programs-> Windows OpenFabrics
+ - Control Panel-> Add Remove Programs-> Windows OpenFabrics-> Remove
-For unattended uninstalls (WinOF only, from a command window)
-
- - Recorded an uninstall answer file:
- "%ProgramFiles(x86)%\InstallShield Installation
- Information\{51798BCA-98EE-43ED-95D6-CCA11E369044}\setup.exe" -runfromtemp
- -l0x0409 /r /f1%TEMP%\uninstall.iss
- - Uninstal using the answer file:
- "%ProgramFiles(x86)%\InstallShield Installation
- Information\{51798BCA-98EE-43ED-95D6-CCA11E369044}\setup.exe" -runfromtemp
- -l0x0409 /s /sms /f1%TEMP%\uninstall.iss
- - see setup.exe /? for details.
- - Add/Remove Programs for InstallShield-12 uses the following registry
- entries for WinOF:
Windows 2003 Server: HKLM\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall\Install_Shield_{51798BCA-98EE-43ED-95D6-CCA11E369044}\UninstallString
Windows XP: HKLM\Microsoft\Windows\CurrentVersion\Uninstall\Install_Shield_{51798BCA-98EE-43ED-95D6-CCA11E369044}\UninstallString
- - If for some reason the Product Code {GUID} changes, the latest code can
- be located via
Programs-> Windows OpenFabrics-> Uninstall WinOF<right-click>Properties
-
+Unattended
+Uninstall
+From a Command Window invoke the following command; a system reboot will
+occur after the uninstall.
+
+ start/wait msiexec.exe /x {51798BCA-98EE-43ED-95D6-CCA11E369044} /quiet /passive
+ - or -
+ start/wait msiexec.exe /x WinOF_R1-1_x64.msi /quiet /passive
+ # WinOF_xxxx.msi is the file used to install WinOF.
+ msiexec.exe /help for details.
+ '/log dev:path\logfilename.log' if you wish to later view the install
+ results.
+ If for some reason the Product Code {GUID} changes, the latest code can
+ be located via
Programs-> Windows OpenFabrics-> Uninstall WinOF<right-click>Properties
+
+Infrequently, the 'System Device->Infiniband Fabric' may not correctly uninstall. Make sure the Infiniband Fabric device is
+ completely uninstalled; use device manager for checking. The effect of a
+ partially uninstalled Infiniband Fabric device is IPoIB load failure
+ upon the next WinOF install.
Trouble Shooting
@@ -676,16 +613,18 @@ sufficient, although redundant Subnet Managers are supported.
- After a 'typical' WinOF install, OpenSM is installed as a disabled
Windows service named "InfiniBand Subnet Management". To start the OpenSM
- service, use My computer->Manage->Device
- Manager->Services->InfiniBand Subnet Manager->Start.
+ service, use My computer->Manage->Services and Applications->Services->InfiniBand Subnet Manager->Start.
Set the service properties to 'auto' in order to restart upon the next
system reboot.
- Install OpenSM as an automatic/running Windows service:
a) Request a 'Custom' install, selecting the 'OpenSM_service_enabled' feature. Once
the install has completed, check that the Infiniband Subnet Manager service is
- running: My computer->Manage->Device Manager->Services->InfiniBand Subnet
- Manager
+ running: My computer->Manage->Services and Applications->Services->InfiniBand Subnet
+ Manager.
+
+ - Consult the OpenSM log file @ %SystemRoot%\temp\osm.log to see what
+ OpenSM thinks is happening.
Local Network Adapter Ordering
@@ -732,7 +671,21 @@ of the double-quotes is the library specification is treated as a Windows string
which implies the '\' (backslash character) is treated as an 'escape' character.
Hence all backslashes in the library path must be duplicated when enclosed in
double-quotes (e.g., "C:\\Programs Files\\WinOF\\dapl.dll").
-
+
+SRP - SCSI RDMA Protocol Driver Installation
+The WinOF stack does not install the SRP driver by default.
+If SRP is
+selected in the custom installation window, it will only be copied during WinOF
+installation. To complete the SRP driver installation, an SRP target must be
+detected; a Subnet Manager must be running somewhere in the InfiniBand subnet.
+
+Upon the detection of an SRP target, the "New Hardware Found" Wizard pops up.
+- Select Install Automatically and click Next. This installs the I/O unit
+device.
+
+Once completed, the "New Hardware Found" Wizard pops up again.
+- Select Install Automatically and click Next. This installs the SRP driver.
+
Known Issues
@@ -750,7 +703,18 @@ double-quotes (e.g., "C:\\Programs Files\\WinOF\\dapl.dll").
WinOF x64
- Add/Remove Programs entry for support does not display all ARP information.
+ Add/Remove Programs entry for support does not display all ARP information.
+
+
+ The Windows
+ OpenFabrics release includes a WSD provider library that has been
+ extensively tested with Microsoft Windows Server 2003.
+ During testing, bugs where found in the WSD switch that could lead to hangs,
+ crashes, data corruption, and other unwanted behavior. Microsoft released a
+ hotfix to address these issues which should be installed if using WSD.
+ The Microsoft Windows Server 2003 hotfix for WSD can be located
+ here.
+