I'm trying to install XP with a Microsoft preinstallation CD and I don't know what step 2 is. I boot the computer with the preinstall disk and I get to a "D:\i386\system32>" and I'm lost. Could someone tell me what next
If for some reason you can't see the .doc file, this is what it says:
<i>"Folder Structure for Windows XP OEM Preinstallation Kit CD
The main structure for the Microsoft Windows XP OPK CD is as follows (but is subject to change):
\DOCS—Opk.chm and Ref.chm OPK online documentation files
\I386—Fonts, INF, and System 32 information used during preinstallation
\SAMPLES—Samples to use to build your own Internet service provider signup information
\SBSI—Step-By-Step Interactive files
\TOOLS—Tools such as Cvtarea.exe, Factory.exe, Netcfg.exe, Oformat.com, Setupcl.exe, and Sysprep.exe
\WINPE—Windows Preinstallation Environment files
\WIZARD—Generic Oeminfo.ini, Oobeinfo.ini, Opkinput.inf, Setupmgr.exe, Unattend.txt, and Winbom.ini files
You must create at least one configuration set to preinstall Microsoft Windows XP. Use Setup Manager Wizard to create the configuration set. A configuration set is a directory structure containing all files you add to your installation, including Windows Welcome customizations; answer files (such as Unattend.txt, Sysprep.inf, Oobeinfo.ini, and Winbom.ini), preinstalled applications, and additional hardware drivers. You need to create only one configuration set for each configuration you manufacture. Use the set repeatedly as you preinstall Windows. See <A HREF="http://members.microsoft.com/partner/products/windows/w..." target="_new">Checklist: Items to Prepare for Building Master Installation</A> to make sure you haven't forgotten anything that belongs in the configuration set.
The computer on which you install Setup Manager. Normally, the configuration sets and the distribution share are located on this computer.
A fully assembled computer containing a master installation.
The computers on which you preinstall Windows to be distributed to customers.
Windows XP Preinstallation Tools and File Descriptions
Setup Manager Tool (Setupmgr.exe)
Use Setup Manager to create or modify the files contained in a configuration set.
Setup Manager does not affect the system files of the technician computer on which the tool is run. Setup Manager manages the directory structure that contains the configuration set but does not actually run Windows Setup. Create only one configuration set for each computer type you manufacture. You then can use the set repeatedly as you preinstall Windows. You can modify the baseline configuration set to accommodate differences in preinstalled applications and other variations.
You do not need to specify all of your customizations using Setup Manager. Instead, you can create a configuration set in Setup Manager and then manually edit one of the preinstallation text files in the configuration set (such as Unattend.txt, Sysprep.inf, Oobeinfo.ini, or Winbom.ini). If you later open that configuration set in Setup Manager, the tool displays your changed settings. For more information, see “Structure and Content of a Configuration Set” in the OPK online documentation.
The recommended location for configuration sets is directly on the technician computer, which you then make available on the local area network as the distribution share. For more information, see “Structure and Content of the Distribution Share” in the OPK online documentation.
System Preparation Tool (Sysprep)
The System Preparation (Sysprep) tool prepares a personal computer's hard disk for disk duplication, auditing, and customer delivery.
Sysprep configures the computer so that Windows Welcome or Mini-Setup runs the next time the computer is started. This first-run experience is a shortened GUI Mode Setup that takes 3–10 minutes instead of the usual 30–45 minutes, and prompts the end user for only required and user-specific information such as accepting the End-User License Agreement, entering the Product Key, and adding user and company names.
Sysprep lets you copy fully installed systems when the hardware is similar. It modifies the local computer security identifier (SID) so that it is unique to each computer. Sysprep allows you to start the computer, skip Windows Welcome or Mini-Setup, audit the installation, and then return the operating system to a customer-ready state.
This file, when used on a floppy disk in your master computer, will connect to your technician computer to run the Windows operating system from a specified network location using the standard universal naming convention \\servername\sharename.
When using Winbom.ini, Sysprep includes a Factory mode, sysprep -factory, for preinstallation of Windows in an OEM manufacturing environment. Factory mode provides the maximum amount of flexibility for customizing the installation of individual computers. It is a completely automated installation and configuration process that runs in the least amount of time possible. Factory mode uses the Winbom.ini bill-of-materials file to guide the installation and configuration process.
The sysprep -factory command starts very early in the operating system boot sequence to enable operations that must take place prior to other system processes running, such as Plug and Play device enumeration. During sysprep -factory, Plug and Play enumeration and other system services and boot processes are started, so that other tasks performed by the sysprep -factory command occur with the full Windows operating system up and running.
Sysprep.inf is an optional answer file that can be used to automate Mini-Setup. Normally, when Mini-Setup runs, it prompts the end user for some standard information that is used to configure the computer. However, if Sysprep.inf is present, Mini-Setup uses information in Sysprep.inf instead of prompting the end user. By using Sysprep.inf, you can have Mini-Setup prompt the end user for certain information, or you can create a completely automated installation that does not prompt the end user for information at all.
The Sysprep.inf file must reside in the same location as Sysprep.exe and Setupcl.exe. These Sysprep files can exist either in the %systemdrive%\Sysprep folder, located on the hard disk of the destination computer, or on a floppy disk.
If you run Sysprep.exe from %systemdrive%\Sysprep, Sysprep removes the entire folder and its contents after it finishes running.
This is the answer file that is used to determine how the Windows Setup process interacts with the distribution folders and files that you create. The entries in the answer file determine what information Setup will prompt the user for during the Setup process. For example, the answer file contains a FullName entry in the [UserData] section. This entry instructs Windows XP Setup to prompt the user to provide a full name.
Unattend.txt contains optional sections that you can modify to supply information about your preinstallation requirements. You can create or modify Unattend.txt by using a text editor or Setup Manager.
This file specifies the Windows Welcome screens that appear when the end user turns on the computer for the first time. You can modify this file to add customized text and your company name and logo to certain Windows Welcome screens.
This file configures Setup Manager for OEM use. If Oem.tag is not present, Setup Manager is configured for use by corporate administrators only.
This batch file is used to create a new configuration set based on an existing configuration set. For example, you can create a base configuration set to preinstall Windows XP in one language and then use the Cfgbatch.txt file to create a configuration set with the same characteristics that you can use to preinstall Windows XP in a different language.
The Cmdlines.txt file contains the commands that GUI Mode Setup executes when installing optional components such as applications. For example, you can use the commands specified in this file to run a .inf file or to perform some other action. If you plan to use Cmdlines.txt to install an application, be sure to place the application you are installing in the \$OEM$ subfolder of the distribution folder. Important: Be sure that your answer file [USERDATA] is set to oempreinstall=yes.
Oemlogo.bmp must strictly conform to the following requirements:
§ Logo display location—System Properties
§ Bitmap file name—Oemlogo.bmp
§ Bitmap size and color depth—176 by 110 pixels for small fonts, 176 by 120 pixels for large fonts; 256 colors
If your bitmap image is smaller than this specification, it appears centered in the rectangle. If it is larger than this specification, part of it may appear to be cropped under certain font and screen resolutions, or it may not appear at all. To make sure the logo displays correctly, copy Oemlogo.bmp to the %windir%\System32 subfolder.
You can customize the Windows Welcome screen with your own branding. You can do this in two ways:
§ Add your company name to the Welcome and Finish pages.
§ Add a logo to appear in the upper-right corner of the Windows Welcome pages.
Note the following requirements:
§ You must prepare the logo graphic before you run Setup Manager.
§ The graphic should be in Graphics Interchange Format (GIF), based on the Windows 256-color palette, and have a dimension of 255 by 40 pixels. If the image is larger than the specified dimension, Windows Welcome crops any additional pixels on the right side or bottom of the image. For example, if the computer resolution is 800 by 600 pixels and your image is 275 by 50 pixels, Windows Welcome only displays a 255-by-40-pixel section of your logo.
§ Name the file Oemlogo.gif."</i>
If you're just installing XP, then you don't need to use the pre-install disk. That disk is meant for OEMs to use so when they sell the computer, the customer sees the "hp invent" boot up screen, and all that other sh!t that they put on.
Some day I'll be rich and famous for inventing a device that allows you to stab people in the face over the internet.