don't have time to read bsod computer reboot too fast, in safe mode= reboot without bsod (or really too fast to see it)

You can prevent the reboot by hitting F8 and choosing "no reboot at system failure". Then you have plenty of time to read the error message.

By the way: Is there a MBR on your 3rd (non-Raid) hdd, for example from earlier installation tests? If yes, you should delete it.

no there no mbr on my third disk, it's just a storage disk. I'll make some other test on xp32 with 2 other sata disk.

Err sorry I didn't read the whole post (too many replies) but what about using bashrat the sneaky driverpacks? they're so easy to integrate in just a few seconds you can have plenty of updated drivers in your cd!. Give them a try they rock! Naturally massstorage drivers are directly integrated so the setup uses them to recognize scsi/sata devices.

This thread was started within the nLite Forum and is dedicated for home users, who want to create their special Windows XP or XPx64 CD with integrated nForce SataRaid drivers by using nLite.
The integration of Driver Packs and especially MassStorage Driver Packs into a Windows CD has primarily nothing to do with nLite. There is a special forum "DriverPack MassStorage" within the MSFN Board. That forum is dedicated for pc system administrators, who want to create a Windows CD useful for nearly each mass storage combination.

Cu
Fernando

here my test for xp32 on nf4 16x platform:
using xp pro sp1, added sp2 + all hotfix
using nForce4_x16_6.82_winxp2k_international: sataraid driver as txt and sataide as pnp.
No other driver plug on sata port, only 2 raptor set in raid0
Install fully complet, hotplug an other driver on nf4 sata port ok, reinstall of nf4 16x package, reboot ( third drive still plug) = bsod , same in safe mode.

Hello Blank,
thank you for your test results.
As I know, that you like testing, please try the following:
Take an original XP CD (without SP1) or an XP CD with integrated SP2 as origin, then let nLite do the same work as before.
I think, that your problem can have something to do with inteference between SP1 and SP2.

CU
Fernando

hum don't have a proper xp cd, only my xp +sp1 slipstream by hand. I look at my work if i can found one.

The following I posted on nuhi's bug tracker blog after I could no longer burn error free dvd of any nature and through much trial and error and some help/suggestions posts in this thread have reached the following:

More info on this after 3 fresh installs, 3 different ways:

If you use cdimage in place of what ships with nlite 1.0rc5 all your folders are dated 2002.

If you integrate modified nforce4 sataraid 6.82 drivers on the ASUS A8N32-SLI Deluxe using the Legacy folder from the 6.70 and 3 files from the sata_ide folder neither Nero 6.6 or 7 will write any DVD's and some CD's without error.

A fresh install integrating the 6.82 as is and allowing the MS ATAPI drivers to load at first logon and using Nero 6.6 cured all; plus performance is better than a modified 6.82 install-reading from 2 DVD-RW simultaneously is faster and uses less resources.

Nero 7 is extremely finicky/unstable; Nero support is no longer what it once was so Nero 6.6 is the way to go for now coupled with the MS ATAPI.

Nero 7, on my machine at least, will not burn error free DVD's; bootable or not using either 6.82 incarnation and multitasking 2 read operations simultaneously after integrating modified; vs unmodified- 6.82 is not good.

I lost 30% of my files on one DVD due to Nero 7 corrupting them during burning-fails write verification with either driver integration.

Once the nforce sw drivers are installed rollback is buggy at best and caused me to do a fresh install.

I am now using nlite 1.0rc5 and makeiso that it ships with error free; 6.82 unmodified have been integrated and DVD-RW performance is exemplary.

Hi RickSteele,
I have to thank you for your post, because you pointed out the interdependency between the IDE drivers and the burning results of Nero Burnig ROM.
As a consequence of your post I would like to correct my guide regarding nForce4 SLI x16 systems, but before I do this I have to crearify something.
You propose to integrate the SataRaid drivers off the 6.82 package as it is (without NVATABUS.INF) and to replace the nForce PATA drivers by the MS ATAPI ones after the successful installation.
My questions:
1. Is my summary of your findings correct?
2. Did you integrate just the original SATARAID subfolder of the 6.82 package or did you copy the content of the SATA_IDE subfolder into the SATARAID one prior to the integration?
3. How did you replace the nForce PATA by the MS ATAPI driver (real install or driver update within the device manager)?

Thank you in advance for your answers.

CU
Fernando

Hi , help the noob

I am not on raid first off but i get the same problems you guys had. Trying to set up a western digital 160gb s-ata2 on a dfi lanparty nf4 sli-dr xpert. I enabled sata port in bios and disabled Raid like fernando suggested and still get endless reboots/bluescreens at startup.

ideas ?

-simon

My guide is dedicated for users with an nForce Raid system.
As you have no Raid, you should not integrate the SataRaid drivers as textmode drivers.
Try to install XP without any nForce Sata/IDE drivers (no F6, no integration of these drivers by nLite).

CU
Fernando

Yeah that is what i did. Still get the errors

Could you boot in safe mode?
Have you integrated SP2 into XP?

Yes i integrated sp2 into xp and i could not boot into safe mode.

everytime i try booting i get this : stop: 0x0000007B (0xf7a2b528, 0xc0000034, 0x00000000, 0x00000000)

Fernando 1

1. Is my summary of your findings correct?

I extracted the 6.82 drivers as downloaded from NVIDIA and integrated the sataraid folder as it extracted-absolutely no modifications.

The MS ATAPI drivers install after final reboot before first logon-popup PNP dialogue and you select "let me choose....", then the "primary IDE...."-you select Ok, then a second PNP dialogue; same procedure only this is for "secondary IDE..."; now the MS drivers are installed and Windows XP finishes booting to the desktop. They're labelled unsigned but, in Device Manager in driver details they show certified with cat files sooo.... However, they work great.

Because the 6.82 contain no Legacy-ATAPI-folder there are no nforce sw drivers for your ATAPI devices in this build. If you go into safe mode and do a manual install of the 6.82 you are asked if you want to install the NVIDIA sw dr; if you hit "yes" install goes through the motions but when you reboot you still have the MS ATAPI installed. nforce ATAPI pending in a future release I suppose.

Thanks for your interest and hope this clarifies...

Rick

Try the following:
1. Take default BIOS settings (no overclocking).
2. Use only 1 RAM stick.
3. Unplug all not needed hardware components (audio card, usb devices etc.)
3. Try to boot with a normal (not nLited) XP CD with integrated SP2. Don't use F6/floppy method.
What happens?
Thank you for the clarification. I will mention your experience within post 1 of this thread.
That is not totally correct. Within the SATA_IDE subfolder of the 6.82 package there is a file named NVATA.SYS. This driver is nothing else as the nForce IDE (P-ATA) driver.

Fernando 1

"That is not totally correct."

True, but, it is not installed-invisible in the unmodofied 6.82 on the A8N32-SLI Deluxe-no inf.

One other thing, I also integrated the sata_ide as PNP in all 3 installs with no adverse reactions because I read somewhere that if you wish to install just SATA-no RAID-you will have to reinstall to gain the functionality if sata_ide not already present from a previous install. I can not confirm this because I only run RAID but, if it does no harm.................

It seems to me that for now NVIDIA wants the standard MS PNP ATAPI drivers to install, you know?....I mean this being the first X16 release and generic for both Intel and AMD.

Good, that you have added this information.
I don't think, that your install would have succeeded without the additional integration of the SATA_IDE subfolder.
Reason: There is no file named NVATABUS.INF or NVATA.INF within the SATARAID subfolder, but such an INF file is absolutely necessary for a successful installation of Windows XP onto an nForce SataRaid system.

CU
Fernando

Fernando 1

"I don't think, that your install would have succeeded without the additional integration of the SATA_IDE subfolder."

I've done both ways and makes no difference-the install succeeds either way and the end result-MS ATAPI drivers install without incident. The contents of the F6 package-which I have also done-from ASUS; are the same as the 6.82 sataraid folder from NVIDIA.

I know it makes no sense and believe me with the 1009 BIOS concerns cropping up every now and then it was actually 5 fresh installs before I got 3 that were consistant and, therefore, credible.

The MS drivers are already in SP2 and ATAPI simply installs as PNP.

The untouched 6.82 sataraid will install nlite integrated with no modifications everytime-all other things being equal-and no manual install in safe mode is required afterwards. My system is fast and stable using BIOS 1009-it took 4 fresh installs prior to all this and some fidgetting in CMOS to get this release BIOS to do the job-ACPI issues mainly. The mobo is, afterall, still relatively new-a few kinks to work out; I think ASUS and NVIDIA have to talk more.

I hope all this helps.

Thank you, Rick, for this reply.
I believe you, that this worked with your ASUS board, but I'm not sure, that people with other boards will succeed by just integrating the SATARAID subfolder.
As a result of your posts I have modified my guide regarding the use of the 6.82 driver package by users with an Asus A8N32-SLI Deluxe.

Big thanks again - your tests were very important!

CU
Fernando

I read all of first page, and it seems that the method does not differ from any driver integration (at least for BIOS ver 4.84 or less)

I followed your setup and I get "could not find nvraid.sys" in setup mode.

I know putting nvraid.sys file in i386 folder fixes this problem, but would like to know if you misses a step in the first page .

thanks for great info

I think, that you have done something wrong.
If you follow my guide, you will find the driver NVRAID.SYS within that folder, which you take for the nForce SataRaid driver integration (LEGACY or SATARAID). nLite will copy all files into the driver folder OEMDIR and additionaly the drivers as copressed files (NVATABUS.SY_ and NVRAID.SY_) into the I386 folder. Have a look, if you find them there.

CU
Fernando

Ok, since I was little vague on my setup, if i had given any, let me give you detail

I have shuttle sn85g4v3 (nforce3) . i checked RAID BIOS ver, and it is 4.34 (latest BIOS from shuttle site) so I followed your guide and downloaded 6.53 nforce driver,

I used nlite 1.0 RC6 to integrate the nvraid (which is within IDE\WINXP folder) , and selected both SATA and RAID like the tutorial said.

nlite successfully completed its job.

now I have "NLDRV" folder inside my i386 folder . and all the compressed nvraid drivers are inside that folder, but not a single nvraid related files are inside i386 directly.

I have tried to integrate nvraid long time ago (with nlite .98 i think) and the result was pretty much same as what i have right now.

so either I must've missed step, or something's wrong.. I read your guide three times and this was the correct step ( at least for me, who is w/ BIOS 4.34)

thanks in adv

The SataRaid drivers are only copied into the i386 folder, when you integrate them as "Mass Controller" (= textmode driver). If you integrate them as "normal" device drivers (pnp drivers), you will not find them within the i386 directory.
EDIT:
Which driver subfolder did you integrate for the SataRaid drivers?
Did you get at this point of integration a pop-up window with the question, if you want the following 2 drivers to be installed:
NVIDIA nForce Storage Controller (required)
NVIDIA RAID CLASS DRIVER (required)?
If not, you really missed to choose the integration as TEXTMODE DRIVER.

When I selected the nvraid.inf file inside the IDE\winxp folder of 6.53 driver nlite automatically selects it as TEXTMODE Drv. (yes the popup)

it even asks me if I want to check out this page for more info.

now, under the WINXP subfolder, there's another subfolder named 'raidtools' . do i need to copy those files out to 'ide\winxp' folder? or just leave it as it is?

Hi@all thanks to everybody for your numerous posts about integrating nVidia sata drivers.

however i must say that i still havent succeded in anyway.
So what i try is to integrate more than one SATA/RAID driver:
VIASRAID
SI3112r
SI3114r
AND
NVATABUS/NVRAID Drivers
sofar integrating the other drivers seem to work properly, i veryfied that integration of the viasraid driver was successful, but still as soon as i add the nvidia nvatabus.sys/nvraid.sys files etc. to my unattended cd i resice a BSOD right after setup finishes loading the drivers listed in TXTSETUP.SIF.
To make this clear. setup states: LOADING WINDOWS and then the BSOD appears right befor the screen to edit partitions is supposed to apear, showing this BSOD: *** STOP: 0x0000007B (0xf7a2b528, 0xc0000034, 0x00000000, 0x00000000)
im quite sure that this is due to the nvraid/nvatabus driver, as if i choose to not compress the nvatabus.sys/nvraid.sys to .sy_ puting them into the i386 i get the message that windows cant find them instead of the BSOD
My hardware is the ABIT KN8 (NOT ULTRA) with a WD200G HDD, not sure which Bios version.
besides this my unatteded install works fine so far.
I tried integrating the drivers using the LEGACY folder as much as using the SATARAID folder (both from 6.70 package) and even the files from the floppydisk that have been include with the MB.
I also tried hacking TXTSETUP.SIF my self using the numberous guides in this forum, as much as having the latest version of nLITe installing my drivers. both times no success!!!

thanks to everybody so far.

Lanoxx

The "Raidtools" are tools and no drivers. I have never used them.
So you can leave the "Raidtools" folder as it is. I personally remove this folder, before I begin with the integration.

1. Why did you try to integrate all those Raid drivers at once? AFAIK your ABIT KN8 has neither a VIA nor a Sil Raid Controller. So I recommend to integrate only the nForce SataRaid drivers and to see what happens.
2. You have to verify your nVRaid BIOS (look at your second boot screen). If your version is lower than 4.84, you should take the nForce chipset package 6.53 for the integration.
3. Don't manipulate the TXTSETUP.SIF and the WINNT.SIF.

Good luck for you both!
Fernando

hey, work fine great job¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡¡

thanks for you help on this fernando 1. i checked my txtsetup.sif again and found double entries for the nvatabus.sys and nvraid.sys, i also removed the viasraid and si311x drivers. now it works great with the nlite method.
still i would like to use viasraid, si311x AND nvatabus/nvraid drivers all together.

i need this as im using the cd to setup lots of pcs with different configurations, using the defaulthide unattended option, and just changing names and cdkey each time.
therefore i need to add multiple drivers to suit the different systems. i managed to include nfore2 and 4 drivers as much as nvidia forceware drivers, but im still having troubles on the catalyst drivers and the SATA raid drivers.
no idea how to solve that...
is it generaly not possible to include multiple SATA raid drivers in textmode setup, or do i just do something wrong?

thank so far
Lanoxx

Congratulations, that you got it to work.
Normally it is no problem to integrate drivers you don't need, because the MS setup routine will only pick the ones for existing devices.
Contrary to that is the behaviour of some mass storage drivers and especially SataRaid drivers, which are not correctly digitally signed. These drivers may induce problems within the setup. It took me a lot of work and many weeks of time to find a way to successfully integrate the nForce SataRaid drivers. As you know, nLite has incorporated a sytem to prevent the preference of the MS IDE standard driver, but AFAIK this system does not work for VIA RAID drivers.
If you really want to integrate several mass storage drivers into a Windows XP CD, you should look into this forum: http://www.msfn.org/board/-f107.html .

CU
Fernando

have you tried to integrate nvidia 6.53 drv with rc6 ? can you check if you get same results as mine?

Whom do you ask and which results do you mean?

EDIT:
I just had a look onto Shuttle homepage and found a special Raid driver disk for your SN85G4 V3: http://global.shuttle.com/Download/Downloa...tem=SN85G4%20V3.
Users with an nForce3 250 chipset can use the 6.53 driver package, but now it seems to me, that you have an older nForce3 chipset, that is not compatible with the newer drivers. Maybe this is reason why no drivers could be integrated as textmode drivers.
Normally it should be no problem for you just to integrate the old nForce Raid drivers from the Shuttle homepage, but I am not sure, if the integration works, because the TXTSETUP.OEM file is not in the same folder as the driver files. Maybe you have to copy the TXTSETUP.OEM into the RAID\WinXP subfolder of the Raid disk and to edit the first lines of the TXTSETUP.OEM file prior to the integration.

the result meaning like the one in picture i uploaded.

existance of "NLDRV" folder inside i386 is something that your guide did not mention.

I just manually put NVRAID.sy_ file inside i386 folder and my computer reboots

*just tried with the shuttle driver. same thing. dang..

Your first picture shows the files inside the folder "Raidtools" (which youdo not need at all), the second shows, that the only drivers you had integrated were the SataRaid ones. Which results do you mean?
Why should I mention that within my guide? Important is the folder where the drivers come from before they are integrated. Users of nLite have nothing to do with the folder, where nLite stores the integrated driver files. By the way: nLite 1.0 RC4 and RC5 stored these files within a folder named "OEMDIR". So Nuhi changes the folder names if he wants, but this is without any influence on users who follow my guide. Tere is no reason for them to work on this folder.

i just wanted to mention that I really appreciate your replies!.

now on to the prob.

the first picture shows that all nvraid related files are in subfolder and not i386 directly (thus, causing the missing nvraid.sys error)

'raidtools' in second picture is neglectant, as i just did not erase the folder before i integrated.. (having raidtools folder shouldn't matter anyway to this problem.)

*do you have any idea why nvraid.sy_ is not copying to i386 folder? (yes it's setup as textmode)

Not really, unless you had downloaded a corrupted driver package. Maybe you should redownload the 6.53 package.
If you find the file NVATABUS.SY_ within the i386 folder, you probably did not choose both required drivers nLite propose to integrate as textmode drivers.

For the moment I propose the following tests:
1. If you have a floppy disk drive, try to install Windows XP by F6 method, by using the old Shuttle RAID driver disk.
2. If the install succeeds, try the same with the SataRaid drivers off the 6.53 package (copy the whole content of the IDE\WinXP folder exepting the RAIDTOOLS subfolder onto an empty floppy).

After these tests take the best driver for the integration by using nLite. Do nothing else, just integrate these **** nForce SataRaid drivers. Don't change anything within the nLited folders and files (as I have seen on your pics, you have created an $OEM$ folder and an OEM subfolder).

Good luck!
Fernando

Fernando 1

NVIDIA has just released a new set of nforce4X16 drivers dated Feb 7, 2006, version 6.85. Have not installed yet-just downloaded them now.
Thought you might like to know.

Hi Fernando, I just wanted to say thanks for taking the time to create this guide and still tend it attentivly. Creating the RAID was easy enough and I made sure I had the 4.84 RAID Bios. The system reported it as healthy. Setting up RAID using a floppy and the F6 method would never work for me. I would get the symptom of the endless reboots at the end of a seemingly sucessful XP GUI install. I think I remember seeing that you are a DFI nF4 LANparty SLI-DR user. That's what I have as well and I tried following your guide for using nLite to integrate the Nvidia RAID drivers. I think I was doing that part right but I would always be confused as to what file, if any I needed to modify (edit by hand in a text editor)

Well, in frustration, I re-checked DFI's website for the motherboard and they had posted on 2006/01/27 a new RAID driver.
http://us.dfi.com.tw/Support/Download/driv..._FLAG=A&SITE=NA
I used nLite RC 1.06 to intergrate the driver DFI posted there and it worked without needing to do any further modification! I don't know how these files are different,
(because I tried the driver from Nvidia and the old ones from DFI and they would give me the endless reboots too. I can only guess that somehow these drivers have some portion of the code re-written, or differently called, or that infact the drivers are now properly WHQL certified. Just thought I would bring this to your attention.

my system:
DFI nF4 LANparty SLI-DR
2x200 Samsung Spinpoint SATA 3.0g in RAID0 (finally, yeah!)
IDE DVD burner
etc
nLite XP pro with slipstreamed SP2 integrated RAID drivers

Thanks again, without this forum I never would have gotten this far!

Hi Rick,
thank you for this information, but I already knew it (I started this thread: http://www.nforcershq.com/forum/1-vt64530....er=asc&&start=0)
There is no big difference betweeen the older 6.82 and the new 6.85 package concerning the version of the various drivers, but one thing is brandnew: The 6.85 package has a LEGACY folder, which contains all necessary files. So the integration of these drivers will be much easier than before. As a consequence I will adapt my guide regarding this point.
Hi Thornsword,
thank you for the flowers!
You are right - I have very similar hardware as you have (my DFI Lanparty NF4 is the best board I ever had).
What was it, what you have edited by hand? It's a while ago, that people needed to do some "handmade" editing. Since nLite 1.0 RC1everything works automaticly, if you follow my guide.
At least a tip: The Raid driver you have downloaded from DFI homepage is a very old version from 2004. You should update the SataRaid drivers by a newer version (off the 6.70 package).

CU
Fernando

Fernando1

"has a LEGACY folder, which contains all necessary files (even the CAT ones"

No CAT files in the Legacy folder and they install unsigned; also if you nlite integrated just the sataraid folder-installing the PNP MS ATAPI drivers you will have to update the ATAPI to the NVIDIA sw drivers manually after reboot in Device Manager, even though during 6.85 setup you are-as with the 6.82-asked if you wish to install the sw ATAPI-MS ones stay though-I guess the system feels MS unsigned are better than third party unsigned.

Just a side note; I will be doing the nlite thing with these drivers this weekend and trying out the image in an install but, I don't know.....I have a bad feeling about these.......

You are right, that was my bad. I had it already corrected before you have written this.
Thank you for this statement. I am very curious about your test results.
As I know, that you like testing, I would like to stimulate you to test the nForce SataRaid driver integration by using another tool named Windows Unattended CD Creator. This tool is rather simple and cannot be compared with nLite according the options, but has fully integrated a special method to prevent the substitution of the correct nForce driver by the wrong MS driver without any manipulations on the IDE controller drivers.
It would be interesting to know your experience with this tool and its alternative method.
If you want to use the WUCD Creator: The link to my guide in english language is here.

CU
Fernando

Hey there,

Just successfully integrated nVRaid in my winxp home ed. using your method (s. quote). I copied the additional file into the sataraid folder and just selected it for integration in nLite 1.0 RC6 Tx!

Thanks!
CU
Fernando

From Fernando (as I don't know how to add a quote like you guys do)
-----------------
Hi Thornsword,
thank you for the flowers!
You are right - I have very similar hardware as you have (my DFI Lanparty NF4 is the best board I ever had).
What was it, what you have edited by hand? It's a while ago, that people needed to do some "handmade" editing. Since nLite 1.0 RC1everything works automaticly, if you follow my guide.
At least a tip: The Raid driver you have downloaded from DFI homepage is a very old version from 2004. You should update the SataRaid drivers by a newer version (off the 6.70 package).

CU
Fernando
-------------------

After meticiously re-reading the first post I think my issues came about when I tried to integrate the \NVIDIA\nForceWin2KXP\6.70\IDE\WinXP\sataraid folder without first moving the files below as listed in your first post:

1) Open the LEGACY subfolder and copy the file NVATABUS.INF into the SATARAID subfolder.
2) Open the SATA_IDE subfolder and copy the files NVATA.CAT, NVIDE.NVU and NVCOI.DLL into the SATARAID subfolder.
Now your SATARAID subfolder of the 6.70 package is well prepared for the later integration of the SataRaid drivers

I was sure your method was not working for me as I was still getting the random reboots even after integrating the drivers from sataraid folder. I wish I had noticed before that I was missing the step to move those files. My apologies for not being as careful a reader as I should have been, if I had caught that I probablly could have saved myself several hours of frustration as I went to download other revisions of the Nvidia drivers and try to integrate them!

You are right to say the drivers dfi posted on thier website for the LANparty nF4 SLI-DR are old drivers from 2004, but I think the Windows XP install worked for me with these drivers because all the files that I needed (the ones I would have moved as stated in your first post) were already in the same directory. Its curious that dfi would post a new RAID driver on 2006/01/27. but have those drivers be time stamped at 2004/12.

I will re-try the method you list in your first post as soon as I am home from work. I'll post here with my new results, although I'm pretty sure I will be sucessful now that I see where my apparant mistake was.

On the right hand bottom of each post you find 2 buttons: a "Quote+" and a "Quote" one. Just click on the "Quote" button, then you have the quoted text like here. If you want to answer at once to more than one post, you have to hit the "Quote+" button of each post and then the Reply button at the site bottom.
That would be fine. Before you start, please verify, that you have a Raid BIOS v. 4.84 (official BIOS 623-3 has it included).

Good luck!
Fernando

Nope, didn't figure it out.

Okay, so I noticed on DFI's site that they have new RAID Driver versions available dated 1/23/06. How would I go about installing these without reformatting and integrating them for the future?

New dated download links on the homepage of a mainboard producer does not mean, that the drivers are really new.
Can you give me the link to the drivers and the details of your system?

I'm back! Though I guess that's a bad thing I got help a few months ago on this thread and everything was going great. I did a few hardware upgrades recently though, which included switching out some HDD's and I am back to having problems with NF4 driver integration.

Here is the hardware I am using:
ASUS A8N-SLI Deluxe
A64 3500+ Venice
2gb (2x 1gb) OCZ DDR 3200
2 eVGA 7800GT's
2x 74gb WD Raptors

One of the raptors is new, the other isa year old or so. Both have been working fine for me though.

I have the latest BIOS update for the motherboard, which adds the 4.84 nvraid. The drivers I am slip streaming are from the nForce 4 AMD 32bit set, verison 6.70.

So anyway. After creating a stripped array of the raptors, I load up the windows installer. Windows sees them as one big drive and everything seems normal. I create a 50gb partition, format, and load setup files. Then, on the first reboot, all I get is a blank black screen. The CDROM spins up, but it stops there. It never gets to the actual install and configure portion of the setup.

Any ideas what the problem could be? I think it may be hardware related because I am using an older slipstream that I had working with 2 other raptors. I looked through the BIOS, making sure all my boot priorities are correct and nothing else seems to be conflicting with previous setups.

I have also tried using a new slipstream that was made with the same 6.70 and nLite 1.0 rc6. Still getting the same blank screen though.

Thanks for any help!

Do you mean it stops after the install of the setup files and before the hardware installation begins?
Is the cursor on left hand top of the screen blinking?
Did you change anything else unless you have a new raptor?
Is your PSU strong enough?
Have you tested your RAM sticks (memory test)?
Do you have the correct voltage for your RAM?
My tip: Set BIOS timings at default (no overclocking), unplug all unnecessary hardware devices and try it once more. Maybe you should test it with a little enhancement of the RAM voltage (0,1 V).