Connecting to mapped network drive after Windows has booted

[nas8e9]

I'm currently running V9.2, and while very happy with the tool, do regularly find that XY doesn't cope aswell as windas explorer when it comes to navigating around mapped network drieves, especially when connectivity to those drives is flakey.

Has anything changed in this area since V9.2? I couldn't see anything in the changelogs.

There have been improvements for when network shares are unavailable:

Code: Select all

    v9.90.0801 - 2011-04-16 12:55
        % Network browsing: Before, you would get long delays when browsing
          a folder with LNK files pointing to unavailable network locations,
          as well as when selecting such a file. These delays should be gone
          now.

and

Code: Select all

    v9.90.0807 - 2011-04-29 13:08
        ! Mini Tree: Did not respect the setting of "Configuration | Advanced
          | Use generic icons for super-fast browsing", and thus would
          generate long delays when unavailable network paths were featured
          in the Mini Tree. Fixed.

eg. just like XY is leaping ahead in functionality for more logical file management (filters, colours, etc..) I'd love to see it gain some more mapped drive diagnostics and troubleshooting features... like... to recognise when a drive is no longer available, and if nothing else, pop up an icon indicating thus, and then not freeze (as windas explorer also does). I know this is trying to dance around inadequacies of Windows own inadequacies, but I still imagine there being potential for improvement.

I don't remember this having been discussed or implemented. I suspect the problem here is that XYplorer can't use a separate thread for the (attempted) network browsing, thus blocking the main thread. For technical reasons, this can't currently be worked around.

[sTu_Deimus]

Cool, thanks for the detailed info