Microsoft KB Archive/165672

= Batch File Containing UNC Connection Fails When Run from PIF =

Article ID: 165672

Article Last Modified on 11/1/2006

-

APPLIES TO


 * Microsoft Windows NT Server 3.5
 * Microsoft Windows NT Server 3.51
 * Microsoft Windows NT Server 4.0 Standard Edition
 * Microsoft Windows NT Workstation 3.5
 * Microsoft Windows NT Workstation 3.51
 * Microsoft Windows NT Workstation 4.0 Developer Edition

-



This article was previously published under Q165672



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 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: kbnetwork KB165672

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.