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/tdi/sample/tdiclient.htm

181 lines
8.5 KiB
Raw Permalink Normal View History

commiting as it is
4 years ago
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
  1. <html>
  3. <head>
  4. <meta http-equiv="Content-Language" content="en-us">
  5. <meta name="GENERATOR" content="Microsoft FrontPage 5.0">
  6. <meta name="ProgId" content="FrontPage.Editor.Document">
  7. <meta http-equiv="Content-Type" content="text/html; charset=windows-1252">
  8. <title>TdiClientSample</title>
  9. </head>
  11. <body>
  13. <h2>TDISAMPLE.SYS -- Sample Tdi Client Driver</h2>
  14. <p></p>
  15. <h3>SUMMARY</h3>
  16. <p></p>
  17. <h4>Sample Tdi Client Driver</h4>
  18. <p>
  19. The TdiClient sample is a simple driver that demonstrates many of the
  20. the basic principles involved in a Tdi Client. It is written to work with a variety
  21. of Tdi providers in order to more completely demonstrate how the Tdi interface is used.
  22. <br><br>
  23. The sample is composed of the Tdisample.sys driver, which is the actual Tdi client, and
  24. a simple user application, Tdisamp.exe, which communicates through this driver. The user
  25. application is itself divided into two parts--a library, which knows how to talk to Tdisample.sys,
  26. and the actual program, which uses these library functions to communicate between two machines.
  27. </p>
  29. <h3>BUILDING THE SAMPLE</h3>
  30. <p>
  31. Run the <b>build</b> command from this directory to build the sample�it creates the
  32. binaries Tdisample.sys and Tdisamp.exe.
  33. <br><br>
  34. To install this driver on Windows� 2000, use the INF also found in this directory.<br>
  35. </p>
  37. <h3>INSTALLING THE SAMPLE</h3>
  38. <p>
  39. Tdisample is installed as a service (called �Tdisample Driver� in the supplied
  40. INFs/notification object). To install, follow the steps below.
  41. <br><br>
  42. Prepare a floppy disk (or installation directory) that contains these files:
  43. nettdic.inf, Tdisample.sys and Tdisamp.exe.
  44. <br><br>
  45. On the desktop, right-click the <b>My Network Places</b> icon and choose <b>Properties</b>.
  46. <br><br>
  47. Right-click on any Local Area Connection icon and choose <b>Properties</b>.
  48. <br><br>
  49. Click <b>Install</b>, then <b>Service</b>, then <b>Add</b>, then <b>Have Disk</b>.
  50. <br><br>
  51. Browse to the drive/directory containing the files listed above. Click <b>OK</b>. This
  52. should show �Tdisample Driver� in a list of Network Services. Highlight this and
  53. click <b>OK</b>. This should install the Tdisample driver.
  54. <br><br>
  55. Click <b>OK</b> or <b>Yes</b> each time the system prompts with a warning regarding
  56. installation of unsigned files. This is necessary because binaries generated via
  57. the DDK build environment are not signed.
  58. </p>
  60. <h3>RUNNING THE SAMPLE</h3>
  61. <p>
  62. The sample is designed to be run between two machines, one running as the <i>server</i> and the
  63. other running as the <i>client</i>. In addition, it can be run over several different Tdi providers
  64. (ie, protocols). The server should always be started first, then the client. The two machines must
  65. be on the same network--preferable on the same network segment--in order for the test to run. Also,
  66. they must both be running over the same protocol. The examples below show the various ways in
  67. which the tests can be run.
  68. <br><br>
  69. Running test over ipx:<br>
  70. tdisamp /server /ipx<br>
  71. tdisamp /ipx
  72. <br><br>
  73. Running test over tcpip (ipv4)<br>
  74. tdisamp /server /ipv4<br>
  75. tdisamp /ipv4
  76. <br><br>
  77. Running test over Netbios<br>
  78. tdisamp /server /netbt<br>
  79. tdisamp /netbt
  80. </p>
  83. <h3>CODE TOUR</h3>
  84. <h4>File Manifest</h4>
  85. <pre><u>File Description</u>
  86. <br>
  87. dirs causes lib, sys, and tdisamp directories to be built
  88. tdiclient.htm this help file
  89. nettdic.inf installation file
  90. inc\glbconst.h constants shared between library and driver
  91. inc\glbtypes.h structure types shared between library and driver
  92. inc\libbase.h constants and structures shared between library and application
  93. inc\libprocs.h library functions available to the application
  94. lib\makefile makefile for the library
  95. lib\sources file listing sources to be used in building the library
  96. lib\libvars.h defines private to the library
  97. lib\stdafx.h precompiled header for library
  98. lib\connect.cpp user mode apis for making and breaking connections
  99. lib\events.cpp user mode apis for enabling event handlers
  100. lib\misc.cpp user mode apis for miscellaneous operations
  101. lib\open.cpp user mode apis for opening and close control, address, and endpoint objects
  102. lib\receive.cpp user mode apis for receiving data
  103. lib\send.cpp user mode apis for sending data
  104. lib\stdafx.cpp for creating binary associated with precompiled header
  105. lib\tdilib.cpp user mode apis for starting and ending communication with driver
  106. lib\tdiquery.cpp user mode apis for querying tdi provider
  107. lib\utils.cpp library internal functions for communicating with the driver
  108. tdisamp\makefile makefile for user mode application
  109. tdisamp\sources file listing sources used in building the user mode application
  110. tdisamp\tdisamp.cpp actual source for user mode application
  111. sys\makefile makefile for driver
  112. sys\sources file listing sources used in building the driver
  113. sys\sysprocs.h prototypes for driver functions
  114. sys\sysvars.h driver-specific types and constants
  115. sys\buffer.cpp functions for doing posted receives
  116. sys\connect.cpp functions for establishing and breaking connections
  117. sys\events.cpp functions for enabling event handlers
  118. sys\open.cpp functions for opening and closing control, address, and endpoint objects
  119. sys\rcvdgram.cpp functions for receiving datagrams using event handlers
  120. sys\receive.cpp functions for receiving data over a connection using event handlers
  121. sys\recvcom.cpp common receive utilities
  122. sys\requests.cpp function dealing with device io requests
  123. sys\send.cpp functions for sending data or datagrams
  124. sys\tdipnp.cpp functions for dealing with pnp and power management events
  125. sys\tdiquery.cpp functions for dealing with tdi requests
  126. sys\tdisample.cpp functions dealing with driver initialization and unloading
  127. sys\utils.cpp some utility functions
  128. sys\tdisample.rc resources file for driver
  129. </pre>
  132. <h4>Programming Tour</h4>
  133. <p>
  134. The general layout of the source code is that the user application calls the functions provided by
  135. the library to do all the work. The library function packs up the arguments for the driver and calls
  136. TdiLibDeviceIO. This function is essentially a wrapper for the system's DeviceIoControl function,
  137. which calls the driver at its TSDispatch entry point. The execution is then routed to TSIssueRequest,
  138. which determines what driver function needs to be called to support the request. The appropriate
  139. function is then called. In most cases, the function called in the driver is in a file having the
  140. same name as the function originally called in the library.
  141. <br><br>
  142. Tdisample.sys is writen to be as independent as possible of which protocol is being used as the
  143. tdi provider. For this reason, opening devices as well as sending and receiving data is handled
  144. through the DeviceIoControl mechanism rather than through Open, Read, and Write. An actual Tdi client
  145. is more likely to use these rather than DeviceIoControl.
  146. <br><br>
  147. Since the more interesting part of this sample is the driver, the rest of this section will concentrate
  148. on what goes on there. Hopefully, the inline comments will be helpful in understanding what is
  149. going on throughout the code.
  150. <br><br>
  151. 1) During DriverEntry, the TdiSample driver registers itself with the system, informing it of its
  152. various entry points. It then registers itself with TDI by informing it of its pnp handlers
  153. (see sys\tdisample.cpp, function DriverEntry).
  154. Intermediate miniport driver.
  155. <br><br>
  156. 2) TDI next calls the TSPnpAddAddressCallback handler once for every address which has been
  157. registered with it. This function will store the name and address of each one received. Both the
  158. name and address are required, since NetBios opens devices on the basis of their name, while ipx
  159. and ipv4 open devices on the basis of their address.
  160. <br><br>
  161. 3) TDI also calls the TSPnpBindCallback handler once for each protocol. The sample does nothing
  162. with these calls except to output the call information to the debugger.
  163. <br><br>
  164. 4) <b>Memory Management</b> The driver uses a wrapper around the system memory management functions.
  165. This is useful during development and debugging to help track memory leaks and overwrites.
  166. 5) <b>Handling Power Management</b>
  167. <br><br>
  168. 5.1 During initialization, the TdiSample registers its power management handler
  169. with TDI.
  170. <br><br>
  171. 5.2 Power management messages are handled by the TSPnpPowerHandler function. Note that it does
  172. not do anything useful with these messages, but just outputs the messages to the debugger.
  173. <br><br>
  174. </p>
  176. <p>Top of page</p>
  177. <p>� 1999 Microsoft Corporation</p>
  180. </body>
  182. </html>