KnowledgeBase Archive

An Archive of Early Microsoft KnowledgeBase Articles

View on GitHub

Q37023: Link Error No Stack Segment after Using Windows SDK Install

Article: Q37023
Product(s): See article
Version(s): 5.00 5.10
Operating System(s): MS-DOS
Keyword(s): ENDUSER | | mspl13_c
Last Modified: 12-DEC-1988

If a C program generates linker errors stating that no stack segment
exists and that there are several unresolved externals references made
by the startup code, the program may have been linked with libraries
modified by the Windows SDK Install program.

The Windows install program modifies C libraries, upon your request,
so that when linking Window applications it can look for the standard
library names with no other linker options specified. A more detailed
explanation can be found in the README.WRI on the Development
Utilities Disk 1 that comes with Windows SDK Version 2.00.

The install program retains the original C library. The library will
have its same name with a "C" appended. For instance, SLIBCE.LIB will
be copied to SLIBCEC.LIB. When you link with this library, make sure
to use the /NOD option and specify the library by name.

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.