Delay when network drive no longer available

[nealeh]

When I quit x2 where the last access was a network drive, there is a delay when restarted if the drive is no longer available. It 'feels' worse if the drive was accessed via UNC than a mapped drive.

Is there a way to control the level of delay?

[nikos]

have you tried pressing ESC?
network reads should be escapable, but i'm not sure if it'll work for disconnected drives

[danielrod]

Same thing happens to me, except that I don't have to shut down X2 to experience this. I've tried hitting Esc. to no avail.

As we speak, I'm waiting for X2 to unfreeze after the network drive it was accessing went down.

...ok...just came back. The network drive must have come back online. All in all, about 3 min. or more.

--Daneil

[nikos]

that's abominable
however poor x2 is only trying to establish if the path exists
it's windows that takes its time searching in vain
i can't think how this can be helped with a fix of some sort

if you leave x2 on such folders a lot perhaps a workaround would be to start it from a shortcut that used specific local paths like

xplorer2.exe c:\ c:\

then once started you could use bookmarks or any of the other methods to make it point where you want to work

[vserghi]

I have also seen this problem recently on our internal network drives. They are reaching their capacity and seem to drop out every now and again.

Can't the ESC sequence used to terminate a network drive search, be used in this instance?

[nikos]

only with some major redesign...