Jump to content

Unable to integrate NVRAID drivers for K8N Neo2


userguy

Recommended Posts

I have searched the board and not found a resolution to this (although it'd be nice if google was allowed to cache the documents, to make them easier to skim).

I've been trying for the last week to make a slipstreamed XP CD that includes the RAID drivers for my K8N Neo2 Platinum motherboard. Every try has failed and the system always comes up with a 7B stop error after "Windows is starting" in textmode setup. If anyone can help I'd appreciate it. I'll try to outline the methods I've tried.

I've tried with both the 6.53 and the 5.10 nForce drivers (this is an nForce3 board). I also tried the MSI drivers provided directly from their site. My setup is 2x80GB drives in a RAID 0 stripe. The drives are connected to the PARALLEL cables, in other words IDE, not SATA.

For the DriverPacks, I tried 5.06 and 5.07 MassStorage drivers. Neither worked. I tried both with method 1 and method 2. Neither worked.

I was going to try the RASOR utility, but it doesn't seem possible to download it.

I tried the method shown here: http://www.dfi-street.com/forum/showthread.php?t=6907 with both the 5.10s and 6.53s and MSI drivers, none worked.

I've tried nLite's method of integrating text mode drivers, all three versions, neither worked.

I have not tried this method: http://www.msfn.org/board/index.php?showtopic=12566

If anyone here has successfully gotten their MSI K8N Neo2 Platinum to work, or if anyone has a *working* disc with the nVidia text-mode drivers for nForce boards that would like to share with me exactly what they did to make it work, or if anyone is just interested in figuring out why this doesn't work, I would appreciate your help.

Edited by userguy
Link to comment
Share on other sites


The latest one I made, with nLite, doesn't have a winnt.sif. I tried making it after I read this:

http://www.msfn.org/board/index.php?showtopic=49505

and found a line missing from txtsetup.sif (*NVRAIDBUS = "nvraid"). I burned it, booted it, and same old story: BSOD with 7B.

I would like to think I'm not doing anything wrong but maybe I am. I have exactly followed the steps in this one for sure:

http://www.dfi-street.com/forum/showthread.php?t=6907

because I did it so many times with different driver versions.

Is there some specific order the txtsetup.sif file is supposed to have the driver entries? nLite puts them in backwards (bottom to top) from how it's shown in every tutorial (and I've tried it both ways).

Link to comment
Share on other sites

In the interest of being as helpful as I can be, I did the following:

- Recopied the source files from my XP SP2 disc

- Redownloaded the DriverPack files Base 5.07.1 and MassStorage 5.07

- Re-integrated drivers using method 1 with the option of RunOnceEx and Keep drivers

I then made an ISO of the files with nLite (latest version, downloaded yesterday) and burned it (again) to my CD-RW. Rebooted, ran through, same error: STOP 7B.

Here's my WINNT.SIF file:

;Generated by Bashrat the Sneaky's DriverPacks BASE 

[Data]
MsDosInitiated = "No"
[Unattended]
OemPnPDriversPath = "D\M\3\1;D\M\3\2;D\M\3\3;D\M\A\1;D\M\A\2;D\M\A\3;D\M\A\4;D\M\A\5;D\M\A\6;
D\M\A\7;D\M\A\8;D\M\AD\1;D\M\AD\2;D\M\AD\3;D\M\AD\4;D\M\AD\5;D\M\AD\6;
D\M\AD\6\C;D\M\AD\7;D\M\AD\8;D\M\AD\9;D\M\AM;D\M\AR;D\M\AT;D\M\AU\1;
D\M\AU\2;D\M\AU\3;D\M\AU\4;D\M\D;D\M\H\1;D\M\H\1\R;D\M\H\2;D\M\H\3;
D\M\H\4;D\M\H\5;D\M\I\1;D\M\I\2;D\M\IN\1;D\M\IN\2;D\M\IT;D\M\L\1;D\M\L\2;
D\M\L\3;D\M\L\4;D\M\N;D\M\P\1;D\M\P\2;D\M\P\2\A;D\M\P\3;D\M\P\4;D\M\P\5;
D\M\P\6;D\M\P\7;D\M\P\8;D\M\Q\1;D\M\Q\2;D\M\Q\3;D\M\Q\4;D\M\S\1;D\M\S\2;
D\M\S\3;D\M\S\4;D\M\S\5;D\M\S\6;D\M\S\7;D\M\S\8;D\M\SI\1;D\M\V\1;D\M\V\2;
D\M\V\3"
NonDriverSigningPolicy = "Ignore"
DriverSigningPolicy = "Ignore"
OemPreinstall = "Yes"

(Line breaks in the OemPnPDriversPath made by me so it won't break the forum width).

One thing I noticed is that the TXTSETUP.SIF is missing the line I mentioned above:

*NVRAIDBUS = "nvraid"

but it does have:

*_NVRAIDBUS = "nvraid"
GenNvRaidDisk = "nvraid"

Would it make a difference if I (a) added that line in, (b) used GuiRunOnce instead of RunOnceEx, (c ) told it not to keep the drivers, and/or (d) used method 2 or 3?

Edited by userguy
Link to comment
Share on other sites

Tried again using method 3, here's my WINNT.SIF:

;Generated by Bashrat the Sneaky's DriverPacks BASE 

[Unattended]
NonDriverSigningPolicy = "Ignore"
DriverSigningPolicy = "Ignore"
OemPreinstall = "Yes"
OemPnPDriversPath = "D\M\3\1;D\M\3\2;D\M\3\3;D\M\A\1;D\M\A\2;D\M\A\3;D\M\A\4;D\M\A\5;D\M\A\6;
D\M\A\7;D\M\A\8;D\M\AD\1;D\M\AD\2;D\M\AD\3;D\M\AD\4;D\M\AD\5;D\M\AD\6;
D\M\AD\6\C;D\M\AD\7;D\M\AD\8;D\M\AD\9;D\M\AM;D\M\AR;D\M\AT;D\M\AU\1;
D\M\AU\2;D\M\AU\3;D\M\AU\4;D\M\D;D\M\H\1;D\M\H\1\R;D\M\H\2;D\M\H\3;
D\M\H\4;D\M\H\5;D\M\I\1;D\M\I\2;D\M\IN\1;D\M\IN\2;D\M\IT;D\M\L\1;D\M\L\2;
D\M\L\3;D\M\L\4;D\M\N;D\M\P\1;D\M\P\2;D\M\P\2\A;D\M\P\3;D\M\P\4;D\M\P\5;
D\M\P\6;D\M\P\7;D\M\P\8;D\M\Q\1;D\M\Q\2;D\M\Q\3;D\M\Q\4;D\M\S\1;D\M\S\2;
D\M\S\3;D\M\S\4;D\M\S\5;D\M\S\6;D\M\S\7;D\M\S\8;D\M\SI\1;D\M\V\1;D\M\V\2;
D\M\V\3"
[Data]
MsDosInitiated = "No"
[GUIUnattended]
Arguments = "/Q /C START /MIN /HIGH %SystemDrive%\D\BTS_DPs_M3.cmd"
DetachedProgram = "CMD.exe"
[GUIRunOnce]
command9 = "%SystemDrive%\D\BTS_DPs_finish.cmd"

TXTSETUP.SIF is still missing:

*NVRAIDBUS = "nvraid"

I chose GuiRunOnce this time.

Link to comment
Share on other sites

I have this same motherboard and have experienced the same error. Sorry to tell you but the only thing that worked for me was the RASOR util.....I can post the util but it downloads the drivers and if the util is not up, I doubt he still has the drivers up.

Link to comment
Share on other sites

I have this same motherboard and have experienced the same error.  Sorry to tell you but the only thing that worked for me was the RASOR util.....I can post the util but it downloads the drivers and if the util is not up, I doubt he still has the drivers up.

Do you still have the disc you made from it? Can I bother you for the WINNT.SIF and TXTSETUP.SIF?

PS... thanks for replying. It's nice to know that I'm not the only one with the problem. It's even nicer knowing there's a fix.

Edited by userguy
Link to comment
Share on other sites

unfortunately, after I used the disc, I erased it to update it. The update did not include the drivers this time since I used it on my second machine. But I am going to fool with RASOR today because I remember reading somewhere that you could integrate locally if you tell it to look locally. If that's the case, I'll post the util here.

Link to comment
Share on other sites

You know I really wish I could have a final working version with the drivers. These motherboards are mega popular! You think nvidia would have released the method by now!! in fact I am headed over to their forums to see if there's anything new on it.

Link to comment
Share on other sites

As i postet in the driverpackage forum http://www.msfn.org/board/index.php?showtopic=47397http://www.msfn.org/board/index.php?showtopic=47397. You need both nvraid.sys et nvatabus.sys in your txtsetup.sif and you were absolutely correct with this :

*_NVRAIDBUS = "nvraid"

GenNvRaidDisk = "nvraid"

They have to be in the txtsetup.sif.

I show you mine :

[sourceDisksFiles]

iaStor.sys  = 1,,,,,,4_,4,1,,,1,4

Si3112.sys  = 1,,,,,,4_,4,1,,,1,4

NvAtaBus.sys = 1,,,,,,4_,4,1,,,1,4

nvraid.sys  = 1,,,,,,4_,4,1,,,1,4

sisraid.sys  = 1,,,,,,4_,4,1,,,1,4

sisraid1.sys = 1,,,,,,4_,4,1,,,1,4

sisraid2.sys = 1,,,,,,4_,4,1,,,1,4

viamraid.sys = 1,,,,,,4_,4,1,,,1,4

FastSx.sys  = 1,,,,,,4_,4,1,,,1,4

ftsata2.sys  = 1,,,,,,4_,4,1,,,1,4

ulsata.sys  = 1,,,,,,4_,4,1,,,1,4

ulsata2.sys  = 1,,,,,,4_,4,1,,,1,4

[HardwareIdsDatabase]

PCI\VEN_8086&DEV_2652&CC_0104 = "iaStor"

PCI\VEN_8086&DEV_2652&CC_0106 = "iaStor"

PCI\VEN_8086&DEV_2653&CC_0106 = "iaStor"

PCI\VEN_8086&DEV_24DF&CC_0104 = "iaStor"

PCI\VEN_8086&DEV_25B0&CC_0104 = "iaStor"

PCI\VEN_1095&DEV_3112&SUBSYS_31121095 = "Si3112"

PCI\VEN_1095&DEV_3112&SUBSYS_34238086 = "Si3112"

PCI\VEN_1095&DEV_3112&SUBSYS_311215D9 = "Si3112"

PCI\VEN_1095&DEV_3112&SUBSYS_B0021458 = "Si3112"

PCI\VEN_1095&DEV_3112&SUBSYS_01661028 = "Si3112"

PCI\VEN_1095&DEV_3112&SUBSYS_82141033 = "Si3112"

PCI\VEN_1095&DEV_3512&SUBSYS_35121095 = "Si3112"

*_NVRAIDBUS  = "nvraid"

GenNvRaidDisk = "nvraid"

PCI\VEN_10DE&DEV_008E = "NvAtaBus"

PCI\VEN_10DE&DEV_0085 = "NvAtaBus"

PCI\VEN_10DE&DEV_00E5 = "NvAtaBus"

PCI\VEN_10DE&DEV_00EE = "NvAtaBus"

PCI\VEN_10DE&DEV_00E3 = "NvAtaBus"

PCI\VEN_10DE&DEV_00D5 = "NvataBus"

PCI\VEN_10DE&DEV_0035 = "NvataBus"

PCI\VEN_10DE&DEV_0036 = "NvataBus"

PCI\VEN_10DE&DEV_003E = "NvataBus"

PCI\VEN_10DE&DEV_0053 = "NvataBus"

PCI\VEN_10DE&DEV_0054 = "NvataBus"

PCI\VEN_10DE&DEV_0055 = "NvataBus"

PCI\VEN_1039&DEV_0180&REV_01 ="SiSRaid"

PCI\VEN_1039&DEV_0181&REV_01 ="SiSRaid1"

PCI\VEN_1039&DEV_0180&REV_01 ="SiSRaid2"

PCI\VEN_1039&DEV_0182&REV_01 ="SiSRaid2"

PCI\VEN_1106&DEV_3249 = "viamraid"

PCI\VEN_1106&DEV_3149 = "viamraid"

PCI\VEN_1106&DEV_3164 = "viamraid"

PCI\VEN_105A&DEV_6621 = "FastSx"

PCI\VEN_105A&DEV_3571 = "FtSata2"

PCI\VEN_105A&DEV_3519 = "FtSata2"

PCI\VEN_105A&DEV_3574 = "FtSata2"

PCI\VEN_105A&DEV_3375 = "UlSata"

PCI\VEN_105A&DEV_3D75 = "UlSata2"

PCI\VEN_105A&DEV_3D18 = "UlSata2"

[sCSI.Load]

iaStor = iaStor.sys,4

Si3112 = Si3112.sys,4

NvAtaBus = NvAtaBus.sys,4

nvraid = nvraid.sys,4

sisraid = sisraid.sys,4

sisraid1 = sisraid1.sys,4

sisraid2 = sisraid2.sys,4

viamraid = viamraid.sys,4

fastsx = fastsx.sys,4

ftsata2 = ftsata2.sys,4

ulsata = ulsata.sys,4

ulsata2 = ulsata2.sys,4

[sCSI]

iaStor = "Intel® 82801ER-FR/6300ESB SATA AHCI/RAID Controller"

Si3112 = "Silicon Image SiI 3112 SATALink Controller"

NvAtaBus = "NVIDIA NForce Storage Controller"

nvraid = "NVIDIA RAID class driver"

SiSRaid = "SiS 180 RAID Controller"

SiSRaid1 = "SiS 180/181 RAID Controller"

SiSRaid2 = "SiS 180/182 RAID Controller"

viamraid = "VIA VT64XX SATA/RAID Controller"

FastSx = "Promise FastTrak S150 SX4/SX4000 Series"

FtSata2 = "Promise FastTrak TX Controller"

UlSata = "Promise SATA150 TX Series IDE Controller"

UlSata2 = "Promise SATAII150 TX Series IDE Controller"

You may ignore all the others brands but the Nvidias may interrest you.

And as i sad in the other thread, it worked only with the drivers from the nforce 6.53.

I hope this helps you.

Greetings from Belgium

Edited by Jackrip5
Link to comment
Share on other sites

Hi Bashrat,

Yes indeed, i tried all the series of nforce drivers i could find (whql, beta, amd, intel, 5.10, 6.11, 6.31, 6.37, 6.39, 6.53, 7.11, 7.12, 7.13 ... all you find at guru3d) but only the raid/ide drivers from the 6.53 set worked in my unattended environment. Even the IDE/RAID drivers MSI proposes on their site (NV11 - which are from the 6.37 set) don't work with my K8N Neo2(Nf3).

The results with my test were very different : some drivers did'nt recognize my Hdd drivers allready in text mode, others did and copied files correctly but at first gui install resulted with BSOD. Only with the drivers from 6.53 everything went flawlessly.

The Intel Editions have changed the driver layout so that the IDE arent whql !!

I didn't try the 6.66 in unattended, because :

A- the 6.66 layout is build just as the Intel Editions so i guess my unattended install wont work because tha lag of whql

conclusion -> no correct IDE SW drivers = No working Raid !!

B- i have this **** bootscreen problem which seems to appear when i use other IDE SW drivers than the one of the 5.10 set.

I installed the 6.66 on my working system by setup. First the install blocks because of the NAM (but thats not the point here), second i managed to install Ide and Raid drivers (ide arent whql) but my bootscreen problem does not disappear ! So i'm not interrested in testing the 6.66 in unattended - they don't eliminate my prob.

I'm now considering to make a mix of IDE SW drivers and Raid drivers, clearly mix the IDE SW from 5.10 with Raid from 6.53 but i guess it wont work because:

a- the files may need to be from same version ;

b- the whql certificate may go lost !

I know your are very experienced in this stuff, if u have a hint for me it would be nice !

Edited by Jackrip5
Link to comment
Share on other sites

In the new DriverPack MassStorage all these things are handled now (the structures of both the nForce 4 AMD & Intel Edition drivers are integrated in the folder structure/txtsetup.sif structure).

Please let me know if it works for you (when the new version has been released, should be tomorrow).

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...