The information in this article applies to:
SYMPTOMSWhen you call out CreateProcess on Cmd.exe, for example: CreateProcess(NULL, "cmd /c copy file1 file2", ....),and the current directory has been set to a universal naming convention (UNC), Cmd.exe returns the following message:
CAUSE
Cmd.exe checks to verify if a UNC name is used for the current directory.
It does this because a UNC name may cause problems with child processes
launched from such a console when that console is exited or halted.
Microsoft Windows NT versions prior to 4.0 did not check this; thus it was
possible to use a UNC name as a current directory.
RESOLUTION
Obtain the updated Cmd.exe. You must also make a registry entry to be able
to use a UNC path as the current directory.
add the value DisableUNCCheck REG_DWORD and set the value to 0 x 1 (Hex). WARNING: If you enable this feature and start a Console that has a current directory of an UNC name, start applications from that Console, and then close the Console, it could cause problems in the applications started from that Console. STATUSMicrosoft has confirmed this to be a problem in Windows NT version 4.0. This problem was corrected in the latest Microsoft Windows NT 4.0 U.S. Service Pack. For information on obtaining the service pack, query on the following word in the Microsoft Knowledge Base (without the spaces): S E R V P A C K Additional query words: prodnt
Keywords : kbnetwork kbbug4.00 kbfix4.00.sp2 nt32ap NTSrvWkst |
Last Reviewed: January 22, 1999 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |