Control Panel/Setup Does Not Recognize OEMSETNT.INF

 Last reviewed: August 22, 1995
Article ID: Q129820
The information in this article applies to:
  • Microsoft Windows NT operating system version 3.1
  • Microsoft Windows NT Advanced Server version 3.1
  • Microsoft Windows NT Workstation version 3.5
  • Microsoft Windows NT Server version 3.5

SYMPTOMS

The Windows NT Device Driver Kit (DDK) states that OEMSETNT.INF is a valid name for a Windows NT OEMSETUP file. However, if you update a network component using Control Panel, Windows NT Setup does not look for OEMSETNT.INF and results in the following error: 

   Error is: "INF file a:\oemsetup.inf does not exist"
OEMSETNT.INF is recognized by Setup only during original installation.

WORKAROUND

To work around this problem, rename OEMSETNT.INF to OEMSETUP.INF.

STATUS

Microsoft has confirmed this to be a problem in Windows NT versions 3.1 and 3.5. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.

KBCategory: kbsetup kbbug3.10 kbbug3.50
KBSubcategory: ntsetup
Additional reference words: 3.10 3.50 prodnt ncpa

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: August 22, 1995
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.