>
>After several times when we were not completely sure what went wrong, we have decided to either disable the SpeedSend, or, when updating an executable, open its folder on target side and rename it. Saved a lot of time with that, because WExplorer will regularly report sharing violation if someone is still using the exe on their side, while pcAW will freeze if you try to rename it from its File Manager. This is also a good backup - if there's something wrong with the new exe, the old one is still siting there. I usually like to keep last three versions, just in case. Never used them, though, except when upload failed because of bad connections - no matter how bad it is, you can always stop uploading and rename the old executable back to original.

Dragan,
Thanks for the input. Yes, I always copy the existing exe file, and anything else I am changing, to a \back sub dir before the change. We also upload the new file to a \new sub dir so the users don't have to get out while we do the time consuming upload. We then get everyone out for 30 seconds and copy the new files from \new to the app dir after copying the existing files from the app dir to \back. Not sure what you mean when you talk about disable SpeedSend. Have you had problems with it or do you mean only when someone has the file open? I am somewhat hesitant to use SpeedSend in place of a Zip file because PCZip has the CRC error checking. I would love to hear back from you about how SpeedSend has worked. Do you feel safe with it?