[v9.0b3] Autoupdate didn't work

[pdavit]

With the default ini setting that acknowledges also beta releases I was prompted about beta 2 while beta 1 was installed.

The same did not happen though for the b2 -> b3 move.

Whether a bug or a server availability issue I believe Christian should be able to distinguish.

Neither the manual check has worked for me this time.

[ghisler(Author)]

Auto update will notify you only once about a new version, then it stores that version in the wincmd.ini. Apparently you were not notified about b2 before.

You get something like this in the wincmd.ini:

AutoUpdateCheckDate=2016062306
AutoUpdateInformedVersion=589955
or in hex: 9 00 83

It's calculated like this:
updatecheckversion=(updatemajor << 16) | (updateminor shl | updateabc;

So 9 is the major version, 0 the minor, 80 means beta, and 3 means beta 3. Once this is set, you should no longer be informed about beta 3. The idea is that the user shouldn't be constantly be reminded when starting older versions.

[pdavit]

Apparently you were not notified about b2 before.

I was notified when b2 came out. I was not for b3.

I assumed that with AutoUpdateCheck=1 in use I'm autovalidating beta releases.

[ykhabins]

Same here.
I have TC b2.

1. No notification about b3.
2. Even clicking Help -> Check for updates now gives the following:

---------------------------
Total Commander
---------------------------
Total Commander is up to date.
---------------------------
OK
---------------------------

[ghisler(Author)]

Sorry, I don't know where the problem is. When I use
nslookup releaseversion.ghisler.com
I still get 10.9.0.130
although I have set it to 10.9.0.131 already last week.

[phantom]

No problem here.

Code: Select all

Server:  speedport.ip
Address:  192.168.2.1

Nicht autorisierende Antwort:
Name:    releaseversion.ghisler.com
Address:  10.9.0.131