New ide raid drivers for install LOOK INSIDE

**webmedic** · September 11, 2003

Ok somebody pm'd me wanting his fastrack raid drviers slipstreamed into the install here they are I thought others may enjoy them also.

You need to put IDE_RAID into your drivers directory then the stuff in i386 goes into your i386 directory. THESE FILES WILL ONLY WORK WITH SERVICE PACK ! slipstreamed into your install. The txtsetup.sif changed between sp1 and the original windows xp otherwise it would work with both.

If anybody has problems with it let me know.

http://www.webmedic.net/drivers.cab

**jonnywi** · September 11, 2003

hi webmedic

thx for integrating

FASTTRAK2.INF

But i think, the fasttrak2 raid controller will not be install

because

you not changed txtsetup.sif

like

[HardwareIdsDatabase]

pci\ven_105a&dev_0d30&cc_0104 = "fasttrak"

.......

i think i can't use the raidcontroller on setup.

i'm now trying to integrate my fasttrak controller with your methode and kicking your fasttrak.sys inf cat and editing the txtsetup.sif

thx

**webmedic** · September 11, 2003

the raid is done down below wiht the settings of = ultra

also to note i have it working just fine wiht raid now on other boards let me know hot it goes for you.

**jonnywi** · September 11, 2003

ok, i toast fast a cd and try it!

see you in some minutes

**jonnywi** · September 11, 2003

i added the files to i386

and to $oem$/$1/...

ok, i try to translate to english

no storrage-device found

f3=abort instalation

**webmedic** · September 12, 2003

alright I'll see. That is during the text part. make sure that for the winnt.sif you also add the IDE_RAID directory to your oempnpdrivers path.

Let me look at it again. The inf file for them was very strange. and the funny thing is that it is hte smae hardware as is already there. The identfication strings are just different from everything I have seen before.

**webmedic** · September 12, 2003

ok one more thing is this a sata raid device or only an older ide raid device?

from the drivers I would say older ide raid device.

not only that does it do raid at all? there is no driver asigned for raid in the original inf file. Did you hack the inf files in any way? If you did purchase this card hoping for raid and these are the original driver files well you have way to do raid with them. They can only be used as a regular ide controler.

**webmedic** · September 12, 2003

ok update I jsut looked through all the files with that set of drivers and it only includes the fastrack drivers witch are not the promise raid drivers so this is only a normal ata 100 ide controler. It wll not do raid at all. For promise he raid drivers use ultra.sys and not fastrack.sys.

also I just noticed the device strings are really strange for your drivers. For all the others the same device string as in yours they are assinged as a raid device but in yours the device string is a regular ata contoler.

This controler card is very strange were did you get it? If i was to guess it was a failed bach if raid contolers that they didn't want ot throw away so they hacked it to work as a regular ide controler but it still identifies itself with a device id as a raid controler but then only loads regular ide drivers. This is the strangest controler i have seen.

**webmedic** · September 12, 2003

ok never mind my babelings above but whatever this is it only does one or the other but not both as the drivers are not there to do both raid and regualr ide controler stuff. Ok i added some more vender strings that are in one of the other files that go with this device. I'll uplaod a drivers.cab here in a second. It will be the same link as above.

**jonnywi** · September 12, 2003

thx for the new driver.cab

i test it at home in some h.

This is a onboard controller from msi kt266pro2(i think this is the right name) board.

if i integrate it normaly without unattand with f6 and my windowsregistry say after sucessfull installation. this is a raidcontroller and the driver is the fasttrak.sys

the drivers which i sended you, was the original which i downloaded from msi.

**webmedic** · September 12, 2003

ok yes it is not so much the drivers but it is the inf files as they are what has the vvender and device id strings in them the driver files are the same for them all.

This board has some very strange device strings the board identifies itself as a raid device but loads the regualr ide drivers. or maybe the other way arround it is very strange.

**jonnywi** · September 12, 2003

s***!

same error with your second version of driver.cab.

The error occured on Textmode

one how to which i had done was successfull for integrating the controller to the textmode. but after setup was sucessfull, the driver are lost or the pc was automaticaly restart on booting

i post you the strings

**jonnywi** · September 12, 2003

cd\i386\txtsetup.sif

[sourceDisksFiles]

FASTTRAK.SYS = 1,,,,,,4_,4,1,,,1,4

[HardwareIdsDatabase]

pci\ven_105a&dev_0d30&cc_0104 = "fasttrak"

[sCSI.Load]

fasttrak = fasttrak.sys,4

[sCSI]

fasttrak = "WinXP Promise FastTrak100 Lite Controller"

cd\i386\winnt.sif

[unattended]

OEMPnPDriversPath="drivers\det30-82;drivers\fasttrak;drivers\joe\via82333b"

and copied the fasttrak.sys to cd\i386\fasttrak.sys

**jonnywi** · September 12, 2003

cd\I386\$oem$\$1\drivers\fasttrak\FASTTRAK.CAT

cd\I386\$oem$\$1\drivers\fasttrak\wxp\FASTTRAK.CAT

cd\I386\$oem$\$1\drivers\fasttrak\FASTTRAK.sys

cd\I386\$oem$\$1\drivers\fasttrak\wxp\FASTTRAK.sys

cd\I386\$oem$\$1\drivers\fasttrak\FASTTRAK

[inhalt]

fasttrak

[/inhalt]

cd\I386\$oem$\$1\drivers\fasttrak\FASTTRAK.INF

cd\I386\$oem$\$1\drivers\fasttrak\wxp\FASTTRAK.INF

[inhalt]

; FASTTRAK.INF

[Version]

CatalogFile=Fasttrak.cat

signature="$CHICAGO$"

Class=SCSIAdapter

ClassGUID={4D36E97B-E325-11CE-BFC1-08002BE10318}

Provider=%PROMISE%

DriverVer=03/13/2001, 2.00 Build 9

[DestinationDirs]

DefaultDestDir = 12 ; DIRID_DRIVERS

MoveMiniPort.NT = 12;

[ControlFlags]

[Manufacturer]

%Promise%=Promise

[Promise]

%PCI\VEN_105A&DEV_6268&CC_0104.DeviceDesc%=FasttrakPCITX2, PCI\VEN_105A&DEV_6268&CC_0104

%PCI\VEN_105A&DEV_1275&CC_0104.DeviceDesc%=FasttrakPCI275, PCI\VEN_105A&DEV_1275&CC_0104

%PCI\VEN_105A&DEV_5275&CC_0104.DeviceDesc%=FasttrakPCI276, PCI\VEN_105A&DEV_5275&CC_0104

%PCI\VEN_105A&DEV_7275&CC_0104.DeviceDesc%=FasttrakPCI277, PCI\VEN_105A&DEV_7275&CC_0104

%PCI\VEN_105A&DEV_0D30&CC_0104.DeviceDesc%=FasttrakPCI100_265, PCI\VEN_105A&DEV_0D30&CC_0104

%PCI\VEN_105A&DEV_4D30&CC_0104.DeviceDesc%=FasttrakPCI100, PCI\VEN_105A&DEV_4D30&CC_0104

%PCI\VEN_105A&DEV_4D38&CC_0104.DeviceDesc%=FasttrakPCI66, PCI\VEN_105A&DEV_4D38&CC_0104

%PCI\VEN_105A&DEV_4d33.DeviceDesc% =FasttrakPCI33, PCI\VEN_105A&DEV_4d33

[FasttrakPCI33.NT]

CopyFiles=MoveMiniPort.NT

Reboot

[FasttrakPCI33.NT.Services]

AddService = fasttrak, 2, FasttrakPCI_Service_Inst, Miniport_EventLog_Inst