DOC: HalSetBusData/HalSetBusDataByOffset Supports CMOS Bus

Last reviewed: April 7, 1997
Article ID: Q140267

3.51 WINDOWS NT kbprg kbdocerr kbdocfix

The information in this article applies to:

Microsoft Win32 Device Driver Kit (DDK), version 3.51

SUMMARY

The Windows NT DDK documentation incorrectly states that HalSetBusData and HalSetBusDataByOffset will only support "PCIConfiguration" for the bus data type. These HAL APIs will also support "Cmos" as the bus data type.

If "Cmos" is specified, the caller-supplied buffer contains the data to be written to CMOS (BusNumber equals zero) or ECMOS (BusNumber equals one) locations starting with the location specified by the SlotNumber.

Note that HalSetBusDataByOffset only works if the Offset parameter is zero.

This documentation error has been corrected in the Windows NT DDK version 4.0 documentation.

KBCategory: kbprg kbdocerr kbdocfix
KBSubcategory:
Additional reference words: 3.51 4.00 HAL kernel
Keywords : kbprg NTDDKKMode kbdocerr kbdocfix
Version : 3.51
Platform : NT WINDOWS

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: April 7, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.