QUOTE (araczek @ Nov 16 2010, 03:25 PM)

Well, an update. I did remove them and rebuilt BartPE. Still no good. Boots fine but does not see the virtual drive created in the PERC 6/i.
Yes perc drivers are problematic. Sometimes helps to Update driver in Device manager - you will see device probably under unknown devices and let install automaticaly.
It doesn't help, that the correct driver is in Driverpack -you need to detect it manually. Do NOT reboot.
But generaly my experience is for Storage drivers (not network) not slipstream and use Kares Driver Import
http://www.kare-net.de/plugins.htmlI use older free version .
Something like this (this is example for my environment !!! not generaly build plugin)
; altdriverload.inf
; PE Builder v3 plug-in INF file for alternative driver load after startup
; by profp62
; requires kares Driver Import and fbwf and drivers packs disabled
[Version]
Signature= "$Windows NT$"
[PEBuilder]
Name="[profp62] Alternative drivers load"
Enable=1
[WinntDirectories]
a="Programs\alternativedrivers",2
;a="Programs\OfflineSysPrep\DriverPacks-MassStorage",2
[SourceDisksFiles]
driversload.cmd=a,,1
driverpacks\DP_MassStorage_wnt5_x86-32_1010.7z=a,DP_MassStorage_wnt5_x86-32.7z,1
[Software.AddReg]
; XPE Shortcuts
0x2,"Sherpya\XPEinit\Programs","Device Management\Drivers Load\MassStorage Drivers","%SystemDrive%\Programs\alternativedrivers\driversload.cmd|DP_MassStorage_wnt5_x86-32.7z"
driversload.cmd
@echo off
color 1f
SETLOCAL ENABLEEXTENSIONS
TITLE=Driverpacks - Drivers Load...
cd /d "%SystemDrive%\Programs\Driver Import"
set driverspack=%1
DrvImpe.exe -i:"%SystemDrive%\Programs\alternativedrivers\%driverspack%"
endlocal
EXIT
This way to do it is QUICK and RELIABLE. (for me at least :-) )
Bye