Hi
On Monday 26 August 2019 at 5:15:46 PM, in
<mid:441136254.20190826111...@charter.net>, Jack S. LaRosa wrote:-
> I just noticed that one of the macros in my sig no
> longer works. You'll see that
> none of the "Windows" macros returns the actual
> version number which is 10. Any thoughts?
My first thought is that I didn't realise "Windows 10" was an actual
version number, rather than a marketing name like Windows
95/98/2000/ME/XP/Vista/7/8. However, when I open a command window the
first line says:-
Microsoft Windows [Version 10.0.17134.885]
This seems to match the string "Windows 10.0 Build 17134" in my
signature, so at least some of the Windows version macros work in TB!
v8.8.2.5 (BETA)(64-bit). My template has %WINDOWSPLATFORMNAME %-
%WINDOWSMAJORVERSION.%WINDOWSMINORVERSION Build %- %WINDOWSBUILDNUMBER
%WINDOWSCSDVERSION%-. The last one of those macros seems to return
nothing, where I would have expected 885.
I also notice %THEBATVERSION macro fails to return the "(64-bit)"
suffix. I just reported this at
https://bt.ritlabs.com/view.php?id=1809.
--
Best regards
MFPA <mailto:2017-r3sgs86x8e-lists-gro...@riseup.net>
To know what we know, and know what we do not know, is wisdom.
Using The Bat! v8.8.2.5 (BETA) on Windows 10.0 Build 17134
________________________________________________
Current version is 8.0.18 | 'Using TBUDL' information:
http://www.silverstones.com/thebat/TBUDLInfo.html
