32b Build 54 does not match MD5 in tcmd.aiu

[Steve Fabian]

MD5=a87c27778f0477aff86c3e539b6d7c29 from tcmd.aiu

md5=EE5BC0576FE0900DEC837B67FA07B147 from pdir/(m)

 

[Rodolfo]

I do not know if my issue is related. I tried to update with the command option. It said that there was a new version, but then when I started the download it said wrong size. I downloaded by hand the complete file from the http site and there it worked.


Regards

Rodolfo Giovanninetti

 

[vefatica]

I updated successfully with "OPTION /U" shortly after build 54 was announced. I think there was a little tweak to it after that.

 

[Steve Fabian]

I do not know if my issue is related. I tried to update with the command option. It said that there was a new version, but then when I started the download it said wrong size. I downloaded by hand the complete file from the http site and there it worked.i

Yes, I forgot to mention it - the size reported in tcmd.aiu is also wrong. I downloaded tcmd.exe twice, into separate directories, they matched, so I made the assumption the .aiu file is incorrect, and successfully installed. No issues using it so far...

 

[Bob Chapman]

I downloaded by hand the complete file from the http site and there it worked.

Apparently, this is the official upgrade path for 32 bit Build 54? Sigh! :(

 

[Steve Fabian]

BTW, though many are aware, I need to install TCMD in multiple systems, and have volume-measured internet service, so I normally avoid the multiple downloads of the same installer (which you would do by using the UPDATE on each system) by explicitly downloadiing them to my "installation server" system.

 

[Steve Fabian]

Charles:
I noticed that on your FTP site the MD5 for 32b TCMD.EXE is the same as the one I calculated from the HTTP download (see above), but as of an hour ago both the size and hash code in http://jpsoft.com/downloads/v15/tcmdupdate.aiu are still not matching the installer, unchanged from my OP above. Did you just recalculate for your version.txt?

BTW, I appreciate the availability of the alternate download site, but I no longer use it. I now have my own jpupdate.btm, which unconditionally downloads the current .aiu files, and compares them with the saved versions to determine whether or not my system is up to date. The files are so small that the download volume is only insignificantly more than FTP would use to make the same determination, and Rex standardized the HTTP file names, so I can now test even for future versions. Run time is a little more, but it's while I get my coffee...

 

[Charles Dye]

I noticed that on your FTP site the MD5 for 32b TCMD.EXE is the same as the one I calculated from the HTTP download (see above), but as of an hour ago both the size and hash code in http://jpsoft.com/downloads/v15/tcmdupdate.aiu are still not matching the installer, unchanged from my OP above. Did you just recalculate for your version.txt?

I don't look at the AIU file; the checksums and so on are calculated when the files are uploaded to the server. (That's why the dates don't relate to anything else.)