6.1, still can't create long paths

[jimspoon]

I saw the headline "deep path improvements" in the readme for version 6.1, and thought maybe that I would finally be able in xplorer2 to create pathnames longer > 260 characters, as can be done with other programs (like Directory Opus). Still no go.

This path can be created in Directory Opus, and I think other programs as well, but not xplorer2:

C:\-----10--------20--------30--------40--------50\-------60--------70--------80--------90-------100\------110-------120-------130-------140-------150\------160-------170-------180-------190-------200\------210-------220-------230-------240-------250\------260-------270-------280-------290-------300

Not sure exactly what is the maximum path length that xplorer2 will create, but this one failed:



Of course I had followed Microsoft's instructions for enabling long path support -

https://learn.microsoft.com/en-us/windo ... limitation

[Kilmatead]

You now (apparently) need to also use:

Tools -> Advanced Options -> Global -> Miscellaneous -> Enable Deep Path Support

...and it will work. (I just tested it using your example-path.)

What's curious about this, is that in older versions this option would remain unchecked (and was unnecessary) if you already had long path support enabled in Windows. Now, apparently, you have to tick the box explicitly in x2 as well.

I don't recall this change (to needing the option checked) being mentioned (it's not in the changelog), but it appears to be true.

I do remember complaining once about how completely illogical it was, but I don't often win logic-arguments with nikos (he clings most stubbornly to his backwards and provincial way of looking at the world), so this surprises me.

(You'd never know he was raised as a sheep herder. He rebelled, ran away to the big city, and discovered that the price of prostitutes there was substantially higher than in his rural village, so he decided to get a real job, like this programming thing, which would enable him his luxuries. And also, most conveniently, make it possible for him to afford for those syphilis treatments as well. But we're not allowed to mention those for some reason. He's a sensitive soul, bless him.)

[nikos]

ha-ha-ha, such a comedian

the xplorer2 flag MUST be turned on
in the past you could only set the registry value LongPathsEnabled to enable them system-wide, but somewhere along the line the OS support wasn't there, so just keep the xplorer2 own advanced setting enabled

quite a few deep path glitches were fixed, please let me know if you find any more

[Kilmatead]

the xplorer2 flag MUST be turned on
in the past you could only set the registry value LongPathsEnabled to enable them system-wide, but somewhere along the line the OS support wasn't there, so just keep the xplorer2 own advanced setting enabled

A comedian with a long memory to combat you historically revisionist techno-plutocrats!

if your registry key LongPathsEnabled is enabled, then xplorer2 turns off its special handling

Somewhere in there you changed this, but never mentioned it to the great unwashed!

[nikos]

xplorer2 is no longer doing that because of the change in OS behavior

[Kilmatead]

Always blaming the other guy, eh? My point was that as probably all users would have already had that option rudely UN-TICKED by x2, you neglected to mention that now everyone has to go digging around to tick something they previously weren't even allowed to tick!

Were we just supposed to guess this?

See, this logic-thing again... it's so inconvenient...

[nikos]

you shouldn't be using long paths anyway, they are half broken because you cannot open most documents

[jimspoon]

Well, I checked that "Enable Deep Path Support" setting, and thought I would finally be able to cry out "Hallelujah", but when I tried to rename a folder and thereby exceed the old pathname length limit, I got this:



So my Hallelujah is still on hold.

[nikos]

even kilmatead managed to do it.... please double check your settings and that you are running v6.1

[jimspoon]

It's so strange that Microsoft gives us a registry edit to support paths up to 32767 characters but then does not support it in its shell (e.g. File Open / File Save dialogs), even after quite a few years. Funny thing - it seems that the ext4 filesystem supports path lengths up to 4096 characters. 4096 characters would be plenty for me. But sometimes I do want to create a path greater than 260 characters.

[jimspoon]

Confirmed, I'm running "6.1.0.0 ULT x64 02/08/25" - and I tried again to create the same long path - got the same error message.

Also confirmed I have Deep Path Support enabled:



Running Windows 11.

[nikos]

what is the format of this partition?
try going through the back door, browse the folder at the boundary, then copy/paste (or F5) into it a couple of folders (with subfolders) and see what happens

[nikos]

ok I managed to reproduce it myself, fix coming