Jump to content
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble

MSFN is made available via donations, subscriptions and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. Alternatively, register and become a site sponsor/subscriber and ads will be disabled automatically. 


Sign in to follow this  
webmedic

The complete how to for getting your raid working.

Does this method work for you yet  

23 members have voted

  1. 1. Does this method work for you yet

    • No
      4
    • Yes
      6
    • Yes but not durring gui mode.
      1


Recommended Posts

Ok I'll atempt to discribe how to add your own raid drivers. I would apriciate knowing which boards you ahave all got this working on and which raid controler you are using. If possible I would also like to keep sets so that others can benefit from this also. We can slowly work throguh them all till as many as we can get to work do work.

For the first set I'll post mine. It is known to work with

epox 8k5a2+, 8k3a+, and I assume 8k5a3+, motherboards using highpoint 372 and 374 controllers,

Gigabyte ga-7vrxp using promise 20276

Shuttle ak35gtr? using high point 372 in both regular and raid mode

Aopen ak79D max using promise pdc20375 Sata150. This works both with regular ide drives and sata drives.

Soltek using promise pdc20376 sata150. I was only able to get it to work with the sata drive but this motherboard has issues and it is not an issue with drivers as far as I can see.

UPDATE VERIFIED WORKING WITH:

Abit kd7 raid using high point 372

Abit be6-II using high point 370

epox 8kra2+ using high point 372

msi kt400

These all work with this driver set: Drivers

Now If I have forgotten anything let me know. Also to note If there are any questions please post them here. I'm truly interested in getting this working for all of you.

Now for driver cab you will find ide_raid extract that and place it into your drivers folder and add it to your winnt.sif like so

OemPnPDriversPath="Drivers\nforce;Drivers\4in1442v;Drivers\IDE_RAID;"

this will allow you to use the raid controler after you reboot into graphical install mode.

For all the files in the i386 place these into your i386 directory. These are the files that will allow you to use the raid controler durring text mode. I have included in the 1386 folder a file callled txtsetup.sif This file works with english windowsxp with service pack 1 slipstreamed. Dont try to use it if you dont have service pack one slipstreamed.

If you dont have service pack 1 slipstreemed nto your install please use the guide below.

Now for the how to:

This is copied from here:

http://www.ee.ethz.ch/~slist/realmen/msg00045.html

but I have added to it since I read this and this explination is very complete so I have just copied it here

++++++++++++++++++++++++++++++++++++++++++++++++++++

Anyway, in order to thank you all for the work done, I'd like to bring

my own little brick to the building, just in case it might be

useful...

I met the same kind of problem than Alain : wanted to include

third-party mass storage drivers to be used during the text-mode part

of a Windows 2000 CD-based setup.

In other words, I wanted to get rid of the boring "F6 curse".

Pierre's tip works great for the GUI-part of the setup but text-mode

setup repeatedly ended with the error :

"File txtsetup.oem caused an unexpected error (18)

at line 1041 in F:\nt\private\ntos\boot\setup\oemdisk.c",

no matter where I put the drivers : the root of the CD, $OEM$, I386 or

I386\$OEM$.

Here's how I got it working :

======================================================================

My example is based on the IBM ServeRAID driver v5.10.

I guess it could be easily adapted to other hardware

1. Copy the driver (nfrd960.sys) in the I386 directory

2. Update the file I386\txtsetup.sif, picking parts of the

txtsetup.oem file provided on the ServeRAID driver disk, adapted to

the txtsetup.sif's syntax. There are 4 sections concerned :

[sourceDisksFiles]

nfrd960.sys = 1,,,,,,_x,4,1

[sCSI]

nfrd960 = "IBM ServeRAID 4M/4Mx/4L/4Lx/5i Controller (Windows 2000)"

[sCSI.Load]

nfrd960 = nfrd960.sys,4

[HardwareIdsDatabase]

"PCI\VEN_1014&DEV_01BD"= "nfrd960"

======================================================================

Comments :

--------

1. I think that, in the text-mode part of the setup, drivers are used

in a rather less sofisticated way than under the GUI part. That would

explain why there is no need (in this part) for the .dll, .cat or .inf

files (and the parameters stored in them).

2. But being loaded during the text-mode doesn't mean installed on

Windows 2000. So you still have to install your driver in the GUI

part, using Pierre's method.

3. For the "Line 2 of the INF file is invalid" error, I suggest to

check the following KB article :

http://support.microsoft.com/default.aspx?...EN-US;Q304305&;

Guesses :

--------

1. I didn't succeeded in loading drivers for the text-mode setup by

copying them in the

$OEM$ tree.

During this part of the setup, the CDFS file system is not yet loaded,

so the only character-set that setup is able to read is the ISO9660,

which doesn't include "$" In other words I think that, at that time,

the directory is read as "_OEM_" :-)

2. During my investigations, I parsed the txtsetup.sif file to see how

and where the "retail" SCSI drivers were listed.

In the [sourceDisksFiles] section, they are all referenced in the form

:

driver.sys = 1,,,,,,3_,4,1

I changed the "3_" to "_x" because I noticed that all the files that

where not

compressed in the I386 directory where referenced this way

======================================================================

APPENDIX - Content of the original TXTSETUP.OEM file (from the

ServeRAID driver diskette) :

[Disks]

d1 = "IBM ServeRAID Device Driver Diskette",

\Win2kSrv\driver\i960\NFRD960.SYS, \Win2kSrv\driver\i960

[Defaults]

scsi = NFRDWin2k32

[scsi]

NFRDWin2k32 = "IBM ServeRAID 4M/4Mx/4L/4Lx/5i Controller (Windows

2000)"

# If you hit F6 and specify to load an OEM driver, NT loads the first

driver in

# the list. If you don't hit F6 and specify to load an OEM driver, NT

loads

# the last driver in the list.

[Files.scsi.NFRDWin2k32]

driver = d1, nfrd960.sys, NFRD960

dll = d1, nfrdci01.dll

driver = d1, nfrd960.sys, NFRD960

catalog = d1, ibmnfrd.cat

inf = d1, oemsetup.inf

[Config.NFRD960]

value = parameters\PnpInterface,5,REG_DWORD,1

value = parameters\Device,NumberOfRequests,REG_DWORD,128

[Config.IPSRAIDN]

value = parameters\PnpInterface,5,REG_DWORD,1

value = parameters\Device,NumberOfRequests,REG_DWORD,128

[HardwareIDs.scsi.NFRDWin2k32]

id = "PCI\VEN_1014&DEV_01BD", "nfrd960"

======================================================================

++++++++++++++++++++++++++++++++++++++++++++++++++++

Share this post


Link to post
Share on other sites

ok ive used ur how to before for integrating the raid drivers and ive successfully got it too work with a Abit kd7 raid and epox 8kra2+ mobo which both use the highpoint 372/374 drivers.

Share this post


Link to post
Share on other sites

thanks for the update and yes I forgot myself that it works with my abit board. I'll add that also.

Share this post


Link to post
Share on other sites

Well let's start from the beginning, I have a Gigabyte 8PE667U mobo with raid integreded the light promise raid 20276 chip.

I use a modified BIOS for my pc from http://lumberjacker.kettenfett.com/

which offers me more options in BIOS menu and modifies my light RAID to a Full working TX2000 controller! :rolleyes::D

So i'm trying to integrade my modified Raid drivers to work with XP setup without having to press F6 during textmode setup.

They can be reached there : http://www.anycities.com/user/treiber/

I've managed to find allot of information but nothing seemed to work except that post i've had from Cheesehead yesterday.

It Goes Like this :

[sourceDisksFiles]

fasttrak.sys = 1,,,,,,_x,4,1

fasttrak.inf = 1,,,,,,,20,0,0

[HardwareIdsDatabase]

PCI\VEN_105A&DEV_5275 = "fasttrak"

[sCSI.Load]

fasttrak = fasttrak.sys,4

[sCSI]

fasttrak = "Promise FastTrak TX2000 Controller (PDC20276)"

That code entered in TXTSETUP.SIF worked for me just fine during textmode setup, my controller identified just fine, setup continued and ended just fine.

But then when setup finished and my Pc restarted, then only terror!!!!!!!!! :D

My pc reboots all the time during loading.........

Well guys what next???????????

Thanks :)

Share this post


Link to post
Share on other sites

now make sure that you put your whole driver set under $OEM$\$1\drivers\IDE_RAID

and then make sure to add the path to your winnt.sif as I've mentioned above in this how to.

Share this post


Link to post
Share on other sites

hi here is my report.

MB= Gigabyte 8IRXP

Raid cont. on board= WinXP Promise MBUltra133 (PDC20276) IDE Controller

TX2000 in full Raid modus!

[sourceDisksFiles]

ultra.sys = 1,,,,,,_x,4,1

ultra.inf = 1,,,,,,,20,0,0

[sCSI]

ultra = "WinXP Promise MBUltra133 (PDC20276) IDE Controller"

[sCSI.Load]

ultra = ultra.sys,4

[HardwareIdsDatabase]

"PCI\VEN_105A&DEV_5275"= "ultra"

Winnt.sif

OemPnPDriversPath="Drivers\NVIDIA;Drivers\infinst_enu\xp;Drivers\IDE_RAID;Drivers\RASPPPOE_098B;Drivers\PRO100\WS03XP32;Drivers\LXKZ12;Drivers\SM3800"

$OEM$\$1\drivers\IDE_RAID

Bios

Raid/ATA set=ATA

boot:

Raid/Scsi = Scsi

HD0,1,2;floppy....scsi = Scsi

If I set RAid PC boots with Full working TX2000 controller.

If I set ATA and Scsi PC boots with ATA 133.

The point is XP finds still no HD`s :rolleyes: dam!

Djus :)

Share this post


Link to post
Share on other sites
hi  here is my report.

MB= Gigabyte 8IRXP

Raid cont. on board= WinXP Promise MBUltra133 (PDC20276) IDE Controller

                                                      TX2000  in full Raid modus!

[sourceDisksFiles]

ultra.sys = 1,,,,,,_x,4,1

ultra.inf = 1,,,,,,,20,0,0

[sCSI]

ultra = "WinXP Promise MBUltra133 (PDC20276) IDE Controller"

[sCSI.Load]

ultra = ultra.sys,4

[HardwareIdsDatabase]

"PCI\VEN_105A&DEV_5275"= "ultra"

Winnt.sif

OemPnPDriversPath="Drivers\NVIDIA;Drivers\infinst_enu\xp;Drivers\IDE_RAID;Drivers\RASPPPOE_098B;Drivers\PRO100\WS03XP32;Drivers\LXKZ12;Drivers\SM3800"

$OEM$\$1\drivers\IDE_RAID

Bios

Raid/ATA set=ATA

boot:

Raid/Scsi = Scsi

HD0,1,2;floppy....scsi = Scsi

If I set RAid PC boots with Full working TX2000 controller.

If I set ATA and Scsi PC boots with ATA 133.

The point is XP finds still no HD`s :rolleyes: dam!

Djus :)

did you try using the drivers cab listed above?

Also to note by loadeing the ultra.sys and not the fasttrack.sys you are only laoding hte raid controler an dnot the regualr ide ata 133 controler. so if you aren't using raid on that board then it will simply not work.

Share this post


Link to post
Share on other sites
did you try using the drivers cab listed above?

Also to note by loadeing the ultra.sys and not the fasttrack.sys you are only laoding hte raid controler an dnot the regualr ide ata 133 controler. so if you aren't using raid on that board then it will simply not work.

Yes, I did use your *.cab

What do you mean?

why shoul I use fastrak.sys?

It is WinXP Promise MBUltra133 (PDC20276) ™ IDE Controller so I use ultra.sys!

If I intend to us RAID than it would be fastrak.sys.

Or am I wrong.

I dont use my RAid controler for raid, I us it as ATA133/UDMA6!!!

Is it not posiblle to boot with ATA133???only with Raid :)

My MB has IDE1 & 2 = UDMA5 and IDE 3 & 4 RAID/UDMA6.

Share this post


Link to post
Share on other sites

I may be wrong but hte fasttrack driver is if you are not using raid. I believe . Dont quite me on that. Hold on I'll upload a new cab shortly and you all can try that instead.

Share this post


Link to post
Share on other sites

You will not believe this.

I just did a update of my driver for my WinXP Promise MBUltra133 (PDC20276) IDE Controller and coose your *.cab as source.

Now I have Promise Fasttrak full raid 133 controller (pdc 20276) in my Device Manager.

My HD conected to Raid controller shows as:

Promise 1 + 0 Stripe/Raid SCSi disk drive.

How is this posiblle, and what is 1+0 stripe ?

How is Raid posiblle with only one HD?

Share this post


Link to post
Share on other sites

lol it is not. but you may have set it to something funny in hte raid controler bios.

raid 1+0 is mirror and stripping raid. at the same time.

Share this post


Link to post
Share on other sites
lol it is not. but you may have set it to something funny in hte raid controler bios.

raid 1+0 is mirror and stripping raid. at the same time.

I didnt touch contoller bios!

I just rebooted and chacked my PC bios - nothing is wrong.

On PC boot shows MB ultra 133 2.201.12 and finds my HD at UDMA6.

XP commes up and showes in Device Manager "Promise Fasttrak full raid 133 ™ controller (pdc 20276)"

Promise 1 + 0 Stripe/Raid SCSi disk drive

so Im confused :):rolleyes::D

Djus :/

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Sign in to follow this  

  • Recently Browsing   0 members

    No registered users viewing this page.

×
×
  • Create New...