Long file name issue?

[xewill0155]

Hi,
We're moving application data from a NW 4.2 volume to a new location on a clustered 6sp5 nss volume. In the same tree
We've discovered the that application will not run. If we rename the folder from a 9 charector name to an 8 charactor name and rejig the desktop shortcut, it works !
We thought that lfn support was better on our shiney cluster, hevae we missed something?
Thanks for reading, opinions or suggestions about where to look for answers welcomed

 

[TheLad]

The desktop shortcut will have to contain the full pathname in quotes in order to get the "long" filename to work. This has nothing to do with NetWare, this is a desktop issue. This is the same for any long filenames on server or desktop. Eg: your MS Word shortcut would be something like:

"C:\Program Files\Microsoft Office\Office\WORD.EXE"

And on the same lines, change your shorucut to include the path in quotes and it should work ok.

-----------------------------------------------------
"It's true, its damn true!"
-----------------------------------------------------

 

[xewill0155]

thanks for that but maybe i should shed a bit mor light on the matter.
All we're doing is moving the application data from one place to another. The shortcut points at a drive mapped by the login script G:\folder\application.exe at startup which we have adjusted to point at the new location, however existing desktop shortcuts do not work. If we browse to the mapped drive , the folder name is correct as is the name of the executable. It just does not work unless we manually rename the folder from 9 chars to 8

Essentially the desktop should not know anything has changed. It would be a right pain to a new shortcut to all the users

Thanks for responding though

 

[terry712]

what do they get when they try the shortcut - ie what message

does the app support long file names - i must confess i still prefer to keep everything below this

how was the shortcut created originally - i've seen it before if it's a drag shot then underlying it has a unc

why dont you nal the shortcut and then this can clean the shortcut up as well