PRB: Cannot Build in PWB with SHARE.EXE and OutputTo=NUL

 Last reviewed: July 17, 1997
Article ID: Q88508
7.00 | 7.00 MS-DOS | WINDOWS kbtool kberrmsg kbbuglist kbprb

The information in this article applies to:

  • Microsoft Programmer's WorkBench for MS-DOS, version 2.0

SYMPTOMS

Microsoft Programmer's WorkBench (PWB) version 2.0 supplied with Microsoft C/C++ version 7.0 may generate the following error messages when building a project: 

   NUL - Permission Denied

   cannot compile
These errors will appear in PWB message boxes.

CAUSE

The following conditions will cause PWB to display the messages:

  • SHARE.EXE has been executed.
  • "OutputTo=NUL" has been added to the SYSTEM.INI file under the [Debug] section.
  • An application is being built in PWB.

PWB is using the NUL device that is already in use by Windows. You can see similar behavior simply by typing "ECHO > NUL" at an MS-DOS command prompt with SHARE.EXE loaded and "OutputTo=NUL" set.

RESOLUTION

To work around this problem, do one of the following:

  • Remove SHARE.EXE.

    -or-

  • Remove the "OutputTo=NUL" statement and only insert this when running the Windows debug kernel. You can append a couple statements to N2D.BAT and D2N.BAT to change SYSTEM.INI files; one with the [Debug] section and one without.

    -or-

  • Build the project outside of PWB.

Additional reference words: 2.00 7.00 buglist7.00
KBCategory: kbtool kberrmsg kbbuglist kbprb
KBSubcategory: PwbIss
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.