Today I tried driver from Post #6 at BartPE: booting fails, incorrect driver.
At second glance: link refers to a 64 bit driver.

There are 32 bit drivers too.
http://www.3ware.com/download/Escalade9 … nstall.zip

I doubt SCSI\Processor_* is required at textmode. Don't include this to ini file.

Slightly offtopic:
Funny txtsetup.oem

[HardwareIds.scsi.AMCC]
id = "PCI\VEN_13C1&DEV_1002","3wareDrv"
id = "PCI\VEN_13C1&DEV_1003","3wareDrv"
id = "PCI\VEN_13C1&DEV_1004","3wareDrv"
id = "PCI\VEN_13C1&DEV_1005","3wareDrv"
id = "USB\VID_03F0&PID_2001", "usbstor" #--HP
id = "USB\VID_054C&PID_002C", "usbstor" #--Sony
id = "USB\VID_057B&PID_0001", "usbstor" #--Y-E Data
id = "USB\VID_0409&PID_0040", "usbstor" #--NEC
id = "USB\VID_0424&PID_0FDC", "usbstor" #--SMSC
id = "USB\VID_08BD&PID_1100", "usbstor" #--Iomega
id = "USB\VID_055D&PID_2020", "usbstor" #--Samsung

3ware did add HardwareIDs for high capacity floppies too.
Compare http://www.msfn.org/board/Using-a-F6-Dr … 82711.html
http://support.microsoft.com/kb/916196

That's because you have the USB floppy driver here. The regular floppy driver (which I use and slipstream with nLite for my Windows Setup CD), does not use the USBSTOR driver.

About the 64-bit thing: you are right, sorry my fault. The proper link to the 2008 version of the regular floppy 32-bit Windows XP driver is:

http://www.3ware.com/download/Escalade9 … .5.0.1.zip

There are 32 bit drivers too.
http://www.3ware.com/download/Escalade9 … nstall.zip

I doubt SCSI\Processor_* is required at textmode. Don't include this to ini file.

Slightly offtopic:
Funny txtsetup.oem

[HardwareIds.scsi.AMCC]
id = "PCI\VEN_13C1&DEV_1002","3wareDrv"
id = "PCI\VEN_13C1&DEV_1003","3wareDrv"
id = "PCI\VEN_13C1&DEV_1004","3wareDrv"
id = "PCI\VEN_13C1&DEV_1005","3wareDrv"
id = "USB\VID_03F0&PID_2001", "usbstor" #--HP
id = "USB\VID_054C&PID_002C", "usbstor" #--Sony
id = "USB\VID_057B&PID_0001", "usbstor" #--Y-E Data
id = "USB\VID_0409&PID_0040", "usbstor" #--NEC
id = "USB\VID_0424&PID_0FDC", "usbstor" #--SMSC
id = "USB\VID_08BD&PID_1100", "usbstor" #--Iomega
id = "USB\VID_055D&PID_2020", "usbstor" #--Samsung

3ware did add HardwareIDs for high capacity floppies too.
Compare http://www.msfn.org/board/Using-a-F6-Dr … 82711.html
http://support.microsoft.com/kb/916196

remember you are not in windows.
you are in WinPE - BartPE ( windows Preinstallation Environment ).
in WinPE PnP support is not yet fully on line. so you will not see a clean device manager (ever)
for mass storage and most other devices the textmode drivers are used for access not the PnP drivers.
PE is not meant to be a replacement for windows. it is just an installation and repair tool.

However, by just replacing the 3WARE9K.SY_ file by a compressed copy of the 2007 driver (why not 2008 driver?) from Massstorage 805, I have no BSOD and my RAID drives are recognized. But then something interesting is visible in "Device Manager". Eventhough my RAID array is perfectly accessible, Windows still does not recognize my card! It is listed with the "Other Devices" (the yellow question mark icon), with its SCSI/RAW device name with underscores. It says it has the following hardware IDs:

SCSI\Processor__AMCC__SATA_RAID_9650SE____
SCSI\Processor__AMCC__SATA_RAID_9650SE
SCSI\Processor__AMCC__
SCSI\__AMCC__SATA_RAID_9650SE_
__AMCC__SATA_RAID_9650SE_

It seems I am indeed lucky it works...

I will now download the newest version of the massstoragedriverpack and try building the UBCD4Win with that.

2008 has fourth line as this
PCI\VEN_13C1&DEV_1005&SUBSYS_100513C1

I will try this again, with this

[3]
ms_count=1
ms_1_deviceName="3ware AMMC 9000/9500 Series SATA RAID Controller"
ms_1_tag="3wareDrv"
ms_1_sysFile="3wareDrv.SYS"
ms_1_hwids="PCI\VEN_13C1&DEV_1002&SUBSYS_100213C1,PCI\VEN_13C1&DEV_1003&SUBSYS_100313C1,PCI\VEN_13C1&DEV_1004&SUBSYS_100413C1,PCI\VEN_13C1&DEV_1005&SUBSYS_100513C1,SCSI\Processor__AMCC__SATA_RAID_9500S_,SCSI\Processor__AMCC__SATA_RAID_9550SX,SCSI\Processor__AMCC__SATA_RAID_9650SE,SCSI\Processor__AMCC___SAS_RAID_9690SA"
ms_1_isBusExtender=false

I just noticed that the HWID posted was the fourth?
And PE does not care for that?
The CAT for the 2008 version has DEV_1005&SUBSYS_100513C1 inside, so that new INF file is not wrong..
I've added the SCSI lines to the INI hoping that will work.

he was surprised it didn't just crash when you did this - so you were lucky

as far as directions please see my signature for the tutorial - lol

It's also available in the PEbuilders 'plugin page' by highlighting base or a pack and hitting the help button...

I will have to think of a way to make that easier to find

have a great day!!!
and to quote Jaak - "Thanks for helping us to help you"

the tutorial is still in Revision 1, feedback on that is also appreciated!

PS you can skip most of the way down to where it says
" you will have the following new folder under \plugins... ' \plugin\DriverPacks.net\BASE' "
but please read it so you're familiar with the basic process...

Since your PlugIn is already created for you - just copy the new mass storage pack to ' \plugin\DriverPacks.net\BASE\DriverPacks\' 
and then press the 'config' button in pebuilder with DP-Base highlighted in the plugins window.
this will automagicaly update your current plugin to the latest pack version in the \DriverPacks folder.

Simple and Easy!

OH, I have to tell one thing to slimesmile.
the HWIDS list is NOT the same
There are four HWIDs, and the fourth has a difference.
You are lucky your bartPE runs, and that your machine does not use the fourth.

Ok, if you say so, I am lucky. Strange that your test with the new driver does not work. I do not have enough understanding of hardware-id's to see why I am lucky though.

I do not know how to put another pack in to the UBCD4WIN, but my workaround (replacing the .sys file) is easy and works for me.

I remember causing a false corrupt driver message when I tried to load it from floppy long ago during Windows XP setup wit $OEM$ preinstall, luckily nLite warns for this issue now.

Also, are you sure you did not use a 32-bit driver in a 64-bit environment?

Sorry if I sound stupid, but I don't understand why I am lucky that the .sys file replacing works. I have noticed the driver archive contains two INF files, but I also know nLite can slipstream it into my XP Setup CD without problems.

might be something to that... however, they are not sorted. so...

i can change mass storage around pretty fast now about 75% of that module is written since version 7

The hyperion (VIBUS) we load has support for 571 and ANOTHER.
What triggered my attention to this is basically this.
DriverPacks BASE 7052 loaded this later on.
DriverPacks BASE 805 has changed something in load order.
The busdrivers now show before scsi?

and 3waredrv loaded after ali and Qware and adaptec.. ??
It is first in INI, it should have loaded first.

The live machine I tested on ran vista x64 setup with good result, and vista tests memory pretty good.
----
OH, I have to tell one thing to slimesmile.
the HWIDS list is NOT the same
There are four HWIDs, and the fourth has a difference.
You are lucky your bartPE runs, and that your machine does not use the fourth.

Thanks for posting yours!

Have you tried just useing the current pack - instead of the one that came with your build?
I belive the included pack is from last year...