Delays XYplorer hangs

[LittleBiG]

When you right-click the Network node in the Tree and select "Browse for Network Server..." do you see all servers or only the ones in your office?

Only the ones in the office.

I have to admit, that with this kind of far away servers are XY's weekness. The moving from one folder to another is almost instant in WE, but 2-3 sec in XY. Also the custom copy doesn't work well. WE refreshes the copy window real-time, but in XY there are 8-10 second lags in refreshing, so it is unresponsive for 8-10 minutes, the clicking on the Cancel button is processed only after the lag.

[admin]

Did you try to tick Configuration | Controls and More | Miscellaneous | Assume that servers are available?

[Borut]

Don, answers to your previous questions here (using 0004, Fresh)...

::text get("network", 0); //use shell

1. Do they generate a complete list of servers (all workgroups)?
Yes -the complete list.
2. Are they slow?
5-10 sec
3. Are they slow only the first time?
2nd+ time: Instantly.

::text get("network", 1); //use NetServerEnum

1. Do they generate a complete list of servers (all workgroups)?
No - only the "current" workgroup.
2. Are they slow?
Instantly.
3. Are they slow only the first time?
2nd+ time: Also Instantly.


BTW, since some time I do not have "Assume that servers are available?" ticked, since I could not stand that under certain conditions I am not having access without being offered a login-dialogue.

[LittleBiG]

Did you try to tick Configuration | Controls and More | Miscellaneous | Assume that servers are available?

Of course it is ticked. From the get-go.

[Borut]

Hey Don, in my current test network the things are going on pretty smoothly!! Let's see what will the report of LittleBiG be.

In the meantime, two possible refinements:

Refinement 1:

Under Win7, the MS WE gives the following columns in the Netzwerk-List: Name; Kategorie; Arbeitsgruppe; Netzwerkadresse.

I can locate the same resource in MS WE as
\\<Name>\Share

OR as
\\<name>.<Netzwerkadresse>\share

This second option does not work in 0004 (am not sure if it worked previously, but it might well have worked).


Refinement 2:

In the newly introduced handling of nonexisting deep paths, after you settle on the existing leaf, you should check the conditions for possible folder view definitions anew. I think that you currently do not do that. (Example: The initial target might have one defined, but the existing leaf, might not.)

[LittleBiG]

Error message remained and the delay moving between folders increased from 2-3 second to 10 seconds :-(

[Borut]

@LittleBiG

Maybe it would help Don if you would answer his questions for your network (ShellEnum vs. NetServerEnum), like I did.

[admin]

@LittleBig

Thanks for your movies.

Now it would help if you would answer my questions for your network (ShellEnum vs. NetServerEnum).

[admin]

Don, answers to your previous questions here (using 0004, Fresh)...

::text get("network", 0); //use shell

1. Do they generate a complete list of servers (all workgroups)?
Yes -the complete list.
2. Are they slow?
5-10 sec
3. Are they slow only the first time?
2nd+ time: Instantly.

::text get("network", 1); //use NetServerEnum

1. Do they generate a complete list of servers (all workgroups)?
No - only the "current" workgroup.
2. Are they slow?
Instantly.
3. Are they slow only the first time?
2nd+ time: Also Instantly.


BTW, since some time I do not have "Assume that servers are available?" ticked, since I could not stand that under certain conditions I am not having access without being offered a login-dialogue.

Thanks for testing!

I assume that the 2nd test (NetServerEnum) was instant because it was the 2nd test (i.e. they are using the same Windows cache). Please wait some time, then test the NetServerEnum call again, and this time as the first test. I assume it will be slow as well.

In the meantime I will try to find a way to use NetServerEnum to list all workgroups.

[admin]

Hey Don, in my current test network the things are going on pretty smoothly!! Let's see what will the report of LittleBiG be.

In the meantime, two possible refinements:

Refinement 1:

Under Win7, the MS WE gives the following columns in the Netzwerk-List: Name; Kategorie; Arbeitsgruppe; Netzwerkadresse.

I can locate the same resource in MS WE as
\\<Name>\Share

OR as
\\<name>.<Netzwerkadresse>\share

This second option does not work in 0004 (am not sure if it worked previously, but it might well have worked).


Refinement 2:

In the newly introduced handling of nonexisting deep paths, after you settle on the existing leaf, you should check the conditions for possible folder view definitions anew. I think that you currently do not do that. (Example: The initial target might have one defined, but the existing leaf, might not.)

1. not possible
2. works fine here

[LittleBiG]

A last try. In the next beta (v15.10.0004) please try these two script lines:

Code: Select all

text get("network", 0); //use shell

Code: Select all

text get("network", 1); //use NetServerEnum

1. Do they generate a complete list of servers (all workgroups)?
2. Are they slow?
3. Are they slow only the first time?
4. Which is faster?

text get("network", 0);
1. Running more times gives back nothing. Empty.
2. No. It is very fast.
3. Not really.

text get("network", 1);
1. All computers in the office.
2. Yes. 8-10 seconds.
3. No. Stable 8-10 seconds.
4. The previous one.

Running text get("network", 0); again:
1. All computers in the office.
2. No. It is almost immediate.
3. Yes, it was about 10 seconds at the first time, then very fast.

WAIT. I ran it on Fresh. If I run it on my live, "text get("network", 0);" gives back other things. First time I got the list of the recent network location I used (or tried to use if they were unreachable). Every other try gave back the computers in the office again, immediately.

[Papoulka]

I'm getting fewer "XY hang" situations with v15.10.0002, updated from 15.00.0521.

More usage will tell, but my first impression is that there are far fewer hangs and the ones remaining are no worse than WE would have. That would mean that one of the speedup fixes this week has had a major effect when a LAN and/or big USB drives are connected.

Cautiously optimistic... but it will be great if this has been cured. I sometimes had to start WE to keep working while XY was paralyzed, then switch back when XY returned. It is/was the only major issue remaining for me.

http://www.xyplorer.com/xyfc/viewtopic. ... ng#p117150

Thanks!

[admin]

A last try. In the next beta (v15.10.0004) please try these two script lines:

Code: Select all

text get("network", 0); //use shell

Code: Select all

text get("network", 1); //use NetServerEnum

1. Do they generate a complete list of servers (all workgroups)?
2. Are they slow?
3. Are they slow only the first time?
4. Which is faster?

text get("network", 0);
1. Running more times gives back nothing. Empty.
2. No. It is very fast.
3. Not really.

text get("network", 1);
1. All computers in the office.
2. Yes. 8-10 seconds.
3. No. Stable 8-10 seconds.
4. The previous one.

Running text get("network", 0); again:
1. All computers in the office.
2. No. It is almost immediate.
3. Yes, it was about 10 seconds at the first time, then very fast.

WAIT. I ran it on Fresh. If I run it on my live, "text get("network", 0);" gives back other things. First time I got the list of the recent network location I used (or tried to use if they were unreachable). Every other try gave back the computers in the office again, immediately.

OK, this is totally confusing. I will not go this way. Network sucks.

Thanks for the report anyway!

[admin]

I'm getting fewer "XY hang" situations with v15.10.0002, updated from 15.00.0521.

More usage will tell, but my first impression is that there are far fewer hangs and the ones remaining are no worse than WE would have. That would mean that one of the speedup fixes this week has had a major effect when a LAN and/or big USB drives are connected.

Cautiously optimistic... but it will be great if this has been cured. I sometimes had to start WE to keep working while XY was paralyzed, then switch back when XY returned. It is/was the only major issue remaining for me.

http://www.xyplorer.com/xyfc/viewtopic. ... ng#p117150

Thanks!

That's good news, thanks!

Due to LittleBiG's unfortunate findings regarding non-primary domain servers I have to remove the improvements though. At least from the hard code. So, I will make them a tweak or even a setting, not sure yet. All will be good.

[LittleBiG]

Thanks, Don. I am happy because everything works as before. Additionally I appreciate that you created this new settings, because it can be fine-tuned now. Today ticking the Pre-check made my network connection faster too, there is no 8 seconds delay as yesterday. But the "network seems to be unavailable" error message remained when I go back or up. May I ask for a setting or tweak to suppress it? Or exile it into the info bar? In this way on these kind of stupid servers I could go back one folder without clicking on "OK" in the error message dialog.
(EDIT: anyway, why this error message is needed at all? It pops up immediately.)