Network Setup with Customized SETUP.INF Doesn't Work

 Last reviewed: November 21, 1994
Article ID: Q115925
The information in this article applies to:
  • Microsoft Windows operating system versions 3.1, 3.11
  • Microsoft Windows for Workgroups versions 3.1, 3.11

SYMPTOMS

When you try to install Microsoft Windows or Microsoft Windows for Workgroups version 3.1 or later with a customized network installation, you receive the following error message: 

   Windows Setup

   Cannot find the SETUP.INF file necessary to run Setup.
   Be sure that the file is in a directory of the default path.
For example, using the following command could generate the above error message 

   setup /n /o:example.inf
where /o: is pointing to a customized SETUP.INF file (in this case, EXAMPLE.INF).

Also, no customized files specified to be copied in the [win.copy] section (or similar sections) are actually copied, and no new Program Manager groups are created.

CAUSE

This error occurs because the character-mode portion of the Windows Setup program uses the customized name for the SETUP.INF file, but the graphical portion of Setup expects to find the actual SETUP.INF filename.

WORKAROUND

To avoid this error, you must not use the /O switch when you use the /N option. If you need customized setup files, make a backup copy of SETUP.INF, then copy your customized .INF (EXAMPLE.INF in the example above) over SETUP.INF and run SETUP /N.

KBCategory: kbnetwork kbsetup
KBSubcategory: win31 wfw wfwg
Additional reference words: 3.11 3.1 3.10

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: November 21, 1994
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.