Help - Search - Members - Calendar
Full Version: Integration of NVIDIA nForce Raid (and SATA) drivers
MSFN Forums > Member Contributed Projects > nLite
Pages: 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29

   
Google Internet Forums Unattended CD/DVD Guide
liqnit
QUOTE (Fernando 1 @ Dec 31 2007, 05:41 AM) *
QUOTE (liqnit @ Dec 31 2007, 12:34 PM) *
Thanks for all the help
just a small update i am using Tyan S2915-E with NVRaid BIOS 9.83 version.
In order for Win XP SP2 x64 to work i needed to work with 9.24 release , older driers are not working
Thanks for posting the working nForce chipset driver package version, which might help other users with the same mainboard.
Which is the exact nForce chipset name of your mainboard? Is it the nForce Professional 3000 series?


The board is Tyan S2915 which is Nforce 3600 + Nforce 3050
http://www.tyan.com/product_board_detail.aspx?pid=541
Fernando 1
QUOTE (liqnit @ Jan 1 2008, 09:16 AM) *
The board is Tyan S2915 which is Nforce 3600 + Nforce 3050.
Thanks for the response and the link to the details of your mainboard (I already found this page before).
My question had another background. Future users with the same nForce chipset mainboard should know where they can download the suitable nForce chipset drivers as mentioned within my guide.
Is it possible to get the 9.24 package from NVIDIA? If yes, which chipset series and chipset will the user have to choose at NVIDIA's download homepage to be leaded at least to these drivers?

EDIT:
Meanwhile I found the chipset driver package v.9.24, which has successfully been used for Windows XP x64 by liqnit. If you are at NVIDIA's driver homepage, you have to choose "nForce", "nForce Professional 3000 Series", "driver" and then "Windows Server 2003 x64" as OS. So you won't get them, if you are searching for Windows XP x64 nForce chipset drivers!
deanm
Hi!

I have an Nforce2 motherboard MSI K7N2-ILSR with Promise pdc20376 chip (which can also be called "Promise 376" or "Promise FastTrak"). I did not find a solution in this topic to install Windows XP without floppy, BUT it did help me to try different things which led to a successful floppy-free installation! And the solution is very simple.

MSI offers a package for my motherboard on their website called "nVidia nForce2 SATA RAID Driver (For floppy driver)" which seems like the right one, given that it is listed on the driver page for this motherboard model, but this driver does not work.
So I started looking for a different package and noticed that there was one more driver package which sounded right located on the bottom of the drivers list. This package was "Promise Serial-ATA RAID Drivers".

The guidance in this post told me that I should add the drivers as PNP, which I did try, but the right choice was TEXT mode. By clicking on add -> single driver -> pointing to the WinXP folder and fasttx2k and clicking ok gave me a list which had "WinXP Promise FastTrak 376 ™ Controller" on it. Seemed correct so I selected it and continued.

Burned the image on the cd and finally it worked.

I am not sure if this post would have been the correct post for my system, since as far as I now understand, I don't have an NVIDIA nForce SATA raid chip although I have NVIDIA nForce chipset.

Anyways, thought I'd post this here for people with the same motherboard or same SATA chip, so that they can find help more easily than I did.

Thanks to Fernando for the help your post and testing has provided me with!
Fernando 1
QUOTE (deanm @ Feb 13 2008, 08:38 AM) *
I have an Nforce2 motherboard MSI K7N2-ILSR with Promise pdc20376 chip (which can also be called "Promise 376" or "Promise FastTrak"). I did not find a solution in this topic to install Windows XP without floppy, BUT it did help me to try different things which led to a successful floppy-free installation! And the solution is very simple.
MSI offers a package for my motherboard on their website called "nVidia nForce2 SATA RAID Driver (For floppy driver)" which seems like the right one, given that it is listed on the driver page for this motherboard model, but this driver does not work.
So I started looking for a different package and noticed that there was one more driver package which sounded right located on the bottom of the drivers list. This package was "Promise Serial-ATA RAID Drivers".

The guidance in this post told me that I should add the drivers as PNP, which I did try, but the right choice was TEXT mode.
Storage Controller drivers with a file named TXTSETUP.OEM always have to be integrated as TEXTMODE. You won't find anything else within my guide.

QUOTE
By clicking on add -> single driver -> pointing to the WinXP folder and fasttx2k and clicking ok gave me a list which had "WinXP Promise FastTrak 376 ™ Controller" on it. Seemed correct so I selected it and continued.
Burned the image on the cd and finally it worked.
I am not sure if this post would have been the correct post for my system, since as far as I now understand, I don't have an NVIDIA nForce SATA raid chip although I have NVIDIA nForce chipset.
Anyways, thought I'd post this here for people with the same motherboard or same SATA chip, so that they can find help more easily than I did.
Thanks for this report about the intagration of the Promise FastTrak Controller drivers.
Hopefully other users with the same Controller will find your post here.

CU
Fernando

EDIT: More than 500.000 views now - I am overwhelmed with emotions!
Olograph








That sexy ride welcome.gif :

Asus M2N32-SLI Deluxe
AMD Athlon 64 X2 6000+
4 x 1gb Crucial Ballistix PC6400 4-4-4-12
2 x Western Digital Caviar SE16 500GB, 7200rpm, 16MB, SATA-300
1 x EVGA GeForce 8800 GTS

is having a lot of problem with its Windows Xp 64 bit installation

I tried with out of the box drivers pressing f6 during windows installation initialisation.

But each time I get the message Starting Windows (Before the 1st interactive menu in the installation)
it shows an evil BSOD.

I tried to make a nLight disk with the nForce 590 drivers from nVidia site but no luck. I've put SATARAID textmodes and the othe in PNP. (Should I try to make one with drivers form the chipset driver package from the Asus site?)

I'm having an healty RAID 0 setup on the two disks!

Can someone troubleshoot this?

Thanks a lot!!
Fernando 1
QUOTE (Olograph @ Feb 19 2008, 06:45 PM) *
That sexy ride welcome.gif :
Really fine system, but obviously no luck with the OS installation.

QUOTE
Asus M2N32-SLI Deluxe
AMD Athlon 64 X2 6000+
4 x 1gb Crucial Ballistix PC6400 4-4-4-12
2 x Western Digital Caviar SE16 500GB, 7200rpm, 16MB, SATA-300
1 x EVGA GeForce 8800 GTS
is having a lot of problem with its Windows Xp 64 bit installation
Have you tried to remove 1 or better 2 of the memory sticks during the installation?
I am nearly sure, that this will solve your problem.

QUOTE
I tried with out of the box drivers pressing f6 during windows installation initialisation.
But each time I get the message Starting Windows (Before the 1st interactive menu in the installation)
it shows an evil BSOD.
It would have been a good idea to take a picture from that BSOD. Did you get any error message? If, yes, which one?

QUOTE
I tried to make a nLight disk with the nForce 590 drivers from nVidia site but no luck. I've put SATARAID textmodes and the othe in PNP.
You probably should only integrate the SATARAID folder as textmode and nothing else.

QUOTE
(Should I try to make one with drivers form the chipset driver package from the Asus site?)
You may try it, if the removal of the memory sticks doesn't help.

QUOTE
I'm having an healty RAID 0 setup on the two disks!
That is not enough. You need a rock stable system (no overclocking and rock stable memory sticks).
Olograph
QUOTE
It would have been a good idea to take a picture from that BSOD. Did you get any error message? If, yes, which one?


I got a 0x0000007B error that tells me to run chkdsk. It is a storage device error. Need precision?

QUOTE
Have you tried to remove 1 or better 2 of the memory sticks during the installation?
I am nearly sure, that this will solve your problem.


Seriously, I already installed WinXp 64 bit and even 32 bit on the same system without any issue. When I say Installed, I mean, tested with benchmarks. I had a lot of problem in the past with memory with another system and I don't think it's the case....Also, the error I get is about HDD anyway....I'll do it if it is the last available solution......man changing a ram bracket in that monster is insane tongue.gif !!!

QUOTE
You probably should only integrate the SATARAID folder as textmode and nothing else.


Should the extra drivers cause interference?

QUOTE
You need a rock stable system (no overclocking and rock stable memory sticks).


What do you mean? Because overclocking mess up the southbridge? (I did no overclocking)

Additionnal informations :

I got a DVD Burner plugged in another SATA controller.
My Hard Drives are healty, I used the Western Digital diagnostic tool.
I know there's a lot of RAID issues with my motherboard M2N32-SLI and Western Digital HDDs

What I'm gonna try now is to put nVidia RAID controller drivers and Silicon Image(Other sata/raid controller) sata driver on a floppy and do the f6 trick again.


Thanks a lot dude!!!
Olograph
Wow, it worked.

I just put the both controller drivers on an nLight disk and voila!

I've been able to install windows but see next post!!!
Olograph
I talked too fast, Windows crashed during the install and now I'm stuck in a reboot loop woot.gif .

It crashes always after it shows the Windows logo.

In safe mode it stuck at acpitabl.dat file.

HELP!!!!
Fernando 1
QUOTE (Olograph @ Feb 20 2008, 12:42 AM) *
QUOTE
It would have been a good idea to take a picture from that BSOD. Did you get any error message? If, yes, which one?
I got a 0x0000007B error that tells me to run chkdsk. It is a storage device error. Need precision?
No, not necessary. This sort of BSOD is a very common one and mostly related to a memory issue.

QUOTE
QUOTE
Have you tried to remove 1 or better 2 of the memory sticks during the installation?
I am nearly sure, that this will solve your problem.
Seriously, I already installed WinXp 64 bit and even 32 bit on the same system without any issue. When I say Installed, I mean, tested with benchmarks. I had a lot of problem in the past with memory with another system and I don't think it's the case....Also, the error I get is about HDD anyway....I'll do it if it is the last available solution......man changing a ram bracket in that monster is insane tongue.gif !!!
It is not a good idea to build a monster where you cannot easily remove any hardware like a memory stick.
I am still very confident that the removal of 1 or 2 sticks could be able to solve your problem.

QUOTE
QUOTE
You probably should only integrate the SATARAID folder as textmode and nothing else.
Should the extra drivers cause interference?
This is possible with nForce 5-7 RAID systems. The installation of the nForce SataRaid drivers at actual nForce systems is managed by one single INF file, which is associated with the nVRAID driver within the SATARAID folder. Only older nForce SataRaid systems additionally need the nForce S-ATA driver INF file (which you only find within the SATA_IDE folder) to get the nForce SataRaid drivers installed. The integration of the unneeded SATA_IDE driver folder might be critical with NF5-7 chipsets.

QUOTE
QUOTE
You need a rock stable system (no overclocking and rock stable memory sticks).
What do you mean? Because overclocking mess up the southbridge? (I did no overclocking)
The installation of an OS is a very complicated thing. Especially 64bit Windows Operating Systems need fully compatible memory sticks and rock stable BIOS settings.

QUOTE
Additionnal informations :
I got a DVD Burner plugged in another SATA controller.
My Hard Drives are healty, I used the Western Digital diagnostic tool.
I know there's a lot of RAID issues with my motherboard M2N32-SLI and Western Digital HDDs
Your S-ATA connected DVD Burner might be a problem while installing an OS onto an nForce SataRAID array. I had to remove my previously built-in S-ATA DVD Burner, because it was impossible to get any OS installed onto my RAID by booting off this device.

QUOTE
What I'm gonna try now is to put nVidia RAID controller drivers and Silicon Image(Other sata/raid controller) sata driver on a floppy and do the f6 trick again.
Why have you done that? Are you not sure, if you have created a NVIDIA or a Silicon Image RAID?

QUOTE (Olograph @ Feb 20 2008, 01:35 AM) *
I talked too fast, Windows crashed during the install and now I'm stuck in a reboot loop woot.gif .
It crashes always after it shows the Windows logo.
In safe mode it stuck at acpitabl.dat file.
What about your Power Management settings?
You should have enabled ACPI within your BIOS and within your nLite settings.

Good luck!
Fernando
Olograph
QUOTE
It is not a good idea to build a monster where you cannot easily remove any hardware like a memory stick


It is not that dramatic...I mean, I'm lazy to change memory sticks for any PC.....it's a pain in the a**.

QUOTE
I am still very confident that the removal of 1 or 2 sticks could be able to solve your problem.


I'll try it just to humiliate yourself joke... tongue.gif

QUOTE
The integration of the unneeded SATA_IDE driver folder might be critical with NF5-7 chipsets


OK newwink.gif

QUOTE
Why have you done that? Are you not sure, if you have created a NVIDIA or a Silicon Image RAID?


M2N32 motherboard got 2 SATA/RAID controllers.....1st is nVidia, 2nd is silicon image. I've put both on my nLite disk nVidia RAID drivers (since that controller is on RAID mode) and Silicon Image Sata drivers (since that controller is on sata mode). (I got my DVD drive plugged into Silicon Image controller)

That is what I needed to avoid Windows install BSOD - > both controller drivers. But now I got the reboot loop sh**

QUOTE
What about your Power Management settings?
You should have enabled ACPI within your BIOS and within your nLite settings.


Tell me more about ACPI vs nLite and ACPI vs BIOS....I took a quick look at my BIOS and found nothing about ACPI.

QUOTE
Your S-ATA connected DVD Burner might be a problem while installing an OS onto an nForce SataRAID array. I had to remove my previously built-in S-ATA DVD Burner, because it was impossible to get any OS installed onto my RAID by booting off this device.


I'll try rather than to put both controller drivers on an nLite disk.....only use the nVidia SATA/RAID controller. I mean, I'll unplug the DVD Drive to the Silicon Image controller and desactivate the controller. Then I'll plus the cd drive on the nVidia controller.
I'll thy to load only nVidia drivers with f6 method since I got only one divers to insert.

"since I got only one divers to insert"....is the only advantage of nLite in this post is to be able loading several drivers at the same windows installation?

1000 Thanks
Fernando 1
QUOTE (Olograph @ Feb 20 2008, 04:43 PM) *
QUOTE
Why have you done that? Are you not sure, if you have created a NVIDIA or a Silicon Image RAID?
M2N32 motherboard got 2 SATA/RAID controllers.....1st is nVidia, 2nd is silicon image. I've put both on my nLite disk nVidia RAID drivers (since that controller is on RAID mode) and Silicon Image Sata drivers (since that controller is on sata mode). (I got my DVD drive plugged into Silicon Image controller)
That is what I needed to avoid Windows install BSOD - > both controller drivers. But now I got the reboot loop sh**
Which Silicon Image S-ATA driver did you integrate (give me the download link) and how did you do it (as textmode or PnP)? I ask this, because Windows XP x64 shouldn't have a problem to detect the S-ATA connected DVD drive without any third party drivers.

QUOTE
QUOTE
What about your Power Management settings?
You should have enabled ACPI within your BIOS and within your nLite settings.
Tell me more about ACPI vs nLite and ACPI vs BIOS....I took a quick look at my BIOS and found nothing about ACPI.
BIOS will be no problem, if you leave the default settings untouched.
When you are working with nLite, you get the option of different "Computer type" settings. You should either choose the correct setting (depending on your processor type, but with ACPI support) or leave it at "automatic" or "default".

QUOTE
QUOTE
Your S-ATA connected DVD Burner might be a problem while installing an OS onto an nForce SataRAID array. I had to remove my previously built-in S-ATA DVD Burner, because it was impossible to get any OS installed onto my RAID by booting off this device.
I'll try rather than to put both controller drivers on an nLite disk.....only use the nVidia SATA/RAID controller. I mean, I'll unplug the DVD Drive to the Silicon Image controller and desactivate the controller. Then I'll plus the cd drive on the nVidia controller.
I'll thy to load only nVidia drivers with f6 method since I got only one divers to insert.
"since I got only one divers to insert"....is the only advantage of nLite in this post is to be able loading several drivers at the same windows installation?
If you want, you can integrate more than 1 textmode driver by using nLite.
It might be a good idea to generally connect the DVD Burner with a Silicon Image S-ATA port, because this way you get a clear separation between your SATA2 hdd's, which are working in RAID mode and your DVD drive, which is running in SATA1 mode and doesn't need any Silicon Image drivers.

One more thing: Please try to get the error message of your infinite reboot loops. It is quite easy to get it: Just hit F8 a few seconds after the reboot and choose the option "don't reboot at system failure". Then you can read the BSOD message and maybe see the driver which causes the BSOD.
Olograph
QUOTE
Which Silicon Image S-ATA driver did you integrate (give me the download link) and how did you do it (as textmode or PnP)? I ask this, because Windows XP x64 shouldn't have a problem to detect the S-ATA connected DVD drive without any third party drivers.


First nLite DVD I tried was:

Silicon Image Drivers

I went to download : Silicon Image 3132 Serial ATA Driver V1.0.5.0 for Windows 64bit XP/2003(WHQL)

From: Motherboard/AM2/M2N32-SLI Deluxe/IDE/

http://dlsvr03.asus.com/pub/ASUS/misc/ide/..._SATA_V1050.zip

+

nVidia Drivers

http://www.nvidia.com/object/nforce_nf590_winxp64_9.35.html

Criterion: nForce, nForce 5 Series, nForce 590 SLI AMD, Driver, Windows XP 64-bit

Second was

Silicon Image SATA Drivers for x64 for 2003/Xp from Mobo CD

+

nVidia Drivers WinXp x64 from Mobo CD

Both results in the same issue....Reboot loop

QUOTE
One more thing: Please try to get the error message of your infinite reboot loops. It is quite easy to get it: Just hit F8 a few seconds after the reboot and choose the option "don't reboot at system failure". Then you can read the BSOD message and maybe see the driver which causes the BSOD.


Exactly same 0x0000007B error. I'll send you a picture of it tonight

QUOTE
BIOS will be no problem, if you leave the default settings untouched.
When you are working with nLite, you get the option of different "Computer type" settings. You should either choose the correct setting (depending on your processor type, but with ACPI support) or leave it at "automatic" or "default".


I'll take a look

QUOTE
doesn't need any Silicon Image drivers.


Never been able even to install Windows without Silicon Image Drivers. I mean, with x64 and that RAID 0 config

Thanks
Fernando 1
QUOTE (Olograph @ Feb 20 2008, 06:38 PM) *
QUOTE
Which Silicon Image S-ATA driver did you integrate (give me the download link) and how did you do it (as textmode or PnP)? I ask this, because Windows XP x64 shouldn't have a problem to detect the S-ATA connected DVD drive without any third party drivers.
First nLite DVD I tried was:
Silicon Image Drivers
I went to download : Silicon Image 3132 Serial ATA Driver V1.0.5.0 for Windows 64bit XP/2003(WHQL)
From: Motherboard/AM2/M2N32-SLI Deluxe/IDE/
http://dlsvr03.asus.com/pub/ASUS/misc/ide/..._SATA_V1050.zip
Here you can get the newest textmode SATA drivers for your Sil3132 S-ATA chips.

QUOTE
QUOTE
One more thing: Please try to get the error message of your infinite reboot loops. It is quite easy to get it: Just hit F8 a few seconds after the reboot and choose the option "don't reboot at system failure". Then you can read the BSOD message and maybe see the driver which causes the BSOD.
Exactly same 0x0000007B error. I'll send you a picture of it tonight
No file name within the message?

QUOTE
QUOTE
doesn't need any Silicon Image drivers.
Never been able even to install Windows without Silicon Image Drivers. I mean, with x64 and that RAID 0 config
I am a little bit unsure about that, because it is a long time ago when I have used a Silicon Image S-ATA port. AFAIK Windows XP (32/64bit) is able to detect and to manage all non-AHCI SATA1 devices by using the MS Standard Dual Channel PCI IDE Controller, but maybe you are right and you will need to load/integrate the Silicon Image S-ATA textmode driver.
Olograph
QUOTE
I am a little bit unsure about that


I tried twice, one without and once with the Silicon Image driver.
Without wasn't working at all! (Crash when seeing starting windows in the installation as if a driver was missing)

QUOTE
No file name within the message?


no.gif No, nothing that I remember. I'll still shoot you a screenshot of that BSOD.

QUOTE
how did you do it (as textmode or PnP)?


Sorry, old question...I selected TextMode for Silicon Image and only half of the two options....there was 1 for "Itanium" processor and 1 for x64 multi-processor. I choosed only x64 multi-processor.

For the nVidia SATA/RAID Drivers I selected both TEXTMODE rows with "required" at the end.

Do I need PNP somehow?

QUOTE
Here you can get the newest textmode SATA drivers for your Sil3132 S-ATA chips.


I got the latest BIOS version, maybe I need the latest Silicon Driver too in addition.

I'll try that......too! smile.gif

And thanks a lot!
Fernando 1
QUOTE (Olograph @ Feb 20 2008, 10:19 PM) *
QUOTE
how did you do it (as textmode or PnP)?
Sorry, old question...I selected TextMode for Silicon Image and only half of the two options....there was 1 for "Itanium" processor and 1 for x64 multi-processor. I choosed only x64 multi-processor.
For the nVidia SATA/RAID Drivers I selected both TEXTMODE rows with "required" at the end.
Everything regarding the textmode driver integration seems to be ok.

QUOTE
Do I need PNP somehow?
No.

QUOTE
QUOTE
Here you can get the newest textmode SATA drivers for your Sil3132 S-ATA chips.
I got the latest BIOS version, maybe I need the latest Silicon Driver too in addition.
I'll try that......too! smile.gif
That's a good idea.

Good luck!
Fernando
Olograph
QUOTE
No, nothing that I remember. I'll still shoot you a screenshot of that BSOD.


There are some pictures of the most evil BSOD:







Seem the RAID drivers disapeared.....!? It is the same error I get when installing windows without drivers!

QUOTE
I got the latest BIOS version, maybe I need the latest Silicon Driver too in addition.
I'll try that......too!


Man, that is worse with the Silicon Image driver you sent me look at the cd error I got in Windows installation:




I can do retry forever, nothing happens, even if I change the DVD.

QUOTE
You should either choose the correct setting (depending on your processor type, but with ACPI support) or leave it at "automatic" or "default".


About ACPI.....default was already selected, the available options are the following:

-ACPI Multiprocessor x64
-ACPI Uniprocessor x64

I'm just about desactivating the Silicon Image controller and use only the nVidia one.

Thanks,
Fernando 1
QUOTE (Olograph @ Feb 21 2008, 03:05 AM) *
Man, that is worse with the Silicon Image driver you sent me look at the cd error I got in Windows installation:
I doubt, that the new Silicon Image S-ATA driver is the reason for that error message.
Are you sure, that your DVD Burner and the previously burned CD is ok?

QUOTE
QUOTE
You should either choose the correct setting (depending on your processor type, but with ACPI support) or leave it at "automatic" or "default".
About ACPI.....default was already selected, the available options are the following:
-ACPI Multiprocessor x64
-ACPI Uniprocessor x64
OK. ACPI Multiprocessor x64 would have been the correct one, but if you have chosen "default", Windows Setup will detect it by its own.

QUOTE
I'm just about desactivating the Silicon Image controller and use only the nVidia one.
You may try it.
If this doesn't help either, you should take any IDE CDROM drive from somewhere or borrow it from a friend, connect it to the IDE port and install the OS from there. Once the OS is up, you will be able to use your SATA DVD Burner again.
Olograph
QUOTE
I doubt, that the new Silicon Image S-ATA driver is the reason for that error message.
Are you sure, that your DVD Burner and the previously burned CD is ok?


The DVD is ok, burnt twice to be sure and another with previously tried drivers and got no error.

QUOTE
I'm just about desactivating the Silicon Image controller and use only the nVidia one.

The only thing that changes is that I no more need Silicon Image Drivers.

It still crash, so we can conclude that the problem isn't from Silicon Image.

---

I tried to use a floppy (f6) with latest drivers since I only got one driver to load in and before copying every files to HDD, it says that it couldn't find drivers files on CD!??! It prompted for every files...I know cause I press the key to skip. First file was ndrvx64.sys and all others are the one of my CD.

I just got another theory...is it possible the x64 DVD I'm using has already been nLited and that a previously added driver make the reboot loop?
how can I verify that......should I look into AMD64/NDRV/001 and see if there's additionnal drivers?

QUOTE
nce the OS is up, you will be able to use your SATA DVD Burner again


I'll try to consider the fact that using my DVD burner in SATA can be the problem in itself.


QUOTE
ACPI Multiprocessor x64 would have been the correct one


I'll force the option for ACPI Multiprocessor x64 and give another shot, just not to presume it is ok.

***

Whatever...... what I feel the most is that ....the error I get on before windows statup after install is caused by wrongly installed drivers...Is there a way I can validate my drivers installation through DOS?

I'm not sure if I should say this here but, I'll try Windows Iso Builder, I doubt on nLite txtsetup.sif building for driver copying. tongue.gif

***

I'll also try memtest86 for DOS as Memory Diagnostic tool...

Thanks
Olograph
Ok, I just read in another forum and someone is having the same pain.....

http://www.planetamd64.com/lofiversion/index.php?t32025.html

That is

-when using a floppy is cannot copy drivers and does bsod

-when using a nLited disk is works but do the reboot loop thing

Seems that it is due to an already nLited disk.

And guess what? Mine has already been! I didn't know it matters ....

Does it mean I get conflicting drivers on the nLite disk?
or
Does it means that every already nLited disk shouldn't ever be used?

Thanks
Fernando 1
QUOTE (Olograph @ Feb 21 2008, 04:14 PM) *
Ok, I just read in another forum and someone is having the same pain.....
http://www.planetamd64.com/lofiversion/index.php?t32025.html
That is
-when using a floppy is cannot copy drivers and does bsod
-when using a nLited disk is works but do the reboot loop thing
Seems that it is due to an already nLited disk.
And guess what? Mine has already been! I didn't know it matters ....
Does it mean I get conflicting drivers on the nLite disk?
or
Does it means that every already nLited disk shouldn't ever be used?
That is true. You should never use a modified (for example an already nLited) CD as source, if you are going to create an nLited CD.

This is what I have written within my guide (first post of this thread):
QUOTE
Important Requirements:

You only will succeed with the integration of the nForce SataRaid drivers, if you have
- a correctly created nForce RAID array (shown as "healthy" and set as bootable, for further informations look here)
- an up-to-date mainboard and nVRaid BIOS (= MediaShield IDE ROM), which is part of the mainboard BIOS. Actual nVRaid drivers may need a Raid Bios v. 4.81 or higher.
- a stable system (proper RAM modules and stable BIOS settings)
- an original or perfectly created clean (not nLited or modded) OS CD as source
- a proper working IDE-connected CD or DVD drive
- an enabled ACPI power management (within BIOS, don't disabe it by nLite settings).

Users, who are asking for help here, should have read and followed my guide.
Olograph
At least now you know the consequences....

I am extremely sorry dude! I should have read it more carefully. blushing.gif

There is so much of thing to do in life and so few of time that we try to make some shortcuts....It never pays anyway no.gif ....this is ironic.

At least even If I had read before, I realized later that it was nLited.

What does make the nLited versions so non-reusable?

I'll get a non-nLited version shifty.gif .... Legal?whistling.gif and keep you informed.

Thanks!!!!!
twfry
Hi Fernando,

This is my first time posting and I wanted to thank you for all of your advise, posts and work over the past few years. I've read a lot of what you have put up on different boards and it has been so helpful. NVIDIA should definitely pay you something..

I wanted to give you some feedback on how the drivers are working on my chipset since you have asked for this before and also for some advise. I've been struggling for 4 weeks with getting an nForce 570 RAID setup stable and have run out of things to try. The system is:

ASUS M2N-E motherboard
nForce 570 Ultra AMD chipset
Athlon x2 4000+ CPU (Brisbane stepping)
G-Skill memory 2 sticks 2GB each
Western Digital 500GB hard drives
RAID 1 setup on SATA ports 1 and 2 (1.0 & 1.1)
Windows XP x64 SP2 clean install (only VMWare workstation 6.0.2 installed)
nForce 6.99 drivers
latest BIOS/all windows updates

The install process you outlined with nLite went fine and the RAID setup is working. However, when the hard drives are put under a little bit of work, performance drops to a crawl (< 1MB/sec, when normally ~20MB/sec when copying a file). If I really stress the system I can guarantee a BSOD with either IRQL_NOT_LESS_OR_EQUAL or PAGE_FAULT_IN_NONPAGED_AREA. For example, if I try to copy a 10GB file on the host and suspend/resume two vmware guests at the same time, HD performance becomes horrible and then a BSOD happens.

Microsoft says that the combination of these two faults can be due to faulty drivers.

For hardware tests, I have tried 3 different pairs of memory, all of which pass memtest+ 1.70 for days. I have also stress tested two different Athlon CPUs for days. All tests pass fine, I am convinced this is not a hardware issue. Also tried different SATA cables.

Reinstalling the system without nForce RAID drivers makes the BSOD goes away with the same tests. So it is definitely not a motherboard/software issue, other than maybe the RAID controller.

Any ideas on what else I can try? Turning NCQ off allowed me to push the system harder, but did not fix it.

You may ask why do this and the reason is that I run a few guest OSes and sometimes I might have to startup and shut down more than one at a time. If the system crashes and invalidates one of the vmware guests, this is a problem, sort of defeats the whole purpose of using raid.

I might just have to give up and go back to a non-RAID setup, but as a last resort I wanted to see if you had any ideas or hopefully if you had heard of this problem before.

Thanks so much,

Tom
Fernando 1
QUOTE (twfry @ Feb 22 2008, 03:34 AM) *
Hi Fernando,
This is my first time posting and I wanted to thank you for all of your advise, posts and work over the past few years. I've read a lot of what you have put up on different boards and it has been so helpful. NVIDIA should definitely pay you something..
Thank you for the flowers. What I have done was not for NVIDIA, but for the customers of their nForce chipsets and the users of their drivers.

QUOTE
I wanted to give you some feedback on how the drivers are working on my chipset since you have asked for this before and also for some advise. I've been struggling for 4 weeks with getting an nForce 570 RAID setup stable and have run out of things to try. The system is:

ASUS M2N-E motherboard
nForce 570 Ultra AMD chipset
Athlon x2 4000+ CPU (Brisbane stepping)
G-Skill memory 2 sticks 2GB each
Western Digital 500GB hard drives
RAID 1 setup on SATA ports 1 and 2 (1.0 & 1.1)
Windows XP x64 SP2 clean install (only VMWare workstation 6.0.2 installed)
nForce 6.99 drivers
latest BIOS/all windows updates

The install process you outlined with nLite went fine and the RAID setup is working. However, when the hard drives are put under a little bit of work, performance drops to a crawl (< 1MB/sec, when normally ~20MB/sec when copying a file). If I really stress the system I can guarantee a BSOD with either IRQL_NOT_LESS_OR_EQUAL or PAGE_FAULT_IN_NONPAGED_AREA. For example, if I try to copy a 10GB file on the host and suspend/resume two vmware guests at the same time, HD performance becomes horrible and then a BSOD happens.
Microsoft says that the combination of these two faults can be due to faulty drivers.
For hardware tests, I have tried 3 different pairs of memory, all of which pass memtest+ 1.70 for days. I have also stress tested two different Athlon CPUs for days. All tests pass fine, I am convinced this is not a hardware issue. Also tried different SATA cables.
Reinstalling the system without nForce RAID drivers makes the BSOD goes away with the same tests. So it is definitely not a motherboard/software issue, other than maybe the RAID controller.
Any ideas on what else I can try? Turning NCQ off allowed me to push the system harder, but did not fix it.
You may ask why do this and the reason is that I run a few guest OSes and sometimes I might have to startup and shut down more than one at a time. If the system crashes and invalidates one of the vmware guests, this is a problem, sort of defeats the whole purpose of using raid.
I might just have to give up and go back to a non-RAID setup, but as a last resort I wanted to see if you had any ideas or hopefully if you had heard of this problem before.
Hello Tom,
thanks for your interesting and detailed report.
I cannot give you any concrete advice how to solve your problem. There are so many possible reasons for it, that it is not easy to find out the real one.
There are nForce SataRaid users who have a rock stable system from scratch and others who only have problems.

Nevertheless I will try to give you some advices:
1. Have a look onto your PSU. Many pc problems can easily be solved by a new PSU. The most important thing is not the power itself, but the ability to provide exactly the voltage (not more, not less), which is needed by the different devices.
2. Maybe you should have a look into this thread and try the new nForce IDE drivers v9.98.

Good luck!
Fernando
Olograph
FYI Everything is working flawlessly! thumbup.gif I used another copy of Windows XP x64 Pro shifty.gif and the floppy.

Thanks 1000 times! laugh.gif
Fernando 1
QUOTE (Olograph @ Feb 22 2008, 02:50 PM) *
FYI Everything is working flawlessly! thumbup.gif I used another copy of Windows XP x64 Pro shifty.gif and the floppy.
Thanks 1000 times! laugh.gif
Thanks for your final success report, but it is not the primary intention of this forum and this thread, that users at least boot off the original OS CD and load the textmode drivers by F6/floppy.

My impression: "Much Ado About Nothing" (William Shakespeare).

CU
Fernando
twfry
Hey Fernando,

Thanks for the quick reply, yes I had seen those packages but didn't try them since my board is non-AHCI. So I tried the 9.98 versions and the results.....

They work thumbup.gif , not only did the BSODs go away, but I could push the system as hard as I want to with no issues. Also, hard drive activity behaves as you would expect in the windows xp perfomance window. Before there was always 10-20MB/sec of write activity, even if the drive was just reading or being idle. And now it shows idle states that are idle, just read activity when reading, etc. Basically 9.98 drivers are better on a nforce 570 ultra amd rig no question.

The update process was a little funky though and I thought you would be interested in the results/process. I probably should post this to the other thread, but since we are already talking here whistling.gif

I used device manager->update driver to do the update. Here were the steps.

1) Went to SCSI and RAID controllers -> NVIDIA nForce RAID controller -> update driver -> and selected the sataraid folder. The system updated the raid controller driver to 9.98. Strange thing though, before there were 3 separate NVIDIA nForce Serial 550/570/590 ATA controllers (one for each pair of SATA ports, 6 total). Updating the RAID controller also updated just the first SATA controller (the one with both raided HDs attached). The other 2 SATA controllers were left at 6.99 version.
2) Rebooted, rebooted again, now in device manager -> SCSI and RAID controllers there was 1 updated raid controller, 1 updated SATA controller and 2 older 6.99 SATA controller.
3) Used update driver to update the other 2 SATA controllers. Doing so moved them out of the SCSI and RAID controllers area and into the IDE ATA/ATAPI controllers area.
4) Rebooted, now the SATA controllers all had the 9.98 drivers, but one was listed in the SCSI and RAID controllers area and the other 2 in the IDE section. Strange.
5) I then used the installer to update the Ethernet, SMBus and Mediatool. The installer first asked to uninstall old and reboot, on restart it installed the drivers.
6) On next reboot, there was now listed an "Other PCI controller" (or something close). There was also no local network connection. There was no option to rollback driver on the PCI controller. Selected install driver and selected the ethernet directory from your package. Install reboot.
7) Network functionallity was now back and the system looked good except for the misplacement of the SATA controllers.

8) Opened the MediaShield tool which is now version 5.10.2600.663 (is this right). Disturbing results. The 465GB raid drive was now listed as 0.37GB and healthy even though the drive was fully functional. Started a rebuild to see if that would help, it is now at 40029% and counting.

I'm assuming this is the old media shield and it is not fully compatible with the new drivers and the installer did not update it.

Any idea what to try to fix this, is there something else I missed? Might just do a clean install and see how that goes.

Thanks again, your packages rock!!

Tom
Fernando 1
QUOTE (twfry @ Feb 23 2008, 02:41 AM) *
Hey Fernando,
Thanks for the quick reply, yes I had seen those packages but didn't try them since my board is non-AHCI. So I tried the 9.98 versions and the results.....
They work thumbup.gif , not only did the BSODs go away, but I could push the system as hard as I want to with no issues. Also, hard drive activity behaves as you would expect in the windows xp perfomance window. Before there was always 10-20MB/sec of write activity, even if the drive was just reading or being idle. And now it shows idle states that are idle, just read activity when reading, etc. Basically 9.98 drivers are better on a nforce 570 ultra amd rig no question.
The update process was a little funky though and I thought you would be interested in the results/process. I probably should post this to the other thread, but since we are already talking here whistling.gif
I used device manager->update driver to do the update. Here were the steps.
Hello Tom,
thanks for your interesting and useful report. This certainly will help other users with similar problems.
I have put a link to your how-to description into my nForcersHQ forum thread.

QUOTE
8) Opened the MediaShield tool which is now version 5.10.2600.663 (is this right). Disturbing results. The 465GB raid drive was now listed as 0.37GB and healthy even though the drive was fully functional. Started a rebuild to see if that would help, it is now at 40029% and counting.

I'm assuming this is the old media shield and it is not fully compatible with the new drivers and the installer did not update it.
You obviously didn't install the RAIDTOOL v9.99, which is part of my NF4-7 AHCI pack.

QUOTE
Any idea what to try to fix this, is there something else I missed? Might just do a clean install and see how that goes.
You should manually replace the RAIDTOOL v663 (should have been v6.95) by v9.99 using my new AHCI driver package.

QUOTE
Thanks again, your packages rock!!
Fine, that I could help you with this package.

CU
Fernando
devaaki
Hi, I have a rather poor understanding of how this whole setup works and have thus run into a bit of a problem while following your process.

The system I'm trying to install Windows XP onto is an HP a6347c: AMD 64x2 5600+, 4gb RAM, 640gb HD (2x320gb) SATA, NVIDIA nForce 430 chipset and NVIDIA GeForce 6150 SE.

Using nLite, I've loaded three separate XP SP2 CDs with nForce drivers v.11.09, putting in sata_ide as PNP and sataraid as textmode. After formatting drives, installing, etc... I still go into infinite rebots.

Are there anymore files that I need to edit in order for this system to get working?

Thank you so much for your help so far - I really appreciate the detailed guide, but for some reason I cannot get this computer to get working.

Jeff

Edit - here is some more information. If I remove the boot disk and force it to boot from C: (I've formatted and tried to install on both hard drives), I a few screen flickers and an instant reboot. If I force boot from D:, I get a blinking '_' in the top corner of my screen.
Fernando 1
QUOTE (devaaki @ Mar 30 2008, 05:27 AM) *
The system I'm trying to install Windows XP onto is an HP a6347c: AMD 64x2 5600+, 4gb RAM, 640gb HD (2x320gb) SATA, NVIDIA nForce 430 chipset and NVIDIA GeForce 6150 SE.
Using nLite, I've loaded three separate XP SP2 CDs with nForce drivers v.11.09, putting in sata_ide as PNP and sataraid as textmode. After formatting drives, installing, etc... I still go into infinite rebots.
If this happened at the end of the installation (at last reboot), have you tried to boot in safe mode (by hitting F8) and look into the Device Manager for any yellow marks?
Did you see any error message? You can get it, when you hit F8 while booting and choose the option "don't reboot at system failure".
Did you take the correct nForce IDE drivers? The 11.09 chipset driver pack is suitable for MCP51 (with CPU socket 939) and MCP61 (with AM2 CPU socket) chipsets. Since you obviously have an nForce 430 chipset mainboard with an AM2 CPU socket, you have to integrate the drivers of the MCP61 directory.

QUOTE
Are there anymore files that I need to edit in order for this system to get working?
No, but rather less.
If you had chosen the nForce IDE driver folders from the correct directory (MCP51 or MCP61), you can try to integrate just the SATARAID driver folder as textmode (without the additional integration of the SATA_IDE driver folder).
Some nForce chipsets need the SATA_IDE drivers separately, some don't like them.
devaaki
I really appreciate your prompt reply.

The endless reboot occurs at the first reboot, with the wait 15 seconds before reboot screen. Upon rebooting, it returns to the very beginning of setup. After loading the drivers from the SATARAID folder within the MCP61 subdirectory, I burned an XP Pro SP2 disk. I get the same problem - the computer runs through the initial copying of files for setup. Then it says it will reboot after 15 seconds, etc. etc... After rebooting it goes right back to the start of setup (asking for F6, repair, etc...). In short, it didn't work.

I've read elsewhere that I need to enable RAID in my BIOS, but I can't seem to find it. I can look at both of the harddrives, but I think they're controlled by IDE. The only mention of SATA I can find is in the advanced tab is enabling the PATA/SATA drivers. Should these all be enabled here?

Thanks

Jeff
Fernando 1
QUOTE (devaaki @ Mar 30 2008, 05:52 PM) *
The endless reboot occurs at the first reboot, with the wait 15 seconds before reboot screen.
So you came to the point where you have to decide, where you want to get the OS installed.
Is this correct? If yes, have your hdd(s) and their partitions been correctly detected?

QUOTE
Upon rebooting, it returns to the very beginning of setup.
Did you hit a key when prompted while rebooting? You should not do that. Hitting a key only makes sense during the first boot off the CD/DVD.

QUOTE
I've read elsewhere that I need to enable RAID in my BIOS, but I can't seem to find it. I can look at both of the harddrives, but I think they're controlled by IDE. The only mention of SATA I can find is in the advanced tab is enabling the PATA/SATA drivers. Should these all be enabled here?
You certainly mean drives and not "drivers". Yes, the nForce S-ATA Controllers, where your S-ATA hdd's are connected, should be enabled within BIOS, otherwise your hdd's won't be detected at all by any OS you want to install.
I don't believe, that you have to enable RAID too, since you obviously haven't built a RAID array. Nevertheless you should have look into your mainboard/pc manual.
devaaki
Both hard drives have been detected by setup. Since I've tried to install WinXP on both drives, they both say that I have a previous version of windows already on the drive, and then asks if I want to format the drive or not.

The rebooting process usually takes place by itself... although it prompts you to hit enter or wait the 15 seconds out.

The computer was bought as a display model, and thus have no included documentation, manuals or disks... I made the blunder of deleting the recovery partition and am currently making a Vista reinstall disk. I have a licensed XP Pro installation, but that is not working as I would like it to.
Fernando 1
QUOTE (devaaki @ Mar 30 2008, 07:57 PM) *
Both hard drives have been detected by setup. Since I've tried to install WinXP on both drives, they both say that I have a previous version of windows already on the drive, and then asks if I want to format the drive or not.
OK, in this case the discussion about missing or wrong BIOS settings seems to be obsolete.
You probably have set the optical drive (CD/DVD-ROM) as first bootable device and the HDD as second one, haven't you?

QUOTE
The rebooting process usually takes place by itself... although it prompts you to hit enter or wait the 15 seconds out.
Yes,but you may not hit any key while rebooting.

QUOTE
The computer was bought as a display model, and thus have no included documentation, manuals or disks... I made the blunder of deleting the recovery partition and am currently making a Vista reinstall disk. I have a licensed XP Pro installation, but that is not working as I would like it to.
So you think, that your XP source is not ok? That would be an explanation for the strange behaviour of the Setup process.
devaaki
I say it's not working as I'd like it to because the nForce 430 drivers aren't working. I've spent the last two days working over this and I don't think I can resolve the problem here. I will probably end up installing Vista Business and hope for compatability between the clinical software that I need to use on this machine.

Thank you very much for your time, keep up the good work
Fernando 1
QUOTE (devaaki @ Mar 30 2008, 10:01 PM) *
I say it's not working as I'd like it to because the nForce 430 drivers aren't working. I've spent the last two days working over this and I don't think I can resolve the problem here. I will probably end up installing Vista Business and hope for compatability between the clinical software that I need to use on this machine.
Have you tried any other nForce chipset drivers than those of NVIDIA's 11.09 pack? If not, you may have a look here.
calixguy18
Fernando,

Thanks for the writeup, but I REALLY need your help.

I am upgrading someone's computer to an ECS 6100SM-M Nforce 405 motherboard and AMD 4400 Processor, 2 gigs ram. I have no other hardware installed, using the onboard video. Windows XP home.

I ghosted the original harddrive (WD80gig PATA) to a 500 gig SATA Maxtor. I go to do the repair from the XP CD and it loads everything, reboots, the windows splash screen shows up for a few seconds and blue screens. It does not make it through the first reboot and does not go into the windows installation screen with the bullet points.

I have tried so many combinations of NLite installation cd's but I get the same result. I am not sure if I am doing something wrong. I make a new folder with the XP cd contents and copy everything over. I run NLite and add the single driver, in textmode. I've tried this with several different versions of the drivers but none seem to work. I've downloaded ones from ECS, NVidia, and the legacy ones you linked.

I have done a clean install on the same hard drive with the same hardware with no problems. I tried to do a repair on the original PATA drive on the new mobo and it does not work either. It blue screens at the same place.

Can you tell me exactly which drivers (version) to incorporate into NLite with respect to my system specs?

I have spent hours and hours on this and am about to go crazy. I am about to go buy a new non nvidia mobo at this point. Any help is appreciated. Thanks.
Fernando 1
QUOTE (calixguy18 @ Apr 5 2008, 12:46 AM) *
I am upgrading someone's computer to an ECS 6100SM-M Nforce 405 motherboard and AMD 4400 Processor, 2 gigs ram. I have no other hardware installed, using the onboard video. Windows XP home.
I ghosted the original harddrive (WD80gig PATA) to a 500 gig SATA Maxtor. I go to do the repair from the XP CD and it loads everything, reboots, the windows splash screen shows up for a few seconds and blue screens. It does not make it through the first reboot and does not go into the windows installation screen with the bullet points.
I have tried so many combinations of NLite installation cd's but I get the same result. I am not sure if I am doing something wrong. I make a new folder with the XP cd contents and copy everything over. I run NLite and add the single driver, in textmode. I've tried this with several different versions of the drivers but none seem to work. I've downloaded ones from ECS, NVidia, and the legacy ones you linked.
I have done a clean install on the same hard drive with the same hardware with no problems. I tried to do a repair on the original PATA drive on the new mobo and it does not work either. It blue screens at the same place.
Can you tell me exactly which drivers (version) to incorporate into NLite with respect to my system specs?
You probably have to do a fresh install, if the repair function of your old ghosted OS doesn't work for you.
Before I can give you any further advice, you should tell me, if you are using RAID or not. As far as I understood your post, you only have 1 single S-ATA hdd within your system. If this would be correct, you wouldn't need to integrate any NVIDIA textmode drivers.
calixguy18
QUOTE (Fernando 1 @ Apr 5 2008, 01:33 AM) *
QUOTE (calixguy18 @ Apr 5 2008, 12:46 AM) *
I am upgrading someone's computer to an ECS 6100SM-M Nforce 405 motherboard and AMD 4400 Processor, 2 gigs ram. I have no other hardware installed, using the onboard video. Windows XP home.
I ghosted the original harddrive (WD80gig PATA) to a 500 gig SATA Maxtor. I go to do the repair from the XP CD and it loads everything, reboots, the windows splash screen shows up for a few seconds and blue screens. It does not make it through the first reboot and does not go into the windows installation screen with the bullet points.
I have tried so many combinations of NLite installation cd's but I get the same result. I am not sure if I am doing something wrong. I make a new folder with the XP cd contents and copy everything over. I run NLite and add the single driver, in textmode. I've tried this with several different versions of the drivers but none seem to work. I've downloaded ones from ECS, NVidia, and the legacy ones you linked.
I have done a clean install on the same hard drive with the same hardware with no problems. I tried to do a repair on the original PATA drive on the new mobo and it does not work either. It blue screens at the same place.
Can you tell me exactly which drivers (version) to incorporate into NLite with respect to my system specs?
You probably have to do a fresh install, if the repair function of your old ghosted OS doesn't work for you.
Before I can give you any further advice, you should tell me, if you are using RAID or not. As far as I understood your post, you only have 1 single S-ATA hdd within your system. If this would be correct, you wouldn't need to integrate any NVIDIA textmode drivers.


You are correct. It is NOT a raid system- it is just a single SATA hdd. Is it at all possible to do a repair then? Is there some other workaround?
Fernando 1
QUOTE (calixguy18 @ Apr 7 2008, 04:37 AM) *
You are correct. It is NOT a raid system- it is just a single SATA hdd. Is it at all possible to do a repair then? Is there some other workaround?
At first step I recommend to boot the machine with the ghosted XP partition in safe mode (F8, without Network support). If you succeed, look into the Device Manager for errors or missing drivers.

If you cannot boot in safe mode, I would do a fresh XP install. Since you don't have a RAID system, there is no need to integrate any textmode driver. The XP in-box IDE drivers will support the S-ATA hard disk drive. So you should be able to get Windows XP istalled with just a clean (=untouched) XP CD without integrating or loading (F6) any third party drivers.
If you want, that the OS uses the special nForce S-ATA driver, you can integrate the content of the SATA_IDE folder of the nForce chipset package v11.09 (for MCP61) as PnP driver. You can try to integrate the SATARAID driver folder as textmode as well, but you should not highlight the NVIDIA RAID Class Controller, although it is shown as "required".
calixguy18
QUOTE (Fernando 1 @ Apr 7 2008, 04:14 AM) *
QUOTE (calixguy18 @ Apr 7 2008, 04:37 AM) *
You are correct. It is NOT a raid system- it is just a single SATA hdd. Is it at all possible to do a repair then? Is there some other workaround?
At first step I recommend to boot the machine with the ghosted XP partition in safe mode (F8, without Network support). If you succeed, look into the Device Manager for errors or missing drivers.

If you cannot boot in safe mode, I would do a fresh XP install. Since you don't have a RAID system, there is no need to integrate any textmode driver. The XP in-box IDE drivers will support the S-ATA hard disk drive. So you should be able to get Windows XP istalled with just a clean (=untouched) XP CD without integrating or loading (F6) any third party drivers.
If you want, that the OS uses the special nForce S-ATA driver, you can integrate the content of the SATA_IDE folder of the nForce chipset package v11.09 (for MCP61) as PnP driver. You can try to integrate the SATARAID driver folder as textmode as well, but you should not highlight the NVIDIA RAID Class Controller, although it is shown as "required".


Thanks for the help so far. I tried to boot in to safe mode but when it got into windows it said there was some kind of error and had to shut down.

So this is what I have done so far. I moved that hdd with the ghosted image to a ECS L4VXA2 motherboard (VIA chipset) and it repaired fine. For some strange reason the motherboard died and would not read the RAM. So I moved it to the ECS 6100 motherboard (Nforce chipset). No Luck. So I purchased an Asus motherboard (AMD chipset) and same problem.

Do you know what's preventing me from doing the repair on the newer motherboards?
Fernando 1
QUOTE (calixguy18 @ Apr 7 2008, 11:12 PM) *
Thanks for the help so far. I tried to boot in to safe mode but when it got into windows it said there was some kind of error and had to shut down.
Which error message did you get? This might be important to detect the reason for your problem.

QUOTE
Do you know what's preventing me from doing the repair on the newer motherboards?
I have no idea, but it is never a good idea to transfer an OS installation from one system to another.
You really should do a clean install of Windows XP.
Yurek3
I need some drivers but for Vista.
My Vista du not see SATA HDD.

Fernanndo you can take care for this please.
Fernando 1
QUOTE (Yurek3 @ Apr 12 2008, 08:48 PM) *
I need some drivers but for Vista.
My Vista du not see SATA HDD.
Fernanndo you can take care for this please.
Although this problem is off topic, I will try to help you, but I need some informations:
1. Which nForce chipset does your mainboard have (if you don't know, give me the name of the board).
2. Are you running Vista or did you try to install Vista and the hdd has not been detected by Vista Setup?
Yurek3
This is link for my matherboard

http://www.giga-byte.com/Products/Motherbo...?ProductID=1644

I have 4 HDD two 200GB IDE i did RAID and this Vista see and two 500GB SATA II but i can not do RAID so too big for my SATA BIOS and thisone vista do not see.

Fernando when you help ne please i will very glad.
Fernando 1
QUOTE (Yurek3 @ Apr 13 2008, 01:57 AM) *
This is link for my matherboard
http://www.giga-byte.com/Products/Motherbo...?ProductID=1644
I have 4 HDD two 200GB IDE i did RAID and this Vista see and two 500GB SATA II but i can not do RAID so too big for my SATA BIOS and thisone vista do not see.
Fernando when you help ne please i will very glad.
I am sorry, but I cannot help you.
Since your motherboard has an nForce2 chipset and NVIDIA didn't develop any Vista nForce IDE drivers, which are supporting nForce2 RAID systems, you will not be able to run Vista with an nForce RAID system.
Vista is not a useful OS for your hardware configuration.

CU
Fernando
badkarma
Just upgraded my main computer to a E8400/P35-DS3R, so I'm trying to get RAID5 working on my old DFI NF4 Ultra-D mobo with Windows 2003 32bit for server duty. I'm not installing on the RAID5 array, so I initially just installed the drivers created the array, and then booted into windows. I was able to get the raidtool to install, and the Nvidia SATA RAID controller driver installed, however whenever I look at drive manager, it sees 3 drives. Also the Nvidia RAID tool doesn't see any arrays. In my bios it says the array is healthy. I tried slipstreaming the drivers like mentioned here but without success. I slipstreamed your v1.8 XP drivers into my install CD. Any suggestions? I just can't seem to get Windows 2003 to see the array, the RAID bios says 1.36 TB RAID5 Healthy.
Fernando 1
QUOTE (badkarma @ May 2 2008, 09:48 PM) *
Just upgraded my main computer to a E8400/P35-DS3R, so I'm trying to get RAID5 working on my old DFI NF4 Ultra-D mobo with Windows 2003 32bit for server duty. I'm not installing on the RAID5 array, so I initially just installed the drivers created the array, and then booted into windows. I was able to get the raidtool to install, and the Nvidia SATA RAID controller driver installed, however whenever I look at drive manager, it sees 3 drives. Also the Nvidia RAID tool doesn't see any arrays. In my bios it says the array is healthy. I tried slipstreaming the drivers like mentioned here but without success. I slipstreamed your v1.8 XP drivers into my install CD. Any suggestions? I just can't seem to get Windows 2003 to see the array, the RAID bios says 1.36 TB RAID5 Healthy.
If you don't install the OS onto a RAID partition, the OS Setup won't automaticly install the needed nForce S-ATA driver.
Solution:
Open the Device Manager and check within the "SCSI and RAID Controllers" section, if the "NVIDIA nForce RAID Controller" is correctly installed (by using the nForce RAID driver).
If yes, do the following:
1. Open the "IDE/ATAPI Controllers" section of the Device Manager. You will see a lot of devices named "Standard Dual Channel PCI IDE Controller".
2. Check, which of them is managing your natively IDE connected devices (for example CD-ROM/DVD).
3. Right-click onto all other "Standard Dual Channel PCI IDE Controllers" - one after the other - and let the Device Manager show all compatible devices ("Update Driver Software" > "Browse my computer ...." > "Let me pick ...."). Choose the listed "NVIDIA nForce Serial ATA Controller".
4. After having replaced all "Standard Dual Channel PCI IDE Controllers" by the "NVIDIA nForce Serial ATA Controller" (UNLESSS the one, where your natively IDE devices are connected), you can reboot.

Now your RAID array should be correctly detected by your OS.

Good luck!
Fernando
badkarma
QUOTE (Fernando 1 @ May 3 2008, 03:32 PM) *
if you don't install the OS onto a RAID partition, the OS Setup won't automaticly install the needed nForce S-ATA driver.
Solution:
Open the Device Manager and check within the "SCSI and RAID Controllers" section, if the "NVIDIA nForce RAID Controller" is correctly installed (by using the nForce RAID driver).
If yes, do the following:
1. Open the "IDE/ATAPI Controllers" section of the Device Manager. You will see a lot of devices named "Standard Dual Channel PCI IDE Controller".
2. Check, which of them is managing your natively IDE connected devices (for example CD-ROM/DVD).
3. Right-click onto all other "Standard Dual Channel PCI IDE Controllers" - one after the other - and let the Device Manager show all compatible devices ("Update Driver Software" > "Browse my computer ...." > "Let me pick ...."). Choose the listed "NVIDIA nForce Serial ATA Controller".
4. After having replaced all "Standard Dual Channel PCI IDE Controllers" by the "NVIDIA nForce Serial ATA Controller" (UNLESSS the one, where your natively IDE devices are connected), you can reboot.

Now your RAID array should be correctly detected by your OS.

Good luck!
Fernando


Thanks Fernando but it didn't seem to work. I only have 1 "Standard Dual Channel PCI IDE Controller". I tried to use "Nvidia nforce Seral ATA Controller" driver but when I rebooted the device is unable to start and no RAID in OS.
Fernando 1
QUOTE (badkarma @ May 4 2008, 03:41 AM) *
Thanks Fernando but it didn't seem to work. I only have 1 "Standard Dual Channel PCI IDE Controller". I tried to use "Nvidia nforce Seral ATA Controller" driver but when I rebooted the device is unable to start and no RAID in OS.
Look into the "SCSI and RAID Controllers" section.
Which devices are listed there?
Google Internet Forums Unattended CD/DVD Guide
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.