BUG: Linking P-Code with /w Option Gives L4000 Warnings

Last reviewed: July 17, 1997
Article ID: Q83940
7.00 | 1.00 MS-DOS | WINDOWS kbtool kbbuglist

The information in this article applies to:

   The Linker (LINK.EXE), included with:
    - Microsoft C/C++ for MS-DOS, version 7.0
    - Microsoft Visual C++ for Windows, versions 1.0

SYMPTOMS

Linking a p-code application with the /w option causes more than 500 warnings if the application was built with Microsoft C/C++ version 7.0 and Visual C++ version 1.0. The warnings are of the form:

   <lib>(wcore.asm): warning L4000: segment displacement included
      near <offset> in segment (null)
   frame segment $$PCD_INTERP, target segment $$PCD_INTERP,
      frame segment 42c

   -or-

   <lib>(wcore.asm): warning L4000: segment displacement included
      near <offset> in segment (null)
   target external '__pcdi_snMac'

CAUSE

The warnings may be caused by an incorrect ASSUME directive in the p- code interpreter source (segment instead of group).

RESOLUTION

After running the Make P-Code utility (MPC) on the resulting executable, it runs without error.

STATUS

Microsoft has confirmed this to be a bug in the Microsoft products listed at the beginning of this article. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.


Additional reference words: 7.00 1.00 pcode plus
KBCategory: kbtool kbbuglist
KBSubcategory: LinkIss
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.