This entry causes Setup to extend this destination partition into any available unpartitioned space that physically follows it on the disk.

ExtendOemPartition automatically leaves the last cylinder on the hard disk free to allow dynamic disk support.

Note

• You can extend only NTFS file system partitions.
  
  
• The partition that you want to extend must have unpartitioned space available following the partition.
  
  

If your manufacturing process requires FAT32, use the Oformat command-line tool included in the OEM Preinstallation Kit to format the hard disk so that you configure it for NTFS. Use the Convert command-line tool to convert the file system.

You can also convert the partition during the intermediate (text-mode) stage of Setup by setting the FileSystem in the [Unattended] section of the answer file to ConvertNTFS. However, the hard disk performs better if you use the Convert command-line tool instead of the FileSystem entry.

If there is a copy of the \I386 folder in the root of the user's system drive, you need to specify a value for the InstallFilesPath entry in the Sysprep.inf file so that Setup can find the files.

The InstallFilesPath entry does not support environment variables (for example, %systemdrive%). Instead, you must use a valid path with an actual drive letter. Enclose path_to_installation_files_on_computer in quotation marks if it is a long file name.

The default value is 0.

After Sysprep runs, Mini-Setup or Windows Welcome automatically regenerates the system's page file to accommodate differences in the amount of random access memory (RAM) between the master computer and the destination computer. The default setting ensures that the page file is large enough to accommodate the amount of RAM on the computer.

If the amount of RAM is the same on both the computer used to create the master installation and the destination computers, you do not need to regenerate the paging file.

You must also use the entry OEMPreinstall = Yes.

The folders must contain all the files necessary to install the particular devices: catalog files, .inf files, and drivers.

For example, if you have a folder called \Drivers with subfolders called \Audio and \Net, use the entry OemPnPDriversPath = drivers\audio;drivers\net in the answer file. Setup adds:

• %systemdrive% to each of the folder names
  
  
• Path for each subfolder to the Plug and Play device search path.
  
  

The length of the OemPnPDriversPath entry in the answer file must not exceed 4096 characters.

You cannot use environment variables to specify the location of a folder.

Always use signed drivers. Signed drivers make the operating system more stable and significantly reduce requests for product support.

When using OemPnPDriversPath in the answer file, be sure that the folders are available during the Mini-Setup stage or during the first logon. The easiest way to do this is to place the Plug and Play drivers in the \$OEM$\$1 folder. To prevent users from inadvertently deleting driver folders located at the root of the drive, you can place drivers under the \$OEM$\$$ folder (for example: $OEM$\$$\PnP\Audio).

If the drivers are not in the Drivers.cab file on the computer’s hard disk or in the location specified by OemPnPDriversPath, Setup prompts the user for the location of the drivers during the first startup of the computer, before Windows Welcome or the Mini-Setup stage.

You can also use the [PnPDrivers] section in Winbom.ini to update drivers on a previously-created image of the installed operating system.

You must not use this entry to remove the Microsoft End-User License Agreement screen because users must see and accept it.

The default value is “*.”

If this directory does not exist or is set to the systemroot directory, Windows Welcome or Mini-Setup resets the path to the first CD drive.

The default value is Yes.

If you specify the entry name but do not specify a value, TAPI settings are not altered. This is the same as the entry TapiConfigured = Yes.

This entry is not required in Windows XP or the Windows Server 2003 family.

Do not use a Sysprep.inf file containing this entry on destination uniprocessor computers. A multiprocessor kernel on a uniprocessor computer noticeably reduces the computer's performance.

An image created on a computer with a single processor (with no multiprocessor support) cannot be used on a multiprocessor computer.

Add the modified Sysprep.inf file to the destination computer, in the systemdrive\Sysprep folder.

The default value is No.

Do not use the UpdateInstalledDrivers entry with the sysprep -pnp command.

This entry is required if the master installation is built on an Advanced Programmable Interrupt Controller (APIC) multiprocessor computer and the image of that master installation is on compatible APIC uniprocessor or multiprocessor destination computers.