Windows NT 4.0 source code leak
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.

154 lines
4.8 KiB

4 years ago
  1. //
  2. // Values are 32 bit values layed out as follows:
  3. //
  4. // 3 3 2 2 2 2 2 2 2 2 2 2 1 1 1 1 1 1 1 1 1 1
  5. // 1 0 9 8 7 6 5 4 3 2 1 0 9 8 7 6 5 4 3 2 1 0 9 8 7 6 5 4 3 2 1 0
  6. // +---+-+-+-----------------------+-------------------------------+
  7. // |Sev|C|R| Facility | Code |
  8. // +---+-+-+-----------------------+-------------------------------+
  9. //
  10. // where
  11. //
  12. // Sev - is the severity code
  13. //
  14. // 00 - Success
  15. // 01 - Informational
  16. // 10 - Warning
  17. // 11 - Error
  18. //
  19. // C - is the Customer code flag
  20. //
  21. // R - is a reserved bit
  22. //
  23. // Facility - is the facility code
  24. //
  25. // Code - is the facility's status code
  26. //
  27. //
  28. // Define the facility codes
  29. //
  30. //
  31. // Define the severity codes
  32. //
  33. //
  34. // MessageId: NDIS_ERROR_CODE_OUT_OF_RESOURCE
  35. //
  36. // MessageText:
  37. //
  38. // Adapter %2 : Insufficient memory or system resources was available
  39. // for the netcard driver to initialize. (The last DWORD of the data section
  40. // below contains a detailed error code.)
  41. //
  42. #define NDIS_ERROR_CODE_OUT_OF_RESOURCE ((NDIS_ERROR_CODE)0xC0001389L)
  43. //
  44. // MessageId: NDIS_ERROR_CODE_HARDWARE_FAILURE
  45. //
  46. // MessageText:
  47. //
  48. // Adapter %2 : The adapter hardware failed to initialize. Please
  49. // check that the adapter card is properly inserted into its slot and that the
  50. // network cable is connected. If its is an ISA adapter check that the interrupt
  51. // number, DMA channel and IO location in the adapter configuration match the
  52. // settings on the adapter card. (The data section below includes a driver
  53. // specific error code of 0x07 and the last two DWORDS give a detailed error
  54. // code.)
  55. //
  56. #define NDIS_ERROR_CODE_HARDWARE_FAILURE ((NDIS_ERROR_CODE)0xC000138AL)
  57. //
  58. // MessageId: NDIS_ERROR_CODE_ADAPTER_NOT_FOUND
  59. //
  60. // MessageText:
  61. //
  62. // Adapter %2 : The netcard driver could not allocate sufficient memory
  63. // for transmit and recive buffers. The number of RX and TX slots and
  64. // the maximum frame size may have been reduced to reduce the amount
  65. // of memory required.
  66. //
  67. #define NDIS_ERROR_CODE_ADAPTER_NOT_FOUND ((NDIS_ERROR_CODE)0xC000138BL)
  68. //
  69. // MessageId: NDIS_ERROR_CODE_INTERRUPT_CONNECT
  70. //
  71. // MessageText:
  72. //
  73. // Adapter %2 : The netcard driver was not able to connect the
  74. // adapter card's interrupt. Please ensure that the adapter card is properly
  75. // inserted into its slot. If it is an ISA adapter then check that the
  76. // interrupt number specified in the adapter configuration matches that
  77. // set on the adapter card.
  78. //
  79. #define NDIS_ERROR_CODE_INTERRUPT_CONNECT ((NDIS_ERROR_CODE)0xC000138CL)
  80. //
  81. // MessageId: NDIS_ERROR_CODE_DRIVER_FAILURE
  82. //
  83. // MessageText:
  84. //
  85. // Adapter %2 : One of the paramters in the registry entry for this adapter
  86. // is invalid. If possible a default value will have been used.
  87. //
  88. #define NDIS_ERROR_CODE_DRIVER_FAILURE ((NDIS_ERROR_CODE)0xC000138DL)
  89. //
  90. // MessageId: NDIS_ERROR_CODE_UNSUPPORTED_CONFIGURATION
  91. //
  92. // MessageText:
  93. //
  94. // Adapter %2 : The maximum frame size setting in the registry is too
  95. // large. The driver has trimmed it down to the maximum allowable setting. (The
  96. // data section below includes a driver specific error code of 0xC, followed by
  97. // the actual maximum frame size used in the last DWORD. Replace the value in the
  98. // registry with this).
  99. //
  100. #define NDIS_ERROR_CODE_UNSUPPORTED_CONFIGURATION ((NDIS_ERROR_CODE)0xC0001391L)
  101. //
  102. // MessageId: NDIS_ERROR_CODE_INAVLID_VALUE_FROM_ADAPTER
  103. //
  104. // MessageText:
  105. //
  106. // Adapter %2 : The adapter could not be opened onto the ring. Please ensure
  107. // that the network cable is connected to the adapter and that the token
  108. // ring is fully connected. Also ensure that all the nodes on your ring
  109. // are set to the same speed and that all nodes have different addresses.
  110. //
  111. #define NDIS_ERROR_CODE_INAVLID_VALUE_FROM_ADAPTER ((NDIS_ERROR_CODE)0xC0001392L)
  112. //
  113. // MessageId: NDIS_ERROR_CODE_MISSING_CONFIGURATION_PARAMETER
  114. //
  115. // MessageText:
  116. //
  117. // Adapter %2 : An essential registry parameter is missing for this adapter.
  118. // For MCA and EISA adapters the registry must contain BusType and SlotNumber
  119. // parameters. For ISA adapters the registry must contain IoLocation,
  120. // InterruptNumber and DmaChannel parameters.
  121. //
  122. #define NDIS_ERROR_CODE_MISSING_CONFIGURATION_PARAMETER ((NDIS_ERROR_CODE)0xC0001393L)
  123. //
  124. // MessageId: NDIS_ERROR_CODE_INVALID_DOWNLOAD_FILE_ERROR
  125. //
  126. // MessageText:
  127. //
  128. // Adapter %2 : Either the file MDGMPORT.BIN is not present in the device drivers
  129. // directory, the file is of the wrong version or the file is corrupt.
  130. //
  131. #define NDIS_ERROR_CODE_INVALID_DOWNLOAD_FILE_ERROR ((NDIS_ERROR_CODE)0xC000139CL)
  132. //
  133. // MessageId: NDIS_ERROR_CODE_MEMORY_CONFLICT
  134. //
  135. // MessageText:
  136. //
  137. // Adapter %2 : Either MMIO memory was not assigned or could not be mapped into
  138. // virtual memory. PIO transfer method is being used instead of MMIO.
  139. //
  140. #define NDIS_ERROR_CODE_MEMORY_CONFLICT ((NDIS_ERROR_CODE)0x80001399L)