Location and Language Bar Setup

[Guest]

In our unattended deployment of Windows XP SP2 I have set all available
Regional Settinggs as follows:

[RegionalSettings]
LanguageGroup=1
SystemLocale=00000809
UserLocale=00000809
InputLocale=0809:00000809

In order to make the machine entirely United Kingdom.

Yet when the machine is built the "Location" (Under Regional and Language
Options > Regional Options) is set to United States and The Language Bar is
present with English (United States) available?!?!

How do I change these in an Automated Deployment? Its frustrating me as I
cannont find information anywhere!

Many Thanks,

Danny Russell

 

[Guest]

Is there no-one who can help me? PLEASE!

 

[David Chadwick]

Hi Danny,

I've NEVER found an answer to this problem.

I'm in Australia and have the exact same issue. However, for me my Location
does correctly set itself to "Australia" but the damn "English (United
States)" input locale is always there.

I've had this problems for years and never had a satisfactory solution.
I've worked in several huge companies in Australia and everytime I arrive
somewhere new I check out their build system to see if they've solved it,
and they never have.

The strange thing is that there aren't many people on the Net complaining
about it. Sure you can find the odd message here and there, but not the
volume that I would expect for what is essentially an extremely annoying and
pretty bad bug. It makes me scream to see the "EN" next to the system tray
when it doesn't need to be there but doesn't seem to bother anyone else.

As for why I am successful in getting the Location right when you are not,
try this:

Instead of specifying the SystemLocal, UserLocale and InputLocale seperately
remove all three of those lines and add a single line which says
"Language=00000809" and see if that helps. This is meant to be functionally
the same as using the three lines that you have used. This is how I do it
for my language (00000c09) and the Location works.

Yet another bug as an aside - if you RDP to a server from an PC set to
"English (Australian)" the resulting terminal server session is always in
"English (United States)" with "English (Australian)" as an option. You can
set it to Australian until the cows come home but it will only remain that
way for that session. This is the case whether you are RDPing to Windows
2000, 2003 or even XP.

Cheers,
David


In our unattended deployment of Windows XP SP2 I have set all available
Regional Settinggs as follows:

[RegionalSettings]
LanguageGroup=1
SystemLocale=00000809
UserLocale=00000809
InputLocale=0809:00000809

In order to make the machine entirely United Kingdom.

Yet when the machine is built the "Location" (Under Regional and Language
Options > Regional Options) is set to United States and The Language Bar is
present with English (United States) available?!?!

How do I change these in an Automated Deployment? Its frustrating me as I
cannont find information anywhere!

Many Thanks,

Danny Russell

 

[Guest]

Hi David,

That worked for the Location! Nice one! As for the Language Bar, I guess
I'll just have to keep on fighting that one... its irritating the hell out of
me though! I'll let you know if I get anywhere with that...

Thanks for your help mate,

Danny

Hi Danny,

I've NEVER found an answer to this problem.

I'm in Australia and have the exact same issue. However, for me my Location
does correctly set itself to "Australia" but the damn "English (United
States)" input locale is always there.

I've had this problems for years and never had a satisfactory solution.
I've worked in several huge companies in Australia and everytime I arrive
somewhere new I check out their build system to see if they've solved it,
and they never have.

The strange thing is that there aren't many people on the Net complaining
about it. Sure you can find the odd message here and there, but not the
volume that I would expect for what is essentially an extremely annoying and
pretty bad bug. It makes me scream to see the "EN" next to the system tray
when it doesn't need to be there but doesn't seem to bother anyone else.

As for why I am successful in getting the Location right when you are not,
try this:

Instead of specifying the SystemLocal, UserLocale and InputLocale seperately
remove all three of those lines and add a single line which says
"Language=00000809" and see if that helps. This is meant to be functionally
the same as using the three lines that you have used. This is how I do it
for my language (00000c09) and the Location works.

Yet another bug as an aside - if you RDP to a server from an PC set to
"English (Australian)" the resulting terminal server session is always in
"English (United States)" with "English (Australian)" as an option. You can
set it to Australian until the cows come home but it will only remain that
way for that session. This is the case whether you are RDPing to Windows
2000, 2003 or even XP.

Cheers,
David


In our unattended deployment of Windows XP SP2 I have set all available
Regional Settinggs as follows:

[RegionalSettings]
LanguageGroup=1
SystemLocale=00000809
UserLocale=00000809
InputLocale=0809:00000809

In order to make the machine entirely United Kingdom.

Yet when the machine is built the "Location" (Under Regional and Language
Options > Regional Options) is set to United States and The Language Bar is
present with English (United States) available?!?!

How do I change these in an Automated Deployment? Its frustrating me as I
cannont find information anywhere!

Many Thanks,

Danny Russell

 

[David Chadwick]

Hi Danny,

It irritates me too.

I was mucking around with it today and I think I have worked out what causes
it and how to fix it. However, it's not really an elegant solution.

My belief is that (by testing myself and researching) there is no "proper"
solution. There is no way to come out of an unattended installation without
"English (United States)" being there as an available input locale. I am
only talking about with an English copy of XP and using unattend.txt to
specify "00000c09" as the language. Other combinations I cannot comment
about.

However, by deleting a registry key I can essentially fix it. I'm not sure
if this really counts as a solution as I'm not using pure unattend.txt
commands. I am deleting something after the build has completed rather than
finding a solution within the build process.

My "kludge" solution:
Logon to newly built PC
Open regedit
Highlight HKEY_LOCAL_MACHINE
Choose "File", "Load Hive"
Navigate to C:\Documents and Settings\Default User\NTUSER.DAT (you have to
enable hidden files to see this directory)
Name it anything you want
Navigate to HKEY_LOCAL_MACHINE\<whatever you named it>\.DEFAULT\Keyboard
Layout\Preload
You should find two values here; 1 is your language and 2 is US (409)
Delete the key called 2 (assuming this is the US one)
Highlight <whatever you named it>
Choose "File", "Unload Hive"

I'm not sure if these three steps are required:
Nagivate to HKEY_USERS\.DEFAULT\Keyboard Layout\Preload
You should find two values here; 1 is your language and 2 is US (409)
Delete the key called 2 (assuming this is the US one)

Now when I login as a new user I don't have both input locales. I still
need to stuff around to work out how to turn off the language bar by default
as well I think. It's late so I'll do that tomorrow.

I've only done very preliminary testing but it does seem to work. I also
assume that I can integrate this registry key deletion into the unattend.txt
process somehow (by scripting something in [GuiRunOnce], or adding a command
to commands.txt). I haven't mucked around with this yet.

I consider this to be a workaround rather than a solution. A solution would
be a proper configuration in unattend.txt that worked. I posted this only
to show you the registry key that is causing the problem. Whether this can
be prevented in the first place is the real challenge.

Cheers,
David


Hi David,

That worked for the Location! Nice one! As for the Language Bar, I guess
I'll just have to keep on fighting that one... its irritating the hell out
of
me though! I'll let you know if I get anywhere with that...

Thanks for your help mate,

Danny

Hi Danny,

I've NEVER found an answer to this problem.

I'm in Australia and have the exact same issue. However, for me my
Location
does correctly set itself to "Australia" but the damn "English (United
States)" input locale is always there.

I've had this problems for years and never had a satisfactory solution.
I've worked in several huge companies in Australia and everytime I arrive
somewhere new I check out their build system to see if they've solved it,
and they never have.

The strange thing is that there aren't many people on the Net complaining
about it. Sure you can find the odd message here and there, but not the
volume that I would expect for what is essentially an extremely annoying
and
pretty bad bug. It makes me scream to see the "EN" next to the system
tray
when it doesn't need to be there but doesn't seem to bother anyone else.


As for why I am successful in getting the Location right when you are not,
try this:

Instead of specifying the SystemLocal, UserLocale and InputLocale
seperately
remove all three of those lines and add a single line which says
"Language=00000809" and see if that helps. This is meant to be
functionally
the same as using the three lines that you have used. This is how I do it
for my language (00000c09) and the Location works.

Yet another bug as an aside - if you RDP to a server from an PC set to
"English (Australian)" the resulting terminal server session is always in
"English (United States)" with "English (Australian)" as an option. You
can
set it to Australian until the cows come home but it will only remain that
way for that session. This is the case whether you are RDPing to Windows
2000, 2003 or even XP.

Cheers,
David


In our unattended deployment of Windows XP SP2 I have set all available
Regional Settinggs as follows:

[RegionalSettings]
LanguageGroup=1
SystemLocale=00000809
UserLocale=00000809
InputLocale=0809:00000809

In order to make the machine entirely United Kingdom.

Yet when the machine is built the "Location" (Under Regional and Language
Options > Regional Options) is set to United States and The Language Bar
is
present with English (United States) available?!?!

How do I change these in an Automated Deployment? Its frustrating me as I
cannont find information anywhere!

Many Thanks,

Danny Russell