Skip Ribbon Commands
Skip to main content

Distribution

:

OS Patched Source: XP Professional

Documentation and logs for UVM OS and application distribution methodologies
Tablet PC Edition:
You can use the same source for both XP Pro and XP Tablet PC Editions... XP setup will install Tablet PC extentions if you use a Tablet PC Volume License Key in your setup.
You will need to copy the "cmpnents" directory from the XP Tablet PC setup disk 2 into the installation source, and that is all.

XP Pro:
While it is possible to integrate slipstream service packs and all hotfixes into the installation source, it is not at all clear that this is a maintainable solution.  For one thing, non-hotfix updates (WMP 11, IE 7, .NET framework, DirectX) cannot be slipstreamed into the source since the presence or absence of these applications greatly effects the list of hotfixes that need to be integrated.  For another thing, hotfix dependencies and updates makes maintenance of a hotfix repository an unbearable nightmare.

Use of "AutoPatcher" is of great use here.  I have added AutoPatcher to the "Applications" branch of the BDD console and will have it run all updates to XP after a baseline install.

Handling of drivers is another issue with XP (and soon to be with Vista, too!).  I am investigating use of the DriverPacks tool to add most existing drivers to the base OS installation source.  The main trick here is that DriverPacks was not designed to support unattended installations... it is intended to run off of a modified XP installation CD.  However, It can be modified fairly easily to make it work with BDD:

http://forum.driverpacks.net/viewtopic.php?id=819
This forum entry tells us how to modify an unattended distribution share to ensure that DriverPack files are copied to the target system drive.
  • When adding DriverPacks to source, user "Method 2", and choose "Custom" for the DPS Finisher execution option.
  • copy presetup.cmd and setuporg.exe from the patched i386 source directory to <BDDOSDir>/$OEM$/$$/System32
    (Where BDDOSDir = the directory that holds the "OS" as defined in the BDD workbench.)
  • copy the contents of the OEM directory to <BDDOSDir>/$OEM$/$1/OEM
  • Delete the lines in txtsetup.sif that refer to setuporg.exe and presetup.cmd (this is file located in the i386 directory of the OS Source)
  • Add to the unattend.txt file associated with the BDD XP Build:
    (Insert this before the "cscript" command which launches LiteTouch)
    [GUIRunOnce]
    command0 = "%SystemDrive%\DPsFnshr.exe"
  • Make sure that "OEMPreinstall = Yes" has been specified in the unattend.txt file as well.
http://www.tech-hints.com/oem.html
This link describes the $OEM$ directory contents, for you edification:
  • $OEM$\$$\ - Contains files to be copy/replace over the Operating System source files.  In our case, we are adding the "presetup.cmd" file which gets called before the original windows setup.exe.  This script will extract the DriverPacks drivers to the destination system and make them available via registry injection
  • $OEM$\$1\ - Contains additional files to be copied to the root of the destination system.  In this case we add the DriverPacks "OEM" directory that contains the Driver "7z" archives, and the executables required by the driver injection process.