WinCvs often hangs when one of my sandboxes is on a remote machine (via UNC or shared drives). What can I do ?
In general, it is not advisable to put sandboxes on remote machines. WinCvs relies on the Windows API to provide a realtime view on the directories it displays. For local drives this works pretty well using a notification scheme but for remote directories the underlying WinAPI falls back to polling the remote machine in regular intervals and thus significantly increases the overall network traffic. Especially for large directories or when you enable the “flat view” this constant polling could slow down WinCvs (and in extreme cases the entire network) beyond use. What’s even more annoying is when for some reason the connection to the remote sandbox fails. In that case you will notice a significant slowdown in all WinCvs operations even when the disconnected sandbox is not the currently selected browse location! Yet another aspect of the problem occurs when the remote machine isn’t even a Windows box but a Samba share on a Linux server. In the latter case, there have also been numerous o
