Article ID: 105250
Article Last Modified on 11/1/2006
APPLIES TO
- Microsoft Windows NT Advanced Server 3.1
- Microsoft Windows NT Workstation 3.1
- Microsoft Windows NT Advanced Server 3.1
- Microsoft Windows NT Workstation 3.5
- Microsoft Windows NT Workstation 3.51
- Microsoft Windows NT Workstation 4.0 Developer Edition
- Microsoft Windows NT Server 3.5
- Microsoft Windows NT Server 3.51
- Microsoft Windows NT Server 4.0 Standard Edition
This article was previously published under Q105250
SYMPTOMS
In Windows NT, you cannot specify a UNC (universal naming convention) pathname for the working directory of an icon for a 16-bit application. If you set a UNC pathname as a working directory, you will not receive an error message indicating that the working directory is invalid, but the directory specified will not be the working directory.
WORKAROUND
To work around this limitation, use the NT 3.x File Manager or NT 4.0 Network Neighborhood icon to make a full connection to the desired share and specify that drive as the working directory.
MORE INFORMATION
Steps to Reproduce Problem
- Using NT 3.x File Manager or NT 4.0 Explorer, share a directory either on the local computer or a remote computer.
- In NT 3.x Program Manager, create an icon with the following properties:
Command Line: WRITE.EXE Working Directory: \\computername\sharename
- or -
- On the NT 4.0 desktop, create a shortcut with the following properties:
Target: %WINDIR%\WINHELP.EXE Start in: \\computername\sharename
- Start the application using the new icon and choose Open from the File menu.
In the Directories list of the Open dialog box, you will not see the path to the working directory specified in the Program Item Properties using the UNC pathname, even though you did not receive any error messages.
Additional query words: prodnt 3.x 3.5x 16bit
Keywords: kbnetwork KB105250
