regional setting

  • Thread starter Thread starter gs
  • Start date Start date
G

gs

what registry controls regional settings?

Specifically I want to create a batch file or script to set region to
Canada,
US measurement,
time to HH:mm.ss
short date to yyyy-MM-dd
I know I can manually set via control panel, regional, but I would like to
automate this part for deployment
also to fix some rather "stubborn account" that otherwise works as expected
 
thank you very much. I did successfully set the values as verified by reg
query


However, there are accounts still have the default display date format for
explorer. What else govern date and time format?
 
sLongDate
http://www.microsoft.com/resources/documentation/Windows/2000/server/reskit/en-us/regentry/34666.asp

sTimeFormat
http://www.microsoft.com/resources/documentation/Windows/2000/server/reskit/en-us/regentry/69552.asp

Keep in mind that...

The HKEY_CURRENT_USER key contains the user profile for the user who is
currently logged on to the computer.

The HKEY_USERS\Security ID (SID)# key is for a particular user, whether
logged on or not.

This key lists all of the SIDs.
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList

To tell which user has which SID, click on each SID, look at
ProfileImagePath, the Data has the user name at the end of the path. I.e.
%SystemDrive%\Documents and Settings\Wesley P. Vogel

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In
 
thank you very much for the info.
in the problematic account, I did reg query: "HKCU\Control
Panel\International"
and I got
! REG.EXE VERSION 3.0

HKEY_CURRENT_USER\Control Panel\International
iCountry REG_SZ 2
iCurrDigits REG_SZ 2
iCurrency REG_SZ 0
iDate REG_SZ 2
iDigits REG_SZ 2
iLZero REG_SZ 1
iMeasure REG_SZ 1
iNegCurr REG_SZ 1
iTime REG_SZ 1
iTLZero REG_SZ 1
locale REG_SZ 00001009
sCountry REG_SZ Canada
sDate REG_SZ -
sDecimal REG_SZ .
sLanguage REG_SZ ENC
sList REG_SZ ,
sLongDate REG_SZ MMMM d, yyyy
sShortDate REG_SZ yyyy-MM-dd
sThousand REG_SZ ,
sTime REG_SZ :
sTimeFormat REG_SZ HH:mm:ss
iTimePrefix REG_SZ 0
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 6
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

Despite I have
sShortDate REG_SZ yyyy-MM-dd
sDate REG_SZ -


C:\>date
The current date is: Fri 03/17/2006
Enter the new date: (mm-dd-yy)

Is it the "iDate REG_SZ 2" giving me hassle? or is the format I
choosssen is not supported by seting the registry? The format I chose works
with other accounts in the same workgroup PC.
Actually all the regional settings are identical to the account that the
works with regional setting.
 
Beats me.

iDate
Data type Range Default value
REG_SZ 0 | 1 | 2 0

Value Meaning
0 mm/dd/yy
1 dd/mm/yy
2 yy/mm/dd <-----

REG_SZ 2 is a valid setting.

This may apply...
[[Regional Options in Control Panel links the sDate and sShortDate values.
This ensures that the date separator and the date format are synchronized.

Setting sTime and sTimeFormat independently in the registry *can* result in
conflicting values. To repair these settings, use Regional Options in
Control Panel.

Setting only one value in the registry might not change the date as it
appears in applications, because an application can read either sDate or
sShortDate.]]
from...
sDate
http://www.microsoft.com/resources/documentation/Windows/2000/server/reskit/en-us/regentry/34662.asp

Day, Month, Year and Time Format
http://www.microsoft.com/resources/...000/server/reskit/en-us/regentry/datetime.asp

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In
 
finally, I got figure out - sort of.

If I set sShortDate REG_SZ yy-MM-dd
instead of sShortDate REG_SZ yyyy-MM-dd
then explorer will show with date format of yyyy-MM-dd and the command
prompt date will use
yy-MM-DD

Go figure. I thought I got the reg setting from a working account and
should have worked but ended kludging the value to fit the iDate

I hope no one else will fall for the same trap. There must be something
else undocumented that controls the international setting. the problem
account has the symptoms of not allowing regional setting via the control
panel GUI interface.


Wesley Vogel said:
Beats me.

iDate
Data type Range Default value
REG_SZ 0 | 1 | 2 0

Value Meaning
0 mm/dd/yy
1 dd/mm/yy
2 yy/mm/dd <-----

REG_SZ 2 is a valid setting.

This may apply...
[[Regional Options in Control Panel links the sDate and sShortDate values.
This ensures that the date separator and the date format are synchronized.

Setting sTime and sTimeFormat independently in the registry *can* result
in
conflicting values. To repair these settings, use Regional Options in
Control Panel.

Setting only one value in the registry might not change the date as it
appears in applications, because an application can read either sDate or
sShortDate.]]
from...
sDate
http://www.microsoft.com/resources/documentation/Windows/2000/server/reskit/en-us/regentry/34662.asp

Day, Month, Year and Time Format
http://www.microsoft.com/resources/...000/server/reskit/en-us/regentry/datetime.asp

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In
gs said:
thank you very much for the info.
in the problematic account, I did reg query: "HKCU\Control
Panel\International"
and I got
! REG.EXE VERSION 3.0

HKEY_CURRENT_USER\Control Panel\International
iCountry REG_SZ 2
iCurrDigits REG_SZ 2
iCurrency REG_SZ 0
iDate REG_SZ 2
iDigits REG_SZ 2
iLZero REG_SZ 1
iMeasure REG_SZ 1
iNegCurr REG_SZ 1
iTime REG_SZ 1
iTLZero REG_SZ 1
locale REG_SZ 00001009
sCountry REG_SZ Canada
sDate REG_SZ -
sDecimal REG_SZ .
sLanguage REG_SZ ENC
sList REG_SZ ,
sLongDate REG_SZ MMMM d, yyyy
sShortDate REG_SZ yyyy-MM-dd
sThousand REG_SZ ,
sTime REG_SZ :
sTimeFormat REG_SZ HH:mm:ss
iTimePrefix REG_SZ 0
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 6
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

Despite I have
sShortDate REG_SZ yyyy-MM-dd
sDate REG_SZ -


C:\>date
The current date is: Fri 03/17/2006
Enter the new date: (mm-dd-yy)

Is it the "iDate REG_SZ 2" giving me hassle? or is the format
I choosssen is not supported by seting the registry? The format I chose
works with other accounts in the same workgroup PC.
Actually all the regional settings are identical to the account that the
works with regional setting.
Click to expand...
Click to expand...
 
the problem
account has the symptoms of not allowing regional setting via the control
panel GUI interface.
Click to expand...

Do you mean that Regional and Language Options (intl.cpl) won't open or that
some settings are unavailable?

If intl.cpl won't run.

Check
Group Policy
Administrative Templates\Control Panel\Hide specified Control Panel applets
and
HKLM\Software\Microsoft\Windows\CurrentVersion\
Policies\Explorer\DisallowCpl
and
HKEY_CURRENT_USER\Software\Microsoft\
Windows\CurrentVersion\Policies\Explorer\DisallowCpl

Group Policy
Administrative Templates\Control Panel\Show only specified Control Panel
applets
and
HKLM\Software\Microsoft\Windows\CurrentVersion\
Policies\Explorer\RestrictCpl
and
HKEY_CURRENT_USER\Software\Microsoft\
Windows\CurrentVersion\Policies\Explorer\RestrictCpl

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In
gs said:
finally, I got figure out - sort of.

If I set sShortDate REG_SZ yy-MM-dd
instead of sShortDate REG_SZ yyyy-MM-dd
then explorer will show with date format of yyyy-MM-dd and the command
prompt date will use
yy-MM-DD

Go figure. I thought I got the reg setting from a working account and
should have worked but ended kludging the value to fit the iDate

I hope no one else will fall for the same trap. There must be something
else undocumented that controls the international setting. the problem
account has the symptoms of not allowing regional setting via the control
panel GUI interface.


Wesley Vogel said:
Beats me.

iDate
Data type Range Default value
REG_SZ 0 | 1 | 2 0

Value Meaning
0 mm/dd/yy
1 dd/mm/yy
2 yy/mm/dd <-----

REG_SZ 2 is a valid setting.

This may apply...
[[Regional Options in Control Panel links the sDate and sShortDate
values. This ensures that the date separator and the date format are
synchronized.

Setting sTime and sTimeFormat independently in the registry *can* result
in
conflicting values. To repair these settings, use Regional Options in
Control Panel.

Setting only one value in the registry might not change the date as it
appears in applications, because an application can read either sDate or
sShortDate.]]
from...
sDate
http://www.microsoft.com/resources/documentation/Windows/2000/server/reskit/en-us/regentry/34662.asp

Day, Month, Year and Time Format
http://www.microsoft.com/resources/...000/server/reskit/en-us/regentry/datetime.asp

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In
gs said:
thank you very much for the info.
in the problematic account, I did reg query: "HKCU\Control
Panel\International"
and I got
! REG.EXE VERSION 3.0

HKEY_CURRENT_USER\Control Panel\International
iCountry REG_SZ 2
iCurrDigits REG_SZ 2
iCurrency REG_SZ 0
iDate REG_SZ 2
iDigits REG_SZ 2
iLZero REG_SZ 1
iMeasure REG_SZ 1
iNegCurr REG_SZ 1
iTime REG_SZ 1
iTLZero REG_SZ 1
locale REG_SZ 00001009
sCountry REG_SZ Canada
sDate REG_SZ -
sDecimal REG_SZ .
sLanguage REG_SZ ENC
sList REG_SZ ,
sLongDate REG_SZ MMMM d, yyyy
sShortDate REG_SZ yyyy-MM-dd
sThousand REG_SZ ,
sTime REG_SZ :
sTimeFormat REG_SZ HH:mm:ss
iTimePrefix REG_SZ 0
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 6
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

Despite I have
sShortDate REG_SZ yyyy-MM-dd
sDate REG_SZ -


C:\>date
The current date is: Fri 03/17/2006
Enter the new date: (mm-dd-yy)

Is it the "iDate REG_SZ 2" giving me hassle? or is the
format I choosssen is not supported by seting the registry? The format
I chose works with other accounts in the same workgroup PC.
Actually all the regional settings are identical to the account that the
works with regional setting.


sLongDate
Click to expand...
http://www.microsoft.com/resources/documentation/Windows/2000/server/reskit/en-us/regentry/34666.asp
sTimeFormat
Click to expand...
http://www.microsoft.com/resources/documentation/Windows/2000/server/reskit/en-us/regentry/69552.asp
Keep in mind that...

The HKEY_CURRENT_USER key contains the user profile for the user who is
currently logged on to the computer.

The HKEY_USERS\Security ID (SID)# key is for a particular user, whether
logged on or not.

This key lists all of the SIDs.
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows
NT\CurrentVersion\ProfileList

To tell which user has which SID, click on each SID, look at
ProfileImagePath, the Data has the user name at the end of the path.
I.e. %SystemDrive%\Documents and Settings\Wesley P. Vogel

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In gs <[email protected]> hunted and pecked:
thank you very much. I did successfully set the values as verified by
reg
query


However, there are accounts still have the default display date format
for
explorer. What else govern date and time format?

HKEY_CURRENT_USER\Control Panel\International

See this.
Click to expand...
http://www.microsoft.com/resources/documentation/Windows/2000/server/reskit/en-us/regentry/34646.asp
See these:
iCountry
iMeasure
iDate
sDate

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In gs <[email protected]> hunted and pecked:
what registry controls regional settings?

Specifically I want to create a batch file or script to set region
to
Canada,
US measurement,
time to HH:mm.ss
short date to yyyy-MM-dd
I know I can manually set via control panel, regional, but I would
like to
automate this part for deployment
also to fix some rather "stubborn account" that otherwise works as
expected
Click to expand...
Click to expand...
Click to expand...
 
Back
Top