From: Ilya Zakharevich on 3 Jan 2010 21:27 I cannot manage to build BartPE in a way which allows perl (AS flavor) to run without warnings about (rephrasing): setting locale failed reverting to "C" locale Somebody knowing a workaround? Some environment missing, or do I need some more "language support" components? Thanks, Ilya P.S. I'm getting similar warnings from some other Unixish projects (e.g., Hugin)...
From: Keith R. Watson on 5 Jan 2010 09:50 Ilya Zakharevich <nospam-abuse(a)ilyaz.org> wrote in news:slrnhk2khf.ppg.nospam-abuse(a)powdermilk.math.berkeley.edu: > I cannot manage to build BartPE in a way which allows perl (AS flavor) > to run without warnings about (rephrasing): > > setting locale failed > reverting to "C" locale > > Somebody knowing a workaround? Some environment missing, or do I need > some more "language support" components? > > Thanks, > Ilya > > P.S. I'm getting similar warnings from some other Unixish projects > (e.g., Hugin)... > Ilya, BartPE by default does not have locale information. You can use the following plugin to add locale information to Windows XP: http://www.cc.gatech.edu/~krwatson/files/locale_defaults.zip The locale settings in the plugin are for the United States. If you need the settings for a different locale you will need to find a system configured the way you want, capture the registry settings, and edit the Locale_Defaults.inf file. The settings in the [Default.AddReg] section come from HKEY_CURRENT_USER\Control Panel\International The settings in the [SetupReg.AddReg] section come from HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\Nls Use RegEdit to export the registry settings to a .reg file then use the following web site to convert the settings to the BartPE .inf file format. http://vb.nl.eu.org/homepage/reg2peinf.aspx You can get help with the BartPE .inf file format here: http://www.nu2.nu/pebuilder/help/english/pluginformat.htm keith -- Keith R. Watson Georgia Institute of Technology Systems Support Specialist IV College of Computing keith.watson(a)cc.gatech.edu 801 Atlantic Drive NW (404) 385-7401 Atlanta, GA 30332-0280
From: Ilya Zakharevich on 5 Jan 2010 10:38 On 2010-01-05, Keith R. Watson <keith.watson(a)cc.gatech.edu> wrote: > BartPE by default does not have locale information. You can use the > following plugin to add locale information to Windows XP: > > http://www.cc.gatech.edu/~krwatson/files/locale_defaults.zip A lot of thanks! I did not try it yet - I do not have BartPE-Builder configured to run under BartPE yet, so would need to run real Windows at some moment to rebuild... > The locale settings in the plugin are for the United States. If you need > the settings for a different locale you will need to find a system > configured the way you want, capture the registry settings, and edit the > Locale_Defaults.inf file. > > The settings in the [Default.AddReg] section come from > HKEY_CURRENT_USER\Control Panel\International > > The settings in the [SetupReg.AddReg] section come from > HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\Nls > > Use RegEdit to export the registry settings to a .reg file then use the > following web site to convert the settings to the BartPE .inf file format. Why? Cannot BartPE "just load the .reg" file at runtime? And, btw, would not BartPE-builder be able to emit .reg for a certain subtree automatically? Yours, Ilya
From: Keith R. Watson on 6 Jan 2010 12:26 Ilya Zakharevich <nospam-abuse(a)ilyaz.org> wrote in news:slrnhk6n7g.1o8.nospam-abuse(a)powdermilk.math.berkeley.edu: > On 2010-01-05, Keith R. Watson <keith.watson(a)cc.gatech.edu> wrote: >> BartPE by default does not have locale information. You can use the >> following plugin to add locale information to Windows XP: >> >> http://www.cc.gatech.edu/~krwatson/files/locale_defaults.zip > > A lot of thanks! I did not try it yet - I do not have BartPE-Builder > configured to run under BartPE yet, so would need to run real Windows > at some moment to rebuild... > >> The locale settings in the plugin are for the United States. If you >> need the settings for a different locale you will need to find a >> system configured the way you want, capture the registry settings, >> and edit the Locale_Defaults.inf file. >> >> The settings in the [Default.AddReg] section come from >> HKEY_CURRENT_USER\Control Panel\International >> >> The settings in the [SetupReg.AddReg] section come from >> HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\Nls >> >> Use RegEdit to export the registry settings to a .reg file then use >> the following web site to convert the settings to the BartPE .inf >> file format. > > Why? Cannot BartPE "just load the .reg" file at runtime? During the Windows install process it ask several questions that tell it how to set up locale. The BartPE utility builds a bootable Windows CD using a Windows install CD and some external plugins, it doesn't actually run the Windows installer so the locale questions never get asked. You could try the following: 1. Put the .reg files on a USB flash drive. 2. Plug the flash drive into the machine 3. Boot the machine with the BartPE CD. 4. Import the .reg files This would give the machine running the BartPE CD the locale registry settings. However, I don't know if the locale settings take effect immediately or not. Some registry keys work as soon as you change them in the registry and others require telling the operating system to reload their settings from the registry. You could try it and see if it works. The down side is you would always have use the USB flash drive to load the .reg files every time you boot. If you use the plugin it adds the registry keys to the BartPE image so they work every time without the flash drive. > > And, btw, would not BartPE-builder be able to emit .reg for a certain > subtree automatically? When you the BartPE utility runs it gets the Windows files from a Windows install CD and not from the machine the utility is running on. There are not registry keys on the Windows install CD for it to export. > > Yours, > Ilya > keith -- Keith R. Watson Georgia Institute of Technology Systems Support Specialist IV College of Computing keith.watson(a)cc.gatech.edu 801 Atlantic Drive NW (404) 385-7401 Atlanta, GA 30332-0280
From: Ilya Zakharevich on 7 Jan 2010 18:59 On 2010-01-06, Keith R. Watson <keith.watson(a)cc.gatech.edu> wrote: >> Why? Cannot BartPE "just load the .reg" file at runtime? > You could try the following: .... > 3. Boot the machine with the BartPE CD. > 4. Import the .reg files This is exactly the procedure I was asking about. So why did your plugin goes in circles (via the main HIV of BartPE) instead of going this itself (only, of course, automated)? This might add half-a-second to boot time, but would make customization so much easier... > settings. However, I don't know if the locale settings take effect > immediately or not. Some registry keys work as soon as you change them in > the registry and others require telling the operating system to reload > their settings from the registry. You could try it and see if it works. AHA! This might answer my question... Unfortunately, right now I do not have a Windows machine at hand to export the .reg file (I would use US)... On the other hand, switching users may switch the locale at runtime, right? So it looks like this setting MUST have immediate effect. >> And, btw, would not BartPE-builder be able to emit .reg for a certain >> subtree automatically? > When you the BartPE utility runs it gets the Windows files from a Windows > install CD and not from the machine the utility is running on. There are > not registry keys on the Windows install CD for it to export. My question was, in fact, more about "tools" than about the actually used procedure. Are there command-line tools to emit the .reg file for the given subtree of a running system? I see that you explicitly mention Perl in your plugin. It may be simpler with Perl, right? Thanks again, Ilya P.S. I have not googled for it yet, but maybe people here know right away about installing keyboard layouts with BartPE?
|
Next
|
Last
Pages: 1 2 Prev: Errors during PersistentPerl Compilation Next: passing argument to a subroutine |