Source code of Windows XP (NT5)
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.

141 lines
6.5 KiB

  1. Release Notes for the WBEM DMI Provider beta Release .. 4/15/98
  2. ----------------------------------------------------------------
  3. This file contains information about the above product in the following sections:
  4. A. Release Contents
  5. B. Target Environments
  6. C. Known Issues
  7. D. Operating Instructions
  8. E. Technical Support information
  9. A. Release Contents
  10. -------------------
  11. This package consists of the following files :
  12. 1. The WBEM DMI Provider - WbemDmiP.dll
  13. 2. An OLE interface to the service provider - MOTDmiEngine.OCX
  14. 3. Client Front End of the service provider consisting of files
  15. WCDMI.DLL, WCDMIDCE.DLL, WDMIUTIL.DLL
  16. 4. A MOF file to register the provider with CIMOM - WbemDmiP.mof
  17. 5. A sample application showing how to use the DMI provider to access the DMI data via CIMOM.
  18. The sample application files are in the \DMITEST subdirectory. The directory contains the files
  19. dmitest.cpp, dmitest.h, datatypes.cpp, datatypes.h, defines.h, dmitest.dsp, dmitest.scr, dmitest.dsw,
  20. dmitest.exe, dbtypes1.mif, tempcom1.mif, tempgrp1.mif, dbtype1g.mif.
  21. 6. An example MOF file to be used as a template for describing new machines on a network - Newnode.mof
  22. 7. A Release Notes text file - RelNotes.txt (the currently open file)
  23. B. Target Environments
  24. ----------------------
  25. Windows* NT 4.0 Service Pack 3 and above
  26. Windows* 95 OSR2 with DCOM and above
  27. Windows* 95 with DCOM
  28. C. Known Issues
  29. ----------------
  30. 1 Add Row with duplicate key gives 'success' message.
  31. The row is actually not added to the database.The message
  32. is misleading and can be ignored.
  33. 2 Stopping/Restarting DMI SP (Service Provider) stops the WbemdmiP
  34. operation. While running Wbemdmip, if the service provider is
  35. stopped and restarted, the provider returns the WBEM_E_FAILED message.
  36. The workaround for this is to stop and restart CIMOM.
  37. 3 Modifying a ReadOnly attribute gives success message, when all
  38. the attributes in the row are also ReadOnly. The attribute is not
  39. modified but the message is misleading and can be ignored.
  40. 4 Unsupported attributes have no access qualifiers. The access qualifiers
  41. like 'ReadOnly','WriteOnly' and 'ReadWrite' of 'Unsupported' attributes
  42. are not displayed. This should not pose a problem as these attributes are
  43. Unsupported and would have no need of these operations.
  44. 5 Value of Unsupported attribute displayed as NULL. In the DMI Service
  45. Provider 2.0 the value field of Unsupported attributes contains the text
  46. "Unsupported". Due to interface constraints, the DMI provider cannot get this
  47. information. For consistency with CIMOM data display scheme, the provider
  48. will display 'NULL' for the value field of Unsuppoted attributes.
  49. 6 Modify Unsupported attribute gives 'success' message. The modify
  50. operation fails as it should but the message is misleading and can be ignored.
  51. 7 Invalid value set to date type attribute gives 'success' message
  52. (check with new SP 2.54)
  53. 8 As a general rule key attributes should not be modified. However, DMI permits
  54. modification of key attributes. In the WBEM DMI provider, if the key value is modified:
  55. a) to a value that already exists as a key in the database then that row is overwritten
  56. with the modified values, losing its existing data. The row under modification
  57. remains unchanged and can still be accessed.
  58. b) to a new value then a row add operation is done with the new key and the row under
  59. modification still retails its original values. The database now has an additional row.
  60. In effect, in both cases, the row under modification does not change its key value and
  61. can still be accessed.
  62. Workaround for b) Get the new key values as well the values of all attributes in the row
  63. under modification. Now, do a RowAdd operation with these values. Next do a DeleteRow
  64. operation on the (original)row whose key value you wished to modify. This will leave you
  65. with the new modified row.
  66. 9 Adding another row to a scalar group gives 'success' message.
  67. This is similar to #1, #3 and #6 above. The operation of row addition is not done but the
  68. message is misleading and can be ignored.
  69. 10 Value of Write-Only strings displayed as NULL. This is similar to
  70. #5 above. The value field in the DMI SP contains the text "Write
  71. Only" but in the WbemdmiP provider it is displayed as NULL in the
  72. value field.
  73. 11 Value of Unknown attribute displayed as NULL. This is same as #10
  74. 12 The 'Reserve' and 'Release' operations on an attribute as explained in the
  75. DMI spec v2.0 are not supported.
  76. 13. CIMOM applications won't be able to receive class creation and deletion events that
  77. correspond to DMI group addition and deletion notifications. This is because
  78. CIMOM does not support the above events. This Beta release of the DMI provider does not
  79. support extrinsic DMI events (events other than the standard DMI notifications).
  80. 14. The WBEM* Object Browser is incompatible with the DMI provider. If you try to view
  81. the DMI classes with the object browser, you may get an error. The WBEMTEST*
  82. application, however, works fine with the provider.
  83. 15. The Dmitest.exe sample application requires the sample MIF files be installed in the
  84. C:\TESTMIFS directory. Alternatively, you may edit the dmitest.scr file and change the
  85. location of the MIF files used in the script file to point to where the files exist on
  86. your system.
  87. D. Operating Instructions
  88. -------------------------
  89. For Windows '95, Windows '95 OSR2, you need to have DCOM installed before running the Wbemdmip
  90. provider.
  91. The Intel DMI 2.0 Service provider must be installed and running before starting
  92. Wbemdmip (ie. before starting CIMOM)
  93. E. Technical Support Information
  94. --------------------------------
  95. FAQs and Newsgroups are available from the home page for the product found in the Developer area of:
  96. World Wide Web site: http://www.intel.com/managedpc
  97. Email: developer_support.com
  98. Phone: (800) 628-8686
  99. The Desktop Management Task Force (DMTF) provides documents, files and support through their World Wide Web home page. As the Desktop Management Interface (DMI) technology grows and develops, announcements and updates are distributed through these points of contact:
  100. World Wide Web site: http://www.dmtf.org
  101. Internet FTP site: ftp.dmtf.org
  102. Free electronic copies of the DMI Specification and updated reference MIF files containing the latest revisions of DMTF-approved Standard Groups can also be obtained.
  103. This information was current and correct at the time this product was released.