XYplorer Beta Club

this current problem is frustrating me so much I confess to the mortal sin of occasionally returning to Windows File Explorer - but only momentarily as I'm soon reminded why I bought XYplorer in the first place

This is exactly what happens to me. I'm almost afraid to refresh XY when any network or external drive pane is open because at least half the time it will hang up for 10sec - 2 min. I attribute this to my home LAN (with two 3TB NAS drives), possibly aggravated by having several large external USB drives connected at the same time. If I disconnect from the LAN and keep only the external drives the problem is much less frequent but still does occur. Both together are a killer.

Ironically, the biggest reason I value XY is because it helps so much in managing the giant file collections I have on these drives. I need the multiple tabbed panes, great search tools, color filtering, scripts etc etc. But this is also where XY has IMHO its greatest weakness.

There have been threads on this before. I have all the standard fixes applied, specifically: "No network browsing on startup" enabled; "cache network servers" enabled; "auto-refresh | network locations" disabled; "use generic icons | all controls" enabled; "assume that servers are available" enabled; tweak("genericiconsfornetworklocations") = 1. And anything else I've seen mentioned.

Windows Explorer simply does not have this problem. It can occasionally hang but so rarely that it's a surprise. XY hangs so often (in the above circumstances) that it's a surprise when it doesn't.

This is with Win 7 32-bit.

I realize that a non-repeatable problem can't be fixed, and just hope that eventually it will be tracked down by someone. And it needs to be frequently mentioned to keep the visibility up.

I have also seen this, most often when a network was unstable for some reason, or some server(s) were down.

My hypothesis is that it won't happen when one does not have any currently unavailable network drives mapped to drive letters. However, it is more or less only my feeling and I have not tested it much. And, of course, even if it is so, it would be a nasty workaround.

I also have a big system and tend to work it hard -- which is why I stopped using Xyplorer (sorry). I do check back now and then to search "not responding" to see if anything has been done -- I know it's built on the Windows interface and we're stuck with that. Seems this app has become very specialized, but still lacks some basic functionality.

This might be fixed in v14.80.0218.

I am seeing this issue with v.16.10.0300.

Whenever refreshing a tab (local or network drive, either one) the app hangs and goes "not responding" for 2-3 minutes.

I assume you already did as suggested here?
http://www.xyplorer.com/faq-topic.php?id=mse

I have the same problem on Win 7 x64.

I've been using XY Pro for 6 years.

The network browsing/refreshing has gotten noticeably worse in the past few months.

I tried typing "refresh;" in the address bar, as recommended above, and it pops up a box that says file or item not found.

I have network locations listed in the catalog. Many times, I click one of these and XY hangs and says, "Not responding" in the title. In the meantime, I can browse to that location with Windows Explorer and the instant I reach the location, XY "arrives", as well.

I have tested out Free Commander XE and the network browsing is absolutely stellar. However, I don't care for some other things about the program. I only mentioned it to show that other programs have great network browsing performance. I wish to stick with XY!

I don't think anything changed let alone got worse with network browsing in the last year. I did not even touch that part of the code.

You can easily test your theory by trying an older version from the back catalog:
http://www.xyplorer.com/freezer.php

BTW, it's fresh;, not refresh;

I typed fresh; this time and got the same message.

Why would XY hang, until I browse and get to that spot with WE?

Thank you

I typed fresh; this time and got the same message.

Care to post a screenshot that contains the address bar AND the error message in one picture?

Interesting.

Try

This (fresh; does not work) can only happen if somebody fiddled manually with the INI file and set tweak ScriptSmartDetect=0.

admin wrote:This (fresh; does not work) can only happen if somebody fiddled manually with the INI file and set tweak ScriptSmartDetect=0.

So, to be more exact, it would always be secure to recommend the complete format ::fresh;

(Though I must say that I use fresh; in general, and so often forget to mention the :: )

::fresh

; is not needed for a single command if :: is given.

But IMO fresh; is totally OK. It's the first time this happened for many years.