It results in a blank screen after the first reboot durring an install. Right after formating and loading setup files, it reboots, then just goes to a blank screen. There is no cursor blinking (very important).

I had given someone one of my older raptors to use and just picked up a new one recently. So, besides the raptor, the system has been up and running for quite some time without problems. The new raptor has been tested as well, just not in a raid setup.

The PSU has plenty of juice. It's an Antec NeoPower 480.

I am overclocking but the system is most certainly a rock. I have installed Windows and linux countless times (I do a lot of software and hardware testing) on this system with the current overclock without any issues. I would like to avoid reseting the clocks and having to redo them if at all possible

I think I may have found something. This MS KB article seems to describe my problem perfectly.
http://support.microsoft.com/?scid=kb;en-us;314503

So maybe it's not slipstream related. I will try fixing the MBR and using WD Data Lifeguard to write zeros to both drives when i get home from the shop.

Edit: Oops, wrong KB link.

Before you gave your old raptor away, did you correctly remove your Raid array? If not, you really should clean your hard disk drives by low level formatting.
Good luck!
Fernando

Yup that was the problem. After writting zeros to both drives I tried again (with the version made from nlite 1.0rc6 and the nforce 6.70 drivers) and everything worked fine. Sorry to clog up the thread with useless information

http://us.dfi.com.tw/Upload/Driver/NF4%20RAID%20F6.ZIP

Tweakin

Try it with a normal slipstreamed SP2 Setup-F6.

Fernando 1

"I am very curious about your test results."

Just finished a full nlite 1.0 rc6 install; modified-appropriate files copied from SATA and Legacy folders-6.85 integrated-4.3G bootable DVD-RW and it went like clockwork. The ATAPI drives responded-and are responding-very well, as good as or better than MS PNP. The RAID performance is trouble free and certainly no slower. Nero 7.0.14b is a complete bust still though and 6.6 will not do bootable DVD's using makeiso that ships with nlite-must use cdimage; all the file/folder names are in upper case-I really hate that; plus, of course, all the files/folders carry a 2002 time stamp. But, all installs well.

I do indeed have a Raid BIOS v. 4.84, although I'm using the 704-2 Beta Bios instead of the official BIOS 623-3 I've found the beta bios to be more stable for me. But don't get me started on how I had to loosen my RAM timings just to get stability when I wasn't even overclocking. I used to get blue screens a lot, STOP errors or IRQL errors until I adjusted my RAM timings. I left memtest run for hours and I would only get errors in tests 5 and 8 and I read somewhere that those were do to timings. But thats all behind me now.

Now that my system is stable I decided I would try for the next experiment: RAID. The SATAII RAID hardrive setup has been giving me headaches too, but I look at these things as a challenge. I reinstalled windows over the weekend with my slipstreamed nLite CD following Fernando's instructions to the letter and it worked like a charm. Thanks, Fernando! If only that were the end of things, but its not without new problems too, I now have that annoying "safely remove hardware" icon in the task bar, and I have some unknown devices in device manager that I'm pretty sure weren't there when I used the RAID drivers from the set included posted on DFI's nF4 page. The one I'm most concerned about is a PCI Bridge device, which I assume is related to SLI. But I only have one graphics card right now. Incidently those drivers that I used previsously are the same ones that Reinvented is talking about. They aren't new, the drivers have dates from 2004, but the .zip file was posted on 2006/1/23. I'm going to try to fix the issues above tonight and I'll post here with my results.

thornsword

Try updating driver using the ATK2000.INF from the ASUS Ai Booster Utility\Acpi\WIN2000 folder; or DFI's equivalent. Actually this integrates as PNP system using nlite. ASUS Probe also has it. It's for the PCI Standard ISA Bridge. I believe AMD's Cool&Quiet has this inf also; I do not think this particular inf is brand specific.

Please let us know, which files you used from the LEGACY and the SATARAID subfolder.
There is no reason to install the old drivers or to reinstall XP:
1. The icon "safely remove hardware" is totally normal (it is shown for hot plugging devices).
2. You can easily install the missing "unknown" devices by giving them the correct nForce drivers. Look into the properties and write here what you see (example: DEV_0057 is the NVIDIA Network Bus Enumerator as a part of the nForce Ethernet controller).

CU
Fernando

Fernando

"You can easily install the missing "unknown" devices by giving them the correct nForce drivers."

The nforce drivers will not have this particular solution-for the PCI Standard ISA Bridge-at least not on ASUS boards; is DFI different that way?. My first install using nfirce4 awhile back now had this "unknown device". This is not an "old driver" but is the only driver for this device if that is what thornsword is referring to. If it is wrong WinXP will not install it.
As for the tray icon, I agree with you; it is necessary, except on generic one SATAII disc installs-no other discs attached-this is not hardware RAID. A lot of forum posts around the net I have read ask how to remove this-you can't.

"Please let us know, which files you used from the LEGACY and the SATARAID subfolder."

nvatabus.inf from legacy, nvata.cat, nvuide.exe, nvide.nvu, nvcoi.dll from sata_ide.

The nforce broadband is also quicker-far less DHCP errors in logs after reboot.

I know, that users of some Asus boards have an "unknown device" within their device manager. You have already pointed it out. The problem can be resolved by putting the Asus mainboard CD into the CD drive. The missing driver will currently be found. But this has nothing to do with the integration of nForce SataRaid drivers.
With my DFI mainboard I normally have no trouble at all with "unknown devices", unless I have removed too many drivers by nLite.
Thank you for posting the driver details. If you think I should change my guide regarding this special point, please let me know.

CU
Fernando

Fernando

"I know, that users of some Asus boards have an "unknown device" within their device manager. "

All ASUS nforce4 have this requirement-to solve for unknown device-all else being equal; so, yes, this driver must be either integrated or installed afterwards to eliminate "unknown device". I just do it all with nlite. I have no experience with DFI so I did not know if you were the same; good enough.

As far as the A8N32-SLI Deluxe driver integration/requirements; it is the same as all the other SLI as far as that goes. I am, however, noticing some suttle improvements in system performance/reliability-especially concerning ATAPI; therefore, I would definitely recommend the 6.85 upgrade; my system is just humming along.

Live long and prosper

Thank you for this clarification, Rick.
My guide is already customised to your findings.

Best wishes!
Fernando

Fernando 1, i have just 2 sata drives on raid 0 (Asus A8N SLI premium) connected to nvraid. I had no problem when i installed windows with a floppy but i what to find out something if i will ever reinstall.
Is it ok if i integrate just the sataraid folder and not mess with the legacy folder?
I don't plan to use any other drives other than those 2 on sata raid.

No, that will not be ok. There are some important files missing within the SATARAID subfolder. You have to take either the LEGACY folder or the SATARAID with some extra files in it (see post No 1 of this guide).
You have written, that you have an AN8 SLI Premium, but who is the mainboard producer (ASUS or Abit)?

Sorry for that typo... I've got an ASUS A8N SLI Premium.

And you are sure, that you have an nForce Raid array and not a Sil3114 Raid array?

EDIT: You have 2 different sorts of Raid Controllers on board (the nVRaid and the Sil ones). Check within your device manager, which controller your Raid uses.

Tzeb

"No, that will not be ok."

If using nforce RAID you will have no ATAPI recognition, other than in command prompt, in PNP during install and will not have until GUI has ended and you are at first logon. Any CD/DVDROMS will use the MS PNP 2001 drivers and are not signed. I found the NVIDIA sw drivers faster; regardless of what some "reviews say". Do your install, backup your boot partition and give the sw drivers a go-if using nforce RAID. However, rollback is not a viable-it is buggy-option; so backup before experimenting. Further, if speed is your goal use the nforce4 bios because it utilizes the PCIe bandwidth and is faster than the Siil which travels in PCI. I found the Siil very difficult to setup and boot from-instability-mileage may vary though.

I only use nvraid sata, the Silicon raid controler is disabled in bios
I don't understand the need for sw drivers if my raid is on sata ports. Sure, i have one nec 4551 DVD ram on IDE2 and it works perfectly.
I knew about Sil3114 "problems" and that's why i went with ports 3 and 4 on the nvraid
Btw, i have 2 samsungs 250gb each and they perform awesome in raid 0, while being extremely silent

I just wanted to say thanks - I followed Fernando's guide (the one in the first post of this thread), and it worked perfectly (on my nForce 4 Ultra-based Gigabyte GA-K8N-Ultra9, with 2xMaxtor HDDs in RAID0 )!

Thank you, Fernando, for your (very good) explanation! And a very big THANK YOU to the author of nLite - it's a really AMAZING piece of software!!

If you have an nForce SataRaid system, you have to install the NVATABUS.SYS and this is the S-ATA and P-ATA (=IDE) driver at the same time. If you don't want to use the NVATABUS.SYS as P-ATA (= IDE s/w) driver anymore, you can change the use of the nForce Parallel ATA Controller against the use of the MS Standard Dual Channel PCI IDE Controller, but you should do it only after the successful install of Windows XP.
These are the steps: Device manager > IDE ATA/ATAPI-Controller > right click on the NVIDIA nForce4 Parallel ATA Controller > udate driver > manual update > show compatible drivers > then choose the MS one).
But I confirm what RickSteele wrote - I would not recommend to take the MS IDE drivers unless you get problems with one of your IDE (CD ROM or DVD) devices.

Thank you for your post!

CU
Fernando

RickSteele, how many drive do u have on sata port ?

Hi Blank,
are you sure, that Rick will read all posts of this thread, unless he succeeded with the integration of the nForce SataRaid drivers?
You probably will have more chance to get an answer, if you send him a PM.

CU
Fernando

ok i'll try this, because i want to reinstall an xp 32 and still having bsod. I had use the 6.85 package with nlite and unatend cd creator; with the two it's working find until i'll plug another drive on the nvidia s-ata port.

eheh i'va been a little crazy few minuts ago last i night i reinstall an xp32 coz this f**k*n starforce wont work on a xp64, so there all test i make using an xp32 with nf4 16x 6.85 package:
-make a full unatend cd with content of legacy folder copy in sata_raid (without overwrite) = bsod
-same with copy files describe on first post = same bsod (can stop reboot and error message was on acpi)
-try unatend cd creator and adding only sata_raid folder without modding and follow fernando guide = bsod
So i restart from 0 with floppy and xp pro 32 sp1a, i have copy on the floppy the content of the sata_raid folder and get no bsod.
Then i make a full modded cd with nlite (added sp2 & all hotfix) without driver integration and make it work fine. So for the end i have use the same project before and add the sata_raid folder as txt with no modding on driver and get it work too

Just want to notice that all the stuff describe in this topic is working until i use only two sata drive, in my last working cd nf4 sata controller & parallel ata controller are recognize as standart controller and get no more bsod after reinstall the nf4 6.85 package.

To finish i think the bsod i get when using 3 drives on sata came from moving file before integration.

When did you plug the 3rd hdd (before or after the install)? Did you use the nVRaid utility?

Hi Blank,
your findings may be important for other users with nForce4 SLI x16 mainboard.
Just to clarify:
1. How did you get your Raid array to work "without driver integration"?
2. So you recommend for this special chipset just to integrate the SATA_RAID subfolder as TEXTMODE driver and nothing else? Or did this only work with more than 2 hdd's?

CU
Fernando

i'm mad one more time, after install of drivers/software/4-5 reboots, i unplug my floppy drive, disable it in bios, change boot setting and get the bsod !!!

I just return to bios and enable floppy drive without plug it and windows boot normally So to resume

raid0 set on sata port 1/2 + 3° drive on sata 3 + floppy enable in bios = boot ok
raid0 set on sata port 1/2 + 3° drive on sata 3 + floppy disable in bios = bsod
raid0 set on sata port 1/2 + no drive on sata 3/4 + floppy disable in bios = boot ok
raid0 set on sata port 1/2 + 3° drive on sata 3 + floppy enable in bios = boot ok

that's really awesome

To resume for nf4 16x + 6.85 + xp32
Just add sata_raid folder as txtmode without no mod, make install only with raid disk to prevent windows to put mbr on wrong disk and let's floppy enable in bios


I use a floppy with sata_raid driver + f6 @ windows install

It is not easy to understand.
Do you mean that you integrated the SATA_RAID subfolder as TEXTMODE driver using nLite and additionally presented the same drivers by using F6/floppy method during TEXTMODE part of the installation?
You did not answer to these questions.

EDIT: I have read, that you worked with Windows XP SP1a. There are other users which had problems trying to integrate the nForce SataRaid drivers into a bootable XP CD by using SP1a.
Please try to get a clean XP CD without SP1a or XP with integrated SP2. Maybe the install works this way without any floppy use!

No i use the same driver but don't load it twice, i try floppy without integration and no floppy with integration

I plug my 3° drive at the end on setup, dont use nvraid utility


Don't have a clean cd, in fact the setup work with sp1a or sp2 without floppy, i get bsod until i disable floppy drive in bios.

Maybe I am wrong, but I suppose, that this is the reason for all your troubles. If you want to create a new Raid array with 3 instead of 2 hdd's, it is not enough to enable the 3rd SataRaid port within BIOS, you have to add the new hdd to the array by nForce Raid utility.
Before you do that, I would recommend a backup of your important datas.

CU
Fernando

since i was directed to this thread, which is about NVRaid, i'll ask anyways...
what driver are you supposed to use for Non-Raid, i've tried a few and i just get that retarded BSOD about the bios not being fully ACPI compatable.

Do you have try just to boot with your cd if windows setup can find drive without driver ?


ok ok when i spoke about my 3° drive, it's only a data store drive, don't want to add it to my raid. I just unplugged for mbr problem and add it at the end on setup. I have only sata port 1&2 set in raid mode.

I just had a look into your earlier post within another thread to realize, that you have a board with an nForce SLI x16 chipset and a SATA II harddrive disk.

At first you have to look into your mainboard handbook if you have to enable nVRaid within BIOS (unless you don't use it).
If you have a Maxtor hdd you may look for a new firmware (some Maxtor Sata2 hdd's have trouble with nForce4 chipsets).
At least I would recommend to integrate the SATA_IDE subfolder off the nForce chipset package 6.85 as PnP driver by using nLite.
Please report here, if it worked or not (unless this thread was only dedicated for users with nForce Raid systems).

EDIT:
1. I agree with Blank - the installation should work without any extra drivers during install, if you have XP with integrated SP2.
2. What is about your BIOS? Can't you get a newer one which totally supports ACPI?

If these findings are true, I would bring the board back to the vendor.
By the way: What is the difference between the first and the forth alternative?

thanks alot for the reply, i'll make a cd in a little bit and give it a shot, funny thing, i believe my bios does fully support it, i have the newest one 1009 and i can install with my old windows xp sp1 without any problems at all on this system. So i guess i can just toss sp2 on that cd and nlite some stuff out and i should be fine.

For some reason i do remember reading that i have to intergrate drivers if i do use nlite for unattended or soemthing like that. either way i'll make one without the drivers and one with the drivers just in case and give them both a try. If i get this all worked out i'll make to sure to post which drivers i use here, and maybe we can work on some kind of new sticky thread that has a list of mobo models and the drivers they must have, at least we will know about the a8n32 sli deluxe ; )

Good idea! You can get crazy with these damned nForce Sata drivers, because there are big differences not only between the chipsets, but also between different boards with the same chipset.

Good luck!
Fernando

ok so i used these drivers, remember this is a NON-Raid setup with an SATA hard drive.

A8N32 Sli Deluxe
nForce4_x16_6.85_winxp2k_english
SMBus --- nf4sys.inf
legacy --- nvatabus.inf
sata_ide-- nvata.inf

I'll start a new thread, post this and requesting other to post info on their MB's hopefully an admin can organize the whole thing.

Hi DarqAngels,
thank you for your post, unless it is not easy to understand, because
a ) INF files are no drivers (you can point at any INF file and you will get all files of that INF file folder onto your nLited CD) and
b ) the SMBus has nothing to do with Sata drivers.
So I try to resume for owners of an Asus A8N32 SLI Deluxe, who want to integrate the nForce Sata drivers for a non-Raid-system into a bootable XP CD:
For the successful integration you have to integrate the LEGACY and SATA_IDE subfolder of the 6.85 package as PnP drivers - that's all.
Is this correct?
Or did you mean, that the LEGACY folder has to be integrated as TEXTMODE and the SATA_IDE as Pnp driver? Or did you mix both folders before you began the integration?

Please clarify this if possible.

CU
Fernando

here's my bunch of test with my crappo floppy drive:

fisrt one , clean xp32 sp1, sata_raid folder from 6.85 on floppy
boot install (only raid drives plug)
f6 + load nvraid driver
install ok
install 6.85 package + reboot
plug 3° drive and reboot still ok
disable floppy & reboot still ok

second one, same cd, only sata_raid driver integrated with last nl
(floppy disable and 3° drive unplug)
boot install + delete all partition
nvraid detect ok
reboot after first install part , get bsod on acpi
renable floppy in bios but not plug in & reboot
install follow the end and finish fine
install 6.85 package & reboot still ok
reboot and disable floppy = bsod

So there something wrong with nlite, perhaps someone can try to disable his floppy drive to test if the same thing occur.
I'm remake an xp64 cd and test if it's work too

just finish my xp64 setup, working fine with floppy disable. So i confirm for nf4 16x (asus a8n32-sli), it just need to integrate sata_raid folder as txtmode from 6.85 package without no mod on files. Sata and PATA controller are recognize as standard controller until 6.85 package is not installed.

That is interesting.
So the nForce Sata driver NVATABUS.SYS will not be installed unless you have integrated the SATA_RAID folder, which contains this driver?
Have you ever tried to integrate just the LEGACY folder? If yes, what was the result?

hum i'm was wrong on nforce version, it's 6.83 for x64 and there's no legacy folder. I don't want on integrate others drivers, just need nvraid for windows setup and finish by the hand other drivers with lastest versions.

OK, this belongs to the other (x64) thread, but once mor my question:
Did you ever try to integrate the LEGACY folder of the 6.85 package during your tests with 32-bit XP?

yes, have the same result, nvraid is working but get bsod when disable floppy drive.

Thanks for your reply.
Are you really sure, that your mainboard and especially your floppy port is OK? In other newsgroups I saw a lot of posts from owners of an ASUS A8N32 Sli Deluxe with a lot of hardware troubles. That is why I am unsure, if your findings have anything to do with nLite.
So I would like to encourage other nLite users with an nForce4 SLI x16 mainboard to report about their experiences using my guide and especially about the best driver folder choice.

i cannot say that my floppy/mobo are 100% ok; all i see is that i have only bsod when i'm using nlite not with floppy + f6 setup. And i assume that's really mad coz i don't seen relation between floppy and nvraid.

The connection between your floppy and SataRaid controllers is your mainboard! I am nearly sure, that there is something wrong with your board.

Please report here again, if you get any news about your issues.

CU
Fernando

oh hehe sorry about that.
all i did was download 6.85 extract it, and then point nlite to those .inf files, so i didn't mix anything i just left everything as it was. They were integrated as PnP drivers.
i added the SMBus because i figured a8n32 users needed it anyways for the Hypertransport.
hope that clears stuff up

For the purpose of this gude should a NForce 430 / GF6150 board be counted as nForce4 AMD ie 6.85 drivers or should I use the 6.70 drivers? Anyone know?[quote]nForce4 AMD

[quote name='Methanoid' date='Feb 22 2006, 08:06 AM' post='468727']
For the purpose of this gude should a NForce 430 / GF6150 board be counted as nForce4 AMD ie 6.85 drivers or should I use the 6.70 drivers? Anyone know?[quote]nForce4 AMD
[/quote]
if i'm not wrong 6.85 is only for nforce 4 16x platform.

I don't believe, that you integrated the Raid drivers (off the LEGACY folder) as PnP drivers. You can integrate Sata drivers by this method, but not Raid drivers. Otherwise your Raid array will not be recognized during TEXTMODE part of the install.

For mainboards with an nForce 430/410 chipset there is a special nForce chipset driver package 8.22. The only problem is, that this package has no NVATABUS.INF (no LEGACY folder). If you want to install this driver package, give me your eMail adress and I will send you the correct IDE driver package ready for integration as TEXTMODE driver.

hehe you must have forgot. mine wasn't for a raid, just for a single sata