From c3f0284a5b3e03174731334fa24fa4724b27358c Mon Sep 17 00:00:00 2001 From: stansmith Date: Thu, 28 Jun 2007 22:50:33 +0000 Subject: [PATCH] [WinOF] typos corrected. Discussion of creating DAT config folder %SystemDrive%\DAT if nonexistant. git-svn-id: svn://openib.tc.cornell.edu/gen1@726 ad392aa1-c5ef-ae45-8dd8-e69d62a5ef86 --- .../WinOF/InstallShield/Release_notes.htm | 71 +++++++++++++------ 1 file changed, 49 insertions(+), 22 deletions(-) diff --git a/branches/WinOF/InstallShield/Release_notes.htm b/branches/WinOF/InstallShield/Release_notes.htm index ee16568c..3b790ddf 100644 --- a/branches/WinOF/InstallShield/Release_notes.htm +++ b/branches/WinOF/InstallShield/Release_notes.htm @@ -89,7 +89,7 @@ src=openfabrics.gif>

1.0 Release Notes

-06/25/2007

+06/27/2007
@@ -384,7 +384,7 @@ built from driver source which has been WHQL'ed.

 

-

Unattended Install using InstallShield

+

Unattended Install

@@ -477,27 +477,53 @@ reference.

 

Uninstall

-

To uninstall a WinOF package

+

To uninstall a WinOF package from a single node

  1. Programs-> Windows OpenFabrics-> Uninstall WinOF
    2. -
  2. Control Panel-> Add Remove Programs-> Windows OpenFabrics
    3. +
  3. 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 +

    Unattended Installs

    +
    +

    Add/Remove Programs method

    +
    +

    When you select the Windows OpenFabric Add/Remove Programs entry the + following logic is invoked. This ARP logic can be accomplished by 'hand' + from a command window.

    +
      +
    • Record 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 +
    • 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 +
    • 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 +
    • If for some reason the Product Code {GUID} changes, the latest code can be located via
      Programs-> Windows OpenFabrics-> Uninstall WinOF<right-click>Properties
      • -
    +
+
+

MS uninstall method

+
+

For those who favor simplicity and are willing to run dangerously, + unattended uninstalls from a command window, such as one would use when + managing a Windows Compute Cluster are possible although not without a + price. Although msiexec removes a WinOF install, it operates under the + Add/Remove Programs layer, hence a lingering/non-functional Add/Remove + Programs entry persists. If you click on the ARP entry, it will fail and + cleanup. The existence of an ARP entry does not appear to impact future + WinOF installs.
+ Infrequently, the 'System Device->Infiniband Fabric' may not uninstall + correctly using msiexec. 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.

+

All in all the Add/Remove Programs method is the safest although + involves more work.

+

start/wait msiexec.exe /quiet /passive /forcerestart + /x{51798BCA-98EE-43ED-95D6-CCA11E369044}

+
+

 

Trouble Shooting

@@ -711,8 +737,15 @@ file must be present in the current directory,

The 'typical' WinOF installation places the dat.dll and dapl.dll files in the '%WINDIR%' folder (a.k.a. \Windows).

-

The DAPL configuration file by convention is defined as -'%SystemDrive%\DAT\dat.conf'. This default specification can be overridden by use +

The DAPL/DAT configuration file by convention is defined as +'%SystemDrive%\DAT\dat.conf'. If the folder '%SystemDrive%\DAT' does not exist, +a template configuration file will be installed as '%SystemDrive%\DAT\dat.conf'.
+In order to preserve existing installations, the dat.conf file is not +automatically installed in it's default location if the folder +'%SystemDrive%\DAT' exists.
+A sample, although not used in it's current location, dat.conf file is installed as '\Program Files\WinOF\dat.conf +'.

+

The default DAT configuration file specification can be overridden by use of the environment variable DAT_OVERRIDE. Such that 'DAT_OVERRIDE=D:\MyDAT\test.conf' would be a valid override specification.

Within the dat.conf file, the DAPL library specification can be @@ -725,12 +758,6 @@ 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").

-

A sample dat.conf file is installed as '\Program Files\WinOF\dat.conf -'.
-After the WinOF installation, move the \Program Files\WinOF\dat.conf file to the -default DAT configuration file location
-'%SystemDrive%\DAT\dat.conf'. In order to preserve existing installations, the -dat.conf file is not automatically installed in it's default location.

 

Known Issues

-- 2.41.0