HKEY_CURRENT_USER\Control Panel\International
foxidrive
Can you please paste the file.txt output into a reply? I seem to have
something odd here and I wanted to check a standard install for australia.
Thanks.
@echo off
reg query "HKEY_CURRENT_USER\Control Panel\International" /s >file.txt
--
Regards,
Mic
John Gray
You can (probably) do it for yourself: In XP go to Control Panel ->
Regional and Language Options. Select English (Australia). OK out.
Reboot. Do the Reg Query, then change the Regional and Language
Settings back to your original setting. Preferably reboot.
billious
"foxidrive" <got...@woohoo.invalid> wrote in message
news:vjq7p55adldtobh7j...@4ax.com...
! REG.EXE VERSION 3.0
HKEY_CURRENT_USER\Control Panel\International
iCountry REG_SZ 61
iCurrDigits REG_SZ 2
iCurrency REG_SZ 0
iDate REG_SZ 1
iDigits REG_SZ 2
iLZero REG_SZ 1
iMeasure REG_SZ 0
iNegCurr REG_SZ 1
iTime REG_SZ 1
iTLZero REG_SZ 1
Locale REG_SZ 00000C09
s1159 REG_SZ AM
s2359 REG_SZ PM
sCountry REG_SZ Australia
sCurrency REG_SZ $
sDate REG_SZ /
sDecimal REG_SZ .
sLanguage REG_SZ ENA
sList REG_SZ ,
sLongDate REG_SZ dddd, d MMMM yyyy
sShortDate REG_SZ dd/MM/yy
sThousand REG_SZ ,
sTime REG_SZ :
sTimeFormat REG_SZ HH:mm:ss
iTimePrefix REG_SZ 1
sMonDecimalSep REG_SZ .
sMonThousandSep REG_SZ ,
iNegNumber REG_SZ 1
sNativeDigits REG_SZ 0123456789
NumShape REG_SZ 1
iCalendarType REG_SZ 1
iFirstDayOfWeek REG_SZ 0
iFirstWeekOfYear REG_SZ 0
sGrouping REG_SZ 3;0
sMonGrouping REG_SZ 3;0
sPositiveSign REG_SZ
sNegativeSign REG_SZ -
HKEY_CURRENT_USER\Control Panel\International\Geo
Nation REG_SZ 12
- in as far as anything is "standard" of course. I should point out
(although it's not relevant here) that I use imperial rather than metric
measure, much to the dismay of bureaucrats. "Heresy" they squawk...
So many retailers are so pushed for time that they can't afford to set
machines up to local standards. Consequently, "computer experts" insist that
the default date format/spelling dictionary or whatever is "computer
standard" and anyone who disputes their edict is automatically "rong."
billious
Such touching confidence in the comptence of Microsoft.
I believe that it was DOS6 where they decided that Australia's default
date-separator was "-" just like in the good ol' USofA...
And IIRC, they still insist on trying to impose a 12-hour clock - and the
daylight-savings scam is easy to apply. Turning it off if required - totally
another kettle of fish. Must admit it's been a while since I last installed
and configured a Windows system though, but when I was doing it three or
four times a day, following the procedure to choose the correct parameters
was wearing...
foxidrive
wrote:
>> Can you please paste the file.txt output into a reply? I seem to have
>> something odd here and I wanted to check a standard install for australia.
>>
>> @echo off
>> reg query "HKEY_CURRENT_USER\Control Panel\International" /s >file.txt
> iTimePrefix REG_SZ 1
>- in as far as anything is "standard" of course. I should point out
>(although it's not relevant here) that I use imperial rather than metric
>measure, much to the dismay of bureaucrats. "Heresy" they squawk...
Thanks Billious, everything on mine is the same except for iTimePrefix
which is 0 on mine.
I can't figure out how the day prefix on my %date% command has disappeared.
It reads "08/03/2010" instead of "Mon 08/03/2010" and this change happened
a few weeks ago... I have a backup batch file that sets a folder name to
something like "20100122-2154" and this changed with the day being dropped.
The shortdate dropdown box doesn't have any options for a leading day.
Very curious.
--
Regards,
Mic
Frank P. Westlake
> It reads "08/03/2010" instead of "Mon 08/03/2010" and this change
> happened
> a few weeks ago...
I hope that isn't my fault. When I began writing this date/time stuff
and asked for some testing by others I didn't initially account for
possible spaces in the value read from and restored to the Registry. I
don't know if any of those early scripts were sent here but it seems
likely.
Mine seems to be the reverse. If I specify the format "M/dd/yyyy" I get
"ddd M/dd/yyyy". If I add "ddd" to any format with "M" it doesn't matter
what position the "ddd" is in, the week name is always first.
Frank
Matt Williamson
"foxidrive" <got...@woohoo.invalid> wrote in message
I had that happen too. It seems to have taken place when I was playing
around with those settings,
although I took reg backups before any tweaking and restored them
afterwards.
So, I'm not sure what changed specifically but I wrote this to deal with it:
call :stripdate "%date%" %dtfix%
echo %dtfix%
pause& goto :eof
:stripdate
set dt=%~1&set dt1=%dt:~1,1%
echo=%dt1%|findstr "[^0-9]">nul
if not errorlevel 1 set dt=%dt:~4%
set dt=%dt:/=.%&set tm=%time%
set tm=%tm::=.%
set dtfix=%dt%%tm%
HTH
Matt
Dr J R Stockton
m>, Mon, 8 Mar 2010 09:45:47, foxidrive <got...@woohoo.invalid> posted:
>It reads "08/03/2010" instead of "Mon 08/03/2010" and this change happened
>a few weeks ago... I have a backup batch file that sets a folder name to
>something like "20100122-2154" and this changed with the day being dropped.
Never use the string resulting from DATE (and probably not that for
TIME) for anything important.
Instead (in a batch context) use cscript to run a short piece or
VBScript or JSCript to set a batch variable to YYYY-MM-DD hh:mm:ss,
which can be edited by standard means to get any desired Gregorian
date/time format.
As a luxury, the string could also contain the Week-numbering and
Ordinal Dates, yyyy-Www-d and yyyy-ddd.
See <URL:http://www.merlyn.demon.co.uk/batfiles.htm#WSH> for similar
examples.
--
(c) John Stockton, nr London UK. ?@merlyn.demon.co.uk DOS 3.3 6.20 ; WinXP.
Web <URL:http://www.merlyn.demon.co.uk/> - FAQqish topics, acronyms & links.
PAS EXE TXT ZIP via <URL:http://www.merlyn.demon.co.uk/programs/00index.htm>
My DOS <URL:http://www.merlyn.demon.co.uk/batfiles.htm> - also batprogs.htm.
Frank P. Westlake
> Mine seems to be the reverse. If I specify the format "M/dd/yyyy" I
> get "ddd M/dd/yyyy". If I add "ddd" to any format with "M" it doesn't
> matter what position the "ddd" is in, the week name is always first.
Now "M/dd/yyyy" is producing "M/dd/yyyy" as it should, and not "ddd
M/dd/yyyy" as it was. And I have not made any changes to the system. I
wonder if this is the same change your system experienced Mic. This is
frustrating. Now I have to somehow test "%DATE%" for "ddd" in every case
where the format includes a single "M", because the fix I made to
account for "ddd" is now failing.
I assume that Matt Williamson's system is back to normal now too. This
change occurred to three systems and two OSs (XP and Vista?) in a short
period of time of perhaps only a month. This short period of time has
one other date related event which might be relevant to the change, and
that is that February has a variable number of days. There could be some
other cause but the proximity in time with the leap year test suggests
it might be related. Fortunately this happened while I still have the
scripts fresh in mind so It will be easy to write a work-around.
Frank
Frank P. Westlake
> Now "M/dd/yyyy" is producing "M/dd/yyyy" as it should, and not "ddd
> M/dd/yyyy" as it was.
I was mistaken; it is still producing the error (inserting "ddd"). My
mistake was that I was looking at what my subroutine produced when I
told it to use the specified format and gave it a date to parse that was
in that format. The string I gave it did not have the erroneous "ddd" in
front so my subroutine read it wrong. So I still need to make a fix but
not for the reason I gave.
Frank
Frank P. Westlake
> "Frank P. Westlake" news:hn8gg6$ibi$1...@news.albasani.net...
>> Now "M/dd/yyyy" is producing "M/dd/yyyy" as it should, and not "ddd
>> M/dd/yyyy" as it was.
>
It seems that my error was that in one place I was using "M/dd/yyyy" and
in another I was using "M/d/yyyy"; in the first "dd" and in the second
"d". The single "d" causes the day-of-week to be prefixed to the date
string and when doubled it does not.
I'm still investigating but I wanted to get this out in case someone
else is looking into it.
Frank
Frank P. Westlake
> The single "d" causes the day-of-week to be prefixed to the date
> string and when doubled it does not.
This is occurring with all date formats I have tested, not just with the
single "M" formats.
As you've probably noticed Mic and Matt, this might be the cause of the
change on your machines. The single "d" was probably changed without
noticing it was different to a double "d", or vice versa, and the DOW
string was mysteriously removed or added.
Frank
foxidrive
Bingo! Thanks Frank.
--
Regards,
Mic