offline
- Pridružio: 21 Nov 2005
- Poruke: 277
|
imam taj disk evo sad u racunaru i evo vam read me fajl:
Microsoft Windows XP Service Pack 2 (SP2), RTM
OEM Preinstallation Kit (OPK)
Readme Document
June 25, 2004
Information in this document, including URL and other Internet Web
site references, is subject to change without notice and is provided
for informational purposes only. The entire risk of the use or
results of the use of this document remain with the user, and
Microsoft Corporation makes no warranties, either express or implied.
Unless otherwise noted, the example companies, organizations,
products, people, and events depicted herein are fictitious. No
association with any real company, organization, product, person,
or event is intended or should be inferred. Complying with all
applicable copyright laws is the responsibility of the user. Without
limiting the rights under copyright, no part of this document may
be reproduced, stored in or introduced into a retrieval system, or
transmitted in any form or by any means (electronic, mechanical,
photocopying, recording, or otherwise), or for any purpose, without
the express written permission of Microsoft Corporation.
Microsoft may have patents, patent applications, trademarks,
copyrights, or other intellectual property rights covering subject
matter in this document. Except as expressly provided in any written
license agreement from Microsoft, the furnishing of this document
does not give you any license to these patents, trademarks,
copyrights, or other intellectual property.
All or portions of the OPK documentation may be provided in English
and other localized languages. If the documentation is provided in
more than one language, the language of the documentation that
matches the language of your license agreement specifies your
licensing requirements. Additional versions of the documentation
are provided in other languages solely for your convenience. On
localized versions of the OPK CD, English documentation is located
in the \Docs\English folder. If there are any discrepancies or
inconsistencies in the translation, the documentation that matches
the language of your license agreement controls.
(c) 2004 Microsoft Corporation. All rights reserved.
Microsoft, MS-DOS, Windows, and Windows NT are either registered
trademarks or trademarks of Microsoft Corporation in the United States
or other countries or regions.
The names of actual companies and products mentioned herein may be
the trademarks of their respective owners.
========================
How to Use This Document
========================
To view the Readme file in Microsoft Windows Notepad, maximize
the Notepad window. On the Format menu, click Word Wrap.
To print the Readme file, open it in Notepad or another word
processor, and then use the Print command on the File menu.
========
CONTENTS
========
1. INTRODUCTION
2. UPGRADING FROM PREVIOUS VERSIONS OF THE TOOLS
3. UPGRADING EXISTING CONFIGURATION SETS
4. KNOWN ISSUES
5. DOCUMENTATION CORRECTIONS
---------------
1. INTRODUCTION
---------------
This document provides current information about OEM preinstallation
of Microsoft Windows XP SP2.
For a summary of new features in the Windows OPK, see the "New
Features in the OEM Preinstallation Kit (OPK)" topic in the
OPK User's Guide (Opk.chm).
For an introduction to the OEM preinstallation process, see
the white paper, "Step-by-Step Guide to OEM Preinstallation of
Windows XP Service Pack 1 and Windows Server 2003 Family,"
located in the \Docs\Whitepapers folder on the Windows OPK CD.
For more information about the issues and corrections listed in
this readme, consult your Technical Account Manager (TAM) or visit
the Microsoft OEM Web site at: [Link mogu videti samo ulogovani korisnici]
------------------------------------------------
2. UPGRADING FROM PREVIOUS VERSIONS OF THE TOOLS
------------------------------------------------
Only one version of the OPK tools can be installed on the technician
computer. Except for Sysprep, each version of the OPK tools works
with previous versions of the Windows operating system as listed in
the following table:
OPK tools XP XP SP1 Server 2003 XP SP2 Server 2003 SP1
XP X
XP SP1 X X
Server 2003 X X X
XP SP2 X X X X
Server SP1 X X X X X
Sysprep should always be used with the version of the Windows
operating system on which it shipped, or with the latest service
pack for that specific version of the operating system.
Use the Mkimg tool from Windows PE XP SP2 only with
Windows XP SP2 to create Windows PE.
You can use the Windows XP SP2 OPK to preinstall the following
versions of Windows:
* Original "gold" release of Windows XP
* Windows XP SP1 and SP2
* Windows Server 2003 family
To preinstall the Windows Server 2003 Itanium-based client, use the
Windows Server 2003 SP1 Itanium-based tools.
Do not use the original "gold" release of Windows XP OPK to preinstall
the Windows Server 2003 family.
If you previously installed the OPK tools from the original "gold"
release of Windows XP or the Windows XP SP1 tools, you must upgrade
those tools to the Windows XP SP2 OPK; OPK tools from the original
"gold" release of Windows XP or the Windows XP SP1 tools cannot
coexist on the technician computer with tools from the
Windows XP SP2 OPK.
Do not upgrade an installation of the Windows Server 2003 OPK tools
to Windows Server 2003 SP1 Beta.
To upgrade the OPK tools from the "gold" release of Windows XP tools,
the Windows XP SP1 tools, or the Windows Server 2003 tools to
Windows XP SP2:
1. Run Opk.msi, located in the root of the Windows XP SP2 OPK CD.
Opk.msi is the autorun file that automatically starts when you
insert the CD.
2. When the "Welcome to the Windows OEM Preinstallation Kit" page
appears, click Next.
If you set up a distribution share with OPK tools from the original
"gold" Windows XP release or Windows XP SP1, the Guest account is
enabled.
Setting up a new distribution share with the Windows XP SP2 OPK
tools does not automatically enable the Guest account. Upgrading
the tools from the Windows XP OPK to the Windows XP SP2 OPK does
not change the properties of an existing distribution share.
----------------------------------------
3. UPGRADING EXISTING CONFIGURATION SETS
----------------------------------------
Upgrading to the Windows XP SP2 OPK tools does not change any
existing configuration sets, located in the \Cfgsets folder. Also,
upgrading to the Windows XP SP2 OPK tools does not change any
available Windows product files, located in the \Lang folder.
You must use the Product page in Setup Manager to load the
Windows product files for the newer versions of Windows, such
as Windows XP SP2 or members of the Windows Server 2003 family.
Upgrading to the Windows XP SP2 OPK updates the template files
that Setup Manager uses when creating a new configuration set.
Any new configuration sets created with the Windows XP SP2 Setup
Manager will use the default values obtained from these new
template files.
* To migrate a Windows XP or Windows XP SP1 configuration set to
preinstall Windows Server 2003
1. Open the configuration set in Setup Manager.
2. On the Product page, select the new product, Windows Server 2003.
3. Save the configuration set.
---------------
4. KNOWN ISSUES
---------------
* Adding Symbolic Names of Serial Ports to Windows PE
Windows PE does not create symbolic names such as COM1 and COM2
for serial ports. This means that applications cannot detect
and use the serial ports.
Workaround: To create the symbolic names, you can write an
application that calls the DefineDosDevice function and
uses the full device name of the port. Add this application to
Startnet.cmd so that it runs as part of the Windows PE boot
process. When the application is finished, applications
can detect the serial ports by their symbolic names.
You must add a registry key to your offline Windows PE image
before deploying it in order to use the serial ports.
1. Use Regedit to mount Setupreg.hiv in your offline image
to HKLM\test.
2. Add the following key:
HKLM\test\ControlSet001\Services\serial\Parameters
3. Unmount Setupreg.hiv.
The full device name of COM1 when using the ACPI
HAL is:
\\?\ACPI#PNP0501#1#{4D36E978-E325-11CE-BFC1-08002BE10318}
To identify the full device names for serial ports on other HALs,
use the QueryDosDevice function to search for the string "PNP0501".
To use serial ports in custom applications, either refer to the
ports by their full device names or use DefineDosDevice to create
the symbolic names as in this example:
#define COM_PORT_DEV_NAME(n) \
TEXT("\\\\?\\ACPI#PNP0501#") TEXT(#n) TEXT("#{4D36E978-E325
-11CE-BFC1-08002BE10318}")
#define COM_PORT_NAME(n) \
TEXT("COM") TEXT(#n)
DefineDosDevice( 0, COM_PORT_NAME(1), COM_PORT_DEV_NAME(1) );
* The [Components] topic in Winpe.chm is not indexed. Use the
Content or Search tabs in the HTML Help viewer to look up
optional components by name in Winpe.chm.
* The InputLocale entry in the [RegionalSettings] section of
Unattend.txt and Sysprep.inf can only be used to specify a maximum
of seven input locale and keyboard layout combinations.
Workaround:
See Knowledge Base article 325856 for how to specify regional
settings after Mini-Setup is finished.
* If Automatic Updates is turned on, either by setting
AutomaticUpdates = On in Unattend.txt or by using the "Help Protect
Your PC" page in Windows Welcome, and then Sysprep -reseal is run,
Automatic Updates will remain on.
* Support for both Chinese Traditional (Hong Kong S.A.R) (CHH) and
Chinese Traditional (Taiwan) (CHT) versions of Windows cannot be
added by using the OPK tools in the standard manner. You must
manually add support for both languages.
Workaround:
1. Install CHT OPK Tools or add language support for CHT.
2. Start the CHT Setupmgr.exe. Create a new configuration set or
edit an existing configuration set.
3. On the Tools menu, click "Manage Products."
4. Select "Chinese Traditional (Taiwan)" as Languages to install,
then click "Add Product."
5. Browse to the CHH Windows media or share location.
6. After you complete these steps, repeat step 4 to add more CHH
products (for example, any member of the Windows Server 2003
family).
7. Close the "Manage Products" window. Close Setup Manager.
8. Start Windows Explorer and browse to the "..\Opktools\lang"
folder.
9. Rename the "CHT" folder to "CHH."
10. Repeat steps 1-7 to add the CHT product. Now you have both CHT
and CHH products available on the technician computer.
To create a new configuration set for Hong Kong:
1. Start Setupmgr.exe and select "Create a new configuration set."
2. Proceed to the Target Language page and select "Chinese
Traditional (Hong Kong SAR)."
3. Proceed until you have finished creating a new configuration set
for CHH.
4. Repeat steps 1-2 to create a CHT configuration set, except select
"Chinese Traditional (Taiwan)" on the Target Language page.
You cannot add additional products to the \CHH folder after renaming
the \CHT folder to \CHH. To add additional products for CHH, you must
rename the \CHT folder to another name, such as "Temp," and rename
\CHH folder to \CHT. After renaming the folders, repeat steps 2-5 in
the previous procedure. After you complete steps 2-5, rename the \CHT
folder to \CHH and the Temp folder to \CHT.
* If you preinstall the Multilingual User Interface (MUI) Pack during
Sysprep in Factory mode (Sysprep -factory) and restart the computer
into Mini-Setup, then all pages in Mini-Setup are truncated.
Workaround: Set the default user interface for MUI to English.
* Do not manually modify the Windows installation when Sysprep is
running in Factory mode.
Workaround: Use Winbom.ini to modify the Windows installation when
you run Sysprep -factory.
-OR-
Use the command Sysprep -audit if you want to modify the Windows
installation manually.
* If the OPK tools are installed into a localized directory, and the
User Locale is changed to another language, the OPK help files cannot
be opened.
Workaround: Change the User Locale to match the language of the
localized directory.
* You can use Sysprep to install Test Certificates to enable testing
of drivers that are test signed by Windows Hardware Quality Lab (WHQL)
on an operating system image, even if the image has had Sysprep run
against it. See KB321559 for details.
* You cannot run Update.exe within an I386 directory to update a
Windows XP installation to Windows XP SP2. You must run Update.exe
against the entire contents of a Windows CD. If the entire contents
of a Windows CD is not present in your installation share, Update.exe
fails to complete the installation process.
* You cannot run Sysprep.exe on an installation of Windows XP SP1 that
was upgraded to Windows XP SP2 using Update.exe. Sysprep can be run
only on integrated ("slipstreamed") Windows installations.
* To update the Windows XP I386 directory properly
1. Download Windows XP Service Pack 2.
2. At the command prompt, go to the folder where you downloaded the
XPSP2.EXE file, and then type this command:
xpsp2.exe -x
3. When prompted, type the path from which you want the service pack
to be expanded. For example, type:
C:\XPSP2
4. Create a temporary directory on your system and copy the entire
Windows XP product CD to this directory. For example, type:
MD C:\INTSP2 XCopy CDROM Drive Letter:\*.* C:\INTSP2 /e
5. After the previous step is completed, change to the directory
that contains the Windows XP SP2 files. For example, type:
CD C:\xpsp2\update
6. To update the Windows XP files to include SP2, type:
update.exe -s c:\INTSP2
This procedure results in an I386 directory updated to Windows XP SP2.
* When performing an unattended installation with an answer file
that changes the input locale and uses GuiRunOnce to start a network
printer installation, the unattended installation process will hang
and the Event Viewer will report that the entry logs are broken.
Workaround: Use Cmdlines.txt to start the printer installation.
----------------------------
5. DOCUMENTATION CORRECTIONS
----------------------------
* In the "Customization Guidelines: Windows Software Components" topic
in Opk.chm, add the following:
Configuring the Display of the Bluetooth Icon
By default, the Bluetooth icon appears in the notification area only
when Bluetooth events occur, because usability studies have shown that
users prefer an uncluttered notification area. Although Microsoft
does not recommend changing this default behavior, you can configure
Windows to always display the Bluetooth icon in the notification area
to increase the user's awareness of this feature. To change the default
behavior, set the value of the BluetoothTaskbarIcon entry equal to 1
in the [Shell] section of the Winbom.ini file.
* In the "Preinstalling Applications Using Legacy Techniques" topic
in Opk.chm, replace:
You cannot use [GuiRunOnce] to enable the execution of shells,
other programs, and so on, during the end-user boot, except as
noted in Chapter 1 of this guide.
with
You cannot use [GuiRunOnce] to enable the execution of shells,
other programs, and so on, during the end-user boot, except as
noted in "Requirements for Customizing Windows" in
"Preinstallation Requirements and Customization Guidelines".
* The [WinPE] topic does not list the OptionalSources entry.
OptionalSources
Used when preinstalling Tablet PC or Media Center components as
part of a configuration set.
Syntax
OptionalSources = Yes
Value
Yes
Use the \Cmpnents folder as part of the configuration set.
Example
OptionalSources = Yes
WinbomType
WinPE
Comments
Requires the addition of the \Cmpnents folder containing the Tablet PC
or Media Center files to your configuration set. For more information,
see the installation instructions on the Tablet PC or Media Center CDs.
* In the "Mkimg Command" topic, delete the following sentence:
Use /NOWF only when running server applications such as IIS
on the Windows PE computer.
* The Winpeshl.ini answer file is not listed in the "windows PE Answer
Files" section. For instructions on how to use it, see the "Using a
Custom Shell Application" section of the "Creating a Customizable
Windows PE Image" topic.
* The Windows PE User Guide does not include a topic on the Depend
tool. Located in the \Winpe folder, it identifies missing DLL
dependencies for windows PE applications.
Syntax:
depend [/s] [/l] /f:filespec;filespec;... [/d:directory;directory;..]
/s ;Silent mode.
/l ;List all dependencies
If directories are not specified, the Windows search path will be
used to look for dependencies.
Error codes:
0 = OK
1 = errBAD_ARGUMENTS
2 = errFILE_NOT_FOUND
3 = errFILE_LOCKED
4 = errMISSING_DEPENDENCY
5 = errOUT_OF_MEMORY
Example:
To make sure all DLLs required by Myapp.exe are in your Windows PE
image, run Depend with these parameters:
depend /l /f:c:\winpe\i386\system32\myapp.exe /d:c:\winpe\
i386\system32
* Using Multiple Static IP Addresses
You may now specify multiple static IP addresses for as many
network cards as may be installed in the computer. The syntax for
this functionality is identical to existing documentation; append
additional addresses to existing entries, using a semicolon to
separate multiple addresses.
This example installs DHCP to the first network card found in the
system, applies static IP addresses to the next two detected cards,
and applies DHCP to any additional networking cards.
[WinPE.NET]
Startnet = YES
Ipconfig = DHCP;10.1.100.2;1.2.3.4
SubnetMask = DHCP;255.255.248.0;255.248.255.1
Gateway = DHCP;10.1.101.2;10.1.101.3
* Adding INRAM functionality to Windows PE
The functionality of the /INRAM option of the Osloadoptions command
of the [InfChanges] section of Config.inf has changed. Windows PE
fully loads Win32K.sys into memory, resulting in an improved
CD-swapping experience for recovery scenarios.
To enable INRAM support, add this option to the Osloadoptions command
in the [InfChanges] section of Config.inf:
/INRAM
Example:
Osloadoptions=txtsetup.sif,setupdata,"/fastdetect /minint
/redirect /redirectbaudrate=115200 /INRAM"
* In the OEM Preinstallation Reference (Ref.chm), the functionality
of the AllowConnections entry of the [TerminalServices] section in the
Unattend.txt answer file has changed. If you specify the following:
[TerminalServices]
AllowConnections = 1
Remote Desktop will be enabled during unattended Setup. However,
Remote Desktop will not be added to the Windows Firewall Exceptions
list. The following entries represent the mimimum required entries
in the Unattend.txt answer file to enable Remote Desktop during
unattended Setup and add Remote Desktop to the Windows Firewall
Exceptions list:
[WindowsFirewall]
Profiles = Standard (specify a user-defined profile name)
[WindowsFirewall.Standard]
Services = RemoteDesktop (specify a user-defined service name)
[WindowsFirewall.RemoteDesktop]
Type = 2
[TerminalServices]
AllowConnections = 1
For details on Windows Firewall settings, see the [WindowsFirewall]
sections and entries in the Unattend.txt chapter of the
OEM Preinstallation Reference (Ref.chm).
|
