You are not logged in. Please login or register.
Active topics Unanswered topics
Search options
DriverPacks.net Forum » Posts by slimesmile
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
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...
Thank you for trying to help.
I will now download the newest version of the massstoragedriverpack and try building the UBCD4Win with that.
Jaak wrote: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.
Jaak wrote:I think less than 35 percent of the posts are helping us in the first post, and the people who really want to help you want you to help us by submitting more data and logs.
I think we are getting a little off-topic here... Back to my problem.
Although I still think just replacing the .sys file is enough for all 3ware 9xxx models, for your further research I will now provide more data, i.e. the ID info of my card:
AMCC 3ware 9650SE SATA RAID Controller
Device Instance Id:
PCI\VEN_13C1&DEV_1004&SUBSYS_100413C1&REV_01\4&662654C&0&00E0
Hardware Ids:
PCI\VEN_13C1&DEV_1004&SUBSYS_100413C1&REV_01
PCI\VEN_13C1&DEV_1004&SUBSYS_100413C1
PCI\VEN_13C1&DEV_1004&CC_010400
PCI\VEN_13C1&DEV_1004&CC_0104
Compatible Ids:
PCI\VEN_13C1&DEV_1004&REV_01
PCI\VEN_13C1&DEV_1004
PCI\VEN_13C1&CC_010400
PCI\VEN_13C1&CC_0104
PCI\VEN_13C1
PCI\CC_010400
PCI\CC_0104
Matching Device Id:
pci\ven_13c1&dev_1004&subsys_100413c1
JakeLD wrote:sound good but tellme how do youc ompress a file ? I use expand to decompress, for compressing i have no clue. I've searched for un-expand tool and no luck.
I use makecab, included with Windows XP. It can be used for single files too.
Jaak wrote:I see..
DriverPack MassStorage 7092 used 3ware9k tagname
DriverPack MassStorage 711 uses a new tagname (it updated to the 2006 version then)
and dpm805xx will have to use a the 2008 version of this driver.
(funny how some drivers behave when they get renamed by a tag.. but, since we have not used 3ware9k tag since november 2007 I get this feeling this happened after restreaming the plugin.)
the 2008 version presents me with a problem.. it has two INF files now..
Just replacing the .sys file in the pack is not ok? It works for me...
For as far is I know the entire 9xxx series use the same driver.
One more important thing. Someone on the UBCD4WIN forum said the 3ware9k.sys driver from the driverpack is from 2006. For as far as I have seen, all 3ware 9xxx models have the same DeviceID's and share the same driver. Since 3ware clearly states that new firmware versions require new driver versions, it is unlikely for a 2006 driver to work.
Hence, the 2008 version of 3wareDrv.sys should work for all 3ware 9xxx models and should be the new 3ware9k.sys, which can be compressed to be the new 3ware9k.sy_. It is available in this package:
http://www.3ware.com/download/Escalade9 … .5.0.1.zip
Please use this driver in future driverpack releases, and the UBCD4WIN problem will be solved automatically.
DeTard wrote:Might want to post the exact BSOD error code too.
I recently upgraded to UBCD4WIN 3.13, and built it with Windows XP Professional Service Pack 3. The error is still there, and the text on the BSOD, gives the following information:
A problem has been detected and Windows has been shut down to prevent damage to your computer.
The problem seems to be caused by the following file: 3ware9k.SY_
The driver mistakenly marked a part of it's image pagable instead of nonpagable.
Then after the standard directions:
Technical Information:
*** STOP: 0x000000D3 (0xF693CEC0,0x00000002,0x00000001,0x8040F37F)
3ware9k.SY_
OverFlow wrote:which mass storage pack version are you useing?
The one that is on UBCD4WIN 3.12, I can't find which one that is.
DeTard wrote:Might want to post the exact BSOD error code too.
I will as soon as possible.
I posted this issue before on the UBCD4WIN forum and they told me to post it here.
I have a 3Ware 9650-4LPML PCI-Express RAID controller in my system. When I try to launch the UBCD4WIN, it bluescreens me about failing to load the driver "3ware9k.sy_". Yes, it tries to use it while it's still compressed!
I have been able to resolve this issue by taking the official .sys driver of the 9650, renaming (not compressing) it to 3ware9k.sy_ and replace that file on the UBCD4WIN.
I hope this issue will be fixed in future versions.
Posts found [ 10 ]
DriverPacks.net Forum » Posts by slimesmile
Powered by PunBB, supported by Informer Technologies, Inc.
Currently installed 3 official extensions. Copyright © 2003–2009 PunBB.
[ Generated in 0.012 seconds, 5 queries executed ]