Filename too long bypassed by copying folder on a Mac

[X-13]

Here's a weird one for you.

 

We have a group of users who need access to some files, however the total file path [inc. filename] exceeds 250+ characters [one I tested was 251, others are a lot longer]

 

They're understandably getting hit with a "filename too long" error when they try to do anything with the files.

 

 

Here's the strange part... If someone copies the folders on to a Mac, then copies them back as "[foldername]-Copy" the files can be opened and used, even though the path is now even longer.

 

Anybody have any clues? Because as far as I can see, that's dark magic.

[hallb15]

Because its Apple, and Apple just works!

[Bedders]

Hmmm.... I know that you can delete or rename files on Windows using Command Prompt where the path or filename is too long, but why it would work when moved between file systems I have no idea...

What are the disk formats (e.g. FAT32)? Doubt it's related but it's a start.

[pete]

Click in the address bar of explorer so it displays the *actual* path. I suspect Win 7 is using the shortnames (abcdef~1) in the path.

 

That's what my Win10 VM is doing when I test the above. As soon as it used the shortname, it'll let you go deeper down the path in Windows too.

 

If you went ~28-30 levels deep, it should break again if that's the case.

[X-13]

Click in the address bar of explorer so it displays the *actual* path. I suspect Win 7 is using the shortnames (abcdef~1) in the path.

I've checked that. The full path is >250 characters.