lawson23

My problem with %systemdrive%\DRV is that I did try c:\drv with no success. Maybe it likes the varibles better than hard paths I have yet to try %systemdrive%\DRV.

the drv folder exist on the root just like Windows would handle it. It looks on the pc like C:\DRV not $oem$\$1\drv If I create a $WinPEDriver$ folder like $oem$\$1\$winpedriver$\driverfoldersandfiles What happens to this folder later does it stay on the machine at c:\$winpedriver$? Either way what I'm doing above appears to be working. Not sure how or why but hey it is working.

I could not attach the log file because of the size so I have pasted what I think is the important pieces. 2013-01-21 16:58:48, Info IBS InstallWindows:Successfully loaded resource language [en-US] 2013-01-21 16:58:48, Info [0x0601c1] IBS InstallWindows:Install Path = \\BER-AP21.motorwheelcvs.com\deployment\Task Handler\SOI\63b172c3-308d-4929-a8f5-8d8148ac7be3\sources 2013-01-21 16:58:48, Info [0x0601c2] IBS InstallWindows:Setup Phase = 2 2013-01-21 16:58:48, Info [0x0601e9] IBS CheckWinPEVersion:Compatible WinPE Version 6.0.6001 sp 1.0 2013-01-21 16:58:48, Info [0x0601c9] IBS InstallWindows:Starting a new install from WinPE 2013-01-21 16:58:48, Info IBS InstallWindows: Setup working directory = X:\Windows\panther 2013-01-21 16:58:48, Info [0x0601ce] IBS Setup has started phase 2 at 2013-01-21 16:58:48 2013-01-21 16:58:48, Info [0x0601cf] IBS Install source is \\BER-AP21.motorwheelcvs.com\deployment\Task Handler\SOI\63b172c3-308d-4929-a8f5-8d8148ac7be3\sources 2013-01-21 16:58:48, Info [0x0601d0] IBS Build version is 6.1.7601.17514 (win7sp1_rtm.101119-1850) 2013-01-21 16:58:48, Info [0x06403f] IBSLIB CreateSetupBlackboard:Creating a new persistent blackboard. Path is [X:\Windows\panther\SetupInfo] Setup phase is [2] 2013-01-21 16:58:48, Info [0x090008] PANTHR CBlackboard::Open: X:\Windows\panther\SetupInfo succeeded. 2013-01-21 16:58:48, Info [0x064043] IBSLIB CreateSetupBlackboard:Successfully created/opened Setup black board path is [X:\Windows\panther\SetupInfo] 2013-01-21 16:58:48, Info IBS InstallWindows:No UI language from a previous boot was found on the blackboard. Using selected language [en-US]. 2013-01-21 16:58:48, Info IBS InstallWindows:Setup architecture is [x64] 2013-01-21 16:58:48, Info [0x0601d5] IBS InstallWindows:Starting with Empty Queue. Setup Phase = 2 2013-01-21 16:58:56, Info IBS No <Path> was specified in an <InstallFrom> element for <OSImage>; will assume default one 2013-01-21 16:58:56, Info IBS No credentials specified on <InstallFrom> element 2013-01-21 16:58:56, Info IBS Callback_SetWinPEAndOSImageInfoOnBB: Cannot set image info as source path is not yet set. 2013-01-21 16:58:56, Info PnPIBS: Entering PnP callback to install drivers on WinPE ... 2013-01-21 16:58:56, Info PnPIBS: Checking for pre-configured driver paths ... 2013-01-21 16:58:56, Info PnPIBS: Checking for pre-configured driver directory C:\$WinPEDriver$. 2013-01-21 16:58:56, Info PnPIBS: Checking for pre-configured driver directory D:\$WinPEDriver$. 2013-01-21 16:58:56, Info PnPIBS: Checking for pre-configured driver directory X:\$WinPEDriver$. 2013-01-21 16:58:56, Info PnPIBS: Checking for pre-configured driver directory Z:\$WinPEDriver$. 2013-01-21 16:58:56, Info PnPIBS: Finished checking for pre-configured driver paths. 2013-01-21 16:58:56, Info PnPIBS: Reading driver paths from unattend.xml ... 2013-01-21 16:58:56, Info PnPIBS: $OEM$\$1\DRV is listed as a driver path in unattend.xml ... 2013-01-21 16:58:56, Info PnPIBS: Finished reading driver paths from unattend.xml. 2013-01-21 16:58:56, Info PnPIBS: Building the list of drivers in the path $OEM$\$1\DRV ... 2013-01-21 16:58:56, Info PnPIBS: Found the directory Audio. 2013-01-21 16:58:56, Info PnPIBS: Building the list of drivers in the path $OEM$\$1\DRV\Audio ... 2013-01-21 16:58:56, Info PnPIBS: Finished building list of drivers in the path $OEM$\$1\DRV\Audio. 2013-01-21 16:58:56, Info PnPIBS: Found the directory chipset. 2013-01-21 16:58:56, Info PnPIBS: Building the list of drivers in the path $OEM$\$1\DRV\chipset ... 2013-01-21 16:58:56, Info PnPIBS: Finished building list of drivers in the path $OEM$\$1\DRV\chipset. 2013-01-21 16:58:56, Info PnPIBS: Found the directory misc. 2013-01-21 16:58:56, Info PnPIBS: Building the list of drivers in the path $OEM$\$1\DRV\misc ... 2013-01-21 16:58:56, Info PnPIBS: Finished building list of drivers in the path $OEM$\$1\DRV\misc. 2013-01-21 16:58:56, Info PnPIBS: Found the directory modem. 2013-01-21 16:58:56, Info PnPIBS: Building the list of drivers in the path $OEM$\$1\DRV\modem ... 2013-01-21 16:58:56, Info PnPIBS: Finished building list of drivers in the path $OEM$\$1\DRV\modem. 2013-01-21 16:58:56, Info PnPIBS: Found the directory nic. 2013-01-21 16:58:56, Info PnPIBS: Building the list of drivers in the path $OEM$\$1\DRV\nic ... 2013-01-21 16:58:56, Info PnPIBS: Finished building list of drivers in the path $OEM$\$1\DRV\nic. 2013-01-21 16:58:56, Info PnPIBS: Found the directory SATA_SCSI. 2013-01-21 16:58:56, Info PnPIBS: Building the list of drivers in the path $OEM$\$1\DRV\SATA_SCSI ... 2013-01-21 16:58:56, Info PnPIBS: Finished building list of drivers in the path $OEM$\$1\DRV\SATA_SCSI. 2013-01-21 16:58:56, Info PnPIBS: Found the directory Systems. 2013-01-21 16:58:56, Info PnPIBS: Building the list of drivers in the path $OEM$\$1\DRV\Systems ... 2013-01-21 16:58:56, Info PnPIBS: Found the directory e6410. 2013-01-21 16:58:56, Info PnPIBS: Building the list of drivers in the path $OEM$\$1\DRV\Systems\e6410 ... 2013-01-21 16:58:56, Info PnPIBS: Found the directory NIC. 2013-01-21 16:58:56, Info PnPIBS: Building the list of drivers in the path $OEM$\$1\DRV\Systems\e6410\NIC ... 2013-01-21 16:58:56, Info PnPIBS: Found the file E1K62x64.cat 2013-01-21 16:58:56, Info PnPIBS: Skipping the file E1K62x64.cat because it is not an INF file. 2013-01-21 16:58:56, Info PnPIBS: Found the file e1k62x64.din 2013-01-21 16:58:56, Info PnPIBS: Skipping the file e1k62x64.din because it is not an INF file. 2013-01-21 16:58:56, Info PnPIBS: Found the file E1K62x64.INF 2013-01-21 16:58:56, Info PnPIBS: Added driver $OEM$\$1\DRV\Systems\e6410\NIC\E1K62x64.INF to the list of drivers. 2013-01-21 16:58:56, Info PnPIBS: Found the file e1k62x64.sys 2013-01-21 16:58:56, Info PnPIBS: Skipping the file e1k62x64.sys because it is not an INF file. 2013-01-21 16:58:56, Info PnPIBS: Found the file e1kmsg.dll 2013-01-21 16:58:56, Info PnPIBS: Skipping the file e1kmsg.dll because it is not an INF file. 2013-01-21 16:58:56, Info PnPIBS: Found the file NicCo36.dll 2013-01-21 16:58:56, Info PnPIBS: Skipping the file NicCo36.dll because it is not an INF file. 2013-01-21 16:58:56, Info PnPIBS: Found the file NicInstK.dll 2013-01-21 16:58:56, Info PnPIBS: Skipping the file NicInstK.dll because it is not an INF file. 2013-01-21 16:58:56, Info PnPIBS: Found the file PROUnstl.exe 2013-01-21 16:58:56, Info PnPIBS: Skipping the file PROUnstl.exe because it is not an INF file. 2013-01-21 16:58:56, Info PnPIBS: Found the file Version.txt 2013-01-21 16:58:56, Info PnPIBS: Skipping the file Version.txt because it is not an INF file. 2013-01-21 16:58:56, Info PnPIBS: Finished building list of drivers in the path $OEM$\$1\DRV\Systems\e6410\NIC. 2013-01-21 16:58:56, Info PnPIBS: Finished building list of drivers in the path $OEM$\$1\DRV\Systems\e6410. 2013-01-21 16:58:56, Info PnPIBS: Found the directory e6420. 2013-01-21 16:58:56, Info PnPIBS: Building the list of drivers in the path $OEM$\$1\DRV\Systems\e6420 ... 2013-01-21 16:58:56, Info PnPIBS: Finished building list of drivers in the path $OEM$\$1\DRV\Systems\e6420. 2013-01-21 16:58:56, Info PnPIBS: Finished building list of drivers in the path $OEM$\$1\DRV\Systems. 2013-01-21 16:58:56, Info PnPIBS: Found the directory Video. 2013-01-21 16:58:56, Info PnPIBS: Building the list of drivers in the path $OEM$\$1\DRV\Video ... 2013-01-21 16:58:56, Info PnPIBS: Found the directory ATI. 2013-01-21 16:58:56, Info PnPIBS: Building the list of drivers in the path $OEM$\$1\DRV\Video\ATI ... 2013-01-21 16:58:56, Info PnPIBS: Finished building list of drivers in the path $OEM$\$1\DRV\Video\ATI. 2013-01-21 16:58:56, Info PnPIBS: Found the directory Intel. 2013-01-21 16:58:56, Info PnPIBS: Building the list of drivers in the path $OEM$\$1\DRV\Video\Intel ... 2013-01-21 16:58:56, Info PnPIBS: Finished building list of drivers in the path $OEM$\$1\DRV\Video\Intel. 2013-01-21 16:58:56, Info PnPIBS: Found the directory nvidia. 2013-01-21 16:58:56, Info PnPIBS: Building the list of drivers in the path $OEM$\$1\DRV\Video\nvidia ... 2013-01-21 16:58:56, Info PnPIBS: Finished building list of drivers in the path $OEM$\$1\DRV\Video\nvidia. 2013-01-21 16:58:56, Info PnPIBS: Finished building list of drivers in the path $OEM$\$1\DRV\Video. 2013-01-21 16:58:56, Info PnPIBS: Finished building list of drivers in the path $OEM$\$1\DRV. 2013-01-21 16:58:56, Info PnPIBS: The class GUID for INF $OEM$\$1\DRV\Systems\e6410\NIC\E1K62x64.INF is 4d36e972-e325-11ce-bfc1-08002be10318 2013-01-21 16:58:56, Info PnPIBS: The class GUID 4d36e972-e325-11ce-bfc1-08002be10318 is not boot-critical. 2013-01-21 16:58:56, Info PnPIBS: The driver $OEM$\$1\DRV\Systems\e6410\NIC\E1K62x64.INF is not boot-critical and hence it will not be installed. 2013-01-21 16:58:56, Info PnPIBS: Exiting PnP callback to install drivers on WinPE ... 2013-01-21 16:58:56, Info PnPIBS: Entering PnP callback to add drivers to the offline image ... 2013-01-21 16:58:56, Info PnPIBS: Checking for pre-configured driver paths ... 2013-01-21 16:58:56, Info PnPIBS: Checking for pre-configured driver directory C:\$WinPEDriver$. 2013-01-21 16:58:56, Info PnPIBS: Checking for pre-configured driver directory D:\$WinPEDriver$. 2013-01-21 16:58:56, Info PnPIBS: Checking for pre-configured driver directory X:\$WinPEDriver$. 2013-01-21 16:58:56, Info PnPIBS: Checking for pre-configured driver directory Z:\$WinPEDriver$. 2013-01-21 16:58:56, Info PnPIBS: Finished checking for pre-configured driver paths. 2013-01-21 16:58:56, Info PnPIBS: Reading driver paths from unattend.xml ... 2013-01-21 16:58:56, Info PnPIBS: $OEM$\$1\DRV is listed as a driver path in unattend.xml ... 2013-01-21 16:58:56, Info PnPIBS: Finished reading driver paths from unattend.xml. 2013-01-21 16:58:56, Info PnPIBS: Building the list of drivers in the path $OEM$\$1\DRV ... 2013-01-21 16:58:56, Info PnPIBS: Found the directory Audio. 2013-01-21 16:58:56, Info PnPIBS: Building the list of drivers in the path $OEM$\$1\DRV\Audio ... 2013-01-21 16:58:56, Info PnPIBS: Finished building list of drivers in the path $OEM$\$1\DRV\Audio. 2013-01-21 16:58:56, Info PnPIBS: Found the directory chipset. 2013-01-21 16:58:56, Info PnPIBS: Building the list of drivers in the path $OEM$\$1\DRV\chipset ... 2013-01-21 16:58:56, Info PnPIBS: Finished building list of drivers in the path $OEM$\$1\DRV\chipset. 2013-01-21 16:58:56, Info PnPIBS: Found the directory misc. 2013-01-21 16:58:56, Info PnPIBS: Building the list of drivers in the path $OEM$\$1\DRV\misc ... 2013-01-21 16:58:56, Info PnPIBS: Finished building list of drivers in the path $OEM$\$1\DRV\misc. 2013-01-21 16:58:56, Info PnPIBS: Found the directory modem. 2013-01-21 16:58:56, Info PnPIBS: Building the list of drivers in the path $OEM$\$1\DRV\modem ... 2013-01-21 16:58:56, Info PnPIBS: Finished building list of drivers in the path $OEM$\$1\DRV\modem. 2013-01-21 16:58:56, Info PnPIBS: Found the directory nic. 2013-01-21 16:58:56, Info PnPIBS: Building the list of drivers in the path $OEM$\$1\DRV\nic ... 2013-01-21 16:58:56, Info PnPIBS: Finished building list of drivers in the path $OEM$\$1\DRV\nic. 2013-01-21 16:58:56, Info PnPIBS: Found the directory SATA_SCSI. 2013-01-21 16:58:56, Info PnPIBS: Building the list of drivers in the path $OEM$\$1\DRV\SATA_SCSI ... 2013-01-21 16:58:56, Info PnPIBS: Finished building list of drivers in the path $OEM$\$1\DRV\SATA_SCSI. 2013-01-21 16:58:56, Info PnPIBS: Found the directory Systems. 2013-01-21 16:58:56, Info PnPIBS: Building the list of drivers in the path $OEM$\$1\DRV\Systems ... 2013-01-21 16:58:56, Info PnPIBS: Found the directory e6410. 2013-01-21 16:58:56, Info PnPIBS: Building the list of drivers in the path $OEM$\$1\DRV\Systems\e6410 ... 2013-01-21 16:58:56, Info PnPIBS: Found the directory NIC. 2013-01-21 16:58:56, Info PnPIBS: Building the list of drivers in the path $OEM$\$1\DRV\Systems\e6410\NIC ... 2013-01-21 16:58:56, Info PnPIBS: Found the file E1K62x64.cat 2013-01-21 16:58:56, Info PnPIBS: Skipping the file E1K62x64.cat because it is not an INF file. 2013-01-21 16:58:56, Info PnPIBS: Found the file e1k62x64.din 2013-01-21 16:58:56, Info PnPIBS: Skipping the file e1k62x64.din because it is not an INF file. 2013-01-21 16:58:56, Info PnPIBS: Found the file E1K62x64.INF 2013-01-21 16:58:56, Info PnPIBS: Added driver $OEM$\$1\DRV\Systems\e6410\NIC\E1K62x64.INF to the list of drivers. 2013-01-21 16:58:56, Info PnPIBS: Found the file e1k62x64.sys 2013-01-21 16:58:56, Info PnPIBS: Skipping the file e1k62x64.sys because it is not an INF file. 2013-01-21 16:58:56, Info PnPIBS: Found the file e1kmsg.dll 2013-01-21 16:58:56, Info PnPIBS: Skipping the file e1kmsg.dll because it is not an INF file. 2013-01-21 16:58:56, Info PnPIBS: Found the file NicCo36.dll 2013-01-21 16:58:56, Info PnPIBS: Skipping the file NicCo36.dll because it is not an INF file. 2013-01-21 16:58:56, Info PnPIBS: Found the file NicInstK.dll 2013-01-21 16:58:56, Info PnPIBS: Skipping the file NicInstK.dll because it is not an INF file. 2013-01-21 16:58:56, Info PnPIBS: Found the file PROUnstl.exe 2013-01-21 16:58:56, Info PnPIBS: Skipping the file PROUnstl.exe because it is not an INF file. 2013-01-21 16:58:56, Info PnPIBS: Found the file Version.txt 2013-01-21 16:58:56, Info PnPIBS: Skipping the file Version.txt because it is not an INF file. 2013-01-21 16:58:56, Info PnPIBS: Finished building list of drivers in the path $OEM$\$1\DRV\Systems\e6410\NIC. 2013-01-21 16:58:56, Info PnPIBS: Finished building list of drivers in the path $OEM$\$1\DRV\Systems\e6410. 2013-01-21 16:58:56, Info PnPIBS: Found the directory e6420. 2013-01-21 16:58:56, Info PnPIBS: Building the list of drivers in the path $OEM$\$1\DRV\Systems\e6420 ... 2013-01-21 16:58:56, Info PnPIBS: Finished building list of drivers in the path $OEM$\$1\DRV\Systems\e6420. 2013-01-21 16:58:56, Info PnPIBS: Finished building list of drivers in the path $OEM$\$1\DRV\Systems. 2013-01-21 16:58:56, Info PnPIBS: Found the directory Video. 2013-01-21 16:58:56, Info PnPIBS: Building the list of drivers in the path $OEM$\$1\DRV\Video ... 2013-01-21 16:58:56, Info PnPIBS: Found the directory ATI. 2013-01-21 16:58:56, Info PnPIBS: Building the list of drivers in the path $OEM$\$1\DRV\Video\ATI ... 2013-01-21 16:58:56, Info PnPIBS: Finished building list of drivers in the path $OEM$\$1\DRV\Video\ATI. 2013-01-21 16:58:56, Info PnPIBS: Found the directory Intel. 2013-01-21 16:58:56, Info PnPIBS: Building the list of drivers in the path $OEM$\$1\DRV\Video\Intel ... 2013-01-21 16:58:56, Info PnPIBS: Finished building list of drivers in the path $OEM$\$1\DRV\Video\Intel. 2013-01-21 16:58:56, Info PnPIBS: Found the directory nvidia. 2013-01-21 16:58:56, Info PnPIBS: Building the list of drivers in the path $OEM$\$1\DRV\Video\nvidia ... 2013-01-21 16:58:56, Info PnPIBS: Finished building list of drivers in the path $OEM$\$1\DRV\Video\nvidia. 2013-01-21 16:58:56, Info PnPIBS: Finished building list of drivers in the path $OEM$\$1\DRV\Video. 2013-01-21 16:58:56, Info PnPIBS: Finished building list of drivers in the path $OEM$\$1\DRV. 2013-01-21 16:58:56, Info PnPIBS: Driver $OEM$\$1\DRV\Systems\e6410\NIC\E1K62x64.INF is being queued up for addition to the offline image. 2013-01-21 16:58:56, Info IBS Callback_Compliance_GatherDeviceIDs:Driver package is [$OEM$\$1\DRV\Systems\e6410\NIC\E1K62x64.INF] 2013-01-21 16:58:56, Info IBS GatherDeviceIDsInDriverPackage:Driver package path is [$OEM$\$1\DRV\Systems\e6410\NIC\E1K62x64.INF] 2013-01-21 16:58:56, Info IBS GatherDeviceIDsInDriverPackage:Successfully gathered device ID's from [$OEM$\$1\DRV\Systems\e6410\NIC\E1K62x64.INF] 2013-01-21 16:58:56, Info PnPIBS: Successfully gathered device ID's from [$OEM$\$1\DRV\Systems\e6410\NIC\E1K62x64.INF] 2013-01-21 16:58:56, Info Callback_GatherDiskInfo: Entry: flags = [0x1]; major = [DriveInformation] / minor = [0x90001] 2013-01-21 16:58:56, Info RefreshDiskInfo: Using VDS 2013-01-21 16:58:56, Info RefreshDiskInfo: Found flag DISKINFO_REENUMERATE_DISKS 2013-01-21 17:15:05, Info [0x0602a4] IBS CallBack_AddDriverPackageIntoDriverStore:Driver package path is [$OEM$\$1\DRV\Systems\e6410\NIC\E1K62x64.INF] 2013-01-21 17:15:05, Info [0x0602b2] IBS CallBack_AddDriverPackageIntoDriverStore:Driver package is [NOT critical] 2013-01-21 17:15:05, Info IBS AddDriverPackageIntoDriverStore:Driver package path is [$OEM$\$1\DRV\Systems\e6410\NIC\E1K62x64.INF] 2013-01-21 17:15:05, Info IBS AddDriverPackageIntoDriverStore:Image architecture is [0x9] 2013-01-21 17:15:05, Info IBS AddDriverPackageIntoDriverStore:System root is [C:\Windows] 2013-01-21 17:15:05, Info IBS AddDriverPackageIntoDriverStore:System drive is [C:\] 2013-01-21 17:15:08, Info [0x0602b0] IBS AddDriverPackageIntoDriverStore:Successfully added the driver package [$OEM$\$1\DRV\Systems\e6410\NIC\E1K62x64.INF] into driver store. Destination driver package path is [C:\Windows\System32\DriverStore\FileRepository\e1k62x64.inf_amd64_neutral_bfac63e16fb1c2b4\E1K62x64.INF] 2013-01-21 17:15:08, Info [0x0602a8] IBS CallBack_AddDriverPackageIntoDriverStore:Successfully installed the driver package [$OEM$\$1\DRV\Systems\e6410\NIC\E1K62x64.INF]. Driver store path is [C:\Windows\System32\DriverStore\FileRepository\e1k62x64.inf_amd64_neutral_bfac63e16fb1c2b4\E1K62x64.INF] 2013-01-21 17:15:08, Info IBS Callback_AddDriverPackageIntoDriverStore: Checking for iSCSI deployment scenario

No , just like I said <Path>%systemdrive%\DRV</Path> I do not know if that altiris will use the $OEM$ same way as intended Well I started a test late Friday and had to leave and so far it appears that this did work: <Path>$OEM$\$1\DRV</Path> Going to run another test to be sure. 2nd test also worked great. So far it looks like this solves my problems regarding drivers. Any comments regarding it?

Ok so in the xml file I would put: $OEM$\$1\DRV as I have been putting: c:\DRV <settings pass="windowsPE" wasPassProcessed="true"> <component name="Microsoft-Windows-PnpCustomizationsWinPE" processorArchitecture="AMD64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <DriverPaths> <PathAndCredentials wcm:action="add" wcm:keyValue="201"> <Path>$OEM$\$1\DRV</Path> </PathAndCredentials> </DriverPaths> </component>

MaxXPSoft, So my question is there anyway to kick that driver routine off with the way I'm putting the drivers on the system from the xml? To duplicate what I did with XP? We have so few systems it is just easier to manage drviers this way than injecting and all that stuff. If I renamed my folder from drv to $winpedriver$ would it then possibly work? I'm just trying to learn and understand this. Will say they went from like a few options to way to many. Also I never got an answer regarding how the drivers have to be put in the xml. If I have multiple folders do I have to put multiple entries or just the one root entry. For example currently I only place on driver in my driver folder but it is located: sources\$OEM$\$1\DRV\Systems\e6410\NIC From what I read you can now just define the root location but this was not true with the sif oem method.

ok first maybe I should explain the setup. I'm trying to duplicate the $OEM$ driver install like I could do with XP sif file. Just as in the article you created describe using: $1 <<- Drive Root $1\Drivers <<- where some OEM place driver files but I use: $1 <<- Drive Root $1\DRV <<- where some OEM place driver files I'm not using a dvd I'm using a deployment solution (altiris) to push this stuff out. They capture the sources folder only so not sure if I can add $winpedriver$ folder as you describe. I'm really courious if I can duplicate what I used to do above. Is this possible or not? Also Altiris has a driver setup routine that is putting in the offline service area. I'm not sure I want to pull this out. I would think I could use multiple methods if the xml allows it. I'm thinking of doing a registry modification after deployment to update the driver location key and then forcing a pnp check since nothing appears to be working out with the xml.

processorArchitecture="@ProcessArchitecture" Actually that is filled in based on the system type by our deployment solution but since we will only be deploying x64 systems I can pull that out and put in amd64 to set it static. Above is what is in file before deployment. This is the xml that is seen after deployment is complete. <?xml version='1.0' encoding='utf-8'?> <unattend xmlns="urn:schemas-microsoft-com:unattend"> <settings pass="specialize" wasPassProcessed="true"> <component name="Microsoft-Windows-Shell-Setup" processorArchitecture="AMD64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <ProductKey>*SENSITIVE*DATA*DELETED*</ProductKey> <ComputerName>PC1098</ComputerName> <Display> <ColorDepth>32</ColorDepth> <HorizontalResolution>1280</HorizontalResolution> <RefreshRate>75</RefreshRate> <VerticalResolution>1024</VerticalResolution> </Display> </component> <component name="Microsoft-Windows-UnattendedJoin" processorArchitecture="AMD64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <Identification> <JoinWorkgroup>workgroup</JoinWorkgroup> </Identification> </component> <component name="Microsoft-Windows-DNS-Client" processorArchitecture="AMD64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <Interfaces> <Interface wcm:action="add"> <Identifier>5C-26-0A-48-66-58</Identifier> <DNSDomain>workgroup</DNSDomain> <DNSServerSearchOrder> <IpAddress wcm:action="add" wcm:keyValue="1">10.0.xxx.xxx</IpAddress> <IpAddress wcm:action="add" wcm:keyValue="2">10.0.xxx.xxx</IpAddress> </DNSServerSearchOrder> </Interface> </Interfaces> </component> <component name="Microsoft-Windows-TCPIP" processorArchitecture="AMD64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <Interfaces> <Interface wcm:action="add"> <Identifier>5C-26-0A-48-66-58</Identifier> <Ipv4Settings> <DhcpEnabled>true</DhcpEnabled> </Ipv4Settings><Ipv6Settings> <DhcpEnabled>true</DhcpEnabled> </Ipv6Settings> </Interface> </Interfaces> </component> </settings> <settings pass="windowsPE" wasPassProcessed="true"> <component name="Microsoft-Windows-PnpCustomizationsWinPE" processorArchitecture="AMD64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <DriverPaths> <PathAndCredentials wcm:action="add" wcm:keyValue="201"> <Path>$WinPEDriver$</Path> </PathAndCredentials> </DriverPaths> </component> <component name="Microsoft-Windows-International-Core-WinPE" processorArchitecture="AMD64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <SetupUILanguage> <UILanguage>en-US</UILanguage> </SetupUILanguage> <InputLocale>0409:00000409</InputLocale> <SystemLocale>en-US</SystemLocale> <UILanguage>en-US</UILanguage> <UserLocale>en-US</UserLocale> </component> <component name="Microsoft-Windows-Setup" processorArchitecture="AMD64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <ImageInstall> <OSImage> <InstallTo> <DiskID>0</DiskID> <PartitionID>1</PartitionID> </InstallTo> </OSImage> </ImageInstall> <UserData> <AcceptEula>true</AcceptEula> </UserData> </component> </settings> <settings pass="oobeSystem" wasPassProcessed="true"> <component name="Microsoft-Windows-Shell-Setup" processorArchitecture="AMD64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <OOBE> <HideEULAPage>true</HideEULAPage> <SkipUserOOBE>true</SkipUserOOBE> <NetworkLocation>Work</NetworkLocation> <ProtectYourPC>1</ProtectYourPC> </OOBE> <RegisteredOrganization>Altiris</RegisteredOrganization> <RegisteredOwner>Altiris User</RegisteredOwner> <TimeZone>Eastern Standard Time</TimeZone> <UserAccounts> <AdministratorPassword>*SENSITIVE*DATA*DELETED*</AdministratorPassword> <LocalAccounts> <LocalAccount wcm:action="add"> <Password>*SENSITIVE*DATA*DELETED*</Password> <Name>Altiris</Name> <Description>Altiris User</Description> <DisplayName>Altiris</DisplayName> <Group>Administrators</Group> </LocalAccount> </LocalAccounts> </UserAccounts> <Display> <ColorDepth>32</ColorDepth> <HorizontalResolution>1280</HorizontalResolution> <RefreshRate>75</RefreshRate> <VerticalResolution>1024</VerticalResolution> </Display> </component> </settings> <settings pass="offlineServicing" wasPassProcessed="true"> <component name="Microsoft-Windows-PnpCustomizationsNonWinPE" processorArchitecture="AMD64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <DriverPaths> <PathAndCredentials wcm:keyValue="1" wcm:action="add"> <Path>X:\DRIVERS</Path> </PathAndCredentials> </DriverPaths> </component> </settings> <!-- <settings pass="offlineServicing"> <component name="Microsoft-Windows-LUA-Settings" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <EnableLUA>false</EnableLUA> </component> <component name="Microsoft-Windows-PnpCustomizationsNonWinPE" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <DriverPaths> <PathAndCredentials wcm:action="add" wcm:keyValue="200"> <Path>%systemdrive%\DRV\Systems\e6410\NIC</Path> </PathAndCredentials> </DriverPaths> </component> </settings> <settings pass="auditSystem"> <component name="Microsoft-Windows-PnpCustomizationsNonWinPE" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <DriverPaths> <PathAndCredentials wcm:keyValue="998fe066" wcm:action="add"> <Path>C:\DRV\Systems\e6410\NIC</Path> </PathAndCredentials> <PathAndCredentials wcm:keyValue="6e0a4d58" wcm:action="add"> <Path>C:\temp\Downloads\e6410x64</Path> </PathAndCredentials> <PathAndCredentials wcm:keyValue="ec6923c4" wcm:action="add"> <Path>C:\temp\Downloads\e6410x64\Nic\R290983\Windows7-x64</Path> </PathAndCredentials> </DriverPaths> </component> </settings> --> </unattend>

<settings pass="windowsPE"> <component name="Microsoft-Windows-PnpCustomizationsWinPE" processorArchitecture="@ProcessArchitecture" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <DriverPaths> <PathAndCredentials wcm:action="add" wcm:keyValue="201"> <Path>$WinPEDriver$</Path> </PathAndCredentials> </DriverPaths> </component> This did not appear to work so I'm still trying to understand your article where you state to place the drivers in $oem$ like I do with XP.

Ok but I'm having a hard time understanding <Path>$WinPEDriver$</Path> will this look at $OEM$\$1\Drv or c:\DRV ?? PS sorry for being such a pain.

<component name="Microsoft-Windows-PnpCustomizationsWinPE" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <DriverPaths> <PathAndCredentials wcm:action="add" wcm:keyValue="1"> <Path>c:\DRV</Path> </PathAndCredentials> </DriverPaths> </component> This did not work so now trying <component name="Microsoft-Windows-PnpCustomizationsWinPE" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <DriverPaths> <PathAndCredentials wcm:action="add" wcm:keyValue="1"> <Path>c:\DRV\systems\e6410\nic</Path> </PathAndCredentials> </DriverPaths> </component>

So would this work: put driver files in oem folder like I did in XP: $OEM$\$1\Drv then use this in my unattended.xml <component name="Microsoft-Windows-PnpCustomizationsWinPE" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <DriverPaths> <PathAndCredentials wcm:action="add" wcm:keyValue="1"> <Path>c:\DRV</Path> </PathAndCredentials> </DriverPaths> </component> The other question I have with XP I had to put in every folder that contained a driver. What I have read so far for 7 I only have to put a root folder in the xml. Is this true?

This is easiest method for Drivers if you don't want to inject them. and yes $OEM$ are still useable even on Win 8 MaxXPsoft This is exactly what I want (trying) to do but I have some questions regarding this. Can my path be something else? The way your article reads I'm a bit confused. At the start of the article you do exactly what I want to do by $OEM$\$1\Drivers (I use: $OEM$\$1\Drv) but below you reference $WinPEDriver$ What is that path? From your image it is something outside of the OEM folder? I guess this is where I'm having some confusion.

Ok I have searched but not finding the answer I need regarding driver installation. This is not a driver for PE environment it is a driver for the Windows deployed OS. I'm trying to replicate what I did in the SIF file for drivers: OemPnpDriversPath ="driverpath" this puts this information into this registry entry on the pc: [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion] "DevicePath"= Now for this process I was told to use the auditSystem mode to add these drivers. Here is my xml: <settings pass="auditSystem"> <component name="Microsoft-Windows-PnpCustomizationsNonWinPE" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <DriverPaths> <PathAndCredentials wcm:keyValue="998fe066" wcm:action="add"> <Path>C:\DRV\Systems\e6410\NIC</Path> </PathAndCredentials> <!-- <PathAndCredentials wcm:keyValue="6e0a4d58" wcm:action="add"> <Path>C:\temp\Downloads\e6410x64</Path> </PathAndCredentials> <PathAndCredentials wcm:keyValue="ec6923c4" wcm:action="add"> <Path>C:\temp\Downloads\e6410x64\Nic\R290983\Windows7-x64</Path> </PathAndCredentials> --> </DriverPaths> </component> </settings> This is not putting anything in this reg key and that is ok if Win 7 no longer does this but it is also not installing the driver in the location C:\DRV\Systems\e6410\NIC. [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion] "DevicePath"=

I'm trying to convert my xp soi deployment over to windows 7 but I do not understand the xml at all and have a few questions. 1. Is there a place that explains this pretty clearly so I can try to gain some understanding myself? I would like to learn it so I don't have to ask all the time. I know the xml is much more powerful than what was previously available. Almost two many options to understand. 2. Is there a place where you can run a command say a batch file to do processing like in XP during the setup phase (called in commandlines.txt) The main reason I'm looking for this is because it customized the default user in XP. So all users got the what I set up during this phase. So I would inject HKCU keys and things like Windows Background or shortcuts during this phase that I wanted every user to have on first boot. Then after this they can delete the stuff not needed. 3. What is the proper method to inject folders and files (used to use the OEM section) into the file system to be run in step 2 and after? 4. Where can I control installed components like I did with the sif? Like do not install games...

Are you sure nLite is for personal use only???? from nLite website: Never says personal use only anywhere I could find. One option I could recommend also is not compressing all files you copy over and this would make the file copy longer but would increase the time to execute your task or vice versa compress if you are trying to speed up the network copy process but your execution will get longer.

your sif looks good I think for the [GuiRunOnce] "%systemdrive%\Install\vmtools\install.bat" question would be what do you do in cmdlines.txt?? I also dont' understand why you have 3 different sif files. Second would be how does your folder structure look in your ris for the install folder. Should look like this: RISINSTALLFILES\$oem$\$1\Install\vmtools\install.bat

Ok I have an old topic where I added intel istor and a precision 650 drivers to my txtsetup.sif successfully. Here is my issue and failed understanding. The driver files are for the 650 and 690 use the same names and I know I'm messing something up and this maybe it. SYMMPI.xxx I have added the new drivers for the 690 to the txtsetup.sif so that it now will format and copy files to it successfully but when windows loads to setup it gives me the famous blue screen error 07b. I have added the 690 drivers to my drivers folder for windows but I can't figure out what is going on here. I'm guessing my txtsetup.sif is not perfect. Here is what I have: for the 690 I created a folder: i386\DRV\003 - Copied all the driver files into this folder. txtsetup.sif [sourceDisksNames.x86] 1986 = %cdname%,%cdtagfilei%,,"\i386\DRV\003" [sourceDisksFiles.x86] iaahci.cat = 1,,,,,,3_,4,1,,,1,4 iaahci.inf = 1,,,,,,3_,4,1,,,1,4 iastor.cat = 1,,,,,,3_,4,1,,,1,4 iastor.inf = 1,,,,,,3_,4,1,,,1,4 iaStor.sys = 1,,,,,,4_,4,1,,,1,4 iastor.sys = 1,,,,,,3_,4,1,,,1,4 delpseud.inf = 1986,,,,,,,1986,0,0 mpixp32.cat = 1986,,,,,,,1986,0,0 symmpi.inf = 1,,,,,,3_,4,1,,,1,4 symmpi.inf = 1986,,,,,,,1986,0,0 symmpi.sys = 1,,,,,,4_,4,1,,,1,4 symmpi.sys = 1,,,,,,3_,4,1,,,1,4 symmpi.sys = 1986,,,,,,,1986,0,0 symmpi.tag = 1,,,,,,3_,4,1,,,1,4 symmpi.tag = 1986,,,,,,,1986,0,0 [HardwareIdsDatabase] PCI\VEN_1000&DEV_0054&SUBSYS_1F041028 = "symmpi" PCI\VEN_1000&DEV_0054&SUBSYS_1F061028 = "symmpi" PCI\VEN_1000&DEV_0054&SUBSYS_1F071028 = "symmpi" PCI\VEN_1000&DEV_0054&SUBSYS_1F081028 = "symmpi" PCI\VEN_1000&DEV_0054&SUBSYS_1F091028 = "symmpi" PCI\VEN_1000&DEV_0058&SUBSYS_1F0E1028 = "symmpi" PCI\VEN_1000&DEV_0058&SUBSYS_1F0F1028 = "symmpi" PCI\VEN_1000&DEV_0058&SUBSYS_1F101028 = "symmpi" PCI\VEN_1000&DEV_0058&SUBSYS_021D1028 = "symmpi" PCI\VEN_1000&DEV_0621 = "symmpi" PCI\VEN_1000&DEV_0622 = "symmpi" PCI\VEN_1000&DEV_0624 = "symmpi" PCI\VEN_1000&DEV_0626 = "symmpi" PCI\VEN_1000&DEV_0628 = "symmpi" PCI\VEN_1000&DEV_0030 = "symmpi" PCI\VEN_8086&DEV_2922&CC_0106 = "iaStor" PCI\VEN_8086&DEV_2822&CC_0104 = "iaStor" PCI\VEN_8086&DEV_2821&CC_0106 = "iaStor" PCI\VEN_8086&DEV_2829&CC_0106 = "iaStor" PCI\VEN_8086&DEV_282A&CC_0104 = "iaStor" PCI\VEN_8086&DEV_27C3&CC_0104 = "iaStor" PCI\VEN_8086&DEV_27C1&CC_0106 = "iaStor" PCI\VEN_8086&DEV_27C6&CC_0104 = "iaStor" PCI\VEN_8086&DEV_27C5&CC_0106 = "iaStor" PCI\VEN_8086&DEV_2653&CC_0106 = "iaStor" PCI\VEN_8086&DEV_2682&CC_0104 = "iaStor" PCI\VEN_8086&DEV_2681&CC_0106 = "iaStor" [sCSI.Load] symmpi = symmpi.sys,4 iaStor = iaStor.sys,4 [FileFlags] symmpi.sys = 16 [sCSI] symmpi = "LSI Logic PCI Fibre Channel Host Adapter" symmpi = "LSI Logic Ultra320 1020/1030 Driver (XP 32-bit)" symmpi = "Dell SAS 5x and SAS 6x Controller Driver (Windows XP 32-bit)" iaStor = "Intel® ICH9 SATA AHCI Controller (Desktop/Server/Workstation)" iaStor = "Intel® ICH8R/ICH9R SATA RAID Controller (Desktop/Server/Workstation)" iaStor = "Intel® 82801HR/HH/HO SATA AHCI Controller (Desktop/Server/Workstation)" iaStor = "Intel® 82801HEM/HBM SATA AHCI Controller (Mobile ICH8M-E/M)" iaStor = "Intel® 82801HEM SATA RAID Controller (Mobile ICH8M-E)" iaStor = "Intel® 82801GR/GH SATA RAID Controller (Desktop ICH7R/DH)" iaStor = "Intel® 82801GR/GH SATA AHCI Controller (Desktop ICH7R/DH)" iaStor = "Intel® 82801GHM SATA RAID Controller (Mobile ICH7MDH)" iaStor = "Intel® 82801GBM SATA AHCI Controller (Mobile ICH7M/DH)" iaStor = "Intel® 82801FBM SATA AHCI Controller (Mobile ICH6M)" iaStor = "Intel® 631xESB/632xESB SATA RAID Controller (Server/Workstation ESB2)" iaStor = "Intel® 631xESB/632xESB SATA AHCI Controller (Server/Workstation ESB2)" 690 txtsetup.oem 650 txtsetup.oem I can add these files the way Microsoft recommends in your RIS sif and then in the textmode folder and it works just fine.

Well I figured out my last issue which happened to be the 07b bsod error. Basically in post one I had these files in this location [OEMBootFiles]: iaahci.cat iaahci.inf iastor.cat iaStor.inf Iastor.sys Txtsetup.oem I took these files and put them in my RIS_Base_Image\$oem$\$1\drivers\sata\001\*.* folder and then added this path to my sif file in RIS. Then took these files and added them to RIS_Base_Image\$oem$\$1\drivers\sata\002\*.* folder and then added this path to my sif file in RIS. MPIXP32.CAT SYMMPI.INI SYMMPI.SYS SYMMPI.TAG Txtsetup.oem OemPnPDriversPath="PREVIOUS OTHER DRIVER PATHS ENTERED;\Drivers\SATA\001;\Drivers\SATA\002" I could not use these files placed in i386 folder not sure why but would get the same bsod when using this version created by nlite in the drivers location: IAAHCI.CA_ IAAHCI.IN_ IASTOR.CA_ IASTOR.IN_ IASTOR.SY_ MPIXP32.CA_ SYMMPI.IN_ SYMMPI.SY_ SYMMPI.TA_ dell e6400 ahci laptop now RIS successfully and verified.

Well I'm glad we cleared that up. Either way thank you jaclaz as it didn't resolve the issue the posting did give me the things to do futher searches on to find the resolution. Bottom line without your post I would not have this fixed and my above solution was just verified on a dell e6400 which is AHCI. Update: 6400 copies files so it now sees the drive but later on during the install when it reboots it fails on the startup with blue screen and loops.

Following this thread: http://www.msfn.org/board/index.php?showtopic=13173&st=0 I edited my txtsetup.sif file adding the following: txtsetup.sif [SourceDisksFiles.x86] iaahci.cat = 1,,,,,,3_,4,1,,,1,4 iaahci.inf = 1,,,,,,3_,4,1,,,1,4 iastor.cat = 1,,,,,,3_,4,1,,,1,4 iastor.inf = 1,,,,,,3_,4,1,,,1,4 iaStor.sys = 1,,,,,,4_,4,1,,,1,4 iastor.sys = 1,,,,,,3_,4,1,,,1,4 mpixp32.cat = 1,,,,,,3_,4,1,,,1,4 symmpi.inf = 1,,,,,,3_,4,1,,,1,4 symmpi.sys = 1,,,,,,4_,4,1,,,1,4 symmpi.sys = 1,,,,,,3_,4,1,,,1,4 symmpi.tag = 1,,,,,,3_,4,1,,,1,4 [HardwareIdsDatabase] PCI\VEN_1000&DEV_0621 = "symmpi" PCI\VEN_1000&DEV_0622 = "symmpi" PCI\VEN_1000&DEV_0624 = "symmpi" PCI\VEN_1000&DEV_0626 = "symmpi" PCI\VEN_1000&DEV_0628 = "symmpi" PCI\VEN_1000&DEV_0030 = "symmpi" PCI\VEN_8086&DEV_2922&CC_0106 = "iaStor" PCI\VEN_8086&DEV_2822&CC_0104 = "iaStor" PCI\VEN_8086&DEV_2821&CC_0106 = "iaStor" PCI\VEN_8086&DEV_2829&CC_0106 = "iaStor" PCI\VEN_8086&DEV_282A&CC_0104 = "iaStor" PCI\VEN_8086&DEV_27C3&CC_0104 = "iaStor" PCI\VEN_8086&DEV_27C1&CC_0106 = "iaStor" PCI\VEN_8086&DEV_27C6&CC_0104 = "iaStor" PCI\VEN_8086&DEV_27C5&CC_0106 = "iaStor" PCI\VEN_8086&DEV_2653&CC_0106 = "iaStor" PCI\VEN_8086&DEV_2682&CC_0104 = "iaStor" PCI\VEN_8086&DEV_2681&CC_0106 = "iaStor" [SCSI.load] symmpi = symmpi.sys,4 iaStor = iaStor.sys,4 [SCSI] symmpi = "LSI Logic Ultra320 1020/1030 Driver (XP 32-bit)" iaStor = "Intel(R) ICH9 SATA AHCI Controller (Desktop/Server/Workstation)" iaStor = "Intel(R) ICH8R/ICH9R SATA RAID Controller (Desktop/Server/Workstation)" iaStor = "Intel(R) 82801HR/HH/HO SATA AHCI Controller (Desktop/Server/Workstation)" iaStor = "Intel(R) 82801HEM/HBM SATA AHCI Controller (Mobile ICH8M-E/M)" iaStor = "Intel(R) 82801HEM SATA RAID Controller (Mobile ICH8M-E)" iaStor = "Intel(R) 82801GR/GH SATA RAID Controller (Desktop ICH7R/DH)" iaStor = "Intel(R) 82801GR/GH SATA AHCI Controller (Desktop ICH7R/DH)" iaStor = "Intel(R) 82801GHM SATA RAID Controller (Mobile ICH7MDH)" iaStor = "Intel(R) 82801GBM SATA AHCI Controller (Mobile ICH7M/DH)" iaStor = "Intel(R) 82801FBM SATA AHCI Controller (Mobile ICH6M)" iaStor = "Intel(R) 631xESB/632xESB SATA RAID Controller (Server/Workstation ESB2)" iaStor = "Intel(R) 631xESB/632xESB SATA AHCI Controller (Server/Workstation ESB2)" Then I added these driver files to the I386 dir: IAAHCI.CA_ IAAHCI.IN_ IASTOR.CA_ IASTOR.IN_ IASTOR.SY_ MPIXP32.CA_ SYMMPI.IN_ SYMMPI.SY_ SYMMPI.TA_ These are the drivers created from the nlite change but I believe they are just the drivers and then they rename the prefix from like .cat to .ca_ and .sys to .sy_ and .inf to .in_. This I'm not sure of because I just used the drivers obtained from the nlite build I mentioned above. I have successfully tested this with a Dell Precision 650 LSI SCSI but have not been able to test with a AHCI pc yet.

Actually you posted instructions saying In response to my issue well if you see I did not jump right on this because these are not concerning RIS. Well since this was the only semi logical path that I have received in a year I decided to finally give it a shot. The reason for not posting in that article is because this is not related to RIS which is my issue. So instead of going half way off topic in that thread because it is not concerning RIS I decided to repost in my thread where I asked the specific question. You know instead of taking offense you could of just said hey maybe you should ask someone in the other post as they might know. Say I'm a user reading this thread with my original issue. How would I understand my post with the errors if I didn't refer to the instructions you posted? Doesn't it make logical sense for someone to mention where he got the information he tried. I'm sorry for you feeling offended by my previous post but I had no intentions of offending you, until now. I don't know why you take such offense to someone stating that what you suggested did not work. Either way I fixed the issue myself I believe. I will post with what I did for others to follow or gather information from.

Ok I again followed the instructions posted by jaclaz. But this time I did not do the LSI and only did the AHCI drivers alone. nlite worked fine and created me a iso image. I took the dir where it made the modifications and used this to create a new RIS base image. Now when booting and trying to RIS I get File iastor.sys caused an unexpected error (21) at line 3540 in d:\xpsp\base\boot\setup\setup.c. press any key to continue Anyone have any ideas on how to either fix this or go back and start over on this?

Ok I followed the instructions posted by jaclaz and now I have a problem. Basically I took this opportunity to add two mass storage device drivers to my system one is a scsi driver for LSI. nlite worked fine and created me a iso image. I took the dir where it made the modifications and used this to create a new RIS base image. Now when booting and trying to RIS I get File Symmpi.sys caused an unexpected error (21) at line 3540 in d:\xpsp\base\boot\setup\setup.c. press any key to continue Anyone have any ideas on how to either fix this or go back and start over on this?

http://www.m0j0.net/techsup/ris/ check this article out on cmdlines.txt