1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

Wrong File Size

Discussion in 'Support' started by Glennbo51, Nov 27, 2010.

  1. Glennbo51

    Glennbo51 Guest

    When I do a "Check for Updates" from

    TCC 12.00.36 Windows XP [Version 5.1.2600]
    TCC Build 36 Windows XP Build 2600 Service Pack 3

    I get a "Wrong File Size error"
     
  2. vefatica

    Joined:
    May 20, 2008
    Messages:
    7,788
    Likes Received:
    29
    I get it too (trying to update 38 to 39).
     
  3. rconn

    rconn Administrator
    Staff Member

    Joined:
    May 14, 2008
    Messages:
    9,730
    Likes Received:
    80
    My broadband connection failed during the file uploads. I'm trying to get
    them uploaded via dialup, but it'll probably take a little while.
     
  4. Glennbo51

    Glennbo51 Guest

    On 11/27/2010 15:13, vefatica wrote:

    I would like to point out the ^$ Bit version updated just fine. It
    appears to be only the 32 bit version that has the issue.
     
  5. dim

    dim Dimitry Andric

    Joined:
    May 31, 2008
    Messages:
    202
    Likes Received:
    0
    On 2010-11-27 22:30, GlennBo51 wrote:

    Yep, the 32-bit installer seems corrupt. The tcmd.exe file I
    downloaded is just 2,786,550 bytes, while the installer for 12.0.37 is
    7,522,264 bytes...
     
  6. rconn

    rconn Administrator
    Staff Member

    Joined:
    May 14, 2008
    Messages:
    9,730
    Likes Received:
    80
    Try it again now.
     
  7. rconn

    rconn Administrator
    Staff Member

    Joined:
    May 14, 2008
    Messages:
    9,730
    Likes Received:
    80
    is

    That's what happens when you download when an upload is in progress!
     
  8. Steve Fabian

    Joined:
    May 20, 2008
    Messages:
    3,523
    Likes Received:
    4
    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
     
  9. Kachupp

    Joined:
    Aug 9, 2009
    Messages:
    133
    Likes Received:
    0

    Someone will moan about that as well
     

Share This Page