[burningrave101]

Why wont beta 5 work with the 6.66 drivers if i do the method you outlined? Beta 5 will work fine with the older 6.53 drivers though wont it? I saw a couple of users mention it worked fine for them.

This post has been edited by burningrave101: 21 July 2005 - 08:33 PM

[Fernando 1]

burningrave101, on Jul 22 2005, 03:11 AM, said:

Why wont beta 5 work with the 6.66 drivers if i do the method you outlined? Beta 5 will work fine with the older 6.53 drivers though wont it? I saw a couple of users mention it worked fine for them.

Your first question can only be answered by Nuhi.
Here is what he has written about the small changes between beta4 and beta5 concerning hardware (HW) detection and the integration of chipset drivers:

nuhi, on Jul 20 2005, 08:58 PM, said:

Only thing changed is order of HW ID entries...and I can not believe how important this seems for Nforce line of controllers.
...even small driver version difference makes a difference for them.

It may be, that nLite beta5 works fine with some old nForce Sata Raid drivers. I did not test it. NLite will definitely not work with the nForce chipset packages 6.66 and higher).
So if you want to integrate the old chipset drivers (between v. 5.10 and v. 6.53), you can try nLite beta5 without making any changes I described in post 1 of this thread.
But normally people want to have the newest drivers (although they are not always the best), when they build up a new system. A later upgrade of Sata Raid drivers is not so easy and maybe dangerous too in some cases.

[Metalljens]

Hey Fernando1!
Can you explain the differences in those two txtsetup.oem below

the first one is from the 6.53
and the second one is from the 7.13, but 6.66 is the same too.


6.53

[Files.scsi.RAIDCLASS]
driver = d1,nvraid.sys,RAIDCLASS
inf = d1,nvraid.inf
dll = d1,nvraidco.dll
catalog = d1,nvraid.cat

[Files.scsi.BUSDRV]
driver = d1,nvatabus.sys,BUSDRV <----
driver = d1,nvcchflt.sys,FILTER
inf = d1, nvatabus.inf <---
dll = d1,idecoi.dll
catalog = d1, nvata.cat

in the 6.53 there is both driver and inf entries for nvatabus.sys (marked with arrows)
--------------------------------

7.13

[Files.scsi.RAIDCLASS]
driver = d1,nvraid.sys,RAIDCLASS
inf = d1,nvraid.inf
dll = d1,nvraidco.dll
catalog = d1,nvata.cat

[Files.scsi.BUSDRV]
driver = d1,nvatabus.sys,BUSDRV <---
inf = d1, nvraid.inf <---
dll = d1,idecoi.dll
catalog = d1, nvata.cat

The 7.13 just have an entry for the nvatabus.sys, and an entry for nvraid.inf instead.

I have now tried to slipstream those 7.13 raiddrivers like a hundred times now with different configurations, using your solution and nlite B4, and using only nlite b4 and nlite b5, but nothing seems to work.

What i wonder is would installation of the 7.13 drivers work when doing the
installation the old fashioned way with the F6 method, without copying the nvatabus.inf to the sata_raid folder??

[Fernando 1]

Metalljens, on Jul 22 2005, 11:19 AM, said:

What i wonder is would installation of the 7.13 drivers work when doing the
installation the old fashioned way with the F6 method, without copying the nvatabus.inf to the sata_raid folder??

You may try it and I will try to integrate the SataRaid drivers from v. 7.13 into Windows XP with nLite once more.
A better help would be possible, if I knew your hardware combination (chipset of your board, Sata Raid or Pata Raid).

Although I am not an expert in configurating txtsetup.oem files I will try to answer your first questions too:
You cannot compare a txtsetup.oem file, which is dedicated for all chipset combinations (Sata/Pata/SataRaid/PataRaid) as in packet v. 6.53, and a txtsetup.oem file from a special subfolder (SATARAID, PATARAID and SATA IDE) as you will find it in the v. 7.13 (Question: From which subfolder did you take the 7.13 OEM-file?).
The other big difference between both driver packages is the missing of the filter driver nvcchflt.sys in the newer NVIDIA chipset driver packages.

This post has been edited by Fernando 1: 22 July 2005 - 09:02 AM

[Metalljens]

i got the oemfile from sata_raid folder.

And im running an Amd 64 3200 cpu on a DFI Lanparty UT 250, which has the Nforce 3 Ultra chipset.

Yes, youre right, one shouldnt compare apples with bananas...

But my point is, if i was to make a driver floppy for my sata raid to install winxp32 with the F6 method which files would i have to copy to the floppy? is it enough with the sata_raid folder files?
The point being is there something wrong with the driverpackage? , i mean the official 6.66 is similar in layout and would surely work for updating when your systems online, but would it work when using the F6 method and new install? since that .inf file obviosly isnt where it should be.

[Fernando 1]

Metalljens, on Jul 22 2005, 12:49 PM, said:

But my point is, if i was to make a driver floppy for my sata raid to install winxp32 with the F6 method which files would i have to copy to the floppy? is it enough with the sata_raid folder files?
The point being is there something wrong with the driverpackage? , i mean the official 6.66 is similar in layout and would surely work for updating when your systems online, but would it work when using the F6 method and new install? since that .inf file obviosly isnt where it should be.

You are certainly right. The NVIDIA nForce drivers are making a lot of problems.

I just googled a little bit and found a very interisting message for all owners of a pc with nForce3 chipset and a Sata Raid system within this page:
http://www.nforcershq.com/forum/latest-dri...-3-vt60240.html

In one of the posts you can read, that it is possible to install the drivers from the package 7.13 on a mainboard with an nForce3 chipset, but you have to take the ones laying in the PATARAID subfolder (they even work for Sata systems). If you use the files laying in the SATARAID subfolder, you will get a crash of your system.

Would you test this using my method? The only difference would be, that you take the drivers from the PATARAID subfolder as Textmode drivers. That would be very helpfull for all owners of nForce3 chipsets.
Maybe it is easier for you to test it with F6 method. Put just the files from the PATARAID subfolder of the 32-bit 7.13 onto a floppy!

This post has been edited by Fernando 1: 22 July 2005 - 07:40 AM

[Metalljens]

Thank you Fernando!
Ill try that and get back to you in awhile.
Thanx for the tip

[virtualrain]

Here is my experience slipstreaming 6.66 SATA RAID drivers on XP SP2 Install CD...

First let me say that Fernando, you Rock for figuring this out.

I think it is worth pointing out (assuming I am correct) that the integration of drivers in nLite (which is the first step) is really only to address the Text Mode portion of Windows Install. This is what saves you from having to use a floppy and F6 during initial setup. For whatever reason (lack of WHQL certification I believe) it does not then use these same drivers later for Windows GUI mode installation.

The first time I tried this process, for some reason, nLite did not grab the file nvatabus.sys for inclusion in the install. As a result, half way through loading the text mode drivers, it said "nvatabus.sys file not found" and halted. I redid the process and this time verified that nLite had grabbed the file by checking in the I386 folder for nvatabus.sy_. It worked fine the second time.

The second part of your process where you are copying files to the OEMDIR folder is for the Windows GUI mode install. After doing some research this is a common technique for installing non WHQL certified drivers during Windows GUI mode install.

Overall, it worked well for me the second time. I not only integrated the RAID drivers but also used nLite to integrate the rest of the nForce drivers. Note that when integrating other nForce drivers you only need to select one INF in each of the relevant subdirectories you want to integrate... nLite grabs everything in that directory regarless of what INF file you select for integration.

Good luck to others.

[virtualrain]

If someone knows how to install the NVRAID Windows tool after slipstreaming the driver install, I would be keen to know.

[Metalljens]

I have now tried slipstream with your solution and used the pataraid drivers instead. But still BSOD!!

I read the post that your referring to at nforcershq, but it doesnt say if it works when doing a fresh install using the F6 or slipstreamed.
Because i can update the raiddrivers manually when online, so it cant be the wrong drivers.

I made it work when using the F6 but using the txtsetup.oem from the patadraid and using drivers from sataraid and copy that nvatabus.inf from pataraid to sataraid.

But i cant get it to work when slipstreaming it.

[Fernando 1]

virtualrain, on Jul 22 2005, 05:18 PM, said:

If someone knows how to install the NVRAID Windows tool after slipstreaming the driver install, I would be keen to know.

AFAIK this tool das not make a Raid, it only shows it.
So you can install this tool as every other program, when you have installed your slipstreamed OS.

Thank you for your comment. When you have done such a work, it really is a good feeling, that somebody posts, that he has got it working too.

Meanwhile I tested the method described in the first post once again using the NVIDIA chipset package 7.13. It worked flawless on my nForce4 Sata Raid system.

Then I made another test with nLite 1.0 beta5 trying to integrate the SataRaid drivers without the [OemInfFiles] method. This time I used the 7.13 drivers from the (for Sata Raid systems wrong) PATARAID folder as Textmode drivers. Result: endless reboots!
Conclusion: To take just the drivers from the PATARAID subfolder is not the solution for the problems.

metalljens, on Jul 22 2005, 05:37 PM, said:

I made it work when using the F6 but using the txtsetup.oem from the patadraid and using drivers from sataraid and copy that nvatabus.inf from pataraid to sataraid.

Maybe you have to change only the txtsetup.oem in the subfolder SATARAID and then it works? The system can grab the nvatabus.inf from the $OEM$ folder during GUIMODE section, so you do not need to put it into the SATARAID subfolder.
Do you like to test this?

This post has been edited by Fernando 1: 22 July 2005 - 10:59 AM

[Metalljens]

well, i dont know if i really understand, do you mean i dont copy the nvatabys.inf to the sataraid folder but only to the OEM dir?
Would that make a difference?
I have compared the txtsetup.oem files from pata and sata and the only
difference is the nvatabus.inf entry and a catalog file entry
I have now changed the txtsetup.oem in the satafolder so it also have the nvatabus.inf entry and removed the nvraid.inf, because it is already there under the [Files.scsi.RAIDCLASS] section.

It was this way i made work with F6 method but havent been able to slipstream it.

And many thanx for your help it is much appreciated.

[hajj_3]

fernando, you have made about 5 seperate threads regarding nvraid integration, just use 1 thread, add replies when you find new things out, it saves alot of hassle for us and nuhi.

[Fernando 1]

Metalljens, on Jul 22 2005, 06:19 PM, said:

well, i dont know if i really understand, do you mean i dont copy the nvatabys.inf to the sataraid folder but only to the OEM dir?
Would that make a difference?

You may try to copy the nvatabus.inf into the SATARAID folder too, but as you realized by F6 method, MS does not need this file during the first (Textmode) section of setup. Everything is okay, when your Raid array is correctly detected (as 1 hard disk drive) during this section.
During the next part of installation (GUIMODE) the setup routine can grab the nvatabus.inf (necessary for installation of nvatabus.sys) from the folder X:\$OEM$\$$\OEMDIR. So it will not be necessary to put the nvatabus.inf into the SATARAID subfolder. But you can do it nevertheless.

[Fernando 1]

hajj_3, on Jul 22 2005, 06:33 PM, said:

fernando, you have made about 5 seperate threads regarding nvraid integration, just use 1 thread, add replies when you find new things out, it saves alot of hassle for us and nuhi.

I know only about 3 threads opened by me and running now.
It will not be easy to continue with 1 thread, because the integration of the drivers into a 32-bit OS is another thing as the integration into a 64-bit system.

The 3rd thread with my experiences during the tests with nLite b5 can surely be closed, although this thread will be the most interesting for Nuhi and his team.

How can I do it? Can the topic starter change the title of the thread?

I just got a Junior (>50 posts), 5 minutes ago I was a Newbee.

This post has been edited by Fernando 1: 23 July 2005 - 01:22 AM

[Metalljens]

YEEHAA!!
Thats the way to go!! Now it works!!!

Thanx, Fernando!

[poPsi]

Thnx Fernando, I'll give it a try...

[Fernando 1]

Metalljens, on Jul 22 2005, 08:10 PM, said:

YEEHAA!!
Thats the way to go!! Now it works!!!
Thanx, Fernando!

Congratulations, Metalljens, and thank you for your patience.

How have you done it at least? Did you only change the textsetup.oem or did you copy the nvatabus.inf into the SATARAID folder too? Which chipset driver package version did you use?

The answers may be important for other users with nForce3 systems. Thanx for your reply.

This post has been edited by Fernando 1: 23 July 2005 - 01:20 AM

[Metalljens]

I used the sata_raid 7.13 drivers, and first used nlite to integrate the drivers and did your solution with an oemdir and copied the nvatabus.inf from the pata_raid folder ONLY to the oemfolder and changed the section below in sata_raids txtsetup.oem to look like this:

[Files.scsi.BUSDRV]
driver = d1,nvatabus.sys,BUSDRV
inf = d1, nvatabus.inf <--- old value was nvraid.inf
dll = d1,idecoi.dll
catalog = d1, nvata.cat

This post has been edited by Metalljens: 23 July 2005 - 09:39 AM

[Fernando 1]

Metalljens, on Jul 23 2005, 02:34 PM, said:

I used the sata_raid 7.13 drivers, and first used nlite to integrate the drivers and did your solution with an oemdir and copied the nvata.inf from the pata_raid folder ONLY to the oemfolder and changed the section below in sata_raids oemsetup.txt to look like this:
[Files.scsi.BUSDRV]
driver = d1,nvatabus.sys,BUSDRV
inf    = d1, nvatabus.inf <--- old value was nvraid.inf
dll    = d1,idecoi.dll
catalog = d1, nvata.cat
I also copied the oemsetup.txt to the oemfolder, but i dont know if that changed anything.

Thank you, Metalljens. You helped us finding a resolution for the owners of nForce3 mainboards. I will mention this special way for nForce3 users within my first post.

To make it clear for everyone: Metalljens meant nvatabus.inf (instead of nvata.inf) and txtsetup.oem (instead of oemsetup.txt).

@ Metalljens:
If I am not right, please correct me.

By the way: It will not be necessary to copy the txtsetup.oem file into the OEMDIR folder, because this file is only usefull during TEXTMODE part of installation.