If you are using the OemInfFiles method to enforce the installation of not correctly digitally signed drivers (as the nForce SataRaid ones), you should put all files of the LEGACY subfolder into the OEMDIR folder (although not all of them are really needed). If you have no LEGACY subfolder, you may take the content of the SATARAID subfolder, but you have to add the NVATABUS.INF (from another package) and the files NVCOI.DLL and NVATA.CAT (from the SATA_IDE subfolder).

The OemInfFiles method does only work, when you additionally create a file named WINNT.SIF (situated in the I386 folder) with an OemInfFiles section. This section should look like this:

Okay, I've been going crazy trying to figure out why I couldn't get past a STOP 0x0000007B blue screen of death during textmode setup of WinXP SP2-slipstreamed. Wasted several CDs trying different versions of NVRAID, etc.. Finally got ahold of a floppy drive and tried it that way - SAME !@#(% THING. Booted into UBCD4WIN and ran "Windows XP Setup" under Applications thinking that would solve the problem -- still wouldn't boot into the 2nd stage of setup on the drive (system froze).

So I finally figured out what the problem was. I don't usually use a CD/DVD drive in my system, I use an external USB drive bay. Normally this works fine for everything. It even boots into UBCD4WIN. But for whatever reason the WinXP SP2 textmode setup doesn't like it at all. Hooked it up to my IDE port on the motherboard, problem solved.

Or so I thought; you see, I want to have 16k cluster sizes (formatted it in UBCD4WIN). Now I was getting a "Disk read error occurred - Press Ctrl Alt Del to restart" error message when trying to boot to the drive for 2nd stage setup. But guess what, I found a solution to that problem too. Look in this thread (basically you can't use SP2, you have to use SP1 or earlier to install -- there is also an alternative fix by replacing some files): http://forum.abit-usa.com/showthread.php?t=63931

I hope this helps someone out there, I've been going nuts over trying to figure this out for the past day or so.

Thanks a lot, it give me a great help for my failure of installation XP

nm...

What does that mean? Which language is it?

nm = nevermind

Thanks, with your help I have learned something again today!

I followed the instructions for integrating Server 2003 drivers, and it seemed to work and install OK. Unfortunately, for some reason, my IDE DVD-ROM disappeared after install, and wouldn't reappear until I ran the chipset driver install routine. This involved copying an entire CDROM worth of data over to the PC using a USB pen drive.

Now I can work around this issue if necessary, but it's annoying and I'd like to fix it for future reinstalls. Has anyone any idea what went wrong, or how to resolve this?

That was not necessary.
The reason why your IDE DVD-ROM disappeared after the installation of W2k3 was an incompatibility of your IDE device and the nForce Parallel ATA Controller.
There are 2 easy ways to solve the problem.
At first you should look for new firmware of your IDE DVD-ROM device and - if available - flash the new one.
If there is no new firmware or the firmware update does not change anything, you should replace the nForce Parallel ATA Controller by the MS Standard Dual Channel PCI IDE Controller.
Open the device manager and then the section "IDE ATA/ATAPI Controller".
Then do a right click on the nForce4 Parallel ATA Controller and click "update driver software" > "Browse my computer for driver software" > "Let me pick from a list..."
When the option "Show compatible hardware" is enbled you now can see the "Standard Dual Channel PCI-IDE Controller" as fully compatible hardware. Choose it and go ahead > Done.
After the next reboot you will see your IDE DVD-ROM within the device manager.

OK, that makes sense. I'll have a look for updated firmware - failing that, I'll try replacing the IDE controller driver next time.

Thanks for the help.

What if I want to use the Microsoft drivers and not the nVidia ones?

I had to restore the default Microsoft ones, because that f***ing Safely Remove Hardware service was continuously plugging/unpluggling my SATA II hard drives - even the C drive !? - and I had to run the Recovery Console twice...

Now
I gave a look at the Microsoft driver details and it lists ATAPI.SYS, PCIIDE.SYS and PCIIDEX.SYS.
Considering these files how can I integrate them so that the Windows XP Professional installation is able to install on my SATA drives without the need of external drivers?
What other file - i.e. .INF, .CAT, etc. are needed for them?

Although you didn't mention your hardware config, I assume, that you have an nForce4 SataRaid system.

What you mean are the MS Standard P-ATA(=IDE) drivers for the device named "Standard Dual Channel PCI-IDE Controller". These MS drivers are already "in-the-box" with Windows XP. If you want to install them, there is no need for external drivers or files.
It is no problem to replace the "NVIDIA nForce4 Parallel ATA Controller" by the "Standard Dual Channel PCI-IDE Controller":
a ) open the device manager and open the section IDE ATA/ATAPI-Controller
b ) right-click on the NVIDIA nForce4 Parallel ATA Controller and choose the "update driver software" option
c ) within the following 3 windows always choose the lowest option and click "Continue"
d ) when you enable the option "Show compatible Hardware" within the last pop-up window, you can choose the "Standard Dual Channel PCI-IDE Controller" as fully compatible IDE Controller.
e ) after the next reboot you will have the MS Standard P-ATA drivers instead of the nForce P-ATA drivers.

What I don't understand is your "Safely remove hardware" story. Which service was continuously plugging/unpluggling my SATA II hard drives? Can't you just stop/disable this "service"?

No way, I need that for my USB/Firewire drives.

About the IDE issue I know that, but I also know I have to supply some drivers when Windows installation starts - I am talking about the F6 stuff - otherwise Windows won't detect any SATA / SATA II hard disk.
For some reason the setup doesn't use the Microsoft drivers.

If you have an nForce4 mainboard with the option of using SataRaid and PataRaid ports and if you have created an nForce4 array, you have no chance to install the MS IDE drivers at the beginning or during the OS installation.
The only possibility you have is to replace the NVIDIA P-ATA by the MS IDE drivers (for details see my last post) after the complete installation of the OS.

Exactly what I am doing atm and so will I do then in the future.

I had a bluescreen using NLITE today too, (0x0000007b 0xbacc3524). All windows setup was passed, but just before entering Windows it gave me the BSOD.

Anyway, I read most of the posts here for integrating NForce SATARAID drivers and found that my problem was lying with the NForce SATARAID drivers. (I have a new system MSI K9N NEO (Nforce 550 chipset), AMD AM2 - 4600+, Asus 7900GT. I changed my drivers from the ones on the MSI site to the ones on my CDROM I got with the NForce chipset.

What I did was kept the SCSI/RAID drivers in windows (Deleted all other standard drivers, except SCSI/RAID). And used the shipped drivers (found under folder \nVidia\System\MCP55). Slipstreamed again using WXPPRO (int SP2), unattended, made iso with CDIMAGE, booted and no problems anymore.

Hope this helps for some of you

Thank you very much for your troubleshooting report.
It would be very important to know, which nForce IDE driver version you used at least (check the "properties" of the NVRAID.SYS by right-clicking on the file) and which driver subfolder you integrated.

@ all users with an nForce 590/570/550 chipset and an nForce RAID array:

As I cannot test my guide with these new nForce chipsets, I am very interested to get feedback from you.

• Did you succeed with the integration of the nForce SataRaid drivers by using nLite?
• Which chipset driver packages did you use?
• Did you try to integrate just the SATARAID instead of the LEGACY subfoder? If yes, did the integration succeed?

okay..i followed the latest install guide in this thread, when i got through with the install i rebooted and the windows boot screen popped up real faint and now it reboots infinitely at this same point everytime

the bios info at the bottom of the page says: 07/06/2005-NF-CK804-6A61FD49C-00

IT'S A DFI Lanparty UT NF4 ULTRA-D mobo

i have 4 hitachi 250Gb SATA drives in raid 0+1 and running @3.0gbs

I'm using nLite 1.01 and integrated the following drivers:
NVATABUS.inf
NVRAID.inf

those are the only two things i saw in the window for selection in nLite....the SATARaid and IDE folder contained everything, but it only chose those two things for install

the readme in the nvraid folder states this:

This Win2K/XP nForce (C19/CK804 and C51/CK804) driver package consists of the following components:

Audio Driver (v4.62) "WHQL"
Audio Utility (v4.51)
Ethernet Driver MCP51 (v50.11) "WHQL"
Network Management Tools MCP51 (v50.11)
SMBus Driver (v4.50) "WHQL"
Installer (v5.01)
Win2K IDE Legacy Driver (v5.52)
Win2K IDE SataRAID Driver (v5.52) "WHQL"
Win2K IDE SataIDE Driver (v5.52) "WHQL"
Win2K RAIDTool Application (v5.52)
WinXP IDE Legacy Driver (v5.52)
WinXP IDE SataRAID Driver (v5.52) "WHQL"
WinXP IDE SataIDE Driver (v5.52) "WHQL"
WinXP RAIDTOOL Application (v5.52)


what is going on here and how can i remedy this hellish nightmare...i had similar problems with my last pc

As I have exactly the same motherboard, I suppose, that the present BIOS version of your mobo does not support the integration of the new nForce SataRaid drivers.
My advice:
1. Check your nLited XP CD, if you have integrated the correct IDE\WinXP driver subfolder (only the LEGACY works with your board, don't use the SATARAID or SATA_IDE one!). If necessary, create a new nLited XP CD with integrated LEGACY subfolder off the 6.70 or 6.85 chipset driver package as TEXTMODE driver.
2. Download the newest BIOS for your motherboard dated 2006/04/06 (look here: http://us.dfi.com.tw/Support/Download/bios...=A&SITE=US)
3. Flash the new BIOS named NF4LD406.BIN (look into the tutorial for BIOS flashing at http://www.dfi-street.com/forum/index.php?)
4. Restore the necessary RAID and SATA entries within your BIOS.
5. Install Windows XP by using the nLited CD. If Windows Setup asks for CAT files, just skip. This has no influence at all for a successful installation.

Good luck!
Fernando

i have the 704BTA from OCZ Tony, which is better and more stable than the 0406...the 0406 has some good fixes but overclocking isn't supposed to be as nice with it...i'm also wondering if having multiple session log files in the same folder can be causing issues with the CD

1. What RAID BIOS version do you have (look at the second boot display)?
2. Did you do the XP installation with GENIE BIOS default settings (no overclocking)?

it says 4.84 as the NVRaid bios

i'm going to try it all over from scratch, i just noticed those config files (three different sessions) in my ISO folder, i think that may be affecting the install...then if that fails i will switch bios to 406

and yes the system is completely stock, no overclocking..yet..but she's watercooled, so it'll happen eventually

okay, well i was correct, i had some bad config logs in my folder, i started with a fresh install and now everything went well...i had about 4 trial Nlite configs, three of which were not complete, those must have somehow been messing with the install when nlite created the iso they were in it...also, i did pull the raid drivers from the sata and ide folders, so that may have been the cause as well...thanks for the help

Hello,

Does integrating the nvraid drivers as texmode drivers in nLite resolve the issue of them being replaced by the incorrect IDE ones in guimode? Or is guimode skipped with an unattended install? (My first install with nlite, sorry if this is a stupid question)


Thanks!

rodrif

Thx for this little Guide.

I can report that there is a problem with nForce 6.86 for me.
Endless reboots.
6.85 works fine.

A8N32-SLI Deluxe (Nvidia Raid BIOS 5.50).

Yes! The replacement of the correct NVIDIA SATA drivers by the wrong MS IDE drivers during the GUIMODE part of the installation does not take place, when you integrate the nForce SataRaid drivers as TEXTMODE drivers using a tool like nLite.

That is the reason why I don't suggest to take the nForce SataRad drivers off the 6.86 chipset driver package.

Hey guys, I hope that I can get a helping hand here...

I have been trying to get this to work for a while now with no luck.

I made sure I had all of the files (NVATABUS.INF, NVATA.CAT, NVIDE.NVU and NVCOI.DLL) in the legacy folder and used nlite.

I selected nvraid.inf for the intergrate driver part and selected both of the nForce Sata/Raid Controller drivers nLite proposes.

When I try to install windows, I get hung up right before the EULA and get a BSOD.

"Problem has been detected and Windows has been shut down to prevent damage..."

I can get further with my original disk, but obviously the RAID drivers are not integrated.

I really wish I had a floppy drive as I am getting pretty fed up with this.

This is my first time messing with raid and so, any help is greatly appreciated.

Im using a DFI Ultra D and two 74gb raptors

Thanks

Is your Board the DFI NF4 UltraD (as mine)?
Which driver package did you take for the SataRaid driver integration?
Why and from where did you get the NVATA.CAT into the LEGACY subfolder?
Is your Raid "healthy" and set as bootable device?
Are RAM and PSU ok?
Do you use a SATA connected CD-ROM/DVD device?
Which mainboard BIOS and which Raid BIOS version do you have (look at second boot display)?
Did you use safe BIOS timing settings (no overclocking) during the install?

1. Yes it's a NF4 Ultra D
2. I used the driver package linked in the first post HERE
3. I took NVATA.CAT from the sata_ide folder. It wasn't required?
4. Yes
5. Yes
6. No
7. I have the 704-2bt BIOS installed, but I am unsure of the RAID BIOS. I'll check and get back to you.
8. No OC during install...

All things look good....
It is not required to put any file (for example the NVATA.CAT) into the LEGACY subfolder.
My advice: Control your SATA cables and retry the install with your nLited CD.

Hmm... I just checked and the date on my RAID BIOS is april 26, 2005. It is version number 4.84.
I now have three questions.

Do I need to update RAID BIOS and if so how?
Could nvata.cat be messing things up and should I make another nLited CD without it?
What do you mean by control your sata cables?

1. No, you don't need to update your BIOS, unless you want the new MediaShield 5.50 (new name for Raid BIOS). In this case you have to update your BIOS. If you want a tutorial how to update your BIOS, have a look here:
http://www.dfi-street.com/forum/index.php?
2. No, the NVATA.CAT doesn't mess things up.
3. Problems with SataRaid systems are very often caused by broken or not correctly connected SATA cables.

Two more bits of information...

My "original" CD is a burned sliptreamed SP2 cd that I made earlier.
The hang up and eventual shutdown happenes when the bottom says "Setup is starting Windows..."

I am going to try to borrow a Floppy drive from a friend, but I'd really like to get this to work.

I appreciate all of your help.

As I have the same mainboard and a very similar system, I don't have any ideas about the issue, that might be responsable for your problem.
If you really followed all my advices giving in the first post of this thread, I would suggest the following:
1. Remove 1 of your RAM sticks (if you have more than 1) and retry to install XP using your nLited CD. If you succeed, you can reintegrate the removed RAM sticks.
2. If the installation fails, retry it after having updated your BIOS. Take the BIOS version you can grab here: http://us.dfi.com.tw/Upload/BIOS/NF4LD406.EXE

Good luck!
Fernando

Thanks a lot for this post. Really saved me. I have the 550 chipset (Same MOBO > MSI K9N NEO-F) and I made several coasters trying to find the right drivers. I tried the "Vista Beta" drivers that were suggested on the first post to no avail (still BSOD after windows load). The only thing that worked for me was the drivers off the Motherboard CD.

Thank you both for your posts. Your results are very usefull for other owners of a mainboard with nForce 590/570/550 chipset.
As a consequence I have put your recommendation to integrate the SATARAID subfolder of the mainboard driver CD into my guide (first post ofthis thread).
Thanks again!

CU
Fernando

Hey Fernando, remember this guy from china whith the endless reboots problem? I had the exact same problem at the time with 6.86 + RVMUpdatePack2.1 + latest nlite. I didn't care then, as it was not the time to reinstall, but now since RVMUpdatePack2.1.1 came out, i decided to see if things improved.
I found that the problem is not with nlite or ryan's pack, but with 6.86. I remade a cdrw with the last session and used nForce4_x16_6.85_winxp2k_english. Bingo! No more endless reboots and everything works as advertised.
When i used 6.86, i integrated once the lagacy folder and once the sataraid one but the problem is still there. The strange thing is that after windows got installed OK with 6.85, i manualy installed 6.86 and the raid drivers got updated nicely and there are no reboots. I have no idea how these drivers work when installed manualy and just can't get windows to boot when integrated. The endless reboots are at the point when windws finished installing everything and we are at the forst boot when windows tour should pop. The raid bios shows, and right the next second windows loading screen should apear, but instead i get "endless reboots".
Btw, my mobo is an A8n Sli Premium (latest 1302 bios, 4.84 raid bios) with 2 samsung p120 - 250GB in raid 0.
The windows i used is a SP2 integrated VLK this size - 579 MB (607,250,432 bytes).
Last session atached.

I've read through this whole thread, and I just can't seem to get it.

I downloaded the latest Vista Beta drivers. I copied the SATARAID directory to a floppy (I'm trying to use the F6 method). I copied txtsetup.oem from the \ide\legacy directory, as well as the nvatabus.inf. I modified the txtsetup.oem (from legacy) so that it pointed to nvraid.cat. I also noticed there was pointing to nvcoi.dll, which was in the sata_ide directory, but not sataraid (So I copied that file as well)

When I try to install Win2K3, and use F6, it just doesn't find anything.

Any hints?

Thanks

Siobhan

That is the reason why I recommend to take the 6.85, when you are going to install Windows XP onto an nForce4 RAID array. You won't even find a notice about the 6.86 chipset driver package wthin my guide (first post of this thread).

You obviously did not read accurately the first post of this thread:
1. When you don't have a brandnew nForce5xx mainboard, you should not integrate the SATARAID, but the LEGACY subfolder. There is no need to copy anything, because the LEGACY subfolder contains all needed files.
2. It is not recommended at all to copy the TXTSETUP.OEM from one IDE subfolder to another.
3. When you are going to install Windows Server 2003, you should integrate the SataRaid drivers into a bootable CD as well. Use the drivers I recommend (look into the first post).

Fernando,

thanks for getting back to me. I did read the first post.

"If you want to integrate the newest nVRaid drivers into W2k3, you should take the 32-bit nForce chipset driver package you get here. Although this package is mainly designed for Vista Beta2, it works flawlessly with W2k3 too. Unzip the package and store the IDE\driver\LEGACY subfolder somewhere. Users with an nForce 430/410 or nForce 590/570/550 chipset should take the IDE\driver\SATARAID subfolder. In both cases you will need no other preparation."

I got that, it is v6.67 (which I got from your link). I have nForce 430 so I took the SATARAID subfolder. It didn't work. Then I started reading subsequent folders and there was all kinds of stuff about modifying TXTSETUP.OEM, etc (I was desperate and willing to try anything). Point is SATARAID didn't work for me.

BTW, MB is an ASUS M2NPV-VM, and BIOS is latest at 0303 (Wouldn't even work with XP until I upgraded to that BIOS version)

So, are you saying I should build a new CD, or should I be able to use F6?

Thanks again.

Hi siobhanellis,
as I don't have an nForce430 mainboard, I cannot test it myself.
NVIDIA had announced, that SataRaid systems wth an nForce430/410 or nForce590/570/550 chipset do not need the LEGACY subfolder and can be installed by using the SATARAID one. I cannot verify, if they are right. Users with an nForce5XX chipset reported, that they could install XP onto their RAID by just using the content of the SATARAID subfolder, but I don't have any feedback yet from a user with an nForce430/410 chipset mainboard. This is why your post is very appreciated.

My advice for you:
1. Before you begin to create a new nLited CD, have a look into the nForce chipset driver package of your mainboard CD and report here, if you find a IDE\LEGACY subfolder.
2. Copy the content of the IDE\SATARAID subfolder (as it is) of your mainboard driver CD onto a floppy and try to install XP or W2k3 by using the F6/floppy method.
3. If you succeed, you can create an nLited CD with integrated nForce SataRaid drivers by using the same drivers as with the F6/floppy method.
If the installation with F6/floppy using the SATARAID subfolder fails, then NVIDIA is wrong and you have to use the LEGACY subfolder of your mainboard driver CD (if there is a LEGACY folder) or from the driver package I suggested within my first post. In this case you should not use the F6/floppy method (you will get endless reboots at the end), but create a new nLited CD.
There is no need at all to mix the content of the subfolders.

Please report here about your results, because it may be very helpful for other users.

Thanks and good luck!
Fernando

With the XP drivers from my MB CD I can install Windows XP, but not Windows 2003.
There is no Legacy folder on my MB CD
The Legacy folder from the NVIDIA Vista Beta 2 does not work either.

Guess I'll have to log a call with nVidia, see what they say.

Thanks for all your help and, if I get anywhere, I'll let you know.

Siobhan

I use an Asus mainboard with a 430 chipset. For me the sataraid folder of the Vista package with the 6.67 drivers was not enough. The legacy folder works without any problems, though.

Thanks for your guide
keats

Thanks for your posting. Let's wait, what NVIDIA says.

Thank you for this information. I will modify my guide concerning the suitable SataRaid drivers for users with an nforce 430/410 chipset.

can u guys direct install the ide as nforce ide by using beta vista nforce driver? since it is not whql....
i dun use nlite to intergrate it by the way

Yes, you can use the Vista Beta2 nForce IDE drivers with nearly all nForce chipsets.
By the way: None of the nForce SataRaid drivers usable for nForce2/nForce3/nForce4 are WHQL certified, even not the official ones. Only the drivers within the SATARAID and SATA_IDE subfolder of some nForce packages are digitally signed by MS, but owners of a mainboard with an nForce2, nForce3, nForce4 and even nForce430/410 chipset cannot use them, when they have built a SataRaid system. They get endless reboots at the end of the installation. That is the reason why I propose to take the not WHQL certified drivers off the LEGACY subfolder.

actually i am still using nforce 3 driver ide...
slipstreaming using editiing txtsetup method...
but the driver i use cannot support newest chipset for 570/590
i tested successful to intergrate the vista beta driver into my dvd, but at blue screen installation i can detect the harddisk under nvatabus system....
after entering windows...
windows will use normal microsoft ide....
in the case of nforce3 ide driver.... it is whql and auto use by windows.... it works for my board nforce4 ultra too
need to use the winnt.sif editing but too many oemXX.inf in windows =)
still testing...
always updated to ryan pack, editing drivers, updating drivers... that's why i use manual intergration....

When you don't want to slipstream the newest nForce IDE drivers by using a tool like nLite, you will have to take the IDE drivers off the old nForce chipset driver package v. 6.53. After the successful install you can update the nForce IDE drivers NVATABUS.SYS (as nForce S-ATA Controller driver) and NVRAID.SYS.

Thanks for keep replying fernando...
Using PhreeZ method but the driver need to copy to $oem$\$$ folder
they really works and the vista beta raid driver is installed perfectly =)
windows just ignore the whql and install for me =.=

I hope this hasn't been asked already. This thread is 57 pages, so it's hard to check!

1) I'm slipstreaming an XP cd for my upcoming install. I just got one of those new Seagate's. SATA2, Perp. So I'll need to integrate SATA drivers into it, since I'm going to install on the new drive. I have a VNF4 mobo, nForce4. Is the guide in the first post of this thread for me? Should I follow that to get the right SATA drivers integrated?

2) How would I go about testing the CD? Last time I did a CD I used VMWare to test. This time I'm not sure that will work. I can make VMWare use SATA, I think, but will the nVidia drivers work properly on VMWare?

Any help is greatly appreciated.