[WinOF] DAPL/DAT debug bit values needed more whitespace for readability.

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

diff --git a/branches/WinOF/InstallShield/Manual.htm b/branches/WinOF/InstallShield/Manual.htm
index 57ddc8d035b835789806391c422e3bd475b6df2a..ea69101068c95213f958258ac928585dd0bf3678 100644 (file)
--- a/branches/WinOF/InstallShield/Manual.htm
+++ b/branches/WinOF/InstallShield/Manual.htm
@@ -15,7 +15,7 @@ div.Section1
 <h1 align="center">User's Manual</h1>\r
 <h2 align="center">Release 1.0</h2>\r
 <h3 align="center">\r
-<!--webbot bot="Timestamp" S-Type="EDITED" S-Format="%m/%d/%Y" startspan -->08/01/2007<!--webbot bot="Timestamp" endspan i-checksum="12522" --></h3>\r
+<!--webbot bot="Timestamp" S-Type="EDITED" S-Format="%m/%d/%Y" startspan -->08/14/2007<!--webbot bot="Timestamp" endspan i-checksum="12578" --></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
@@ -1194,13 +1194,13 @@ DAT_DBG_TYPE
 Value specifies which parts of the registry will print debugging\r
 information, valid values are \r
 \r
-DAT_OS_DBG_TYPE_ERROR = 0x1\r
-DAT_OS_DBG_TYPE_GENERIC = 0x2\r
-DAT_OS_DBG_TYPE_SR = 0x4\r
-DAT_OS_DBG_TYPE_DR = 0x8\r
+DAT_OS_DBG_TYPE_ERROR        = 0x1\r
+DAT_OS_DBG_TYPE_GENERIC      = 0x2\r
+DAT_OS_DBG_TYPE_SR           = 0x4\r
+DAT_OS_DBG_TYPE_DR           = 0x8\r
 DAT_OS_DBG_TYPE_PROVIDER_API = 0x10\r
 DAT_OS_DBG_TYPE_CONSUMER_API = 0x20\r
-DAT_OS_DBG_TYPE_ALL = 0xff\r
+DAT_OS_DBG_TYPE_ALL          = 0xff\r
 \r
 or any combination of these. For example you can use 0xC to get both \r
 static and dynamic registry output.\r
@@ -1214,7 +1214,7 @@ Value sets the output destination, valid values are
 \r
 DAT_OS_DBG_DEST_STDOUT = 0x1\r
 DAT_OS_DBG_DEST_SYSLOG = 0x2 \r
-DAT_OS_DBG_DEST_ALL = 0x3 \r
+DAT_OS_DBG_DEST_ALL    = 0x3 \r
 \r
 For example, 0x3 will output to both stdout and the syslog. \r
 </pre>\r
@@ -1228,17 +1228,17 @@ For example, 0x3 will output to both stdout and the syslog.
 <font face="Courier New">Value specifies which parts of the registry will print \r
 debugging information, valid values are</font> <br>\r
 <br>\r
-</font><font face="Courier New"><font size="2">DAPL_DBG_TYPE_ERR = 0x0001<br>\r
-DAPL_DBG_TYPE_WARN = 0x0002<br>\r
-DAPL_DBG_TYPE_EVD = 0x0004<br>\r
-DAPL_DBG_TYPE_CM = 0x0008<br>\r
-DAPL_DBG_TYPE_EP = 0x0010<br>\r
-DAPL_DBG_TYPE_UTIL = 0x0020<br>\r
-DAPL_DBG_TYPE_CALLBACK = 0x0040<br>\r
+</font><font face="Courier New"><font size="2">DAPL_DBG_TYPE_ERR&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; = 0x0001<br>\r
+DAPL_DBG_TYPE_WARN&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; = 0x0002<br>\r
+DAPL_DBG_TYPE_EVD&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; = 0x0004<br>\r
+DAPL_DBG_TYPE_CM&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; = 0x0008<br>\r
+DAPL_DBG_TYPE_EP&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; = 0x0010<br>\r
+DAPL_DBG_TYPE_UTIL&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; = 0x0020<br>\r
+DAPL_DBG_TYPE_CALLBACK&nbsp;&nbsp;&nbsp;&nbsp; = 0x0040<br>\r
 DAPL_DBG_TYPE_DTO_COMP_ERR = 0x0080<br>\r
-DAPL_DBG_TYPE_API = 0x0100<br>\r
-DAPL_DBG_TYPE_RTN = 0x0200<br>\r
-DAPL_DBG_TYPE_EXCEPTION = 0x0400<br>\r
+DAPL_DBG_TYPE_API&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; = 0x0100<br>\r
+DAPL_DBG_TYPE_RTN&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; = 0x0200<br>\r
+DAPL_DBG_TYPE_EXCEPTION&nbsp;&nbsp;&nbsp; = 0x0400<br>\r
 <br>\r
 or any combination of these. For example you can use 0xC to get both <br>\r
 EVD and CM output.<br>\r
@@ -1253,7 +1253,7 @@ Value sets the output destination, valid values are <br>
 <br>\r
 DAPL_DBG_DEST_STDOUT = 0x1<br>\r
 DAPL_DBG_DEST_SYSLOG = 0x2 <br>\r
-DAPL_DBG_DEST_ALL = 0x3 <br>\r
+DAPL_DBG_DEST_ALL&nbsp;&nbsp;&nbsp; = 0x3 <br>\r
 <br>\r
 For example, 0x3 will output to both stdout and the syslog.</font> </font><br>\r
 <br>\r