PRB: STARTUP.BAT Gives U1073: Don't Know How to Make STDIO.H

 Last reviewed: July 17, 1997
Article ID: Q67161
6.00 6.00a 6.00ax 7.00 | 6.00 6.00a | 1.00 1.50 1.51 
MS-DOS                 | OS/2       | WINDOWS
kbtool kberrmsg

The information in this article applies to:

  • Microsoft C for MS-DOS, versions 6.0, 6.0a, and 6.0ax
  • Microsoft C for OS/2, versions 6.0 and 6.0a
  • Microsoft C/C++ version 7.0
  • Microsoft Visual C++ for Windows, versions 1.0, 1.5, and 1.51

SYMPTOMS

When running the batch file STARTUP.BAT that comes with C versions 6.0, 6.0a, and 6.0ax or the CSTARTUP.BAT that comes with C/C++ version 7.0 and Visual C++ for Windows, you may receive the following error: 

   U1073: don't know how to make 'stdio.h'.

CAUSE

This is actually an NMAKE error and may be the result of having more than one search path for the INCLUDE environment variable, as shown in the following example: 

   include=c:\c600\include;c:\masm\include
Because batch files cannot parse out separate paths for environment variables, it is necessary to have only one INCLUDE path specified. This allows the filename to be included to be appended to the end of that path.

RESOLUTION

To correct the problem, only one search path should be used, as in the following example: 

   include=c:\c600\include

Additional reference words: 6.00 6.00a 6.00ax 7.00 8.00 9.00 1.00 1.50
KBCategory: kbtool kberrmsg
KBSubcategory: NmakeIss
Keywords : kb16bitonly

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: July 17, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.