"Use colon as time stamp seperator in log file names" BAD BAD BAD!

[eahm]

Please use dots or dashes for the h mm and ss for the log name file,
filestr can't open the log file anymore and can't search inside for the
keywords and I am unable to send notifications via email.

Please revert or change to . or -.

Thank you.

edit:
The commas you are using on the file naming are not even codified in the standards of Windows? You had to change it because Windows can't write commas on file names. I can't understand how you thought this was a good idea? Sorry not trying to be rude.

[Zenju]

Modern Unicode-aware programs shouldn't have a problem. Is there a particular issue you are seeing?

[micha--]

@eahm: You have given no example. Hence i imagine, you mean someting like this: 17.02.2015 or this for the time: 15:49:00

I suggest to use the ISO 8601 format: 2015-02-17

http://de.wikipedia.org/wiki/ISO_8601#Datum
http://en.wikipedia.org/wiki/ISO_8601#Calendar_dates

and for the time: 15:49:00 or if the colons are difficult in WIN: 154900

http://de.wikipedia.org/wiki/ISO_8601#Tageszeit

and date & time together: 2015-02-17T154900

http://de.wikipedia.org/wiki/ISO_8601#Trenner_bei_festen_Datumsangaben
http://de.wikipedia.org/wiki/Uhrzeit#Numerische_Zeit


And thanks for FFS :)

[eahm]

micha, I didn't write Windows, I can't use something cmd/batch/prompt/Windows or whatever you call it doesn't support.

I just don't understand why a . or a - is not good enough and why the need to change it with something different from the Windows standard and that we don't really need.

Please read from here on: http://www.dostips.com/forum/viewtopic.php?p=39938#p39938

[wm-sf]

This is also being discussed in
Open Discussion
PROBLEM: Illegal Character in Log File Name (Windows)

[eahm]

Sorry Wm I only browse Help when I need something. Issue solved, thanks again Zenju.

[jhirst]

Modern Unicode-aware programs shouldn't have a problem. Is there a particular issue you are seeing?

However you've done it, Windows seems to accept your use of colons in the date format, with one particular exception: In Windows 7 there doesn't seem to be a problem but in Windows XP it only works when the timestamp begins with a two digit hour. For hours zero through nine the timestamp developed is reduced to simply "_x" where x represent the single digit hour. This results in a high probability of duplicate names and the inability to generate the log file. If pop-up is not selected for errors on batch files FFS simply aborts.

Thanks for all your good work!!!

Edit: I've since determined that the timestamp developed in Windows XP is less predictable than I thought - sometimes it's totally missing. In addition the log file is not always created and the actual synchronization doesn't take place!!