LNKs, wsh & OS compatibility?

[PiqueABoo]

I've got lots of .LNK files and a jscript running on XP using the standard wsh stuff (same as used in VBS) can happily read the TargetPath from them i.e. "c:\Program Files\SomeApp\some.exe".

 

Except when it can't

 

Early days and I'll have to make another teensy script to test this, but I think it breaks if the shortcut was created on 2008 (and it's over twice the size in bytes of a similar one created on XP).

 

Does anyone know anything about this?

[PiqueABoo]

By-and- by:

 

a) Map X: to a share, create a shortcut to something on X: and you get a LNK file that doesn't work with the WShell shortcut functions.

 

b) On the server SUBST X: to the shared folder, create a shortcut to the same something on X: and you get a smaller LNK file that does work with the WShell shortcut functions.

 

Both shortcuts work from anywhere when drive X: is mapped to the right place.

[Arthur]

Have you tried a shortcut that uses a UNC path?

[PiqueABoo]

Have you tried a shortcut that uses a UNC path?

 

No, but I'd like them to be portable so haven't been tempted to try that. Still a bit curious over the second format and why wshell doesn't grok them, and wondering if the 5.8 script host you get with IE8 is any different, but as long as I've got that one method to make LNKs that wshell understands then I'm happy.