XnView Software

Firstly, I apologise if this subject has been discussed already; I'm short on time at the moment and haven't had a chance to do much searching.

Anyhow, I noticed this two days ago, and again just now. I was using the file tree to navigate folders in which I wanted to batch-rename the contents. The result was a program crash notification by Vista. After a small investigation to make sure there was nothing wrong with the files themselves, I decided to rename the folder to something shorter (and with fewer underscores). Interestingly, that completely stopped the crashing.

The very same thing happened only moments ago (after updating to 1.97.4), and again I changed the folder name, and again the crashing was resolved. The folder in question's name was 59 characters, including spaces; the renamed folder has 32.

Obviously this is something I'll have to be mindful of for now, but is there a way you devs can fix this? I'd hate to have to guess which folders names are too long all the time, especially if I'm in the middle of file operations.

Thanks for your time.

Running under linux;wine;ext3, I can use up to about 255 characters in complete path (including parent folders).
The article below describes a limit when using windows:
http://msdn.microsoft.com/en-us/library ... px#maxpath

marsh wrote:Running under linux;wine;ext3, I can use up to about 255 characters in complete path (including parent folders).

Best I can do is shrug my shoulders at that. As I detailed above, the pattern was the same both times, with nothing changing except the renaming of the folders. Is XnView choking on the length of the path, then? It's odd to think it would if I have no problem with the files in other contexts.

linkish

Hello !

• I created a 61-character named folder here in Total commander as :

E:\aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa\

in which I copied an image file : No problem when opening it with XnView, View and Browser !

KR
Claude
Clo
XP-Pro SP2 (Fr)

Clo wrote: linkish

Hello !

• I created a 61-character named folder here in Total commander as :

E:\aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa\

in which I copied an image file : No problem when opening it with XnView, View and Browser !

KR
Claude
Clo
XP-Pro SP2 (Fr)

Fascinating. That sounds like a very loud folder. (Eaaaaaaaaaa!)

Obviously, you're not using the same system set-up as I am, so perhaps it's Vista-specific?

linkish wrote:

marsh wrote:Running under linux;wine;ext3, I can use up to about 255 characters in complete path (including parent folders).

Best I can do is shrug my shoulders at that. As I detailed above, the pattern was the same both times, with nothing changing except the renaming of the folders. Is XnView choking on the length of the path, then? It's odd to think it would if I have no problem with the files in other contexts.

Yes, the path length mattered for me. This other note mentions MSDOS limit of 260 bytes.

marsh wrote:

linkish wrote: Best I can do is shrug my shoulders at that. As I detailed above, the pattern was the same both times, with nothing changing except the renaming of the folders. Is XnView choking on the length of the path, then? It's odd to think it would if I have no problem with the files in other contexts.

Yes, the path length mattered for me. This other note mentions MSDOS limit of 260 bytes.

I'm confused. My HDD is NTFS; is there a reason a 260-byte limit would be a factor?

I suppose ultimately none of this matters much, really. It's not a massive inconvenience, and the conjecture doesn't seem to be accomplishing anything.

Though I do thank you all kindly for the assistance! Cheers.

I have recreated same failure with many applications. This suggests to me that MS is defficient.
The linux version views images buried about 4000 deep without problem.