How get data/time independent from localization

[aGerman]

The German translations are
Day - Tag
Month - Monat
Year - Jahr
and yes, abbreviations like TT, MM and JJ are commonly used. The MUI conception of Windows takes care that those German abbreviations will appear in their system programs, e.g.

Code: Select all

C:\>date
Aktuelles Datum: 12.07.2015
Geben Sie das neue Datum ein: (TT-MM-JJ)

But that's not a valid point here because the strings "YYYY=", "DD=", etc. are (hard-coded) string literals in Antonio's tools. For that reason they will not change

[Aacini]

Yes. The output is always the same in all computers. Is the input format the one that must be provided in locale format. This point allows to use StdDate program with the file dates shown by DIR command or by %~T... FOR modifier to get the date values from files. This means that a Batch file that use this feature will get the same result in all computers...

Antonio

[foxidrive]

Yes. The output is always the same in all computers. Is the input format the one that must be provided in locale format. This point allows to use StdDate program with the file dates shown by DIR command or by %~T... FOR modifier to get the date values from files. This means that a Batch file that use this feature will get the same result in all computers...

Antonio

That's clever Antonio.

[npocmaka_]

(Can anybody else confirm - I've used windows 10 and windows 7) Typeperf and Logman logs the date and time always in format MM/dd/YYYY hh:mm:ss.ttt.

So :

Code: Select all

@echo off
setlocal 
set "timeline="
for /f "skip=2 delims=," %%# in ('typeperf "\Processor(_Total)\%% Processor Time" -si 0 -sc 1') do (
   
   if not defined timeline (
   set "timeline=%%#"
   echo %%#
   for /f "tokens=1-7 delims=.:/ " %%a in (%%#) do (
      set mon=%%a
      set date=%%b
      set year=%%c
      set hour=%%d
      set minute=%%e
      set sec=%%f
      set ms=%%g
   )
   )
)

echo %year%%mon%%date%%hour%%minute%%sec%%ms%
endlocal

[aGerman]

What I can confirm ist that the time format of typeperf is the same for me (Win7). But I can't confirm that this is a localization-/language-independent way. The corresponding German command line would be

Code: Select all

typeperf "\Prozessor(*)\Prozessorzeit (%%)" -si 0 -sc 1

That means your posted code would never work for me (actually I'm surprised that it works for you because I didn't expect you're living in an English speaking environment).

I wasn't able to find a similar way using logman. Can you tell us what you tried out?

Regards
aGerman

[Squashman]

(Can anybody else confirm - I've used windows 10 and windows 7) Typeperf and Logman logs the date and time always in format MM/dd/YYYY hh:mm:ss.ttt.

We started talking about typeperf in this thread already starting at this post.
viewtopic.php?p=41976#p41976

[Squashman]

I am betting LOGMAN has the same issue as TYPEPERF

[Squashman]

If the GUID's are the same for each language then maybe you could.

Code: Select all

Provider                                 GUID
-------------------------------------------------------------------------------
Microsoft-Windows-Diagnostics-Networking {36C23E18-0E66-11D9-BBEB-505054503030}

[aGerman]

We started talking about typeperf in this thread already starting at this post.

You're right. I didn't even remember it

What command line did you execute to get the output that you quoted in your latest response?

[npocmaka_]

(Can anybody else confirm - I've used windows 10 and windows 7) Typeperf and Logman logs the date and time always in format MM/dd/YYYY hh:mm:ss.ttt.

We started talking about typeperf in this thread already starting at this post.
viewtopic.php?p=41976#p41976

oh I'm an idiot...

[Squashman]

What command line did you execute to get the output that you quoted in your latest response?

Code: Select all

logman query providers
logman query providers {36C23E18-0E66-11D9-BBEB-505054503030}
logman query providers Microsoft-Windows-Diagnostics-Networking

[npocmaka_]

typeperf -q and getting random performance counter is a possible way to workaround the issue with the localization



other is using name like (faster)

typeperf "\*\*" -si 0 -sc 1

or

typeperf "\*(*)\*" -si 0 -sc 1
typeperf "\*%%\*%%" -si 0 -sc 1

(are these wildcards? - I need to experiment with these to find the least verbose query)

first one seems to be faster

though both will give a latency and precious seconds can be lost if they matter (btw -si argument accepts 0 which makes using it a little bit faster)

[npocmaka_]

Are these performance counter translated (the first part of the name for the last * can be used):

IPv6
IPv4
TCPv6
TCPv4
UDPv4
UDPv6

?

[npocmaka_]

The fastest query with no specific strings I've found

typeperf "\*(%)\1" -si 0 -sc 1 (~424 bytes when redirected to a file ) fills the data with "-1" so I don't know exaclty is queried.


edit
but does not work on XP

this works but is twice as size:

typeperf "\*(%)\*(%)" -si 0 -sc 1

[Squashman]

About a 2 to 3 second delay for me.

Code: Select all

H:\>echo %time% &for /F "tokens=1,2,3,4,5,6 delims=/:. " %G in ('typeperf "\*(%)\1" -si 0 -sc 1 ^|find "/"') do @echo %~I%~G%~H_%~J%~K%~L
14:57:44.21
20151022_145746