Leaked source code of windows server 2003
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

401 lines
19 KiB

  1.  Read Me First for
  2. Microsoft Windows Multilingual User Interface Pack
  3. for
  4. Microsoft(R) Windows(R) Server 2003, Standard Edition
  5. Microsoft(R) Windows(R) Server 2003, Enterprise Edition
  6. Microsoft(R) Windows(R) Server 2003, Datacenter Edition
  7. Microsoft(R) Windows(R) Server 2003, Web Edition
  8. March 2003
  9. -----------------------------------------------------------------------------------
  10. Read Me First
  11. -----------------------------------------------------------------------------------
  12. Welcome to the Microsoft Windows Server 2003 family Multilingual User Interface
  13. (MUI) Pack release. This document provides late-breaking or other information that
  14. supplements the documentation in Microsoft Windows Server 2003 family.
  15. Print and read this document for critical pre-installation information concerning
  16. this product release.
  17. After you install the Windows Multilingual User Interface Pack, print and read the
  18. Release Notes files:
  19. * Relnotes.htm located on MUI CD1
  20. * MSINotes.htm located on MUI CD1
  21. For the latest information about MUI, be sure to visit the following Web site:
  22. http://www.microsoft.com/globaldev/DrIntl/faqs/MUIFaq.mspx
  23. -----------------------------------------------------------------------------------
  24. CONTENTS
  25. -----------------------------------------------------------------------------------
  26. 1. ABOUT THE MICROSOFT WINDOWS MULTILINGUAL USER INTERFACE (MUI) PACK
  27. 2. INSTALLING MUI FROM MUI CDs
  28. 3. SUPPORTED PLATFORMS
  29. 4. UPGRADING TO THE WINDOWS SERVER 2003 MUI PACK FROM WINDOWS 2000 MUI VERSION
  30. 5. INSTALLING MUI IN UNATTEND MODE
  31. 6. DEPLOYING MUI BY USING REMOTE INSTALLATION SERVICE
  32. 7. ABOUT THE MICROSOFT .NET FRAMEWORK LANGUAGE PACK
  33. 8. ABOUT THE MAPPOINT CATEGORIZATION SCHEMES IN UDDI SERVICES
  34. 9. ABOUT THE MICROSOFT EAST ASIAN PRINTER DRIVER PACK
  35. 10. COPYRIGHT
  36. -----------------------------------------------------------------------------------
  37. 1. ABOUT THE MICROSOFT WINDOWS MULTILINGUAL USER INTERFACE (MUI) PACK
  38. -----------------------------------------------------------------------------------
  39. The MUI Pack will only work on top of Windows Server 2003 family. It should not be
  40. installed on top of Windows XP or any other release. Information regarding
  41. supported platforms and available languages in the following sections are provided
  42. for reference purposes.
  43. The Windows Server 2003 family operating systems provide extensive support for
  44. international users, addressing many multilingual issues such as regional
  45. preferences, fonts, keyboard layouts, sorting orders, date formats and Unicode
  46. support.
  47. The Windows Multilingual User Interface Pack builds on top of this support by adding
  48. the capability to switch the user interface (menus, dialogs and help files) from one
  49. language to another. This feature helps make administration and support of
  50. multilingual computing environments much easier by:
  51. * Allowing servers to be shared by users who speak different languages
  52. * Facilitating the roll-out of one system company-wide, with the addition of user
  53. interface languages as they become available.
  54. * Allowing the same US English service pack to update all machines
  55. The Windows Multilingual User Interface Pack allows each user of a server to select
  56. one of the installed user interface languages. This selection is then stored in
  57. their user profile. When a user logs on, the appearance of the system and the help
  58. files associated with the system components change to the selected language. (Note
  59. that this is not quite the same as running a localized version. The Multilingual
  60. User Interface Pack is based on the English version of Windows Server 2003 family.)
  61. The ability to read and write documents in each of the languages supported by
  62. Windows Server 2003 family is a feature of every version of Windows Server 2003
  63. family, not just of the Windows Multilingual User Interface Pack. However, the
  64. ability to switch user interface languages is only provided by the Windows
  65. Multilingual User Interface Pack.
  66. The following languages will be supported by MUI: Arabic, Brazilian Portuguese,
  67. Czech, Danish, Dutch, Finish, French, German, Greek, Hebrew, Hungarian, Italian,
  68. Japanese, Korean, Norwegian, Polish, Portuguese, Russian, Simplified Chinese,
  69. Spanish, Swedish, Traditional Chinese and Turkish. Localization coverage is
  70. different depending on the language. The Arabic, Danish, Finish, Greek, Hebrew and
  71. Norwegian MUI packages only offer localization coverage for the client features.
  72. On Datacenter Edition, only French, German, Japanese, and Spanish will be able to
  73. display a localized user interface for Datacenter Server-specific features.
  74. -----------------------------------------------------------------------------------
  75. 2. INSTALLING MUI FROM MUI CDs
  76. -----------------------------------------------------------------------------------
  77. Before you install any of the files from the Windows Multilingual User Interface
  78. Pack CDs, you must complete the installation of Windows from the English version of
  79. Windows Server 2003 family CDs.
  80. There are two ways to install/deploy MUI pack:
  81. 1. Running MUISETUP.EXE from the MUI CDs:
  82. Each MUI CD includes a group of different MUI language support files. You will only
  83. be able to install the languages that are included on the CD at one time. If you
  84. want to install languages included on another CD, please run the MUISETUP.EXE from
  85. that CD. You have to use this method if you want to:
  86. a. Install multiple languages at the same time.
  87. b. Access some advanced settings, such as "UI Font" setting or "Language for
  88. non-Unicode programs"
  89. c. Deploy MUI by using unattended mode or remote installation service.
  90. You can click the "Help" button on the MUISETUP.EXE screen to learn how to use
  91. MUISETUP.EXE.
  92. 2. Installing MUI through Windows Installer
  93. The Windows Server 2003 family Multilingual User Interface Pack now packages the
  94. user interface languages as Windows Installer .MSI files. These new Windows
  95. Installer packages offer several alternatives for deploying and installing user
  96. interface languages.
  97. Please refer to the msinotes.htm file for more descriptions about this method.
  98. To find out which CD includes which UI language files, you can browse the CD to see
  99. which .MSI files included on the CD. The file name is based on each Language ID
  100. (LangID). The UI languages and their MSI file names are listed below:
  101. Filename
  102. <langID>.MSI <Lang> Language
  103. 0401.msi    ARA Arabic
  104. 0405.msi    CS Czech
  105. 0406.msi    DA Danish
  106. 0413.msi    NL Dutch
  107. 040b.msi    FI Finnish
  108. 040c.msi    FR French
  109. 0407.msi    GER German
  110. 0408.msi    EL Greek
  111. 040d.msi    HEB Hebrew  
  112. 040e.msi    HU Hungarian
  113. 0410.msi    IT Italian  
  114. 0411.msi    JPN Japanese
  115. 0412.msi    KOR Korean
  116. 0414.msi    NO Norwegian  
  117. 0415.msi    PL Polish  
  118. 0416.msi    BR Portuguese (Brazil)
  119. 0816.msi    PT Portuguese (Portugal)
  120. 0419.msi    RU Russian  
  121. 0804.msi    CHS Chinese (Simplified) 
  122. 0c0a.msi    ES Spanish
  123. 041d.msi    SV Swedish  
  124. 0404.msi    CHT Chinese (Traditional) 
  125. 041f.msi    TR Turkish
  126. This list is just for reference purposes; MUI language packs will be released at
  127. staggered intervals after the release of Windows Server 2003. Please visit
  128. http://www.microsoft.com/globaldev/DrIntl/faqs/MUIFaq.mspx for more details about
  129. the supported language list in Windows Server 2003 MUI language packs and their
  130. release schedule.
  131. -----------------------------------------------------------------------------------
  132. 3. SUPPORTED PLATFORMS
  133. -----------------------------------------------------------------------------------
  134. This release of the Windows Multilingual User Interface Pack only works with the
  135. Windows Server 2003 family.
  136. The 32-bit MUI package can only be installed on 32-bit Windows. There is a 64-bit
  137. MUI package to install on 64-bit Windows.
  138. The number of supported MUI languages on 64-bit will be different from 32-bit
  139. version. German, Japanese, Korean, French, Spanish and Italian will be the only
  140. 64-bit MUI packs available for the Windows Server 2003 release.
  141. -----------------------------------------------------------------------------------
  142. 4. UPGRADING TO THE WINDOWS SERVER 2003 MUI PACK FROM WINDOWS 2000 MUI VERSION
  143. -----------------------------------------------------------------------------------
  144. Windows Server 2003 Setup will remove old Windows 2000 MUI support files but will
  145. not automatically add the Windows Server 2003 MUI support files during the upgrade
  146. process. You must install the Windows Server 2003 MUI files from MUI CDs just as
  147. you would on a new installation of Windows Server 2003. The same applies when
  148. upgrading from beta versions of Windows Server 2003 MUI.
  149. We recommend that you set the UI language to English before upgrading the Windows
  150. 2000 MUI system to Windows Server 2003.
  151. You can use the following unattended mode process to add the new MUI files
  152. automatically during the upgrade process.
  153. -----------------------------------------------------------------------------------
  154. 5. INSTALLING MUI PACK IN UNATTEND MODE
  155. -----------------------------------------------------------------------------------
  156. The following steps explain how to install the Windows MUI Pack in unattended mode.
  157. 1. Copy all the MUI files from MUI CDs into a temporary directory on a network
  158. share, such as $OEM$\MUIINST.
  159. In this example, we use a server \\MUICORE. The directory for the MUI CD contents
  160. will be \\MUICORE\UNATTEND\$OEM$\MUIINST.
  161. 2. Add a "Cmdlines.txt" file in \\muicore\UNATTEND\$OEM$ that includes the following
  162. lines:
  163. [Commands]
  164. "muiinst\muisetup.exe [/i LangID1 LangID2 ...] [/d LangID] /r /t"
  165. Note that you must specify " " in your cmdlines.txt file. Use the appropriate
  166. Language IDs, and the muisetup command line parameters to ensure a quiet
  167. installation. Please check muisetup.hlp for a complete description of all the
  168. command line parameters for muisetup.exe (the command line help content is under
  169. "related topics" in the help.).
  170. 3. Create an answer file (mui.txt):
  171. a. add the following entries in the "Unattended" section
  172. [Unattended]
  173. OemPreinstall=Yes
  174. OemFilesPath=\\muicore\unattend
  175. OemSkipEula=YES
  176. "OemFilesPath" must point to a network share or drive containing the MUI install
  177. source stored in the above directory structure.
  178. The Windows install sources can be anywhere else (CD, network share, etc).
  179. b. add a "RegionalSettings" section. Use this section to specify the Language Groups
  180. and locales to install. Use the appropriate Language Group IDs and Locale IDs
  181. (LCIDs). Ensure that the Language Groups you install are sufficient to cover BOTH
  182. the locale settings and the user interface languages you are installing.
  183. Example:
  184. [RegionalSettings]
  185. LanguageGroup="5","8","13"
  186. Language="0401"
  187. Of course, the answer file may also include other OS unattended setup options.
  188. 4. Run winnt32.exe with the appropriate options to use the answer file. If you
  189. require the installation of East Asian language and locale support, you must specify
  190. /copysource:lang or /rx:lang to copy the necessary language files. If you do not,
  191. and the [RegionalSettings] section of your answer file contains East Asian values,
  192. Setup will ignore everything in the [RegionalSettings] section.
  193. For Winnt32.exe, the appropriate syntax is:
  194. winnt32.exe /unattend:"path to answer file" /copysource:lang /s:"path to install
  195. source"
  196. -----------------------------------------------------------------------------------
  197. 6. DEPLOYING MUI BY USING REMOTE INSTALLATION SERVICE
  198. -----------------------------------------------------------------------------------
  199. The following steps explain how to deploy MUI by using Windows Server Remote
  200. Installation Service (RIS). (RIS requirements: Domain Controller running Active
  201. Directory, DHCP server, DNS server, NTFS partition to hold OS images.)
  202. 1. Install Remote Installation Services using the Windows Component Wizard.
  203. 2. Run Risetup.exe. RIS will create a flat image from the CD or network share as
  204. follows:
  205. \Remote installation share\Admin
  206. \OAChooser
  207. \Setup
  208. \tmp
  209. The image is kept in the I386 directory under \Setup (such as \Setup\<OS Locale>
  210. \Images\<Directory name>\I386).
  211. 3. Follow instructions on KB: Q241063 to install additional language support.
  212. 4. Follow instructions on KB: Q304314 to deploy Windows images to client desktop
  213. computers.
  214. 5. Add the following section into the ristndrd.sif (under \Setup\<OS Locale>
  215. \Images\<Directory Name>\I386\Templates) to enable OEM installation
  216. [Unattended]
  217. OemPreinstall=Yes
  218. [RegionalSettings]
  219. LanguageGroup=1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17
  220. ; Language support pack are needed depending on (Q241063 explains how to do
  221. this)
  222. ; UI language you will be installing, please consult unattended document for
  223. more information.
  224. 6. Add $OEM$ directory at the same level as the \I386 image directory that contains
  225. the following installation source
  226. \Setup\<OS Locale>\Images\<Directory Name>
  227. |-\I386
  228. |-\$OEM$
  229. |-\cmdlines.txt (OEM answer file)
  230. |-\MUIINST
  231. In cmdlines.txt, you will need the following structure to start installation of MUI.
  232. The MUIINST folder will include MUI files copied from MUI CD root folder.
  233. [Commands]
  234. "muiinst\muisetup.exe /i <LCID> <LCID> [/d <LCID>] /r /t"
  235. Note that you will need to add "" in as indicate above.
  236. -----------------------------------------------------------------------------------
  237. 7. ABOUT THE MICROSOFT .NET FRAMEWORK LANGUAGE PACK
  238. -----------------------------------------------------------------------------------
  239. .NET Framework localized resources are included with this CD. You will need to
  240. install the .NET Framework Language Pack if you build or run applications using the
  241. .NET Framework and you wish to see errors generated by the .NET Framework in the
  242. current user interface language.
  243. The .NET Framework package is called LangPack.MSI and is located in the MUI CDs in
  244. the netfx\<lang> folders, i.e: the LangPack.MSI for Japanese is located in
  245. netfx\jpn. Please refer to section 2 for the language list.
  246. To install the package, copy the MSI and CAB files to your machine, right click on
  247. the MSI package, select Install and follow the wizard instructions.
  248. You should only install this package after the Windows Multilingual User Interface
  249. pack has been successfully installed. Please reboot the machine if prompted by MUI
  250. installation before installing the .NET Framework Language Pack.
  251. -----------------------------------------------------------------------------------
  252. 8. ABOUT THE MAPPOINT CATEGORIZATION SCHEMES IN UDDI SERVICES
  253. -----------------------------------------------------------------------------------
  254. UDDI Services can only host one MapPoint Categorization Scheme at a time. If you
  255. install MUI onto a system hosting UDDI Services, the MapPoint Categorization Schemes
  256. language is not changed. If you want UDDI Services to host a different language of
  257. the MapPoint Categorization Scheme, you can import a localized scheme using either
  258. the UDDI Services Web user interface, or the bootstrap.exe command-line tool.
  259. Note: You must have Administrator permissions on the computer hosting the UDDI
  260. Services database components to complete this process.
  261. To import data using the UDDI Services Web user interface:
  262. - Open your Web browser and navigate to the UDDI Services Web user interface. For
  263. example http://<servername>/uddi
  264. - On the UDDI Services menu, click Coordinate.
  265. - Click Data Import.
  266. - Click Browse and then select the MapPoint Categorization Scheme you want to
  267. import.
  268. - Click Open, and then click Import
  269. To import data from the command-line using bootstrap.exe:
  270. - From the computer hosting the UDDI Services database components, copy the MapPoint
  271. categorization scheme you want to import into the \inetpub\uddi\bin\ directory.
  272. - Click Start and select Run.
  273. - Type: CMD and click OK.
  274. - Change to the \inetpub\uddi\bin\ directory. For example, type: CD
  275. %systemdrive%\inetpub\uddi\bin
  276. - Type: bootstrap.exe /f <MapPoint Categorization Scheme filename>
  277. Localized versions of the MapPoint Categorization Scheme can be found on the Web at:
  278. http://go.microsoft.com/fwlink/?linkid=5202&clcid=0x409
  279. -----------------------------------------------------------------------------------
  280. 9. ABOUT THE MICROSOFT EAST ASIAN PRINTER DRIVER PACK
  281. -----------------------------------------------------------------------------------
  282. MUI CD1 includes the East Asian Printer Driver Pack. This driver pack provides
  283. support for printer models which are only generally available in East Asia and thus
  284. only in the localized East Asian versions of the Windows Server 2003 family. By
  285. installing the East Asian Printer Driver Pack, you can add support for printer
  286. models which are not included with the US English version of Windows Server 2003
  287. family.
  288. For more information about the East Asian Printer Driver Pack files pack, see the
  289. readme.txt file included on the printer folder in CD1.
  290. -----------------------------------------------------------------------------------
  291. 10. COPYRIGHT
  292. -----------------------------------------------------------------------------------
  293. This document provides late-breaking or other information that supplements the
  294. documentation provided on the US English OS CD of the Microsoft Windows Server 2003
  295. Multilingual User Interface Pack.
  296. Information in this document, including URL and other Internet Web site references,
  297. is subject to change without notice and is provided for informational purposes only.
  298. The entire risk of the use or results of the use of this document remains with the
  299. user, and Microsoft Corporation makes no warranties, either express or implied.
  300. Unless otherwise noted, the example companies, organizations, products, domain
  301. names, e-mail addresses, logos, people, places and events depicted herein are
  302. fictitious, and no association with any real company, organization, product, domain
  303. name, e-mail address, logo, person, place or event is intended or should be
  304. inferred. Complying with all applicable copyright laws is the responsibility of the
  305. user. Without limiting the rights under copyright, no part of this document may be
  306. reproduced, stored in or introduced into a retrieval system, or transmitted in any
  307. form or by any means (electronic, mechanical, photocopying, recording, or
  308. otherwise), or for any purpose, without the express written permission of
  309. Microsoft Corporation.
  310. Microsoft may have patents, patent applications, trademarks, copyrights, or other
  311. intellectual property rights covering subject matter in this document. Except as
  312. expressly provided in any written license agreement from Microsoft, the furnishing
  313. of this document does not give you any license to these patents, trademarks,
  314. copyrights, or other intellectual property.
  315. (c) 2003 Microsoft Corporation. All rights reserved.
  316. Microsoft, ActiveSync, IntelliMouse, MS-DOS, Windows, Windows Media, and Windows NT
  317. are either registered trademarks or trademarks of Microsoft Corporation in the
  318. United States and/or other countries.
  319. The names of actual companies and products mentioned herein may be the trademarks of
  320. their respective owners.
  321. <RTM.RV1.05.25>