Created a WinPE USB boot device, but miss a control over CodePage ...
For testing a Disaster/Recovery situation, I boot from the USB, which is going smooth.
But when I need to enter special chr.'s somewhere in the test, it's a nightmare to find
these chr.'s, because ATI2020 use an other CodePage than mine on my PC.
Is there a way where I manualle can change this setting (Keyboard CP) ???
@ IanL-S
Thanks for your comment. Right now (testing DR) I just made a USB-boot with Rescue Media Builder (Simple)
to my USB stick. Booting up works well, but getting some other problems, which not includes the boot, but CP.
I'll try the other options with the Advanced WRE and ADK.
If your Windows language is not English-US, you can use the MVP Tool to build the WinRE media. The Tool will detect your OS language and give you the option to change the display and keyboard language in the WinRe media.
https://forum.acronis.com/forum/acronis-true-image-2019-forum/mvp-tool-custom-ati-winpe-builder
Paul, I was expecting that should be the case but out of abundant caution decided to defer to more knowledgeable users such as yourself.
Ian
@ Mustang,
Tried building a USB-boot with the MVP Tool:
Selected my system language, but it doesn't work as intended:
::=============================================================::
:: We've detected that that your system is not using ::
:: English [EN-US] as the default language. ::
:: ::
:: Would you like to create WinPE using your system language? ::
:: [EN-US is default for all ADK.] ::
::=============================================================::
:: ::
:: [1.] Yes - Build WinPE using my system language ::
:: [2.] No - Build WinPE with the default language [English] ::
:: ::
:::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
1
CodePage and Keyboard:
Input locale has been set to: en-GB
System locale has been set to: en-GB
User locale has been set to: en-GB
UI language has been set to: en-GB
The operation completed successfully.
My Win10 settings (Language and Keyboard Layout) is (in Danish):
DA-DK (primary)
UK-DK
UK-US
UK-UK
/Leif
Leif,
WinPE doesn't offer language support for DA-DK. Your best option would be to get a en-GB keyboard to use with WinPE.
@Mustang,
Dang =:-) When do MS learn .... weird world ;-)
Ok, then I have to remember this, booting for recovery:
1) Norton Ghost 15: a " \ " is a " ' " on my keyboard
2) Acronis 2020: a " \ " is a " < " on my keyboard
But then... why have the option in MVP Tool, to select system language - if it doesn't work ??
Leif,
I'm sure Mustang will reply but I believe the issue is that a DA-DK language pack is not available for WinPE. This is why he made the suggestion about changing the keyboard.
I looked at a recent ADK and have found that DA-DK is supported. Take a look at your ADK to see if DA-DK is supported. If it is, you can manually change the language.
Look at C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Windows Preinstallation Environment\amd64\WinPE_OCs. Do you see a da-dk folder? If you do, follow the steps below to change the WinPE language:
1. Put your USB WinPE drive in the computer and note the drive letter. I'll use F: in the steps below.
2. Create a folder named C:\mount
3. Open a command prompt as administrator.
4. Enter:
dism /Mount-Wim /WimFile:F:sources\boot.wim /Index:1 /MountDir:C:\mount
where F: is the drive letter of the USB WinPE drive.
5. Enter:
dism /Image:C:\mount /Add-Package /PackagePath:"C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Windows Preinstallation Environment\amd64\WinPE_OCs\da-dk\lp.cab"
6. Enter:
dism /Image:C:\mount /set-allintl:DA-DK
7. Enter:
dism /Unmount-Wim /MountDir:C:\mount /Commit
That should do it.
You asked why have the MVP Tool ask if you want to change the language if it doesn't work. It does for most languages.
You should create a batch file with the above command and save it so you don't have to type the commands all over again the next time you build a new recovery drive. Name the file something like:
Change_Language.bat
Then run the file from a command prompt opened as administrator.
@Mustang,
Thanks for your reply, much appreciated. I'll dig into this solution and let you know, how it goes.
Thanks - Leif
Think i'm (and you) are on the right track :-)
(se uploaded .jpg)
@Mustang,
Have created the "Change_Language.bat" with the commands inside. All went well, no problems.
But now I have some questions:
1) Do I run the "Change_Language.bat" before or after, I create a new USB-boot ??
2) If before, it doesn't help anything, as the USB-stick is formatted before the new creation.
3) Why not include the "Change_Language.bat" script in the MVP Tool, as there are lots of language folders.
(.jpg included)
/Leif
1. You need to run the bat file after the USB drive is created.
3. The MVP Tool already handles it correctly for most languages. DA-DK is an exception. Re-writing the MVP Tool to just add this one language is not an option at this time. I'll try to remember to add DA-DK when a future update is warranted.
@Mustang,
Still testing, but got into problems. Tried again to create a new USB-stick, and after that to run the "Change_Language.bat" as admin. Ups... only error's and a no go. Have looked into the logfile for DISM, but are totally overwhelmed by where to look for errors =:-)
Does the DISM commands need some more "cleanups", than just the "dism /Unmount-Wim /MountDir:C:\mount /Commit"
Have attached the text-file, running the DOS-command. Sorry, that it is a mix of DK versus US language :-(
It looks like the first time you ran the bat file the image didn't completely unmount. This can happen if Windows Explorer is open at the time you run the file. You can clean it up with the following command run from an administrative command prompt:
dism /Cleanup-MountPoints
Then check to make sure C:\mount is empty. That should fix it.
@Mustang,
I think you're right. When I run the command, I do it from Explorer and let it be opened under the creation.
Did a "dism /Cleanup-MountPoints" - but with no errors. After that I ran the the "Change_Language.bat" and all went well.
Tested the Recovery part of Acronis, booting from the USB, and now I dont have problems with special chr's.
Super :-)
Thanks again