TCC 25 @TIMER regession

Dec 10, 2014
65
1
... running Windows 10 Build 17763.

One my x64 desktop system it works as expected, but on my x86 laptop it shows the error below. I cannot pinpoint it to a specific x86 bug, it might have to do something with the locale as my laptop is set to more German ui than my desktop.

TCC 24.02.51
Code:
[C:\Program Files\JPSoft\TCMD24]echo %@TIMER[1]
0:00:00,00

TCC 25.00.20
Code:
[C:\Program Files\JPSoft\TCMD25]echo %@TIMER[1]
TCC: (Sys) The parameter is incorrect.
"%@TIMER[1]"
 
May 20, 2008
10,674
83
Syracuse, NY, USA
... running Windows 10 Build 17763.

One my x64 desktop system it works as expected, but on my x86 laptop it shows the error below. I cannot pinpoint it to a specific x86 bug, it might have to do something with the locale as my laptop is set to more German ui than my desktop.

TCC 24.02.51
Code:
[C:\Program Files\JPSoft\TCMD24]echo %@TIMER[1]
0:00:00,00

TCC 25.00.20
Code:
[C:\Program Files\JPSoft\TCMD25]echo %@TIMER[1]
TCC: (Sys) The parameter is incorrect.
"%@TIMER[1]"
I get the same error on my x86 English Windows 7.
 
Dec 10, 2014
65
1
Well, there you go. I do hope this doesn't speed up abandoning x86, as my small laptop with just 2GB of RAM is only usable running x86 Windows :-\
 

rconn

Administrator
Staff member
May 14, 2008
11,952
133
Fixed in 25.0.21 (MSVC RTL bug).

Note that 32-bit support is deprecated in v25 and will be removed altogether in v26 (along with Win 7 support).

Currently TCMD installations are about 3.7% x86 and 96.3% x64. Most of the x86 installations are pirated copies in China and Russia; take them out and x86 is well under 1% and honestly just not worth the effort. (Particularly when the 3rd party tools are dropping support or at best not testing x86.)
 
  • Like
Reactions: Juppycmd