[Fernando 1]

AJPatel, on Nov 19 2006, 01:01 AM, said:

i tried with legacy of 6.7 and a fresh winxp copy and unchecked oem preinstall
it froze and bluescreened at the same point videoprt.sys

I am really at a loss with your problem.

Another question: Which hdd's are you using (manufacturer, SATA1/2)?
Another idea: Maybe your 430 W PSU is not powerful enough for your system.

[AJPatel]

Fernando 1, on Nov 19 2006, 02:17 AM, said:

AJPatel, on Nov 19 2006, 01:01 AM, said:

i tried with legacy of 6.7 and a fresh winxp copy and unchecked oem preinstall
it froze and bluescreened at the same point videoprt.sys

I am really at a loss with your problem.

Another question: Which hdd's are you using (manufacturer, SATA1/2)?
Another idea: Maybe your 430 W PSU is not powerful enough for your system.

guten morgen

i'm using 2 western digital 250gb sata2 drives RAIDed as JBOD
i've been running the system on the 430w PSU for a few months now with no problems at all - gaming, rendering, etc.

[Fernando 1]

AJPatel, on Nov 19 2006, 09:28 AM, said:

i'm using 2 western digital 250gb sata2 drives RAIDed as JBOD
i've been running the system on the 430w PSU for a few months now with no problems at all - gaming, rendering, etc.

Hi AJPatel,
I am really sorry, but I can't help you.
Your problem has obviously nothing to do with the integration of the SataRaid drivers, but with your hardware.
If you have a multiboot system and you have access to the partition where the XP installation failed, search for the files SETUPERR.LOG and SETUPAPI.LOG. You can find them both within the WINDOWS directory. Look into both files (within SETUPAPI.LOG only the last lines are interesting).
More tips:
1. Control your SATA cables.
2. Test your RAM sticks with MEMTEST, try to install XP with 1 stick.
3. Unplug all unneeded devices (COM, USB etc.) during the XP install.
4. Don't integrate any other drivers unless the nForce SataRaid ones.

Good luck!
Fernando

[maadhatter]

I have been trying to get Windows XP w/SP2 Installed on the this new system in a RAID 0 config for over a week now. Specs:

AMD FX55
Abit A8N SLI x32
2gig Adata RAM
GForce 7600 GT
Cooler MAster 500W PSU
Samsung DVD/CD RW
2 X 150Gig Raptor HDs

I have used Nlite to make the disk with the newest sata_RAid and the 6.70 package
I seem to get windows installed ok, and everything is ok for a while and running (almost) great. OF course there are unistalled devices in teh device manager, so I install those, and I always end up with one 'unknown' device.. and a raid controller.. which I now learned this is the SIL controller.. I am not sure what the unknown is.. this current installation I was able to get rid of it.. I am guessing it is part of the SIL driver or ACPI.

Anyways after many installations the same thing happens after a couple hours, things start to 'lag' a little bit... Internet explorer starts crashing ..normally this expected to a point with MS, i know.. but this happens A LOT!! then a blue screen comes.. goes really fast... then I reboot sometimes it goes to windows, but iut usually wont take to blue screen again.. nvXXX files amongst others (i dont have them all.. this pc is for a friend, and i do not have a log of all of them

Currently I am using the system and it very slow to respond.. also I can not open IE at all, or any type of folder or anything that uses the EXPLORER.exe shell

1. what is the best driver package to use from NVidia?
2. Should I or SHould I not use the IDE PnP driver than Nlite adds automatically
3. Do I need to remove any windows components
4. What steps are required after the install?

[Fernando 1]

maadhatter, on Nov 20 2006, 02:21 AM, said:

Currently I am using the system and it very slow to respond.. also I can not open IE at all, or any type of folder or anything that uses the EXPLORER.exe shell
1. what is the best driver package to use from NVidia?
2. Should I or SHould I not use the IDE PnP driver than Nlite adds automatically
3. Do I need to remove any windows components
4. What steps are required after the install?

1. There is no "best driver package" useful for every nForce chipset and mainboard. For your system I would try either the 6.86 or the 6.91 chipset driver package.
2. You may try to install Windows XP by just loading (F6) or integrating the SATARAID subfolder of the nForce chipset driver package, but I think, that you will probably need the NVATABUS.INF/NVATA.INF (only available with LEGACY subfolder or with the combination SATARAID+SATA_IDE) to get XP installed onto your nForce RAID array.
3. No.
4. Nothing is required.

[maadhatter]

Quote

2. You may try to install Windows XP by just loading (F6) or integrating the SATARAID subfolder of the nForce chipset driver package, but I think, that you will probably need the NVATABUS.INF/NVATA.INF (only available with LEGACY subfolder or with the combination SATARAID+SATA_IDE) to get XP installed onto your nForce RAID array.

Combination SATARAID+SATA_IDE folders is the same as taking the legacy folder or no? ...

Isnt doing that combination the same as using NLite to do the adding the SATARAID as textmode and it automatically taking the IDE as PnP? (which I have tried)

This post has been edited by maadhatter: 20 November 2006 - 11:04 PM

[Fernando 1]

maadhatter, on Nov 21 2006, 04:37 AM, said:

Combination SATARAID+SATA_IDE folders is the same as taking the legacy folder or no? ...

It is not really the same.
Differences:
1. The combination SATARAID+SATA_IDE does not work with some nForce chipsets.
2. You won't get WHQL-certified drivers by using the LEGACY subfolder.
3. The combination SATARAID+SATA_IDE prevents the installation of the nForce P-ATA (=sw/IDE) driver. You will get the MS Dual Channel PCI-IDE Controller driver. When you integrate the LEGACY subfolder, you will get the nForce P-ATA driver installed.

maadhatter, on Nov 21 2006, 04:37 AM, said:

Isnt doing that combination the same as using NLite to do the adding the SATARAID as textmode and it automatically taking the IDE as PnP? (which I have tried)

Yes, nLite v. 1.2.1 integrates automaticly the SATA_IDE subfolder as PnP, if you are going to integrate the SATARAID subfolder of an nForce chipset package.

[maadhatter]

Thank You Very Much Fernando for helping me out, along with everyone else too.

I just copied the contents of the SATARAID folder of 6.86 and loaded an original XP PRo w/SP2 CD then tried loading drivers VIA F6 and it says:

File nvatabus.sys caused an unexpected error (4096) at line 2113 ib d:\xpsprtm\base\setup\oemdisk.c.
Press any key to continue.


EDIT: THAT WAS A BAD FLOPPY DISK... waiting on results


This is extreemly frustrating, its been almost 2 weeks of trying 100 different things... I am wondering if there is some hardware that is failing somewhere(Motherboard), not because of this error, but the fact I have had it working great for several hours and then it falls apart with nvraid and dcom errors in the event viewer)

Alos Ive seen people say putting the Raptors on SATA 1 and 3 instead of 1 and 2.. does that really help?

I am thinking about putting the memory in my machine (2 x RAID 0 arrays, 2 * segate 80gig and 2x 300gig segates.. xp pro on the 80s vista on the 300s) but I dont want to screw up my arrays!

This post has been edited by maadhatter: 21 November 2006 - 08:28 PM

[Fernando 1]

maadhatter, on Nov 22 2006, 04:19 AM, said:

This is extreemly frustrating, its been almost 2 weeks of trying 100 different things... I am wondering if there is some hardware that is failing somewhere(Motherboard), not because of this error, but the fact I have had it working great for several hours and then it falls apart with nvraid and dcom errors in the event viewer)

1. Did you test your RAM with Memtest?
2. What is about your PSU? With your system you need much and extremely constant power.

maadhatter, on Nov 22 2006, 04:19 AM, said:

Alos Ive seen people say putting the Raptors on SATA 1 and 3 instead of 1 and 2.. does that really help?

I don't know.

[maadhatter]

OK so the RAID installed again fine Lst night (or at least it seemed that way) using 6.86 SATARAID Drivers only and doing a standard F6 install.

I then installed the whole 6.86 package WITHOUT SW DRIVERS (is this correct or no.. i found conflicting information about these... and I think I hit yes to install this previous times, so I hit no this time)

I installed 93.71 Video Drivers

Everything OK at this point.. I shut the computer down and then left for the night so I did not do anything else to it.

Got home after working today(and golfing ) turned on the computer got it hooked up to the internet (ICS - Xover cable through my wirless on My computer..works great actually)... Everything seems OK

I installed firefox, Azureus downloaded 2 Small torrents.. Everything still fine... I was just surfing the web, and boom "Internet Explorer has to close" ...Ok its windows... then again.. Went back to FireFox.. even that got a simular error.
so now im like Crap..
Realized I did not do windows updates yet.. so I do this (custom) Downloaded everything OK, then started installing updates ... I got another error

"Generic Host Process for WIN 32 Services has encountered a problem and needs to close"

I rebooted the machine, and it looks like it is starting the whole update process over again.. checked EVENT VIEWER:

NVRAID Erros:
-"The device , , hasa bad block"
Event ID 7
Source NVRAID

DISK Errors:
The Device \Device\HardDisk0\D, has a bad block
Event ID 7
Source DISk
Symbolic NAme: IO_ERR_BAD_BLOCK
Explanation: The device has a bad block of memory, which Windows was unable to read. Data might be missing or corrupted


OK.. Well w/o running memtest yet, according to this the Harddrive(s) is bad!..PowerSupply is 500W CoolerMaster CPT 500T Rock Solid Reviews ( LINK http://www.newegg.com/Product/Product.asp?...N82E16817159040 ) But I do not know if this actually meens the physical drive is bad, or the drivers for the RAID are not properly working... DO I RMA the hard Drives or what?!

JSUT DL western digital diags.. installed checked the box to run the app... and the machine rebooted!.. then got stuck at the Windows XP loading screen..this is not looking good!

This post has been edited by maadhatter: 22 November 2006 - 08:02 PM

[Fernando 1]

maadhatter, on Nov 23 2006, 03:23 AM, said:

I rebooted the machine, and it looks like it is starting the whole update process over again.. checked EVENT VIEWER:
NVRAID Erros:
-"The device , , hasa bad block"
Event ID 7
Source NVRAID
DISK Errors:
The Device \Device\HardDisk0\D, has a bad block
Event ID 7
Source DISk
Symbolic NAme: IO_ERR_BAD_BLOCK
Explanation: The device has a bad block of memory, which Windows was unable to read. Data might be missing or corrupted
OK.. Well w/o running memtest yet, according to this the Harddrive(s) is bad!..PowerSupply is 500W CoolerMaster CPT 500T Rock Solid Reviews ( LINK http://www.newegg.com/Product/Product.asp?...N82E16817159040 ) But I do not know if this actually meens the physical drive is bad, or the drivers for the RAID are not properly working... DO I RMA the hard Drives or what?!

Exactly that would I do.
Everything you reported indicates, that one of your hdd drives is defective. Find out which one by using a hdd checking utility like Drive Fitness Test (Hitachi) or Data Lifeguard (Western Digital).

[chlywly]

I was using Nvidia RAID 1 for 2 Hitachi drives with my new 680i chipset board from Asus... However I had 2 SATA drives formatted through (Partition-Magic) running off the same mobo controller, on the primary/secondary SATA slots... Anyways I installed windows fine, and everything seemed to be working, except when IN windows, installing any drivers across or from drives OTHER than my ROOT C:\ partition, kept rebootnig my computer, until finally a BSOD cycle, and couldn't any longer boot into windows.

ie) I install a sounddriver from e:\ reboot.
I install Maya from C:\ and try to place it into e:\ or d:\ reboot

So i'm not running a RAID for my main system... SHOULD I? Maybe i'll try, perhaps this method will help me as well,,, I also heard I should ONLY connect the SATA drive i'm going to install my system on, do that, then when windows is installed/setup, THEN I can connect the other drives/connect the RAID 1 array, however I certainly don't want to go through all of that to ONLY have MORE reboots after.

Any ideas, or anyone else had an issue of this nature?

Oh I forgot to mention, after my windows installtion, each time I would try to reboot from windows, it seemed to shut down my computer in a strange abrupt way...
Then each time wnidows was BOOTING up, it would run CHECKDISK for 2 of my SATA partitions but never my main C: partition... MADE no sense. EACH time it rebooted, this would happen!

This post has been edited by chlywly: 23 November 2006 - 05:51 PM

[Fernando 1]

chlywly, on Nov 24 2006, 01:49 AM, said:

I was using Nvidia RAID 1 for 2 Hitachi drives with my new 680i chipset board from Asus... However I had 2 SATA drives formatted through (Partition-Magic) running off the same mobo controller, on the primary/secondary SATA slots... Anyways I installed windows fine, and everything seemed to be working, except when IN windows, installing any drivers across or from drives OTHER than my ROOT C:\ partition, kept rebootnig my computer, until finally a BSOD cycle, and couldn't any longer boot into windows.
ie) I install a sounddriver from e:\ reboot.
I install Maya from C:\ and try to place it into e:\ or d:\ reboot

Althgough I have no experience with your new nForce 680i chipset, here are some notes:
If you have RAID devices and non-RAID devices within your system, it is very important, that you don't get more than 1 Master Boot Record (MBR).
Each Windows Operating Systems tries to get installed onto a non-Raid hdd and tries to name it drive C.

chlywly, on Nov 24 2006, 01:49 AM, said:

So i'm not running a RAID for my main system... SHOULD I?

This would be a good idea.

chlywly, on Nov 24 2006, 01:49 AM, said:

I also heard I should ONLY connect the SATA drive i'm going to install my system on, do that, then when windows is installed/setup, THEN I can connect the other drives/connect the RAID 1 array, however I certainly don't want to go through all of that to ONLY have MORE reboots after.

If you want to get any Windows OS installed onto your RAID array, you should unplug all other (non-Raid) storage devices during the installation. As your RAID array is build with more than 1 hdd, you may not unplug the other hdd, because you would break your RAID array this way.

[Dross]

This might have already been answered, but what if I just want SATA and not Raid? I have an AN8 SLI Nforce 4 setup. Right now I'm on IDE and I'd like to install on my SATA. I do not want raid. The guid mentioned something of only working with Riad??

Thanks,

Robert

[Fernando 1]

Dross, on Nov 27 2006, 01:26 AM, said:

This might have already been answered, but what if I just want SATA and not Raid? I have an AN8 SLI Nforce 4 setup. Right now I'm on IDE and I'd like to install on my SATA. I do not want raid. The guid mentioned something of only working with Riad??

Look at the bottom of my guide (first post of this thread). There you will find something about non-RAID S-ATA systems.

[DEVILSGAMER]

I don't mean to be too off topic but I have been following this thread since September, and now that I am done building my system I believe I am ready to set up my raptors in raid 0 on my a8n32 sli dlx using only the information in red along with the new version of nlite. However not completely confident as there are still many who are having problems, I am still concerned. With this said, does the recently released nlite ver. 1.2.1 make selecting the drivers from the chipset package and integrating them easier. Also information regarding the option of updating your nforce drivers after your successful raid creation seems seem ambiguous. I have read that it can be dangerous and I have also read that it is a good option to make integrating sataraid drivers easier using older driver packages ex. 6.66. Then update to the newer drivers on the successfully created raid array. Could some one please clarify these few things for me, I would be most grateful and I am sure it would be a great help for all us raid noobs.

[Fernando 1]

Semiono, on Dec 3 2006, 09:36 AM, said:

And now I try use nLite-1.2.1.installer.exe
And could the same problem this?
nvraid.sys - not found.... Why?
It file realy is present into C:\$WIN_NT$.~LS\I386\NLDRV\001
as NVRAID.SY_
maybe trouble is in extention .SY_?

Within the NLDRV folder all files are compressed to save space on your CD.
You will find the uncompressed NVRAID.SYS file within the I386 directory.

DEVILSGAMER, on Dec 5 2006, 04:19 PM, said:

I don't mean to be too off topic but I have been following this thread since September, and now that I am done building my system I believe I am ready to set up my raptors in raid 0 on my a8n32 sli dlx using only the information in red along with the new version of nlite. However not completely confident as there are still many who are having problems, I am still concerned. With this said, does the recently released nlite ver. 1.2.1 make selecting the drivers from the chipset package and integrating them easier. Also information regarding the option of updating your nforce drivers after your successful raid creation seems seem ambiguous. I have read that it can be dangerous and I have also read that it is a good option to make integrating sataraid drivers easier using older driver packages ex. 6.66. Then update to the newer drivers on the successfully created raid array. Could some one please clarify these few things for me, I would be most grateful and I am sure it would be a great help for all us raid noobs.

I you are able to get the actual nForce SataRaid drivers installed from scratch, you should do it.
It is not really dangerous to install an OS with old mass storage controller drivers and to update them later (the update takes place after the reboot), but you might get problems, if you want a later upgrade from XP to Vista.

[DEVILSGAMER]

I see, so when the time comes if there are any available updates I’ll create a new boot disk. Thank you. Is there any way to install linux on raid array from scratch.

[RoachRage]

Hi Guys, Help me here. I have been trying to install windows on my Father-In-Law's computer for several months. Every time I call Asus they tell me the MB must be bad and it has been replaced 4 times. With the same problem ever time I assume it can't really be that many bad MB's or everyone on the internet would be complaining!
Still I cannot believe that 1) I can't find that many instances of the same problem, and 2) that Asus is unaware or anable to help me with this! The only way I found this thread is because I searched for “nforce4 reboot” rather than A8N32.
It’s an Asus A8N32-SLI deluxe and I am having the same problem you describe, where once all the files are installed and it tries to boot for the first time it goes into a reboot cycle.
Unfortunately your solution is not working for me. I followed all your steps as best I could but when the installation is copying files it keeps telling me that it can’t find at least 75 different files, including nvraid.cat and many other nv files. If I hit escape to skip those files, well, you can guess the result. I tried redoing the iso adding files from the different nforce folders into the i386 folder in the nlite folder, but that doesn’t work either.

Tia

Jim Fain