archive
/
windows-server-2003
mirror of https://github.com/selfrender/Windows-Server-2003
2
0
Fork 0
Code Issues Projects Releases Wiki Activity
Leaked source code of windows server 2003
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
4 Commits
1 Branch
0 Tags
1.5 GiB
Branch: master
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from 'master'
${ noResults }
windows-server-2003/net/ndis/samples/muxim/mux.htm

617 lines
36 KiB
Raw Permalink Normal View History

commiting as it is
4 years ago
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
  1. <html xmlns:v="urn:schemas-microsoft-com:vml"
  2. xmlns:o="urn:schemas-microsoft-com:office:office"
  3. xmlns:w="urn:schemas-microsoft-com:office:word"
  4. xmlns:st1="urn:schemas-microsoft-com:office:smarttags"
  5. xmlns="http://www.w3.org/TR/REC-html40">
  7. <head>
  8. <meta http-equiv=Content-Type content="text/html; charset=windows-1252">
  9. <meta name=ProgId content=Word.Document>
  10. <meta name=Generator content="Microsoft Word 10">
  11. <meta name=Originator content="Microsoft Word 10">
  12. <link rel=File-List href="mux_files/filelist.xml">
  13. <title>MUX Intermediate Miniport Driver Help</title>
  14. <o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags"
  15. name="PlaceType"/>
  16. <o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags"
  17. name="PlaceName"/>
  18. <o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags"
  19. name="place"/>
  20. <!--[if gte mso 9]><xml>
  21. <w:WordDocument>
  22. <w:SpellingState>Clean</w:SpellingState>
  23. <w:GrammarState>Clean</w:GrammarState>
  24. <w:BrowserLevel>MicrosoftInternetExplorer4</w:BrowserLevel>
  25. </w:WordDocument>
  26. </xml><![endif]--><!--[if !mso]><object
  27. classid="clsid:38481807-CA0E-42D2-BF39-B33AF135CC4D" id=ieooui></object>
  28. <style>
  29. st1\:*{behavior:url(#ieooui) }
  30. </style>
  31. <![endif]-->
  32. <style>
  33. <!--
  34. /* Font Definitions */
  35. @font-face
  36. {font-family:Verdana;
  37. panose-1:2 11 6 4 3 5 4 4 2 4;
  38. mso-font-charset:0;
  39. mso-generic-font-family:swiss;
  40. mso-font-pitch:variable;
  41. mso-font-signature:536871559 0 0 0 415 0;}
  42. @font-face
  43. {font-family:"MS Sans Serif";
  44. mso-font-alt:"Times New Roman";
  45. mso-font-charset:0;
  46. mso-generic-font-family:auto;
  47. mso-font-pitch:auto;
  48. mso-font-signature:3 0 0 0 1 0;}
  49. /* Style Definitions */
  50. p.MsoNormal, li.MsoNormal, div.MsoNormal
  51. {mso-style-parent:"";
  52. margin:0in;
  53. margin-bottom:.0001pt;
  54. mso-pagination:widow-orphan;
  55. font-size:12.0pt;
  56. font-family:"Times New Roman";
  57. mso-fareast-font-family:"Times New Roman";
  58. color:black;}
  59. h2
  60. {mso-margin-top-alt:auto;
  61. margin-right:0in;
  62. mso-margin-bottom-alt:auto;
  63. margin-left:0in;
  64. mso-pagination:widow-orphan;
  65. mso-outline-level:2;
  66. font-size:18.0pt;
  67. font-family:"Times New Roman";
  68. color:black;
  69. font-weight:bold;}
  70. h3
  71. {mso-margin-top-alt:auto;
  72. margin-right:0in;
  73. mso-margin-bottom-alt:auto;
  74. margin-left:0in;
  75. mso-pagination:widow-orphan;
  76. mso-outline-level:3;
  77. font-size:13.5pt;
  78. font-family:"Times New Roman";
  79. color:black;
  80. font-weight:bold;}
  81. h4
  82. {mso-margin-top-alt:auto;
  83. margin-right:0in;
  84. mso-margin-bottom-alt:auto;
  85. margin-left:0in;
  86. mso-pagination:widow-orphan;
  87. mso-outline-level:4;
  88. font-size:12.0pt;
  89. font-family:"Times New Roman";
  90. color:black;
  91. font-weight:bold;}
  92. a:link, span.MsoHyperlink
  93. {color:blue;
  94. text-decoration:underline;
  95. text-underline:single;}
  96. a:visited, span.MsoHyperlinkFollowed
  97. {color:purple;
  98. text-decoration:underline;
  99. text-underline:single;}
  100. p
  101. {mso-margin-top-alt:auto;
  102. margin-right:0in;
  103. mso-margin-bottom-alt:auto;
  104. margin-left:0in;
  105. mso-pagination:widow-orphan;
  106. font-size:12.0pt;
  107. font-family:"Times New Roman";
  108. mso-fareast-font-family:"Times New Roman";
  109. color:black;}
  110. pre
  111. {margin:0in;
  112. margin-bottom:.0001pt;
  113. mso-pagination:widow-orphan;
  114. tab-stops:45.8pt 91.6pt 137.4pt 183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt 641.2pt 687.0pt 732.8pt;
  115. font-size:10.0pt;
  116. font-family:"Courier New";
  117. mso-fareast-font-family:"Courier New";
  118. color:black;}
  119. span.SpellE
  120. {mso-style-name:"";
  121. mso-spl-e:yes;}
  122. span.GramE
  123. {mso-style-name:"";
  124. mso-gram-e:yes;}
  125. @page Section1
  126. {size:8.5in 11.0in;
  127. margin:1.0in 1.25in 1.0in 1.25in;
  128. mso-header-margin:.5in;
  129. mso-footer-margin:.5in;
  130. mso-paper-source:0;}
  131. div.Section1
  132. {page:Section1;}
  133. -->
  134. </style>
  135. <!--[if gte mso 10]>
  136. <style>
  137. /* Style Definitions */
  138. table.MsoNormalTable
  139. {mso-style-name:"Table Normal";
  140. mso-tstyle-rowband-size:0;
  141. mso-tstyle-colband-size:0;
  142. mso-style-noshow:yes;
  143. mso-style-parent:"";
  144. mso-padding-alt:0in 5.4pt 0in 5.4pt;
  145. mso-para-margin:0in;
  146. mso-para-margin-bottom:.0001pt;
  147. mso-pagination:widow-orphan;
  148. font-size:10.0pt;
  149. font-family:"Times New Roman";}
  150. </style>
  151. <![endif]-->
  152. <meta name=Template content="C:\Program Files\Microsoft Office\Office\html.dot">
  153. <!--[if gte mso 9]><xml>
  154. <o:shapedefaults v:ext="edit" spidmax="7170"/>
  155. </xml><![endif]--><!--[if gte mso 9]><xml>
  156. <o:shapelayout v:ext="edit">
  157. <o:idmap v:ext="edit" data="1"/>
  158. </o:shapelayout></xml><![endif]-->
  159. </head>
  161. <body bgcolor=white lang=EN-US link=blue vlink=purple style='tab-interval:.5in'>
  163. <div class=Section1>
  165. <h2><a name=MYSAMPLE><span style='font-family:Verdana'>
  167. <!doctype HTML>
  169. <! ---------------- Snip Snip ---------------- >MUX.SYS - Sample NDIS MUX
  170. Intermediate Driver</span></a><span style='font-family:Verdana'><o:p></o:p></span></h2>
  172. <h3><span style='font-family:Verdana'>SUMMARY<o:p></o:p></span></h3>
  174. <p><st1:place><st1:PlaceName><b><span style='font-family:Verdana'>MUX</span></b></st1:PlaceName><b><span
  175. style='font-family:Verdana'> </span></b><st1:PlaceName><b><span
  176. style='font-family:Verdana'>Intermediate</span></b></st1:PlaceName><b><span
  177. style='font-family:Verdana'> </span></b><st1:PlaceType><b><span
  178. style='font-family:Verdana'>Miniport</span></b></st1:PlaceType></st1:place><b><span
  179. style='font-family:Verdana'> Driver<o:p></o:p></span></b></p>
  181. <p><span style='font-size:10.0pt;font-family:Verdana'>The MUX Intermediate
  182. Miniport (IM) driver is an NDIS 5 driver that demonstrates the operation of an
  183. �N<span class=GramE>:1</span>� MUX driver, i.e. one which creates multiple
  184. virtual network devices on top of a single lower adapter. Protocols bind to
  185. these virtual adapters as if they are real adapters. Examples of </span><st1:place><st1:PlaceName><span
  186. style='font-size:10.0pt;font-family:Verdana'>Intermediate</span></st1:PlaceName><span
  187. style='font-size:10.0pt;font-family:Verdana'> </span><st1:PlaceType><span
  188. style='font-size:10.0pt;font-family:Verdana'>Miniport</span></st1:PlaceType></st1:place><span
  189. style='font-size:10.0pt;font-family:Verdana'> drivers that can use this
  190. framework are Virtual LAN (VLAN) drivers.<o:p></o:p></span></p>
  192. <p><span style='font-size:10.0pt;font-family:Verdana'>This sample implements
  193. IEEE 802.1Q VLAN tagging, which is enabled by changing the default VLAN ID to a
  194. non-zero valid value (see �Configuring VLANs� below).<o:p></o:p></span></p>
  196. <p><b><span style='mso-bidi-font-size:10.0pt;font-family:Verdana'>Operation<o:p></o:p></span></b></p>
  198. <p><span style='font-size:10.0pt;font-family:Verdana'>The driver binds to
  199. Ethernet (NdisMedium802_3) adapters as a protocol, and exposes one or more
  200. virtual Ethernet devices over each lower adapter, based on its configuration.
  201. The term �VELAN� is used to denote a Virtual Ethernet LAN adapter implemented
  202. by this driver.<o:p></o:p></span></p>
  204. <p><span style='font-size:10.0pt;font-family:Verdana'>When it binds to a lower
  205. adapter, MUX reads the standard �UpperBind� key to obtain a list of VELANs
  206. configured over this adapter. For each such VELAN, it calls <span class=GramE>NdisIMInitializeDeviceInstanceEx(</span>)
  207. to instantiate the NDIS miniport for the VELAN. NDIS then calls the driver�s
  208. MiniportInitialize (<i>MPInitialize</i>) routine to start the VELAN miniport.<o:p></o:p></span></p>
  210. <p><span style='font-size:10.0pt;font-family:Verdana'>The MUX driver supports
  211. configuring the MAC address for each VELAN miniport using the standard
  212. �NetworkAddress� key that it reads from its MiniportInitialize routine. If this
  213. is not configured, it computes a �locally significant� MAC address for the
  214. VELAN using the MAC address of the lower adapter. The MUX driver sets its lower
  215. adapter to promiscuous mode in order to be able to receive frames directed to
  216. any of the VELAN MAC addresses. <span class=GramE>However it does implement
  217. packet-filtering (and multicast address filtering) logic for all its VELAN
  218. miniports so that it only passes up relevant frames on each VELAN.</span> This
  219. aspect of the driver may be modified if, for example, your driver design uses
  220. the same MAC address as that of the lower adapter on all VELANs. With such a
  221. modification, it is not required to set the lower adapter to promiscuous mode
  222. and incur the costs of receiving all packets on the network.<o:p></o:p></span></p>
  224. <p><span style='font-size:10.0pt;font-family:Verdana'>It supports dynamic
  225. addition and deletion of VELANs in conjunction with <span class=GramE>its</span>
  226. notify object (related sample). If a VELAN is deleted, the virtual device
  227. corresponding to the VELAN is stopped and removed, which in turn results in
  228. NDIS halting the miniport instance for the VELAN (see <i>MPHalt</i>). If a
  229. VELAN is added, NDIS sends a global reconfiguration event to the protocol edge
  230. of this driver. The handler function for this event, PtPNPHandler, goes through
  231. all lower adapters to see if any new VELANs have been added, i.e. if any of the
  232. �UpperBind� keys have been modified.<o:p></o:p></span></p>
  234. <p><span style='font-size:10.0pt;font-family:Verdana'>Since the driver
  235. implements a virtual device, it does not simply pass through most NDIS
  236. queries/sets. It keeps its own device view that is reflected in its responses
  237. to queries/sets. However it does pass through queries/sets for certain OIDs
  238. that are best handled by the lower adapter driver. <o:p></o:p></span></p>
  240. <p><span style='font-size:10.0pt;font-family:Verdana'>The driver supports Power
  241. Management in the sense that it allows Wake-On-LAN and related functionality,
  242. if supported by the lower adapter, to continue to function. It does so by
  243. appropriately forwarding OID_PNP_XXX queries/sets to the lower adapter. <o:p></o:p></span></p>
  245. <p><b style='mso-bidi-font-weight:normal'><span style='font-family:Verdana'>IEEE
  246. 802.1Q VLAN Operation<o:p></o:p></span></b></p>
  248. <p><span style='font-size:10.0pt;font-family:Verdana'>The driver supports
  249. configuring a VLAN ID on each VELAN. It then inserts a tag header containing
  250. this VLAN ID on all outgoing frames. For incoming frames that contain a tag
  251. header, it verifies that a matching VLAN ID is present before indicating it up
  252. to protocols. It removes the tag header, if present, from all indicated frames.
  253. In all cases, received frames that do not contain tag headers are always handed
  254. up to protocols.<o:p></o:p></span></p>
  256. <p><span style='font-size:10.0pt;font-family:Verdana'>With the default
  257. configured VLAN ID of zero, the driver does not insert tag header information
  258. on sent packets, except for sent packets that contain non-zero Ieee8021QInfo
  259. per-packet information, for which the driver does insert corresponding tag
  260. headers. Receive-side filtering on VLAN ID is enabled only with a non-zero
  261. configured VLAN ID, in which case only received frames containing a matching
  262. VLAN ID are passed up. With the default configured VLAN ID of zero, the driver
  263. does not check the VLAN ID on received frames.<o:p></o:p></span></p>
  265. <h3><span style='font-family:Verdana'>BUILDING THE SAMPLE<o:p></o:p></span></h3>
  267. <p><span style='font-size:10.0pt;font-family:Verdana'>Run the <b>build</b>
  268. command from this directory to build the sample�it creates the binary mux.sys.
  269. To disable IEEE VLAN support, comment out the following line in the sources
  270. file before building:<o:p></o:p></span></p>
  272. <p><span style='font-size:10.0pt;font-family:Verdana'>C_DEFINES=$(C_DEFINES)
  273. �DIEEE_VLAN_SUPPORT=1<o:p></o:p></span></p>
  275. <p><span style='font-size:10.0pt;font-family:Verdana'>To install this driver on
  276. Windows� codename Whistler, use the MUX sample notification object and INFs,
  277. also found in this DDK.<o:p></o:p></span></p>
  279. <h3><span style='font-family:Verdana'>INSTALLING THE SAMPLE<o:p></o:p></span></h3>
  281. <p><span style='font-size:10.0pt;font-family:Verdana'>MUX is installed as a
  282. protocol (called �Sample <span class=SpellE>Mux</span>-IM Protocol Driver� in
  283. the supplied INFs/notification object). To install, follow the steps below.<o:p></o:p></span></p>
  285. <p><span style='font-size:10.0pt;font-family:Verdana'>Prepare a floppy disk (or
  286. installation directory) that contains these files: <span class=SpellE>muxp.inf</span>,
  287. <span class=SpellE>mux_mp.inf</span>, mux.sys and mux.dll (notification object
  288. DLL, built in this DDK at network\<span class=SpellE>ndis\mux\notifyob</span>).<o:p></o:p></span></p>
  290. <p><span style='font-size:10.0pt;font-family:Verdana'>On the desktop,
  291. right-click the <b>My Network Places</b> icon and choose <b>Properties</b>. <o:p></o:p></span></p>
  293. <p><span style='font-size:10.0pt;font-family:Verdana'>Right-click on the
  294. relevant Local Area Connection icon and choose <b>Properties</b>. <o:p></o:p></span></p>
  296. <p><span style='font-size:10.0pt;font-family:Verdana'>Click <b>Install</b>,
  297. then <b>Protocol</b>, then <b>Add</b>, <span class=GramE>then</span> <b>Have
  298. Disk</b>. <o:p></o:p></span></p>
  300. <p><span style='font-size:10.0pt;font-family:Verdana'>Browse to the
  301. drive/directory containing the files listed above. Click <b>OK</b>. This should
  302. show �Sample <span class=SpellE>Mux</span>-IM Protocol Driver� in a list of
  303. Network Protocols. Highlight this and click <b>OK</b>. This should install the
  304. MUX driver. <o:p></o:p></span></p>
  306. <p><span style='font-size:10.0pt;font-family:Verdana'>Click <b>OK</b> or <span
  307. class=GramE><b>Yes</b></span> each time the system prompts with a warning
  308. regarding installation of unsigned files. This is necessary because binaries
  309. generated via the DDK build environment are not signed.<o:p></o:p></span></p>
  311. <p><span style='font-size:10.0pt;font-family:Verdana'>Two .INF files are needed
  312. rather than one because MUX is installed both as a protocol and a miniport.<o:p></o:p></span></p>
  314. <p><b style='mso-bidi-font-weight:normal'><span style='font-family:Verdana'>Configuring
  315. VLANs<o:p></o:p></span></b></p>
  317. <p><span style='font-size:10.0pt;font-family:Verdana'>The VLAN ID for each
  318. VELAN (virtual miniport) can be configured as follows. Right-click on the
  319. virtual miniport Local Area Connection icon and choose <b style='mso-bidi-font-weight:
  320. normal'>Properties</b>. Click on the <b style='mso-bidi-font-weight:normal'>Configure</b>
  321. button to bring up the Device Manager UI for the virtual device. Select the <b
  322. style='mso-bidi-font-weight:normal'>Advanced</b> property sheet � this should
  323. contain a �VLAN ID� parameter that is configurable to the desired VLAN ID.
  324. Choosing a value of 0 (zero) disables receive-side filtering based on VLAN ID.<o:p></o:p></span></p>
  326. <h3><span style='font-family:Verdana'>CODE TOUR<o:p></o:p></span></h3>
  328. <h4><span style='font-family:Verdana'>File Manifest<o:p></o:p></span></h4>
  330. <pre><u>File<span style='mso-tab-count:2'>���������� </span>Description<o:p></o:p></u></pre><pre><o:p>&nbsp;</o:p></pre><pre><span
  331. class=SpellE>Makefile</span><span style='mso-tab-count:1'>������ </span>Used during compilation to create the object and sys files</pre><pre>Miniport.c<span
  332. style='mso-tab-count:1'>���� </span>Miniport related routines for the MUX driver</pre><pre><span
  333. class=SpellE>Mux.c</span><span style='mso-tab-count:2'>��������� </span>DriverEntry routine and any routines common to the MUX miniport and protocol </pre><pre><span
  334. class=SpellE>Mux.h</span><span style='mso-tab-count:2'>��������� </span>Prototypes of all functions and data structures used by the MUX driver</pre><pre>Mux.htm<span
  335. style='mso-tab-count:2'>������� </span>Documentation for the MUX driver (this file)</pre><pre><span
  336. class=SpellE>Mux.rc</span><span style='mso-tab-count:2'>�������� </span>Resource <span
  337. class=GramE>file</span> for the MUX driver</pre><pre><span class=SpellE>Muxp.inf</span><span
  338. style='mso-tab-count:1'>������ </span>Installation INF for the service (protocol side installation)</pre><pre><span
  339. class=SpellE>Mux_mp.inf</span><span style='mso-tab-count:1'>���� </span>Installation INF for the miniport (virtual device installation)</pre><pre><span
  340. class=SpellE>Precomp.h</span><span style='mso-tab-count:1'>����� </span><span
  341. class=SpellE>Precompile</span> header file</pre><pre><span class=SpellE>Protocol.c</span><span
  342. style='mso-tab-count:1'>���� </span>Protocol related routines for the MUX driver</pre><pre>Sources<span
  343. style='mso-tab-count:2'>������� </span>List of source files that are compiled and linked to create the MUX driver. This can be modified to create binaries that operate on previous Windows versions (e.g. Windows 2000).</pre>
  345. <h4 style='tab-stops:45.8pt 91.6pt 137.4pt 183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt 641.2pt 687.0pt 732.8pt'><span
  346. style='font-family:Verdana'>Programming Tour<o:p></o:p></span></h4>
  348. <p style='tab-stops:45.8pt 91.6pt 137.4pt 183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt 641.2pt 687.0pt 732.8pt'><span
  349. style='font-size:10.0pt;font-family:Verdana'>When it loads, i.e. from its <i>DriverEntry</i>
  350. function, the MUX driver registers as an Intermediate miniport driver and as a
  351. protocol, in that order.<o:p></o:p></span></p>
  353. <p style='tab-stops:45.8pt 91.6pt 137.4pt 183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt 641.2pt 687.0pt 732.8pt'><b><span
  354. style='font-size:10.0pt;font-family:Verdana'>Binding and VELAN Creation<o:p></o:p></span></b></p>
  356. <p style='tab-stops:45.8pt 91.6pt 137.4pt 183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt 641.2pt 687.0pt 732.8pt'><span
  357. style='font-size:10.0pt;font-family:Verdana'>NDIS calls MUX�s BindAdapter
  358. function, <i>PtBindAdapter</i>, for each underlying NDIS adapter to which it is
  359. configured to bind. This function allocates an ADAPT structure to represent the
  360. lower adapter, and calls NdisOpenAdapter to set up a binding to it. In the
  361. context of BindAdapterHandler, after successfully opening a binding to the
  362. underlying adapter, the driver queries the reserved keyword
  363. &quot;UpperBindings&quot; to get a list of device names for the virtual
  364. adapters that this particular binding is to expose � see <i>PtBootStrapVElans</i>
  365. for more details. Note that the MUX driver does not create bindings (i.e. call
  366. NdisOpenAdapter) from any context other than its BindAdapter function � this is
  367. recommended behavior for all drivers of this type.<o:p></o:p></span></p>
  369. <p style='tab-stops:45.8pt 91.6pt 137.4pt 183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt 641.2pt 687.0pt 732.8pt'><span
  370. style='font-size:10.0pt;font-family:Verdana'>For each device name specified in
  371. the �UpperBindings� key, the MUX driver allocates a VELAN data structure to
  372. represent the virtual miniport, calls NdisIMInitializeDeviceInstanceEx. In
  373. response, NDIS eventually calls the MUX miniport�s MiniportInitialize entry
  374. point, <i>MPInitialize</i>, for each VELAN. After <i>MPInitialize</i>
  375. successfully returns, NDIS takes care of getting upper-layer protocols to bind
  376. to the newly created virtual adapter(s).<o:p></o:p></span></p>
  378. <p style='tab-stops:45.8pt 91.6pt 137.4pt 183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt 641.2pt 687.0pt 732.8pt'><b><span
  379. style='font-size:10.0pt;font-family:Verdana'>Unbinding and Halting</span></b><span
  380. style='font-size:10.0pt;font-family:Verdana'><o:p></o:p></span></p>
  382. <p style='tab-stops:45.8pt 91.6pt 137.4pt 183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt 641.2pt 687.0pt 732.8pt'><span
  383. style='font-size:10.0pt;font-family:Verdana'>NDIS calls MUX�s UnbindAdapter
  384. handler, <i>PtUnbindAdapter</i>, to request it to unbind from a lower adapter.
  385. In processing this, MUX calls NdisIMDeInitializeDeviceInstance for each VELAN
  386. instantiated on the indicated adapter � see <i>PtStopVElan</i> for details.
  387. This call results in NDIS first unbinding any protocols bound to the indicated
  388. VELAN, and then calling the MiniportHalt routine, <i>MPHalt</i>, for that
  389. VELAN. <i>MPHalt</i> waits for any outstanding receives/sends on the VELAN to
  390. finish before unlinking the VELAN from the ADAPT.<o:p></o:p></span></p>
  392. <p style='tab-stops:45.8pt 91.6pt 137.4pt 183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt 641.2pt 687.0pt 732.8pt'><i><span
  393. style='font-size:10.0pt;font-family:Verdana'>PtUnbindAdapter</span></i><span
  394. style='font-size:10.0pt;font-family:Verdana'> itself blocks until all VELANs
  395. associated with the ADAPT structure have been unlinked from it. This is to make
  396. sure that no thread running in the context of a miniport-edge entry point for a
  397. VELAN will ever access an invalid lower binding handle. Once all VELANs have
  398. been unlinked, <i>PtUnbindAdapter</i> closes the lower binding by calling
  399. NdisCloseAdapter. Note that the MUX driver does not close its lower binding
  400. from any context other than its UnbindAdapter function � this is recommended
  401. behavior for all drivers of this type.<o:p></o:p></span></p>
  403. <p style='tab-stops:45.8pt 91.6pt 137.4pt 183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt 641.2pt 687.0pt 732.8pt'><i><span
  404. style='font-size:10.0pt;font-family:Verdana'>MPHalt</span></i><span
  405. style='font-size:10.0pt;font-family:Verdana'> may also be called if the VELAN
  406. device is disabled, e.g. from the Network Connections Folder. There is no
  407. special code within <i>MPHalt</i> to handle this condition. However, <i>PtUnbindAdapter</i>
  408. takes care to not attempt to deinitialize a VELAN miniport (via
  409. NdisIMDeInitializeDeviceInstance) that has already been halted.<o:p></o:p></span></p>
  411. <p style='tab-stops:45.8pt 91.6pt 137.4pt 183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt 641.2pt 687.0pt 732.8pt'><b><span
  412. style='font-size:10.0pt;font-family:Verdana'>Handling Queries<o:p></o:p></span></b></p>
  414. <p style='tab-stops:45.8pt 91.6pt 137.4pt 183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt 641.2pt 687.0pt 732.8pt'><i><span
  415. style='font-size:10.0pt;font-family:Verdana'>MPQueryInformation</span></i><span
  416. style='font-size:10.0pt;font-family:Verdana'> is the MUX driver�s function that
  417. handles queries for OID values on VELAN miniports. Most of the �Ethernet� type
  418. information for the virtual miniport is stored in the VELAN structure itself,
  419. and the driver returns information from this structure. The queries that are
  420. forwarded are OID_GEN_MEDIA_CONNECT_STATUS, OID_PNP_CAPABILITIES and
  421. OID_PNP_WAKE_UP_PATTERN_LIST. See �Handling Power Management� below for more
  422. information about the latter two OIDs.<i><o:p></o:p></i></span></p>
  424. <p style='tab-stops:45.8pt 91.6pt 137.4pt 183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt 641.2pt 687.0pt 732.8pt'><b><span
  425. style='font-size:10.0pt;font-family:Verdana'>Handling Sets</span></b><span
  426. style='font-size:10.0pt;font-family:Verdana'><o:p></o:p></span></p>
  428. <p style='tab-stops:45.8pt 91.6pt 137.4pt 183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt 641.2pt 687.0pt 732.8pt'><i><span
  429. style='font-size:10.0pt;font-family:Verdana'>MPSetInformation</span></i><span
  430. style='font-size:10.0pt;font-family:Verdana'> handles setting OID values on
  431. VELAN miniports. Data management OIDs handled by the MUX driver are
  432. OID_802_3_MULTICAST_LIST and OID_GEN_CURRENT_PACKET_FILTER. The multicast list
  433. is handled entirely within the MUX driver � it just stores the set of multicast
  434. addresses in the VELAN structure, for reference during receive-side data processing.
  435. The packet filter is handled in a different way � the MUX driver combines the
  436. packet filter settings (bitwise OR) of all VELANs associated with the same
  437. lower adapter. If the combined packet filter is non-zero, MUX sends a Set
  438. request with a value of NDIS_PACKET_TYPE_PROMISCUOUS for
  439. OID_GEN_CURRENT_PACKET_FILTER to start receives on the lower adapter. If the
  440. combined packet filter is zero, MUX sets the lower adapter�s packet filter to 0
  441. (turns off all receives if there aren�t any interested protocols).<o:p></o:p></span></p>
  443. <p style='tab-stops:45.8pt 91.6pt 137.4pt 183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt 641.2pt 687.0pt 732.8pt'><span
  444. style='font-size:10.0pt;font-family:Verdana'>Note that setting the lower
  445. adapter to promiscuous mode is only done here in order to be able to receive <span
  446. class=SpellE>unicast</span> frames directed to multiple MAC addresses. If, for
  447. example, all VELANs are assigned the same MAC address (which is identical to
  448. the address of the lower adapter), then the MUX driver should only pass down
  449. the combined (bitwise OR) setting of packet filter settings of all VELANs.<o:p></o:p></span></p>
  451. <p style='tab-stops:45.8pt 91.6pt 137.4pt 183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt 641.2pt 687.0pt 732.8pt'><span
  452. style='font-size:10.0pt;font-family:Verdana'>Some power management OIDs are
  453. forwarded to the lower miniport. See �Handling Power Management� below for details.
  454. <o:p></o:p></span></p>
  456. <p style='tab-stops:45.8pt 91.6pt 137.4pt 183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt 641.2pt 687.0pt 732.8pt'><b><span
  457. style='font-size:10.0pt;font-family:Verdana'>Sending Data<o:p></o:p></span></b></p>
  459. <p style='tab-stops:45.8pt 91.6pt 137.4pt 183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt 641.2pt 687.0pt 732.8pt'><span
  460. style='font-size:10.0pt;font-family:Verdana'>Data sent down on a VELAN miniport
  461. is forwarded to the lower adapter. The MUX driver itself does not generate any
  462. data of its own. The MUX driver allocates a new NDIS_PACKET for each packet
  463. passed to its <i>MPSendPackets</i> function, and saves a pointer to the
  464. original NDIS_PACKET in the reserved area of the packet structure. When the
  465. lower adapter completes the send (<i>PtSendComplete</i>), MUX picks up the
  466. original packet and calls NdisMSendComplete to complete the original send
  467. request.<o:p></o:p></span></p>
  469. <p style='tab-stops:45.8pt 91.6pt 137.4pt 183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt 641.2pt 687.0pt 732.8pt'><span
  470. style='font-size:10.0pt;font-family:Verdana'>If a non-zero VLAN ID is
  471. configured for the VELAN, and/or the packet has non-zero Ieee8021QInfo
  472. per-packet information, then the MUX driver inserts an NDIS buffer containing a
  473. tag header to the front of the packet before sending it down � see function <i
  474. style='mso-bidi-font-style:normal'>MPHandleSendTagging</i> for details.<o:p></o:p></span></p>
  476. <p style='tab-stops:45.8pt 91.6pt 137.4pt 183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt 641.2pt 687.0pt 732.8pt'><b><span
  477. style='font-size:10.0pt;font-family:Verdana'>Receiving Data<o:p></o:p></span></b></p>
  479. <p style='tab-stops:45.8pt 91.6pt 137.4pt 183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt 641.2pt 687.0pt 732.8pt'><span
  480. style='font-size:10.0pt;font-family:Verdana'>Data received from a lower adapter
  481. is indicated up on zero or more VELANs. The <i>PtReceivePacket</i> or <i>PtReceive</i>
  482. function is called for each packet received from the lower adapter. In both
  483. cases, the received data is checked for matches with the packet filter and
  484. multicast list for each VELAN associated with the adapter (see <i>PtMatchPacketToVElan</i>).
  485. Whenever a match is found, a new NDIS_PACKET is allocated and set to point to
  486. the received data. A pointer to the original received packet (if any) is also
  487. stored in the new packet�s reserved area. This packet is indicated up via
  488. NdisMIndicateReceivePacket to all interested protocols on that VELAN. <o:p></o:p></span></p>
  490. <p style='tab-stops:45.8pt 91.6pt 137.4pt 183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt 641.2pt 687.0pt 732.8pt'><span
  491. style='font-size:10.0pt;font-family:Verdana'>The driver�s <i>MPReturnPacket</i>
  492. function is called either by NDIS or by MUX itself when protocols are done with
  493. a received packet. This function returns the original packet indicated by the
  494. lower driver, if any, by calling NdisReturnPackets.<o:p></o:p></span></p>
  496. <p style='tab-stops:45.8pt 91.6pt 137.4pt 183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt 641.2pt 687.0pt 732.8pt'><span
  497. style='font-size:10.0pt;font-family:Verdana'>The driver indicates up received
  498. frames that do not have an IEEE 802.1Q tag header in them � see function <i
  499. style='mso-bidi-font-style:normal'>PtHandleRcvTagging</i>. It always strips off
  500. tag headers, if present, on received frames. If a non-zero VLAN ID is
  501. configured, then it checks received frames that contain tag headers for
  502. matching VLAN Ids � only matching frames are indicated up to protocols. Any
  503. VLAN/priority information present in incoming frames is copied to per-packet
  504. information fields of indicated NDIS_PACKET structures.<o:p></o:p></span></p>
  506. <p style='tab-stops:45.8pt 91.6pt 137.4pt 183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt 641.2pt 687.0pt 732.8pt'><b><span
  507. style='font-size:10.0pt;font-family:Verdana'>Status Indications</span></b><span
  508. style='font-size:10.0pt;font-family:Verdana'><o:p></o:p></span></p>
  510. <p style='tab-stops:45.8pt 91.6pt 137.4pt 183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt 641.2pt 687.0pt 732.8pt'><span
  511. style='font-size:10.0pt;font-family:Verdana'>The only status indications that
  512. are forwarded up by MUX are media connect status indications. See <i>PtStatus</i>
  513. for more details.<o:p></o:p></span></p>
  515. <p style='tab-stops:45.8pt 91.6pt 137.4pt 183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt 641.2pt 687.0pt 732.8pt'><b><span
  516. style='font-size:10.0pt;font-family:Verdana'>Handling Power Management</span></b><span
  517. style='font-size:10.0pt;font-family:Verdana'><o:p></o:p></span></p>
  519. <p style='tab-stops:45.8pt 91.6pt 137.4pt 183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt 641.2pt 687.0pt 732.8pt'><span
  520. style='font-size:10.0pt;font-family:Verdana'>During initialization (<i>MPInitialize</i>),
  521. the MUX miniport sets the attribute <i>NDIS_ATTRIBUTE_NO_HALT_ON_SUSPEND</i> in
  522. its call to NdisMSetAttributesEx. When the MUX miniport is requested to report
  523. its Plug and Play capabilities (OID_PNP_CAPABILITIES), the MUX miniport
  524. forwards the request to the underlying miniport. If this request succeeds, then
  525. the MUX miniport overwrites the following fields before successfully completing
  526. the original request: <o:p></o:p></span></p>
  528. <p style='tab-stops:45.8pt 91.6pt 137.4pt 183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt 641.2pt 687.0pt 732.8pt'><span
  529. style='font-size:10.0pt;font-family:Verdana'>NDIS_DEVICE_POWER_STATE<span
  530. style='mso-tab-count:1'>��������� </span>MinMagicPacketWakeUp =
  531. NdisDeviceStateUnspecified;<o:p></o:p></span></p>
  533. <p style='tab-stops:45.8pt 91.6pt 137.4pt 183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt 641.2pt 687.0pt 732.8pt'><span
  534. style='font-size:10.0pt;font-family:Verdana'>NDIS_DEVICE_POWER_STATE<span
  535. style='mso-tab-count:1'>��������� </span><span class=SpellE>MinPatternWakeUp</span>=
  536. NdisDeviceStateUnspecified;<o:p></o:p></span></p>
  538. <p style='tab-stops:45.8pt 91.6pt 137.4pt 183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt 641.2pt 687.0pt 732.8pt'><span
  539. style='font-size:10.0pt;font-family:Verdana'>NDIS_DEVICE_POWER_STATE<span
  540. style='mso-tab-count:1'>��������� </span>MinLinkChangeWakeUp=NdisDeviceStateUnspecified<o:p></o:p></span></p>
  542. <p style='tab-stops:45.8pt 91.6pt 137.4pt 183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt 641.2pt 687.0pt 732.8pt'><span
  543. style='font-size:10.0pt;font-family:Verdana'>See <i>PtPostProcessPnPCapabilities</i>
  544. for details. <o:p></o:p></span></p>
  546. <p style='tab-stops:45.8pt 91.6pt 137.4pt 183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt 641.2pt 687.0pt 732.8pt'><span
  547. style='font-size:10.0pt;font-family:Verdana'>OID_PNP_SET_POWER and
  548. OID_PNP_QUERY_POWER are not passed to the lower adapter, since the lower layer
  549. miniport will receive independent requests from NDIS.<o:p></o:p></span></p>
  551. <p style='tab-stops:45.8pt 91.6pt 137.4pt 183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt 641.2pt 687.0pt 732.8pt'><span
  552. style='font-size:10.0pt;font-family:Verdana'>NDIS calls the MUX driver�s
  553. ProtocolPnPEvent function (<i>PtPNPHandler</i>) whenever the underlying adapter
  554. is transitioned to a different power state. If the underlying adapter is
  555. transitioning to a low power state, the driver waits for all outstanding sends
  556. and requests to complete.<o:p></o:p></span></p>
  558. <p style='tab-stops:45.8pt 91.6pt 137.4pt 183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt 641.2pt 687.0pt 732.8pt'><span
  559. style='font-size:10.0pt;font-family:Verdana'>Queries/sets received on a VELAN
  560. miniport that are to be forwarded to the underlying adapter are queued on the
  561. VELAN if the underlying adapter is at a low power state. These are picked up
  562. for processing on receiving a notification that the underlying adapter is back
  563. to a powered-up state.<o:p></o:p></span></p>
  565. <p style='tab-stops:45.8pt 91.6pt 137.4pt 183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt 641.2pt 687.0pt 732.8pt'><b><span
  566. style='font-size:10.0pt;font-family:Verdana'>Handling Global Reconfiguration</span></b><span
  567. style='font-size:10.0pt;font-family:Verdana'><o:p></o:p></span></p>
  569. <p style='tab-stops:45.8pt 91.6pt 137.4pt 183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt 641.2pt 687.0pt 732.8pt'><span
  570. style='font-size:10.0pt;font-family:Verdana'>All modifications to VELAN
  571. configuration are accompanied by PnP reconfigure notifications, i.e.
  572. NetEventReconfigure events passed to the MUX�s PnPEventHandler, <i>PtPNPHandler</i>.
  573. This driver takes a broad approach to handling reconfiguration, which is to
  574. simply re-examine all the �UpperBindings� keys for all currently bound
  575. adapters, and start off VELANs for any that do not exist � see <i>PtBootStrapVElans</i>
  576. for details.<o:p></o:p></span></p>
  578. <p style='tab-stops:45.8pt 91.6pt 137.4pt 183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt 641.2pt 687.0pt 732.8pt'><b><span
  579. style='font-size:10.0pt;font-family:Verdana'>NDIS 5.1 Features</span></b><span
  580. style='font-size:10.0pt;font-family:Verdana'><o:p></o:p></span></p>
  582. <p style='tab-stops:45.8pt 91.6pt 137.4pt 183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt 641.2pt 687.0pt 732.8pt'><span
  583. style='font-size:10.0pt;font-family:Verdana'>The NDIS 5.1 features in MUX are
  584. identified by #ifdef NDIS51 compiler directives. The following feature is
  585. illustrated (refer to the DDK documentation for more information on these):<o:p></o:p></span></p>
  587. <p style='tab-stops:45.8pt 91.6pt 137.4pt 183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt 641.2pt 687.0pt 732.8pt'><b><span
  588. style='font-size:10.0pt;font-family:Verdana'>Canceling Sends</span></b><span
  589. style='font-size:10.0pt;font-family:Verdana'>: MUX propagates send
  590. cancellations from protocols above it to lower miniports.<o:p></o:p></span></p>
  592. <p style='tab-stops:45.8pt 91.6pt 137.4pt 183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt 641.2pt 687.0pt 732.8pt'><span
  593. style='font-size:10.0pt;font-family:Verdana'><span
  594. style='mso-spacerun:yes'>�</span><o:p></o:p></span></p>
  596. <p align=center style='text-align:center;tab-stops:45.8pt 91.6pt 137.4pt 183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt 641.2pt 687.0pt 732.8pt'><a
  597. href="#top"><span style='font-size:10.0pt;font-family:Verdana'>Top of page</span></a><span
  598. style='font-size:10.0pt;font-family:Verdana'> <o:p></o:p></span></p>
  600. <table class=MsoNormalTable border=0 cellspacing=0 cellpadding=0 width=624
  601. style='width:6.5in;mso-cellspacing:0in;mso-padding-alt:0in 0in 0in 0in'>
  602. <tr style='mso-yfti-irow:0;mso-yfti-lastrow:yes;height:1.5pt'>
  603. <td style='background:aqua;padding:.75pt .75pt .75pt .75pt;height:1.5pt'>
  604. <p class=MsoNormal><o:p>&nbsp;</o:p></p>
  605. </td>
  606. </tr>
  607. </table>
  609. <p style='tab-stops:45.8pt 91.6pt 137.4pt 183.2pt 229.0pt 274.8pt 320.6pt 366.4pt 412.2pt 458.0pt 503.8pt 549.6pt 595.4pt 641.2pt 687.0pt 732.8pt'><span
  610. style='font-size:7.5pt;font-family:"MS Sans Serif"'>� 1999 Microsoft
  611. Corporation</span><span style='font-size:10.0pt;font-family:Verdana'> <o:p></o:p></span></p>
  613. </div>
  615. </body>
  617. </html>