Re: Ultimate Boot CD for Windows delivers BSOD

I failed to build the UBCD4WIN with the new driverpacks. I read the tutorial but the UBCD4WIN building process is way more complex than a blank BartPE, the building script easily breaks, and all my attempts with DP_BASE gave "not available for this platform" errors. When I desperately just tried to replace the files, I got no drivers at all (the UBCD4WIN CD then booted without BSOD but my RAID drives were not accessible). There must be another way to generate those .inf files, but since it already cost me a lot of time and CD-R's I think it will be best for me to just wait for the UBCD4WIN creators to include Massstorage 805.

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...

Re: Ultimate Boot CD for Windows delivers BSOD

That is the normal behavior for a device like this.

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.

DP BartPE Tutorial   DP_BASE Tutorial   HWID's Tool     Read BEFORE you post    UserBars!
http://driverpacks.net/userbar/admin-1.png
The DriverPacks, the DP_Base program, and Support Forum are FREE!.

Re: Ultimate Boot CD for Windows delivers BSOD

I spent several hours doing several live tests while I was trying to add the 2008 version of that 3wareDrv.
The INI section I posted was the last thing I did.. I had to postpone this.

The answer was 42?
Kind regards, Jaak.

Re: Ultimate Boot CD for Windows delivers BSOD

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

Re: Ultimate Boot CD for Windows delivers BSOD

well, the site is back?
when I looked for 3ware.com the site was inaccessible.

The answer was 42?
Kind regards, Jaak.

Re: Ultimate Boot CD for Windows delivers BSOD

cdob wrote:

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