<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 -->06/25/2007<!--webbot bot="Timestamp" endspan i-checksum="12598" --></h3>\r
+<!--webbot bot="Timestamp" S-Type="EDITED" S-Format="%m/%d/%Y" startspan -->06/27/2007<!--webbot bot="Timestamp" endspan i-checksum="12630" --></h3>\r
\r
<div class=MsoNormal align=center style='text-align:center'>\r
\r
</blockquote>\r
\r
<h3> </h3>\r
-<h3><u>Unattended Install using InstallShield</u></h3>\r
+<h3><u>Unattended Install</u></h3>\r
\r
<blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'>\r
\r
<p> </p>\r
<h2><u>Uninstall</u></h2>\r
\r
-<p>To uninstall a WinOF package</p>\r
+<p>To uninstall a WinOF package from a single node</p>\r
<ol>\r
<li>Programs-> Windows OpenFabrics-> Uninstall WinOF</li>\r
- <li>Control Panel-> Add Remove Programs-> Windows OpenFabrics</li>\r
+ <li>Control Panel-> Add Remove Programs-> Windows OpenFabrics-> Remove</li>\r
</ol>\r
-<p>For unattended uninstalls (WinOF only, from a command window)</p>\r
-<ul>\r
- <li>Recorded an uninstall answer file:<br>\r
- "%ProgramFiles(x86)%\InstallShield Installation \r
+<h3>Unattended Installs</h3>\r
+<blockquote>\r
+ <h4>Add/Remove Programs method</h4>\r
+ <blockquote>\r
+ <p>When you select the Windows OpenFabric Add/Remove Programs entry the \r
+ following logic is invoked. This ARP logic can be accomplished by 'hand' \r
+ from a command window.</p>\r
+ <ul>\r
+ <li>Record an uninstall answer file:<br>"%ProgramFiles(x86)%\InstallShield Installation \r
Information\{51798BCA-98EE-43ED-95D6-CCA11E369044}\setup.exe" -runfromtemp \r
-l0x0409 /r /f1%TEMP%\uninstall.iss</li>\r
- <li>Uninstal using the answer file: <br>\r
- "%ProgramFiles(x86)%\InstallShield Installation \r
+ <li>Uninstal using the answer file: <br>"%ProgramFiles(x86)%\InstallShield Installation \r
Information\{51798BCA-98EE-43ED-95D6-CCA11E369044}\setup.exe" -runfromtemp \r
-l0x0409 /s /sms /f1%TEMP%\uninstall.iss</li>\r
- <li>see setup.exe /? for details.</li>\r
- <li>Add/Remove Programs for InstallShield-12 uses the following registry \r
+ <li>see setup.exe /? for details.</li>\r
+ <li>Add/Remove Programs for InstallShield-12 uses the following registry \r
entries for WinOF:<br>Windows 2003 Server: HKLM\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall\Install_Shield_{51798BCA-98EE-43ED-95D6-CCA11E369044}\UninstallString<br>Windows XP: HKLM\Microsoft\Windows\CurrentVersion\Uninstall\Install_Shield_{51798BCA-98EE-43ED-95D6-CCA11E369044}\UninstallString</li>\r
- <li>If for some reason the Product Code {GUID} changes, the latest code can \r
+ <li>If for some reason the Product Code {GUID} changes, the latest code can \r
be located via<br>Programs-> Windows OpenFabrics-> Uninstall WinOF<right-click>Properties</li>\r
-</ul>\r
+ </ul>\r
+ </blockquote>\r
+ <h4>MS uninstall method</h4>\r
+ <blockquote>\r
+ <p>For those who favor simplicity and are willing to run dangerously, \r
+ unattended uninstalls from a command window, such as one would use when \r
+ managing a Windows Compute Cluster are possible although not without a \r
+ price. Although msiexec removes a WinOF install, it operates under the \r
+ Add/Remove Programs layer, hence a lingering/non-functional Add/Remove \r
+ Programs entry persists. If you click on the ARP entry, it will fail and \r
+ cleanup. The existence of an ARP entry does not appear to impact future \r
+ WinOF installs.<br>\r
+ Infrequently, the 'System Device->Infiniband Fabric' may not uninstall \r
+ correctly using msiexec. Make sure the Infiniband Fabric device is \r
+ completely uninstalled; use device manager for checking. The effect of a \r
+ partially uninstalled Infiniband Fabric device is IPoIB load failure \r
+ upon the next WinOF install.</p>\r
+ <p>All in all the Add/Remove Programs method is the safest although \r
+ involves more work.</p>\r
+ <p>start/wait msiexec.exe /quiet /passive /forcerestart \r
+ /x{51798BCA-98EE-43ED-95D6-CCA11E369044}</p>\r
+ </blockquote>\r
+</blockquote>\r
<p> </p>\r
\r
<h2><u>Trouble Shooting</u></h2>\r
<p align="left">The 'typical' WinOF installation places the dat.dll and dapl.dll \r
files in the '%WINDIR%' \r
folder (a.k.a. \Windows).</p>\r
-<p align="left">The DAPL configuration file by convention is defined as \r
-'%SystemDrive%\DAT\dat.conf'. This default specification can be overridden by use \r
+<p align="left">The DAPL/DAT configuration file by convention is defined as \r
+'%SystemDrive%\DAT\dat.conf'. If the folder '%SystemDrive%\DAT' does not exist, \r
+a template configuration file will be installed as '%SystemDrive%\DAT\dat.conf'.<br>\r
+In order to preserve existing installations, the dat.conf file is not \r
+automatically installed in it's default location if the folder \r
+'%SystemDrive%\DAT' exists.<br>\r
+A sample, although not used in it's current location, dat.conf file is installed as '\Program Files\WinOF\dat.conf \r
+'.</p>\r
+<p align="left">The default DAT configuration file specification can be overridden by use \r
of the environment variable DAT_OVERRIDE. Such that 'DAT_OVERRIDE=D:\MyDAT\test.conf' \r
would be a valid override specification.</p>\r
<p align="left">Within the dat.conf file, the DAPL library specification can be \r
which implies the '\' (backslash character) is treated as an 'escape' character. \r
Hence all backslashes in the library path must be duplicated when enclosed in \r
double-quotes (e.g., "C:\\Programs Files\\WinOF\\dapl.dll").</p>\r
-<p align="left">A sample dat.conf file is installed as '\Program Files\WinOF\dat.conf \r
-'.<br>\r
-After the WinOF installation, move the \Program Files\WinOF\dat.conf file to the \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 align="left"> </p>\r
\r
<h2><u>Known Issues</u></h2>\r