When I boot up Windows 10, and open a Dopus lister, it is very responsive, both on local drives and LAN paths. Even when I connect to my office's Windows network over VPN, the performance is still ok.
The problem starts when I drop the VPN connection. From that point opening a new lister results in a wait of around 12 seconds before it populates the list pane -whether a local drive or a LAN path. It remains in this low-performance state until I restart Windows.
I don't want to leave the VPN connected all the time, so how do I resolve this problem? Note this is definitely a Dopus issue, as Windows File Explorer performance is not impacted when I drop the VPN - it continues to have a 1 or 2 second response.
I'm using Dopus 10.5.7.0 (5215) on Windows 10 Pro X64.
I have the "Net Drives" button on the "Drives" toolbar. One of the network drives is mapped to a share on a remote server, accessible over VPN. I have the share as a mapped drive because I access it 2 or 3 times a day and the unc path is a bit long to remember.
I am not trying to access the mapped drive from Dopus when the VPN is down and the mapping is done through Windows, not Dopus, so why the slow-down in Dopus when it open a lister after closing VPN?
I've tried closing all open listers and killing The Dopus Helper in Task manager. But the moment I open a lister again I get the 12 second wait before I can use it.
Having it there causes the icon to be refreshed when the toolbar it is on is refreshed, which causes an attempt to access the drive and can then cause other things to block.
If you move the drives list into a submenu it will speed things up (until the menu is open).
Alternatively, unmapping the drive letter and then creating a button which goes to it via its UNC path may also work and allow you to keep it at the top level, with no loss of convenience. (If you make such a button, set the icon to one of the internal icons, or an icon from a local file, and set the tooltip to a string. They will prevent the drive being accessed to obtain/generate either thing.)
You may also be able to keep the drive mapped and replace the automatic drive button with a custom button similar to the one I just described, with a predefined icon. (You can also modify the DriveButtons command to exclude a particular drive letter, so the other letters remain automatic.) However, in my experience just having a drive mapped to something inaccessible will cause long delays in random places when using Windows, not just in Opus, so I still would recommend unmapping it.
Thank you very much for that advice. It was very helpful. I'm sure I will be able to work out the best solution that works for me, from the tips you have given.