DOCERR: File Manager Doesn't Associate PWB Makefiles

 Last reviewed: July 17, 1997
Article ID: Q87514
7.00 | 7.00 MS-DOS | WINDOWS kbtool kbdocerr

The information in this article applies to:

  • Microsoft C/C++ for MS-DOS and Windows, version 7.0

SYMPTOMS

Page 67 of C/C++ version 7.0 "Environment and Tools" manual suggests associating a .MAK file with Programmer's WorkBench (PWB) using the File Manager. This will not work as described under Microsoft Windows 3.1; however, it will work as described under Windows 3.0. When a .MAK file is associated with PWB using the command line 

   pwb.pif /PP
with the association feature of the Windows 3.1 File Manager, an error occurs. The error says that the association is not an executable and cannot be used.

CAUSE

Windows 3.1 will not allow parameters to be specified for the command to be executed on an association. Windows 3.0 does allow this syntax.

RESOLUTION

A possible workaround is to create a batch file to be associated with the .MAK files. For example: 

   if "%1" == "" goto label
   call pwb.exe /PP %1
   goto end
   :label
   call pwb.exe
   :end
With the Windows PIF Editor, change the program filename for PWB.PIF from PWB.EXE to the name of the batch file created (for example, PWB.BAT). This will simulate the preferred response.

Additional reference words: 7.00
KBCategory: kbtool kbdocerr
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.