Run Dos Programs In Winpeshl
Keyboard languages are a part of windows and not some kind of driver you can add. That would need to be built within the pre-installation environment that the recovery disc uses and there is no simple way to do that. When Ghost 15 was released I know it came in many different languages so I would assume the recovery discs were also available for the different languages and therefore keyboard layouts. I just looked on the Norton FTP site and the only Ghost recovery disk I can find is English US Canada. Do you happen to have a Finnish Ghost 15 CD?
I tried the system repair and received the winpeshl.ini present but no commands launched. For those of you that may run the Dell HW test, I received a 4C000:0522 error code interrupt controller not working (supposedly motherboard) AND error code 0600:5127 Cable Smart Card not detected. ISO file is not visible in this program ( unlike the tutorial shows ). Since that didn't. The XP run of this program gives me basically the same window that you see in my screen shot (background, transparent window). I select the. 'A winpeshl.ini file is present but no commands were successfully launched. It is started with a script with the following command: 'C: Program Files Symantec Ghost Ghostsrv.exe' 'C: Ghost Data Images G307_000.gho' LOADXP -HL200 –N2. Ghostcast server 11.5.0.2113 (GSS 2.5) need to use a WINPE 2.0 image to work correctely in running Ghost32 command with parameters.
If you do, try booting it. Windows PE is what they call a 'Pre-installation environment', it's a stripped down mini version of windows that can be run without needing to be setup or installed. It's similar to what is know known as a recovery environment. The Ghost 15 recovery disk uses the Vista SP2 version, also known as known as Windows PE 2.0 It's very limited on what it can do, it's not even close to a full featured version of windows.
How To Run Dos Programs
It's most commonly used by system administrators to deploy custom images to a lot of systems without worrying about the limitations that DOS boot discs had. Being a 32bit version of mini-windows it can access NTFS, SATA drives, and has support for much larger drives than DOS. I wrote a very long post here telling you how it could not be done without using or making a PE disk with the keyboard language you want. But looking at the recovery disk contents I just realized that it CAN be changed, you just can't have it boot into the desired layout without remaking it or changing it.
Dos Programs On Xp
See if this is acceptable to you, Boot the recovery disk and when you get to the main screen click Analyze Open a Command Shell Windows Type the following: wpeutil setkeyboardlayout 04b Press the enter button on the keyboard, if the command completes without an error close the command box and the next process started should be using a Finnish Keyboard. It's been so long that I made a recovery disc I don't remember that setting. But I'll look at it when I get a chance. We also happen to have an amazing expert with PE discs that might have some input. Remaking or altering Windows PE is very confusing and time consuming to say the least. I admit it took me the better part of a week to get working results the first time I tried.
But maybe there is a easy way to add that command or put the necessary files somewhere that enables the keyboard option. I'm pretty sure what I found above is undocumented, in all the years I have been here helping people with Ghost I have never seen that documented before. I just happened to notice by chance that the winpeutility was present in the build and ran it, low and behold it showed a whole bunch of keyboard layouts already present, maybe 50 or so. Stay tuned for possible future developments. Hi Red, wonder if you can give any suggestions.
I can't seem to script a command or run a.cmd file. I have tried winpeshl.ini and startnet.cmd and can't get either to run a cmd file (or it's being run too early in the load and something is changing it back). Also tried mounting and changing the default setting in the PE registry and even tired the startup folder of the default user.
Do you remember what worked for you to run a command? BTW- 7-zip now supports.wim files, I have been using it to open, edit, and add files without having to use imagex or dism. Does 7-zip do alright with bootable wim files? I guess it must. To be honest, it has been a LONG time since I have messed with WINPE. I think Deric had a similar situation and figured out a fix for it.
At the time I didn't even know that it mattered if you were from UK or US. What command did you put in winpeshl.ini? IIRC, it has to be very specific.
I think it has to call a program. I would have to read up on it. Can a custom SRD be made that changes keyboard layout? I wish they wouldn't have jacked up the forums here.
I cannot find ANYTHING like I used to be able to. Thanks for responding Red, I thought that last suggestion would work for sure but it didn't. By default the Winpeshi.ini file is LaunchApp AppPath =%SYSTEMROOT% shell sreshell.exe Since I'm trying to launch more than one item I have been changing LaunchApp to LaunchApps then I have tried putting my argument both before and after the recovery shell and with and without the AppPath = statement. In addition to yours I also tried,%windir% System32 cmd.exe, wpeutil setkeyboardlayout 04b and an assortment of bat and cmd files. I made a cmd file with this: wpeutil setkeyboardlayout 04b exit But I can't get it to run from the winpeshi.ini file, or any other place I tried like the program startup folder.
But the.cmd file is there, I can browse to it, run it, and the keyboard layout changes, I just can't for the life of me get it to run automatically. I figured I was maybe changing it but then something later on in the load was changing it back, or not running the command in the first place. Now I just tried launching notepad from winpeshi.ini and I can't get that to work either, even if I put that line after the shell command I can't see notepad so I assume it didn't run. But as for 7-zip, yes indeed it is able to not only open wim files, I can edit, change, delete, and add files to the wim and it saves them into the wim without effecting the boot or causing errors. It's very quick and easy to use ultraiso to extract the boot.wim file, then use 7-zip to open and change the wim file and use ultraiso again to delete the existing wim file and replace it with the one I just changed. I can make changes and re-boot the new iso in virtual pc within a couple minutes so I have been able to try a lot of different things (all failures but each and every time the recovery shell launches, I have yet to encounter a VISABLE error or hang.
I'm actually not setup for imagex anymore, I changed to a new computer since and have not needed to use it for anything. It was very confusing to me in the first place trying to do everything through a limited GUI or all from the command line. I looked and looked for your old posts about adding and changing things but could not find them either.:( What a waste of a whole lot of hard work. Thank you very much for your help Red, Dave. I never used DISM and had no idea it's part of Windows, I have it here on at least my Windows 7 system. I found these 2 articles.
That second article shows exactly what I was looking for, /Set-InputLocale: Sets the input locales and keyboard layouts to use in the offline Windows image. But then right below that section it states this The DISM International servicing commands cannot be used on a Windows Vista® or a Windows Server® 2008 image. The international commands can be used to change international settings only in Windows® 7 and Windows PE 3.0 images. The Intlcfg.exe tool is deprecated in this release but is still available for configuring international settings in Windows Vista® and Windows Server® 2008. For command-line syntax, see Intlcfg Command-Line Options.
For information about using Intlcfg.exe, see the Windows Vista SP1 release of the Windows OEM Preinstallation Kit (Windows OPK) or Windows Automated Installation Kit (Windows AIK). So then I find Inticfg documentation and it says this: Sets the default keyboard to use in the offline Windows image. Defaultkeyboarddescription Can be one of the following:. localename: keyboardlayout For example, 049. languagename For example, en-US You can specify more than one value by using semicolons as separators. This is useful when you want to include support for multiple keyboards on a single computer.
The first value for -inputlocale will be set as the default keyboard. The valid keyboard layouts that can be configured on your computer are listed in the following registry key. HKEYLOCALMACHINE SYSTEM ControlSet001 Control Keyboard Layouts For a list of the default input locale values, see. Use the hexadecimal value of the keyboard layout that you intend to configure. I already tried changing the PE's registry hive on that key, originally it only had a US keyboard present and changing that hex value didn't change the keyboard layout, the above leads me to believe that key maybe doesn't define the keyboard in use.
It just bugs me I cant figure it out. I have some virtual PC systems with Vista SP2 and possibly the WAIK somewhere around here on my old system that fried the motherboard, I was going to try to backup all my old virtual machines and tools from it but I couldn't find an IDE to USB case to access the drives.