I'm a long-term Salamander user (since V2).
I have found that Salamander will not permit me to open (double click file name) for certain files.
Demonstrated so far on Excels.
Maybe it's path length (this is a long path on a network) but same folder but longer name Word docs will open.
Not only open but any other file commands I've tried - such as copy (F5 or CTRL-C CTRL-V).
Copy the same file in Explorer to a shorter path it opens.
The concern is that Salamander is not giving me a message/reason.
I know it's not going to change but would appreciate an understanding of why some files fail (Excels) but others (Words) do not.
Win 11 Office 365.
Cheers,
Chipili
Not opening some files
Re: Not opening some files
It's going to be a fullpathlength of 260 characters.
(Or somewhere right around there. 259 is OK. Didn't have a 260 on hand... 261 fails.)
There could be other reasons too.
Like an "illegal" (perhaps unicode ?) [to Windows] character in a filename, in such cases will cause a no-action result in Salamander.
Maybe ? some of these newer Salamanders can work around said issues (unsure, as I'm still on Win7)?
(Or somewhere right around there. 259 is OK. Didn't have a 260 on hand... 261 fails.)
There could be other reasons too.
Like an "illegal" (perhaps unicode ?) [to Windows] character in a filename, in such cases will cause a no-action result in Salamander.
Maybe ? some of these newer Salamanders can work around said issues (unsure, as I'm still on Win7)?
WinXP Pro SP3 or Win7 x86 | SS 2.54
Re: Not opening some files
More like an Unicode issue. Did you try to rename the file with plain ascii?
Re: Not opening some files
Is there a question mark (or marks) in the filename? Salamander renders unicode characters as "?".
Re: Not opening some files
So, if it's an unicode issue, the issue is in some folder name within the path, not the name of the file itself.chipili wrote:Copy the same file in Explorer to a shorter path it opens.
You can check if it is a long path issue by shortening the path with subst (This works as long as the path is not excessively long, i.e. you can find a location for the new drive letter in a place withing 260 characters from the root of the original drive, leaving a path from the root of the substed drive no longer than 260 characters).