Batch File Containing UNC Connection Fails When Run from PIF

 Last reviewed: June 13, 1997
Article ID: Q165672
The information in this article applies to:
  • Microsoft Windows NT Server versions 3.5, 3.51, and 4.0
  • Microsoft Windows NT Workstation versions 3.5, 3.51, and 4.0

SYMPTOMS

If you try to call a batch file from a .pif file containing a UNC path, you may receive "File not found," "Path not found," or other various error messages. If the batch file is run from a command prompt, it completes as expected.

RESOLUTION

Do not call the batch file from a .pif file. If this is not an option, use a mapped drive letter instead of a UNC path. There is currently no known workaround if a mapped drive letter cannot be used (for example, when you copy <what> to a shared printer).

STATUS

Microsoft has confirmed this to be a problem in Windows NT versions 3.5x and 4.0. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.

Keywords : kbbug3.50 kbbug3.51 kbbug4.00 kbnetwork nt16ap NTSrvWkst
Version : 3.5 3.51 4.0
Platform : WinNT

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