T.C. 9.0a 64+32-bit combined package changed, why?

[karlchen]

Hello, Christian.

Last night I noticed that

• the 64-bit+32-bit combined installation package of T.C. 9.0a which I had just downloaded was different from
  the 64-bit+32-bit combined installation package of T.C. 9.0a which I had downloaded a day before.
  The sha256 hashsums had changed. This is how I noticed.
• Download 14-12-2016 21:10: 50c99d3d5d54568f0073eec4338e8c070b244f019ee4613a08b583abca4a22c5 *tcmd900ax32_64.exe
  Download 14-12-2016 21:10: signed 6:28 PM 12/14/2016 (tab "File Detail")
• Download 15-12-2016 23:00: a5631261c60421a5f99e0669f4493980a68b2598088a745348ae505a939b6fe7 *tcmd900ax32_64.exe
  Download 15-12-2016 23:00: signed: 9:51 PM 12/14/2016 (tab "File Detail")
• Means:
  Both combined installation packages are genuine and signed by you, which is good.

Questions which I would like to ask are:

• What is the difference between the first combined installer, signed 14-12-2016 18:28, and
  the second combined installer, signed 14-12-2016 21:51?
• Will I have to update again using the second installer on my home machine, where I had used the slightly older installer?

Best regards,
Karl

[ghisler(Author)]

The only difference is the displayed release date - this wasn't updated in the initial release, so I re-released and informed all mirror sites. There is no need to update if you can live with the wrong release date in the about box. Btw, the code addresses stayed the same, so a crash report will be the same for the older and newer release.

[karlchen]

Good evening, Christian.
Thank you very much for explaining about the displayed release date in the about box.
I seriously think I can live with it.
Best regards,
Karl