XMBC 2.16 Beta

[JTB3]

I fixed it here on office 2016 - just tried again and its still OK.
What office are you using? maybe it uses different class names?

Edit: Tell a lie - its not working on my 2016 laptop.... sigh.
I better check I published the right version (I made a few internal revisions of beta3)

Cool, that's good to know! I just re-tested on BOTH of my versions of Excel (2013 & 2016). Same issue persists identically on both versions...

[phil]

Something odd with the download I think - can you check the file versions and creation times in
C:\Program Files\Highresolution Enterprises\X-Mouse Button Control
Specifically, the XMouseButtonControl.EXE and XMouseButtonHook.DLL

Should be: 15/06/2017 19:04 (the time may be displayed in your local timezone shortly before I posted the beta above.) The date should be today!

[JTB3]

Something odd with the download I think - can you check the file versions and creation times in
C:\Program Files\Highresolution Enterprises\X-Mouse Button Control
Specifically, the XMouseButtonControl.EXE and XMouseButtonHook.DLL

Should be: 15/06/2017 19:04 (the time may be displayed in your local timezone shortly before I posted the beta above.) The date should be today!

I downloaded the full install version - Digital Signature timestamp is 15-Jun-2017 11:04:45am

Edit: I stand corrected (the above was for the installer) the exe in program files has a digital signature timestamp of June 14th, 12:19:05pm - and the ...Hook.DLL is Jun-14th at 12:18:44pm

[phil]

Yeh thats right, but what about the files I asked for?
I think the installer is OK but for some reason, it hasnt replaced the files under c:\program files.

I just re-ran the same installer on my laptop and now its got the right files and its working. I can sort of understand it here because I already had an older version of the beta (with the same file versions) but you wouldn't have had that. This is why I need to know the file dates and versions in your programfiles folder I mentioned above.

Once you have checked, re-run the installer and see if it fixes it (but please check the files first).

EDIT: Ok I see your edit. Yesterdays build did not have today's Excel fix - the question is why are yesterdays exe/dll in todays installer!!!
I will check the files inside the full install - please try the x64 update.

[JTB3]

Yeh thats right, but what about the files I asked for?
I think the installer is OK but for some reason, it hasnt replaced the files under c:\program files.

I just re-ran the same installer on my laptop and now its got the right files and its working. I can sort of understand it here because I already had an older version of the beta (with the same file versions) but you wouldn't have had that. This is why I need to know the file dates and versions in your programfiles folder I mentioned above.

Once you have checked, re-run the installer and see if it fixes it (but please check the files first).

Sorry, I edited my earlier post. Dates for the Prog Files are both Jun 14th. I re-ran the installer and it still has Jun 14th...

[phil]

As did I

OK the full install has got old files in it - I dont know how that happened but its probably a result of doing more than one build (and i guess the install build failed and just re-signed yesterdays file).

The update should work but I will rebuild ALL of them and re-distribute!

[JTB3]

As did I

OK the full install has got old files in it - I dont know how that happened but its probably a result of doing more than one build (and i guess the install build failed and just re-signed yesterdays file).

The update should work but I will rebuild ALL of them and re-distribute!

The 64bit update worked like a champ! Excel issue is resolved!

[phil]

OK Good, I have rebuilt ALL the installers and they are now all correct (same links as above).

ALL: If you downloaded 2.16.1 Beta 3 then please re-download it and re-install it!

[JTB3]

OK Good, I have rebuild ALL the installers and they are now all correct (same links as above).

Awsesome!

[phil]

FYI, if you are on 2.16.1 Beta then you can upgrade to the final version (its no different than 2.16.1 Beta 3 but is "official".
The auto-update wont work, because it thinks that 2.16.1.3 is greater than 2.16.1 (which it is lol) so thinks the beta is newer... One of the problems with doing beta for patches!

[JTB3]

FYI, if you are on 2.16.1 Beta then you can upgrade to the final version (its no different than 2.16.1 Beta 3 but is "official".
The auto-update wont work, because it thinks that 2.16.1.3 is greater than 2.16.1 (which it is lol) so thinks the beta is newer... One of the problems with doing beta for patches!

Thanks Phil

[phil]

I'm closing this thread now as I have started a new 2.17 Beta thread