Article ID: 263324 - View products that this article applies to.
This article was previously published under Q263324
When you create shortcuts and specify a long file name in the target path, the path is truncated if the hard disk for the target does not exist. For example, create a shortcut with the following target:
If drive J does not exist, the path is truncated to:
This problem can occur because the shell cannot determine whether the hard disk supports long file names, so the path is truncated to be acceptable to all file systems.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.
This problem may be observed when you use any of the following methods to create shortcuts:
The SMS Installer Create Shortcut Method
An extract from an SMS Installer .ipf file that demonstrates the problem:
If you compile a script with this extract and you run it after you have ensured that drive X does not exist, you can observe that the shortcut is created, but the target path is truncated to:
item: Create Shortcut Source English=X:\Pw32\Alongdirectory\Blongdirectory\Longfilename.exe Destination English=C:\Winnt\Shortcut123.lnk Key Type English=1536 Flags=00000001 end
If you connect drive X to a share or use a subst command to point to a local drive and you run the script again, the shortcut is created with the correct target path:
This problem is not caused by the SMS Installer. This problem occurs because the SMS Installer uses the IShellLink interface (refer to "The IShellLink Interface Method") to create shortcuts. The SMS Installer passes the full correct path name to the IShellLink interface, but the path is truncated when the IShellLink::SetPath operation is performed.
The VBScript Create Shortcut methodA sample VBScript that demonstrates the problem:
When you run this script and drive J does not exist, you can observe the created shortcut, but the target path is:
NOTE: Any characters that are not normally supported by file systems that do not want long file names, such as the space character, are replaced by the underscore symbol "_".
To work around this problem, you can use the subst command to point drive J to a local hard disk:
This command points drive J to drive C. If drive C supports long file names, the command creates a shortcut with the following target path:
J:\My long directory\Myapplication.exe
You can also use WshNetwork.MapNetworkDrive to connect drive J to a known share, create the shortcut as outlined in the preceding steps, and then remove drive J by using WshNetwork.RemoveNetworkDrive.
The IShellLink Interface MethodAn extract of code that demonstrates the problem by using the IShellLink interface in Microsoft Visual C++:
You must use IPersistFile::Save to write the shortcut to disk. This action results in a target path of:
This problem occurs on all versions of Windows NT 4.0 and Windows 2000.
Article ID: 263324 - Last Review: October 31, 2006 - Revision: 3.3