Intermittent hangs

Things you’d like to miss in the future...
Forum rules
:warnred20: :warnred20: :warnred20: :warnred20: :warnred20: READ THIS AND DO IT!!! :warnred20: :warnred20: :warnred20: :warnred20: :warnred20:

:info: Please include the following information:
1) Your XYplorer Version (e.g., v28.00.0801)
2) Your Windows Version (e.g., Win 11)
3) Your Screen Scaling Percentage (e.g., 125%).

:info: We recommend adding your Windows Version and Screen Scaling Percentage to the Location field in your Profile or to your Signature. That way, you only have to type them once.

:info: When attaching an Image, please use the Attachment tab at the bottom of your post and click "Add files".

:warnred20: :warnred20: :warnred20: :warnred20: :warnred20: READ THIS AND DO IT!!! :warnred20: :warnred20: :warnred20: :warnred20: :warnred20:
Post Reply
diarrhio
Posts: 83
Joined: 14 Jun 2005 09:42

Intermittent hangs

Post by diarrhio »

I've noticed XY will often hang for a few dozens of seconds, to minutes, if any network resources aren't available. For instance, I have some mapped network drives, which are mapped to \\machinename\share\. When I'm at the office, this machine is visible just fine and XY works as expected. However, if I go home and login through the VPN, these shares aren't available since over VPN I need to use a fully qualified domain name as the mapping (\\machinename.fully.qualified.domain\share). Almost any operation causes XY to freeze for a while, rendering it unusable.

I know I can just change the drive mapping to include the qualified domain name, but there are other situations where this is happening where the domain name is not a factor.

What I'm interested in is seeing if there is a setting which will prevent these lockups from happening?

avsfan
Posts: 554
Joined: 29 Jun 2006 09:00
Location: Fort Collins, Colorado

Re: Intermittent hangs

Post by avsfan »

diarrhio wrote:I've noticed XY will often hang for a few dozens of seconds, to minutes, if any network resources aren't available. For instance, I have some mapped network drives, which are mapped to \\machinename\share\. When I'm at the office, this machine is visible just fine and XY works as expected. However, if I go home and login through the VPN, these shares aren't available since over VPN I need to use a fully qualified domain name as the mapping (\\machinename.fully.qualified.domain\share). Almost any operation causes XY to freeze for a while, rendering it unusable.

I know I can just change the drive mapping to include the qualified domain name, but there are other situations where this is happening where the domain name is not a factor.

What I'm interested in is seeing if there is a setting which will prevent these lockups from happening?
Have you tried going to the "Tools->Configuration->Startup & Exit" settings page, and then selecting "Cache network servers" and possibly "No network browsing on startup" options? They might do just what you need...

Good luck!

andy

Post Reply