Page 1 of 5
Network problems
Posted: 12 Jul 2007 12:03
by serendipity
I am constantly being annoyed by network problems (after 4th xy hangup today)
Problems are:
1. I have to use winexplorer first to log into a network computer and only then XYplorer nethood is usable. Note: I am talking about computers that are passworded.
2. XY freezes (probably searching for network computers) when I try and click on unlogged network place.
3. Even if I uncheck "show my network places", my catalog shows network favorites (which is OK) but when i by mistake try to navigate it XY freezes.
Possible solutions:
1. Throw up a dialogue for logging in if any network computer is not logged in. As of now the only way is to use WinExp to navigate into passworded computers and switch to XY.
2. Hide or disable catalog items that belong to network.
I am a regular user of network PCs at work and I definitely would love to use XY as much as possible.
Anybody facing similar problems?
Have a nice holiday Don.
Re: Network problems
Posted: 24 Jul 2007 08:26
by admin
Throw up a dialogue for logging ... later (needs research ... EDIT: yielded no results).
The other stuff: done.
Posted: 31 Jul 2007 11:02
by serendipity
The catalog thing is still giving problems, as in when i navigate into a network location XY freezes.
I guess XY is looking for that location for quite sometime until it responds again. I tried waiting before i clicked anything and it took like 3-4 mins before it showed path not found.
Is it possible to give the user a handle on how long XY should look for the network location? I mean in my case if a network location is working, XY connects in a flash, if not its like i said 3-4 minutes until i can do anything. Thats my only issue here. thanks.
Posted: 31 Jul 2007 13:46
by admin
serendipity wrote:I guess XY is looking for that location for quite sometime until it responds again. I tried waiting before i clicked anything and it took like 3-4 mins before it showed path not found.
That's extremely long, of course. Here it takes about 0.5 seconds if a computer is not connected. We are talking about UNC (\\computername\share ...) paths, right? Note that I have no control over this timeout. Unfortunately I do not know who has the control... but I guess when you do the same thing in Explorer it takes much less time, so they must be a way. I'm researching...
Posted: 31 Jul 2007 14:26
by serendipity
well, the long wait might also be due to my network being slow in general, but thanks for trying. Just one of those little things that comes in my way of smooth XY experience.
Posted: 31 Jul 2007 16:06
by admin
serendipity wrote:well, the long wait might also be due to my network being slow in general, but thanks for trying. Just one of those little things that comes in my way of smooth XY experience.
When a network location is "not working", what is the case then? (a) is the server (computer) not connected/turned on? (b) or is the server available but the path is wrong?
Posted: 31 Jul 2007 18:11
by serendipity
Mostly it is the first one. The paths to the computers have remained same since past 3 years or so i am sure its not wrong path thing. "not working" also means not logged in using explorer shell. Thanks again.
Posted: 02 Aug 2007 08:46
by admin
serendipity wrote:Mostly it is the first one. The paths to the computers have remained same since past 3 years or so i am sure its not wrong path thing. "not working" also means not logged in using explorer shell. Thanks again.
When is it slower, when faster? When going from Catalog to non-available
(1) \\server
(2) \\server\share
(3) \\server\share\folder
Posted: 02 Aug 2007 09:07
by serendipity
Almost always (3) \\server\share\folder.
Posted: 02 Aug 2007 09:14
by admin
serendipity wrote:Almost always (3) \\server\share\folder.
No, my question is: do you have this long delay also when trying to go to an unavailable \\server or \\server\share or are these processed faster?
Posted: 02 Aug 2007 10:48
by serendipity
Sorry, I realised I was pretty unclear previously, I will try to explain in more detail:
I have in my catalog 3 network locations under the category neighbors. Since the catalog is continuously updating the file/folder info (location, icons etc) it takes about 1.5 mins to just scroll the contents of neighbors category into view. And after clicking, an additional 30 seconds to show that share is not available or about 3 mins or more to show that folder on that share is not available.
If share or folder are available after passwording using explorer then XY is pretty fast to go there.
Posted: 02 Aug 2007 10:57
by admin
serendipity wrote:Sorry, I realised I was pretty unclear previously, I will try to explain in more detail:
I have in my catalog 3 network locations under the category neighbors. Since the catalog is continuously updating the file/folder info (location, icons etc) it takes about 1.5 mins to just scroll the contents of neighbors category into view. And after clicking, an additional 30 seconds to show that share is not available or about 3 mins or more to show that folder on that share is not available.
If share or folder are available after passwording using explorer then XY is pretty fast to go there.
I see. But note that the catalog is
not continuously updating the file/folder info! It is just trying to retrieve the icons, and it tries this only one time per session! Retrieving icons needs access to the files (unless you are happy with generic icons), hence the delay. But 3 minutes is, of course, totally ridiculous. As I said it never takes longer than 0.5 seconds here when you click a locaiton that does not exist.
Anyway, I'm working on some test app...
Posted: 02 Aug 2007 11:28
by admin
Okay, I made a quick test app where various methods (to check if a network path is available) are compared:
Download:
http://www.xyplorer.com/download/ExistUNC.zip
Unpack and check whether the results are correct and which is the fastest method.
Posted: 02 Aug 2007 13:42
by serendipity
Ok, i have the following setup:
\\Computername\Folder\SubFolder\SubSubFolder\...
RESULTS-
##########
Check 1:
For "\\Computername\Folder"
first click is >20 msec and
second click is <0.1 msec
For "\\Computername\Folder\SubFolder\" and beyond
Always >20 msec
Check 2:
For "\\Computername\Folder\" and beyond
Always <2 msec
Check 3:
Shows True ONLY when the textfield is blank.
Show False on "\\Computername\".
The times are
Always >3 msec and
>20 msec on first click on new "\\Computername\"
###########
In my view Check 2 wins.
Thanks for the great support.
Posted: 02 Aug 2007 17:44
by admin
serendipity wrote:Ok, i have the following setup:
\\Computername\Folder\SubFolder\SubSubFolder\...
RESULTS-
...
Thanks! I'll react according to your results tomorrow...
Anybody else with different results?