Options
QAP frozes when network drives are offline
- QAP frozes when network drives are offline
-
RE: QAP frozes when network drives are offline
joeNOR > 2020-10-01 10:14
If there is a registry tweak to this (I doubt it is easily available to find) it will likely be in the HKEY_LOCAL_MACHINE under network, SMB or other such settings.
Changing those requires admin elevation, for me that is a big no-no, I don't let applications arbitrarily change fundamental system settings. A fix should be just that, a fix for users who really know and understand the implications.
But imho this is sidestepping the problem.
1. QAP hangs when waiting for a reply, as with the \\{Clipboard}\c$ problem posted by Orlith. The timeout is there for a reason, the problem is the single-threaded nature of the operation (a limitation in AHK??). QAP should continue working, not freeze, and just pop up an error when timeout occurs.
2. The Drive problem is probably partly point one above, partly the lack of resilience in the underlying function in AHK (as I understand it), and the constant triggering of that function when QAP is activated.
Changing a system wide setting to accommodate one application is bad voodoo, I would never change this because the impact on other parts of the system is unknown.
The Clipboard problem I would get around with a script, it is pretty easy to do, keeping it all contained within the application is not an argument. Where does it end, I have several scripts, RDP-files and other stuff triggered by QAP. Should QAP incorporate all this just to keep it contained within the app? (A rhetorical question
).
The Drives problem is a bummer because when the drive goes down, QAP goes haywire and that should be handled. And drives going down can happen, but it should not be the norm, if it is, fix your file server
Keeping network drives online is kind of the point with network drives to begin with.
Sorry for the rant!
Regards,
joeNOR -
RE: QAP frozes when network drives are offline
QAPuseru8921 > 2020-10-06 14:54
(2020-10-01 10:14)joeNOR Wrote: If there is a registry tweak to this (I doubt it is easily available to find) it will likely be in the HKEY_LOCAL_MACHINE under network, SMB or other such settings.
Changing those requires admin elevation, for me that is a big no-no, I don't let applications arbitrarily change fundamental system settings. A fix should be just that, a fix for users who really know and understand the implications.
But imho this is sidestepping the problem.
1. QAP hangs when waiting for a reply, as with the \\{Clipboard}\c$ problem posted by Orlith. The timeout is there for a reason, the problem is the single-threaded nature of the operation (a limitation in AHK??). QAP should continue working, not freeze, and just pop up an error when timeout occurs.
2. The Drive problem is probably partly point one above, partly the lack of resilience in the underlying function in AHK (as I understand it), and the constant triggering of that function when QAP is activated.
Changing a system wide setting to accommodate one application is bad voodoo, I would never change this because the impact on other parts of the system is unknown.
The Clipboard problem I would get around with a script, it is pretty easy to do, keeping it all contained within the application is not an argument. Where does it end, I have several scripts, RDP-files and other stuff triggered by QAP. Should QAP incorporate all this just to keep it contained within the app? (A rhetorical question ).
The Drives problem is a bummer because when the drive goes down, QAP goes haywire and that should be handled. And drives going down can happen, but it should not be the norm, if it is, fix your file server
Keeping network drives online is kind of the point with network drives to begin with.
Sorry for the rant!
Regards,
joeNOR
No need to apologize
The Clipboard issue was me who had misunderstood its function
The network drives are working as they should - however, when i'm not at work, i'm not connected to them.
i ended up making a macro snippet to open the terminal and connect to the drives. Furthermore, is made a macro snippet to "delete" the drives through the terminal also
-
RE: QAP frozes when network drives are offline
joeNOR > 2020-10-06 15:48
Cool!
I've chosen a different approach, just an ultra simple script (batch file containing the net use command) added to the QAP menu and assigned a shortcut key combo.
And, with the /persistent:no switch Windows doesn't remember the drive connections if I log off or reboot the PC.
Two different solutions to the same problem.
Regards,
joeNOR -
RE: QAP frozes when network drives are offline
QAPuseru8921 > 2020-10-07 06:45
(2020-10-06 15:48)joeNOR Wrote: Cool!
I've chosen a different approach, just an ultra simple script (batch file containing the net use command) added to the QAP menu and assigned a shortcut key combo.
And, with the /persistent:no switch Windows doesn't remember the drive connections if I log off or reboot the PC.
Two different solutions to the same problem.
Regards,
joeNOR
Sounds like a better solution!
I have not tried to make that before...
How do you run a batch file through QAP?
Thanks! -
RE: QAP frozes when network drives are offline
joeNOR > 2020-10-07 08:20
Add it as a normal application, f.ex
connect.cmd with two lines:
Code:net use E: \\servername\shareone /persistent:no
net use F: \\servername\sharetwo /persistent:no
disconnect.cmd with two lines:
Code:net use E: /delete
net use F: /delete
If you want to disconnect from the shares without logging off (won't work if it is a open file or file lock on the share).
Regards,
joeNOR -
RE: QAP frozes when network drives are offline
Jean Lalonde > 2020-10-07 09:13
Hi,
FYI, I compiled answers and solutions to issues related to this thread. Please see:
https://forum.quickaccesspopup.com/showt...p?tid=1235
Jean -
RE: QAP frozes when network drives are offline
QAPuseru8921 > 2020-10-08 02:36
(2020-10-07 08:20)joeNOR Wrote: Add it as a normal application, f.ex
connect.cmd with two lines:
Code:net use E: \\servername\shareone /persistent:no
net use F: \\servername\sharetwo /persistent:no
disconnect.cmd with two lines:
Code:net use E: /delete
net use F: /delete
If you want to disconnect from the shares without logging off (won't work if it is a open file or file lock on the share).
Regards,
joeNOR
Thank you so much - so much faster than snippet text insert
However, i made it as a .bat file - does that make a difference? -
RE: QAP frozes when network drives are offline
joeNOR > 2020-10-08 02:50
Cool, and you're welcome!
No, using .bat (as in BATch) vs .cmd (as in CoMmanD) makes no difference.
.bat is the old extension way back to days of Ms-DOS, for us old geezers who remember autoexec.bat and config.sys......
Don't remember when .cmd was introduced, was it with Windows NT back in the day?
I've just made a habit over the years of using .cmd as it makes more sense to me, a batch-job is something quite different than a simple list of commands (for me).
Happy (dis)connecting!
Regards,
joeNOR -
RE: QAP frozes when network drives are offline
Jean Lalonde > 2020-11-03 15:21
Hi,
Those interested in this thread may wish to test the new beta release available here:
https://forum.quickaccesspopup.com/showt...p?tid=1322
This beta release should prevent delays when network drives are offline. It adds two options under the Options, Advanced Menu Options:- a text field Drive letters for network drives where you can specify the network drives attached to a drive letter
- a checkbox Network drives ("\\" or with with drive letters) are always online that you enable if you are using QAP in an environment where the network drives are always online (except in case of outage, of course)
- a text field Drive letters for network drives where you can specify the network drives attached to a drive letter