Help - Search - Members - Calendar
Full Version: BartPE and Driverpacks Mass Storage
The CD Forum > Bart's PE Builder > General
araczek

I am trying to get BartPE to see my RAID and drives in a Dell r510. Before Driverpacks it would crash with a STOP 7e error. After Driverpacks
it gets past the crash but does not see the partition I created in Gparted. But I still kept the drivers in the SCSIadapter directory in BartPE now
that I think about it so I was wondering if I need to empty that directory since Driverpacks is active??

Can't find much on this, help appreciated.

...AR
Ed_P
QUOTE (araczek @ Nov 16 2010, 08:15 AM) *
I was wondering if I need to empty that directory since Driverpacks is active??

Having similar drivers in two place can cause conflicts as to which one gets installed. Yes, I would remove the drivers from the SCSI folder at this point.
araczek
QUOTE (Ed_P @ Nov 16 2010, 09:16 AM) *
Having similar drivers in two place can cause conflicts as to which one gets installed. Yes, I would remove the drivers from the SCSI folder at this point.


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.
profp62
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.html
I 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
Juozas
You could try to get the right driver files using driver backup software. There're alot free and comercial ones, ones better others not, it's your choice. As you got the driver files, you may make a plugin fot it if it's not included with MS packs or isn't from MS. Or you can more in spec. folder in pebuilder dir.
I done this for my net driver (made a plugin) so it should work ok for you too. Check the device manager too if you got it there working, try hwpnp plugin too.
cdob
QUOTE (araczek @ Nov 16 2010, 03:25 PM) *
PERC 6/i

http://www.911cd.net/forums//index.php?showtopic=20930
rdsok
QUOTE (araczek @ Nov 16 2010, 08:25 AM) *
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.


Are you sure you mean "virtual drive" and not "partition"... there is a big difference between the two and even if you supply the proper driver, you won't ever see a virtual drive within a PE build without using the virtual machine software to load it. Everyone's suggestions up to this point has been on the assumption that you misused the term "virtual drive" and had actually meant to say partition instead.
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.
Invision Power Board © 2001-2013 Invision Power Services, Inc.