I've got a dual pane list opened, with one pane pointed at a C:\ folder, and the other pointed to a networked machine (Say "\Machine1\Share1\MyFolder"
Everything's fine while Machine1 is alive, BUT, if I close Dopus down with that pane still set, then shut down the other machine, then REOPEN Dopus, it basically hangs because it's trying to get to the folder I last had open (I prefer to have Dopus come up where I left off).
Obviously, it's hanging because it's trying to get to a network share that's no longer there.
My question is, is there anyway to abort that process? I'd rather not have opus always come up pointed at a local drive. Most of the time, I leave it in a state that's just fine to bring it back up. But occassionally, i leave it pointed at a network share that's not alive when I bring Dopus back up.
I prefer not to leave DOpus running all the time. I have an icon set that's easy enough to launch it when needed.
Any thoughts? I thought maybe some hotkey combo held down WHILE I started DOpus would prevent it from automatically loading previously set tabs, but no luck. Generally, I have to bring the down machine back up, or clear out DOpus's settings file of the offending path before I can get back into it. A really pain either way.
Is it not possible for Dopus to check if a drive exists before attempting to load it (and thus completely hang if it doesn't)?
Or is it possible there's some setting somewhere I've missed
Try turning on "prevent automatic loading of... network drives" in Preferences. (Type "automatic loading" into the filter at the bottom of the prefs window and it should find the option for you.)
I know this is a v old post, but I recently have been having the same problem with a machine that I don't know if it is off or on due to being owned by someone else.
Following the suggestion to "prevent automatic loading of... network drives" would partially work, but I have several other networked machines that are never off. Hence, it would be disruptive to my work to use the option, as I often leave my computer on with many listers with different tabs open, with the intention of continuing the work the next day.
Is there any way to reduce/eliminate the "not responding " period when the entire application hangs and is non-responsive as it searches for the non-existent network drive?
Have you tried turning the option on? When it is on you can just click to load the folders as and when you want them; they just don't get loaded as soon as you start the program. Give it a try if you haven't already.
I have used it before and also before I made the post to make sure nothing had changed with opus updates.
The problem is that there are often a lot of tabs that are open in this manner. Sometimes ~20-30 as I am working with a several different computers via samba. I know it's only a click, but when you have to repeatedly do this with a lot of of folders, it gets old pretty quick. Plus, there is the added issue that a lot of the folders have similar naming formats (for scripts), so I usually identify where I am by looking at the file list which identifies the information of which directory I am in.
Is the hanging issue because of the underlying windows framework that opus uses?
No worries. It's useful to know that the issue could possibly be fixed with a windows tweak. I've just been looking into it and experimenting with turning the variable windows MTU off amongst other things, but it hasn't seemed to work for this particular issue.
One thing that has come up though (which I had not mentioned previously), during testing of the fix was that if the share was not available, opus would not allow me to remove the defunct share and "greys" out for sometime. Waiting and retrying leads to the same cycle of behavior, till it inevitably crashes. Then the whole procedure starts again. I have two query s regarding this:
As I'm not very keen on the "preventing the automatic loading" option (I can co-ordinate with my colleague to best avoid this), if this situation does occur, how do I launch opus with only local directories loaded. So it does not get in the situation of continually loading the last open tabs that contain inaccessible network shares?
Is there no way that something could be implemented so that if this network related hang & crash occurs, opus closes the tab that caused the problem, so on re-launch we don't get trapped in this cycle?
Thanks for your reply. I think we can rule this out though as my dropbox has not been running for a few days now as I am sorting out a sync issue.
It's a massive pain (just waiting for it to opus to become responsive as I write this!), but hopefully there is a reg hack or something to terminate unresponding network connections somewhere!
