[WinOF] WIX

Document:
  DAPL/2 __stdcall library linkages
  DAPL 2 - IB Extensions (atomics, comp-n-swap).
  OpenSM log file locations

git-svn-id: svn://openib.tc.cornell.edu/gen1/trunk@840 ad392aa1-c5ef-ae45-8dd8-e69d62a5ef86

diff --git a/docs/Manual.htm b/docs/Manual.htm
index c791175..37554e4 100644 (file)
--- a/docs/Manual.htm
+++ b/docs/Manual.htm
@@ -15,7 +15,7 @@ div.Section1
 <h1 align="center">User's Manual</h1>\r
 <h2 align="center">Release 1.0.1</h2>\r
 <h3 align="center">\r
-<!--webbot bot="Timestamp" S-Type="EDITED" S-Format="%m/%d/%Y" startspan -->09/19/2007<!--webbot bot="Timestamp" endspan i-checksum="12660" --></h3>\r
+<!--webbot bot="Timestamp" S-Type="EDITED" S-Format="%m/%d/%Y" startspan -->09/28/2007<!--webbot bot="Timestamp" endspan i-checksum="12652" --></h3>\r
 <h2 align="left"><u>Overview</u></h2>\r
 <p align="left"><span style="FONT-SIZE: 12pt; FONT-FAMILY: 'Times New Roman'">\r
 The Windows OpenFabrics (WinOF) package is composed of software modules intended \r
@@ -401,7 +401,7 @@ Management service.</p>
        Once the installation has completed, check the running InfiniBand Subnet \r
        Management service status via the Windows service manager (see #1).<br>\r
 &nbsp;</li>\r
-       <li>Consult the OpenSM log file @ %SystemRoot%\temp\osm.log to see what \r
+       <li>Consult the OpenSM log file @ %SystemRoot%\Temp\osm.log to see what \r
        OpenSM thinks is happening.</li>\r
 </ol>\r
 <p>&nbsp;</p>\r
@@ -517,8 +517,10 @@ Management service.</p>
        <p align="left">-f<br>\r
        --log_file</p>\r
        <blockquote>\r
-               <p align="left">This option defines the log to be the given file. By \r
-               default the log goes to %SystemRoot%\temp\osm.log.<br>\r
+               <p align="left">This option names the OpenSM log file. By \r
+               default the log goes to %SystemRoot%\Temp\osm.log when started as<br>\r
+               a Windows service. When OpenSM.exe is run from a command prompt, the \r
+               default log file is created as '%TEMP%\osm.log'.<br>\r
                For the log to go to standard output use -f stdout.</p>\r
        </blockquote>\r
        <p align="left">-e<br>\r
@@ -1050,8 +1052,9 @@ See <a href="https://wiki.openfabrics.org/tiki-index.php?page=Winsock+Direct">
 https://wiki.openfabrics.org/tiki-index.php?page=Winsock+Direct</a> for the \r
 latest WSD status.</p>\r
 <h3 align="left">Winsock Direct Service Provider Installation</h3>\r
-<p align="left">When the custom install option 'WSD' is selected the WSD service \r
-is automatically installed and started as part of the installation.<br>\r
+<p align="left">WSD service \r
+is automatically installed and started as part of the 'default' installation; \r
+except on XP systems - WSD not supported.<br>\r
 Manual control is performed via the \Program Files\WinOF\installsp.exe utility.</p>\r
 <blockquote>\r
        <p align="left">usage: installsp [-i | -r | -l]<br>\r
@@ -1079,9 +1082,21 @@ and iWARP.</font></p>
 (Direct Access Provider Library) which now fully supports Infiniband RDMA and \r
 IPoIB.</font></p>\r
 <p align="left"><font face="Times New Roman">WinOF 1.0.1, and future WinOF \r
-releases, include DAT/DAPL version 2.0 runtime libraries along with an optional \r
+releases, will include DAT/DAPL version 2.0 runtime libraries along with an optional \r
 v2.0 application build environment.<br>\r
-&nbsp;</font></p>\r
+DAT 2.0 is configured with InfiniBand extensions enabled. The IB extensions \r
+include</font></p>\r
+<ul>\r
+       <li>\r
+       <p align="left"><font face="Times New Roman">RDMA write with Immediate data</font></p>\r
+       </li>\r
+       <li>\r
+       <p align="left"><font face="Times New Roman">Atomic Compare and Swap \r
+       operation</font></p></li>\r
+       <li>\r
+       <p align="left"><font face="Times New Roman">Atomic Fetch and Add operation<br>&nbsp;</font></p>\r
+       </li>\r
+</ul>\r
 <div id="tiki-main0">\r
        <div id="tiki-mid0">\r
                <table id="table3" cellSpacing="0" cellPadding="0" border="0">\r
@@ -1204,6 +1219,11 @@ v2.0 application build environment.<br>
        '%SystemDrive%\DAT\v2-0'. Your C language based DAT 1.1 application compilation command line \r
        should include'/I%SystemDrive%\DAT\v1-1' with C code referencing '#include &lt;DAT\udat.h&gt;'.<br>\r
        <br>\r
+       The 'default' DAT/DAPL C language calling convention is '__stdcall', not the \r
+       'normal' Visual Studio C compiler default. __stdcall was chosen as MS \r
+       recommended it to be more efficient. An application can freely mix default C \r
+       compiler linkages '__cdecl' and '__stdcall'.<br>\r
+       <br>\r
        Visual Studio 2005 command window - (nmake) Makefile Fragments:</font></p>\r
        <blockquote>\r
                <p align="left"><font face="Courier New" size="2">DAT_PATH=%SystemDrive%\DAT\v1-1<br>\r