DOC: IOConfig Alias-offset Example Incorrect

Last reviewed: April 7, 1997
Article ID: Q163360
4.00 WINDOWS kbprg kbdocerr

The information in this article applies to:

  • Microsoft Win32 Device Development Kit (DDK) for Windows 95, version 4.0

SUMMARY

The Windows 95 DDK contains the following IOConfig alias-offset example:

    The following example shows the use of a Type 1 I/O range value in an
    IOConfig item. This specifies 16 IO port regions of 1 byte each, where
    each region starts at x2E8 where x is 0-Fh.
    IOConfig=2E8-2E8(FFFF:4:)

The example should be:

    IOConfig=2E8-2E8(FFFF:1000:)
    in order to reserve IO regions of x2E8, where x is 0-Fh.  Windows 95
    actually takes the high byte of the low word of the alias-offset
    parameter, and assumes that the low byte is zero. So, any alias-offset
    of 10xxh is treated as 1000h.

    When you try to add a new hardware device that requires a base address
    that is the same as an alias of another hardware device previously
    installed, Windows 95 reports a conflict.  However, when you run the
    Windows 95 Conflict Troubleshooter and use Device Manager to manually
    set the configuration for the conflicting device, no conflicts are
    reported.


KBCategory: kbprg kbdocerr
KBSubcategory:
Additional reference words: 4.00
Keywords : kbprg NTDDKKMode kbdocerr
Version : 4.0
Platform : 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.