rconn:
| That's what happens when you download when an upload is in progress!
You used to announce new builds only after they were uploaded to the server. That would have prevented premature downloads. Regardless, Murphy's Law guarantees that sooner or later there will be someone checking for updates when an upload is in progress, an event of which the user cannot be aware. Some mechanism ought to be provided that even in that event no user would download a partial (and thus corrupt) installer. If this were my product, I would perform the following in order to achieve this:
1/ upload all files of the new build (i.e., both 32-b and 64-b versions of all updated installers, and all new help files) into a holding area on the server (of servers, if the FTP and HTTP servers are not the same).
2/ make the server temporarily unavailable
3/ move all files to their distribution location (this could be just a change of directory name)
4/ make the server available
5/ post the announcement in the forum
6/ update the website
--
Steve