Question in Windows XP Multilingual User Interface

[nonone]

hi everyone

I am new here and I need your help please >

I have a question .

I want to know haw can I install (Windows XP Multilingual User Interface Pack)

In silent mode (Unattended mode )

Here the instruction but I couldn’t do it so please help me ( step by step )

And don't forget that I am new not professional like most of you

instruction:

=========================================================================
5.0  INSTALLING MUI PACK IN UNATTEND MODE
=========================================================================

The following steps explain how to install the Windows MUI Pack in unattend mode. 

1. Copy all the MUI files from MUI CDs into a temporary directory on a 
network share, such as $OEM$\MUIINST. 

In this example, we use a server \\MUICORE. The directory for the MUI CD 
contents will be \\MUICORE\UNATTEND\$OEM$\MUIINST.

2.  Add a "Cmdlines.txt" file in \\muicore\UNATTEND\$OEM$ that includes 
the following lines:

[Commands]
"muiinst\muisetup.exe [/i LangID1 LangID2 ...] [/d LangID] /r /s"

Note that you must specify " " in your cmdlines.txt file. Use the 
appropriate Language ID (LANGID)s, and the muisetup command line 
parameters to ensure a quiet installation. Please check muisetup.hlp 
for a complete description of all the command line parameters for 
muisetup.exe (the command line help content is under "related topics" 
in the help.). 

3. Create an answer file (mui.txt): 

a. add the following entries in the "Unattended" section

   [Unattended]
    OemPreinstall=Yes
    OemFilesPath=\\muicore\unattend
    OemSkipEula=YES

"OemFilesPath" must point to a network share or drive containing the 
MUI install source stored in the above directory structure. 

The Windows install sources can be anywhere else (CD, network share, etc).

b. add a "RegionalSettings" section. Use this section to specify the Language 
Groups and locales to install. Use the appropriate Language Group IDs and 
Locale IDs (LCIDs). Ensure that the Language Groups you install are sufficient 
to cover BOTH the locale settings and the User Interface languages you 
are installing. 

    Example: 
    [RegionalSettings]
    LanguageGroup="5","8","13"
    Language="0401"

Of course, the answer file may also include other OS unattended setup options. 

4. Run winnt32.exe with the appropriate options to use the answer file. If you 
require the installation of East Asian language and locale support, you must 
specify /copysource:lang or /rx:lang to copy the necessary language files. 
If you do not, and the [RegionalSettings] section of your answer file contains 
East Asian values, Setup will ignore everything in the [RegionalSettings] section. 

For Winnt32.exe, the appropriate syntax is:
 winnt32.exe /unattend:"path to answer file" /copysource:lang /s:"path to install source"


=========================================================================
6.0  DEPLOYING MUI BY USING REMOTE INSTALLATION SERVICE
=========================================================================
The following steps explain how to deploy MUI by using Windows Server¡¯s Remote 
Installation Service (RIS). ( RIS requirements:  Domain Controller running Active 
Directory, DHCP server, DNS server, NTFS partition to hold OS images. )

1. Install Remote Installation Services using the Windows Component Wizard. 
2. Run Risetup.exe. RIS will create a flat image from the CD or network share as follows:
   \Remote installation share\Admin
                             \OSChooser
                             \Setup
                             \tmp

   The image is kept in the I386 directory under 
   \Setup (such as \Setup\<OS Locale>\Images\<Directory name>\I386 ). 

3. Follow instructions on KB: Q241063 to install additional languages.
4. Follow instructions on KB: Q287545 or manually copy asms directory form CD 
   or network share into the I386 directory of the image.

5. Add the following section into the ristndrd.sif 
   (under \Setup\<OS Locale>\Images\<Directory Name>\I386\Templates) to enable 
   OEM installation

	[Unattended]
        OemPreinstall=Yes

	[RegionalSettings]
	LanguageGroup=1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17 

; Language support pack are needed depending on (Q241063 explains how to do this)
; UI language you will be install, please consult 
; unattended document for more information.

6. Add $OEM$ directory at the same level as the \I386 image directory that contains 
   the following installation source
     \Setup\<OS Locale>\Images\<Directory Name>
                                                |-\I386
                                                |-\$OEM$
                                                      |-\cmdlines.txt (OEM answer file)
                                                      |-\MUIINST

   In ¡°cmdlines.txt¡±, you will need the following structure to start installation of
   MUI. The MUIINST folder will include MUI files copied from MUI CD root folder. 

	[Commands]
	"muiinst\muisetup.exe /i <LCID> <LCID> /d <LCID> /r /s"
   
   Note that you will need to add ¡°¡± in as indicate above.

waiting for you

thanks in advance

[nonone]

say something please

[nonone]

say something please

[CuBie]

Go through it and then tell us the step u get stuck at - you cant just ask a general question like u did!

I will be more than glad to help if have have a more specific question!

Later,

Chris!

[enuffsaid]

removed

[nonone]

Go through it and then tell us the step u get stuck at - you cant just ask a general question like u did!

I will be more than glad to help if have have a more specific question!

Later,

Chris!

thanks CuBie ( I went through it ) but I coudn't come back till now

enuffsaid+ CuBie thank you very much 4 trying helping me >

I have been trying for 4 days but I coudn't make it

so what I have to write in winnt.sif or svcpack.inf exactly ?

I understand that I have 2 make a file in $oem$ dir.

as microsoft said Cmdlines.txt . and I did but no change > everytime I install windows but no change >so please tell me what I have to write exactly and where I have to save the files >

thanks again enuffsaid+ CuBie

forgive me I am not a professional like most of you.

[Aaron]

Most MSI packages have trouble being installed during GUI-mode setup. Try installing this this on first logon via [GuiRunOnce] or RunOnceEx

[nonone]

thanks AaronXP for visiting my poor post

I Add this line in winnt.sif

[GuiRunOnce]

"%windir%\MUITEMP\muiinst\MUISETUP.exe -i 0401 0409 -d 0409 -r -s"

"%windir%\SYSTEM32\CMD.EXE /c RMDIR %WINDIR%\MUITEMP /s /q"

and in dir. $OEM$ I add 2 txt flies 

mui.txt

[unattended]

OemPreinstall=Yes

OemFilesPath=\MUIINST\unattend

OemSkipEula=YES

and also Cmdlines.txt

[Commands]

"muiinst\muisetup.exe /i 0401 0409 /d 0409 /r /s"

I get an error message ( I attached it )

please download it and tell me what I have to do

thank you

[enuffsaid]

removed

[nonone]

sorry dear friend for not replying to you that's because I was busy .so forgive me .

enuffsaid:

question nr.2 the original installation language of your WindowsXP CD is English.

question nr.1 : I put my MUI files in $OEM$. download my Attachment you will find a screenshot .

please enuffsaid tell me where I have to put this command

winnt32.exe /unattend:"mui.txt" /copysource:"lang" /copydir:"MUITEMP" /s:"path to install source"

where I have to save and what I have to write in "path to install source" ???

thanks in advance

[ToBe]

This is what I have found out for mui installation on Windows 2003 Server, should put you on the right track:

In your cmdlines.txt, put this:

[Commands]
"muiinst\muisetup.exe -i 041d -d 041d -r -s"

(Somehow the /i /r and /s switches didn't work, but -i -r and -s did?)

And in my $OEM$ folder I have a folder called muiinst with the mui-files. remember to put:

[Unattended]
oempreinstall=YES

in your winnt.sif.

I don't use the OemFilesPath= switch since it works this way...

To get the keyboard layout working this is how I've done:

Under the GUIRunOnce in winnt.sif I put:

[GUIRunOnce]
%windir%\system32\regopts.bat

create a folder called $$ in your $OEM$ folder and place a file called regopts.bat in there. Put this in your regopts.bat:

@echo off
title Configuring keyboardlayout
rundll32.exe shell32,Control_RunDLL intl.cpl,,/f:"%windir%\system32\regopts.txt"
exit

then create a file called regopts.txt in the $$-folder and put this in it:

[RegionalSettings]
    LanguageGroup=1
    Language=041d
    SystemLocale=041d
    UserLocale=041d
    InputLocale=041d:0000041d
    UserLocale_DefaultUser=041d
    InputLocale_DefaultUser=041d:0000041d
    MUILanguage=041d
    MUILanguage_DefaultUser=041d

Replace the 041d with your language code... This is working, but took me some time to figure it out...

Your paths doesn't look right:

%windir%\MUITEMP\muiinst\ points to c:\windows\MUITEMP\muiinst when it should point to c:\muiinst. (if you have a folder in your $OEM$ called muiinst windows will copy it to the root of the harddrive during installation)

and OemFilesPath=\MUIINST\unattend points to c:\MUIINST\unattended which doesn't exist...

This is the content of my muiinst folder:

[enuffsaid]

removed

[nonone]

thanks alot ToBe and enuffsaid

finally it works with me > God keeps you All >

Cheers

[-= Mancubus =-]

@ ToBe

---------

Well...

Suffer from inability to point correct regional settings.

I made everything exactly according to your post, and Location was set correctly this time.

But Regional Setting parameter itself is still set to USA :o/

What am I doing wrong?

[what3v3r]

@ ToBe

---------

Well...

Suffer from inability to point correct regional settings.

I made everything exactly according to your post, and Location was set correctly this time.

But Regional Setting parameter itself is still set to USA :o/

What am I doing wrong?

<{POST_SNAPBACK}>

are your keyboard settings correct?

try setting everything as you like, and then export these registry paths:

HKEY_CURRENT_USER\Keyboard Layout\Preload

HKEY_CURRENT_USER\Control Panel\International

HKEY_CURRENT_USER\Control Panel\International\Geo

apply these registry settings on your next reinstall, and see if it works now

Edited July 14, 2005 by what3v3r