<h1 align=center style='text-align:center'>1.0 Release Notes</h1>\r
\r
<h3 align=center style='text-align:center'>\r
-<!--webbot bot="Timestamp" S-Type="EDITED" S-Format="%m/%d/%Y" startspan -->05/08/2007<!--webbot bot="Timestamp" endspan i-checksum="12628" --></h3>\r
+<!--webbot bot="Timestamp" S-Type="EDITED" S-Format="%m/%d/%Y" startspan -->05/11/2007<!--webbot bot="Timestamp" endspan i-checksum="12524" --></h3>\r
\r
<div class=MsoNormal align=center style='text-align:center'>\r
\r
<p>'My Computer->Manage->Device Manager' should display\r
'?Other Devices->?PCI device' which is your Infiniband HCA device.</p>\r
\r
-<h3>Install</h3>\r
+<h3><u>Install</u></h3>\r
\r
<blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'>\r
\r
OpenSM_service - InfiniBand Subnet Management started as a Windows Service</li>\r
</ul>\r
\r
-<p> </p>\r
+</blockquote>\r
+\r
+<h3> </h3>\r
+<h3><u>Unattended Install using InstallShield</u></h3>\r
+\r
+<blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'>\r
+\r
+<div id="main-copy">\r
+ <a target="_blank" rel="external" href="http://www.installshield.com/">\r
+ InstallShield</a> is one of the oldest and most widely used application \r
+ packaging systems.<p>Installers created by InstallShield recognize the <code>\r
+ /r</code>, <code>/s</code>, <code>/sms</code>, <code>/f1</code>, and <code>\r
+ /f2</code> switches. The installer itself is invariably named\r
+ <font face="Courier New">WinOF_arch_M-m_</font><code>setup.exe</code>.</p>\r
+ <p>To perform a silent/unattended installation, you need an InstallShield \r
+ "answer file", customarily named <code>setup.iss</code>. The WinOF \r
+ distribution does not ship with such a file, but you can easily create one \r
+ during a single node installation.</p>\r
+ <p>Here is how it works. Run the installer with the <code>/r</code> \r
+ ("record") switch. Proceed through the dialogs and complete the \r
+ installation. This will create a <code>setup.iss</code> file and place it in \r
+ the <code>%WINDIR%</code> directory (see /f1 switch discussion below to \r
+ alter this behavior). This file will include all of your responses to the \r
+ InstallShield dialogs, allowing you to perform unattended installations as \r
+ if you were giving the same answers again. Simply copy <code>setup.iss</code> \r
+ to the same directory as the installer executable.</p>\r
+ <p>Once you have a <code>setup.iss</code> file, run the installer with the\r
+ <code>/s</code> ("silent") option. This will perform an unattended \r
+ installation.</p>\r
+ <p>Unfortunately, the installer will fork a separate process and exit, \r
+ meaning it will return immediately even if you run it under <code>\r
+ start /wait</code>. This makes it useless for scripting purposes. Luckily, \r
+ there is another switch, <code>/sms</code>, which will cause the installer \r
+ to pause until the installation completes.</p>\r
+ <p>Hence, for an InstallShield application, you want to provide both the\r
+ <code>/s</code> and the <code>/sms</code> switches for the unattended \r
+ install.</p>\r
+ <p>The <code>/f1<var>filename</var></code> switch allows you to specify a \r
+ fully-qualified alternate name for the <code>setup.iss</code> file. Note \r
+ that there must be <strong>no</strong> space between the <code>/f1</code> \r
+ switch and the file name. This switch works both with <code>/r</code> to \r
+ create the file and with <code>/s</code> to read it.</p>\r
+ <p>The <code>/f2<var>filename</var></code> switch specifies a log file. Once \r
+ again, there must be <strong>no</strong> space between the switch and the \r
+ file name.</p>\r
+ <p><strong>WARNING</strong>: Be careful what characters you use in these \r
+ file names, because InstallShield silently strips certain non-alphanumerics \r
+ (like hyphens).</div>\r
+<p>Recording Mechanics (how to generate an .iss answer file):</p>\r
+<ol>\r
+ <li>From a login with administrator privileges bring up a Command Window \r
+ (cmd.exe).</li>\r
+ <li>cd to where the WinOF installation file (.exe) is located, for now \r
+ assume %TEMP% (cd %TEMP%)</li>\r
+ <li>cmd-prompt> <font size="4">start/wait WinOF_arch_1-0_setup.exe /r /f1%TEMP%\WinOF.iss</font><br>\r
+ The above command creates 'WinOF.iss' in the %TEMP% directory. Yes, an \r
+ actual install is performed, be prepared.</li>\r
+</ol>\r
+<p>Unattended/Silent Install Mechanics (using the .iss answer file):</p>\r
+<ol>\r
+ <li>From a login with administrator privileges bring up a Command Window \r
+ (cmd.exe).</li>\r
+ <li>cd to where the WinOF installation file (.exe) and silent install answer \r
+ file (.iss) files are located, for now<br>\r
+ assume %TEMP% 'cd %TEMP%'</li>\r
+ <li>cmd-prompt> <font size="4">start/wait WinOF_arch_1-0_setup.exe /s /sms \r
+ /f2%TEMP%\WinOF.log<br>\r
+ </font>assumes .iss file is in the same directory.</li>\r
+ <li>When the cmd-prompt returns, the WinOF unattended install has completed. \r
+ Results can be viewed in the WinOF.log file.</li>\r
+</ol>\r
\r
</blockquote>\r
\r
+<p>See <a href="http://unattended.sourceforge.net/installers.php">Unattended \r
+Installations</a> for further references.</p>\r
+<h3>Setting the IPoIB Interface IP Address</h3>\r
+<p>The Windows command 'netsh' will assist in assigning an IP address to an \r
+IPoIB interface.<br>\r
+By default, an IPoIB interface is configured to use DHCP. The following \r
+discussion deals with setting a static IP address on an IPoIB interface.</p>\r
+<p>Display all network interface configuration information<br>\r
+ netsh interface ip show config</p>\r
+<p>Config a static IP address for an IPoIB interface: [Local Area Connection 3 \r
+== 1st IPoIB interface], 10.10.4.300 is the assigned IP address<br>\r
+with a netmask of 255.255.255.0, the gateway is 10.10.4.1 metric is 2.</p>\r
+<p> netsh interface ip set address \r
+"Local Area Connection 3" static 10.10.4.300 255.255.255.0 10.10.4.1 2</p>\r
+<p>See <a href="http://support.microsoft.com/kb/257748">netsh</a> for further \r
+reference.</p>\r
+<p> </p>\r
+<h2><u>Uninstall</u></h2>\r
+\r
+<p>To uninstall a WinOF package</p>\r
+<ol>\r
+ <li>Control Panel-> Add Remove Programs-> Windows OpenFabrics</li>\r
+ <li>Programs-> Windows OpenFabrics-> Uninstall WinOF</li>\r
+</ol>\r
+<p>For unattended uninstalls</p>\r
+<ul>\r
+ <li>start/wait msiexec.exe /quiet /passive \r
+ /x{51798BCA-98EE-43ED-95D6-CCA11E369044}</li>\r
+ <li>msiexec.exe /help for the details.</li>\r
+ <li>If for some reason the Product Code {GUID} changes, the latest code can \r
+ be located via<br>\r
+ Programs-> Windows OpenFabrics-> Uninstall WinOF<right-click>Properties</li>\r
+</ul>\r
+<p> </p>\r
+\r
<h2><u>Trouble Shooting</u></h2>\r
<p> </p>\r
\r
default DAT configuration file location<br>\r
'%SystemDrive%\DAT\dat.conf'. In order to preserve existing installations, the \r
dat.conf file is not automatically installed in it's default location.</p>\r
-<p> </p>\r
-<h2><u>Uninstall</u></h2>\r
-\r
-<p>Use the Control Panel-> Add Remove Programs to remove the Windows\r
-OpenFabrics installation.</p>\r
-<p> </p>\r
+<p align="left"> </p>\r
\r
<h2><u>Known Issues</u></h2>\r
\r
projects / ~shefty / rdma-win.git / commitdiff