LNK Files (Shortcuts) Opens Explorer

[admin]

OK, I'm going to have to push this back a little bit. Later...

[Display]

No worries, I'll use UNC links for now

[admin]

Is this still an issue?

[selukwe]

Is this still an issue?

For me it still is. XY Customized File Association for extension type .bms supposed to run a particular EXE still do not run. But v .0133 brought back to XY icons to shortcuts to folders. Prior to this version they did not show, they were just blank generic icons even though they still worked OK as shortcuts to folders. Now they show a standard yellow folder with a shortcut arrow.

[admin]

@selukwe: Stop spreading your case across different threads. What are you thinking?

[Display]

Is this still an issue?

For me, folder shortcut.lnks to a mapped network drive still do not open. Instead of "E:\Folder" it tries to open "VolumeLabel(E:\)Folder" and fails to resolve the address.
• Right-Clicking > 'Go To Shortcut Target' works correctly.
• Thumbnails on LNK folders show correctly.
• UNC paths work correctly.
• Symlinks work correctly.
• LNKs to files work correctly.
It's only double-clicking network mapped folder LNKs that fail.

This appears to be caused by setting the Windows 10 "Downloads" folder to the root of the mapped network drive, e.g. "E:\" - If I set the folder to anything else, e.g. "E:\Downloads", the folder shortcut.lnks work correctly and resolve in the address bar with no issues.

Since last time I've added more storage - I've just tried adding a new/different mapped network drive (Z:\) and the folder shortcut.lnks work fine to it!
I guess there's something 'special' about the "Downloads" shell folder when mapped to root that's causing XY to have issues resolving the addresses to that drive?

If this is a difficult bug to isolate I don't mind continuing to use the UNC workaround (It seems there's not really an issue for anyone else!)

[selukwe]

@selukwe: Stop spreading your case across different threads. What are you thinking?

Sorry, I thought this was about the same issue...

[admin]

Is this still an issue?

For me, folder shortcut.lnks to a mapped network drive still do not open. Instead of "E:\Folder" it tries to open "VolumeLabel(E:\)Folder" and fails to resolve the address.

I could repro sth very similar and fix it:

Code: Select all

    ! Special Folders: There could be a problem mapping real paths to their special path 
      counterparts if the special path root pointed to a drive root. This was ultimately 
      caused by Windows' bizarre habit of returning drive roots with a trailing backslash 
      and all other paths without. Fixed by working around this Windows quirk.

Hopefully this will fix your problem as well.

[Display]

Hopefully this will fix your problem as well.

Cool!
Just tried 24.90.0133 - and it didn't seem to change anything. So I tried loading the default configuration .ini and it DID work!
After comparing my configuration settings with defaults, it seems I need to enable this setting:

Code: Select all

PFAResolveLinksBeforeMatching=1

I'm not sure what it does, but when it's set to 0 it does the weird broken "VolumeLabel(E:\)Folder" resolving in the address bar.

So happy you got my folder .LNKs working again, thank you thank you

[admin]

Well, it should work with every setting. Unfortunately I could not reproduce (regardless of PFAResolveLinksBeforeMatching) what you see. There must be some other factor.

[admin]

Ah, I got it now. Should work in the next beta.

[Display]

Yaahs! It works perfectly now
Thanks again Don and have a great weekend!!