Is anyone aware of any compatibility issues for Windows Shortcuts
created by a Windows 2003 Server application when accessed by Windows
NT4 or Windows 2000 clients? For example, the Windows 2003 Server
application creates a Windows shortcut on Windows 2000 volume
\source\share1\directory1\file.txt.lnk
<file:> that points to a
target \target\share2\directory<kanji_filename>.txt
<file:> (and
Kanji_filename contains double byte Kanji characters). If a user uses
Windows Explorer on Windows 2000 to view the target path of
\source\shar1\directory1\file.txt.lnk
<file:> , the target path looks
corrupted.
Does this has anything to do with Distributed Link Tracking? Also,
what character encoding is used to store the target file path of a
Windows Shortcut?
Thanks
Albert</file:></file:></kanji_filename></file:>