Little did I realise that having an nvRaid setup would cause so many problems

I'm trying to create a custom nLite CD built from WinXP Corp SP2. After 2 days of endless burning and file juggling, I googled for "NVRAID NLITE BSOD" and was rather shocked to find how other people also encountered the exact same problems.

Anyway.... my setup:

ASUS A8N-Premium (Bios 1011)
NVIDIA RAID BIOS 4.84
Athlon X2-3800
2GB OCZ PC4000 Memory
2 x 250GB SATA Samsung Spinpoints (Raid0)

I tried to follow as much as I can from this thread, and I'm hitting the brink of giving up and dumb-founding my PC as non-nLite CD compatible.

I've tried integrating separately SATARAID and LEGACY folders from versions 5.10, 6.53, 6.85 and Vista Beta2 nForce4 drivers into nLite 1.0 (Final) (one folder of drivers per CD burn) and I keep hitting the same bsod wall over and over again on the 2nd reboot after installation completes.

What really confuses me tho, is what the heck you do with the SATARAID and LEGACY folders? The first post was really confusing. Could someone offer a complete n00bs step-by-step guide? (e.g. Copy X to X folder, rename X in X folder, integrate ???.INF as text-mode from X folder etc.)

I've been tearing my hair out for 4 days over this problem, including an all-nighter, and I'm going nuts

I am right there with you Vince. I have the same mobo and the same problems. The good news? From all I've read (and I did have this up and running before) the nVidia raid blows away the Sil3114 also onboard.

To try and simplify things I've removed all but my 2 300GB PATA disks. I've got them in a bootable mirroring array. All other hard disks are disconected.

I've created an nlite install disk with the legacy, bus and ethernet drivers from nvidia along with the other drivers for my system (graphics, audio, mouse). In remove components I've set it to remove all drivers. The disk is set up for a full automated install (I've attached the ini file).

The text mode and GUI mode install seem to work fine and the system reboots automatically. I would be expecting it to boot in to windows and start the media centre customisations at this point however it simple goes to the dreaded BSOD with stop code 7b.

Anyone got any ideas? I'd give up on this and go back to non-raid but I really want to have all my important personal files on redundant storage and DVD is just too much of a pain to keep up to date.

The LEGACY subfolder (if available) is the better solution for users with a SataRaid system, because it contains all needed files.
If you don't succeed with the LEGACY folder integration, you either have done something wrong or you have a hardware issue.

No, you can. The LEGACY subfolder is usable for SataRaid and PataRaid systems.

Exactly the troubles you have described were the reason why I have changed the text of my guide (first post of this thread).
If you think, that the present text is still confusing, remember the following: It is not easy to create a short, easy to understand and exact description of the integration of the nForce SataRaid drivers, because
1. there are many different nForce chipsets and hardware combinations and
2. NVIDIA has done nothing to make it easy for the users with an nForce SataRaid system.

OKay so here is the deal, I have now wasted 8 CD-r's on attemptiong this, and it just won't work for me! I have a DFI nforce4 sli-DR and I am using a pair of raptors in raid0 I am following these directions to a t and well... l,et me be mroe specific
I start with a clean install of windows (singlew drive)

I install a the nvidia 6.85 nforce driversm anbd the newest display drivers.

I install .net 2.0

I install nlite

I take my legti x sp2 RO disc and I copy its entire contents into an empty folder on the desktop

I start nlite and I select that folder I created with my xp in it, and I click next.

I select "integrate drivers" and " make bootable cd" and click next

on the ntegrate drivers folder I click "insert" and then "single driver"

I browse to this folder exactly "C:\NVIDIA\nForceWin2KXP\6.85\IDE\WinXP\legacy\" and I select the nvatabus.inf file

I ensure that the "textmode driver" is selected and that both of the options below are highlit (both of the nvidia required drivers are being integrated)

I click next and then yes to start the process, it seems to integrate everything and then it says FINISHED! and I click next

I create me bootable disc image, and I give it the volume name of XPPROSP2 (like my disc)

I open alcohol 120% and I brun the image to a new CD-r at 4x (to be sure)

I restart and let my computer boot from the floppy, with EVERYTHING unplugged, outside of the case I have the monitor, power, PS2 keyboard and PS2 mouse plugged in, and inside I have the cpu, ram, video card, two raptors in raid, and DVD burner plugged in, THATS IT!

I have my raid built perfectly fine, I have used it on this board before (before I lost the floppy I used and started this whole mess
So windows setup starts and detects my arrey, I make a partition on it, and format it, it installs the files, restarts into the next stage of setup and I enter all my information, it restarts again and this time displays the windows boot screen for about a half a second, I catch a slight glimpse of the BSOD, and it restarts. I've done this a DOZEN TIMES and tried a bunch oif different options, made 7 or 8 discs now, tried everything, different burning options, I even downloaded a pirated copy of XP and tried using the files from that, still produces the exact same problem. I am using the newest version of my bios from the dfi.com.tw site. WHAT AM I DOING WRONG AHHHH! this is SOOO beyond frustrating.
Going on day three I have been working on this.

Thanks in advanced for the help guys.

Oh by the way, I have tried a bunch of different versions for the raid drivers.

ugh I am going to bed.

Hi,
I already have read about your problem on DFI-Street, where you posted, that you are searching for a driver floppy, that works, and that you don't want to slipstream the nForce SataRaid drivers. Now I can see, that you want to integrate the nForce SataRaid drivers into a bootable XP CD. As you had problems with all drivers and installation methods you tried, I suppose, that you don't have a driver, but a hardware problem.

My first advice is, that you should unplug all hdd's outside your Raptor Raid0 array, before you try to install Windows XP onto your Raid (notice: Within your signature at DFI-Street I saw, that you have additionally 2xMaxtor SATA hdd's).
Then I propose the following:
1. Download the 6.53 chipset driver package (you find the link within the first post of this thread), unzip it and copy the content of the IDE\WinXP folder - except the RAIDTOOL folder - onto an empty floppy disk. Now you will have an nForce SataRaid driver floppy, which works with all nForce4 Raid systems.
2. Take your original XP CD and try to install it by F6 using the floppy drivers you just have created. Take both proposed devices (RAID and SATA).

If the installation fails, you have a real hardware problem. Unless you don't solve it, you won't get XP installed onto your Raid system.

If the install succeeds, you have 2 options: You can either update the nForce SataRaid drivers and install the other nForce chipset drivers at once by running the setup of the 6.85 chipset driver package or create a bootable Windows XP CD with integrated 6.85 drivers by following my guide (see the first post oft this thread).

Please report here about the results of your work.

Good luck!
Fernando

Yes when I posted that I didn't want to slipstream anything because I had never gotten it to work right, but it seems that nlite has improved. Yes I do have two other hard drives, and I have taken them out to try this, the problem I am having is that not one time have I had the windows xp setup to read my floppies, no matter what! Here is what I have plugged in when I try the install

externally:
PS2 mouse
PS2 keyboard
one LCD
power

internally

ram
CPU
video card
dvd drive
two hard drives.

there is nothing wrong with my hardware, I have been running these two drives in raid for months now, I just decided to format and without changing one bios or raid controller option I put my xp disc in and started the process. when I turn off raid and my two hard drives show up I can install windows on either of them just fine, in fact I am running it off one of them now. But when I turn raid back on, and I try windows setup it will either

1. not read my floppy
2. install with your meathod but not work on first boot.

ugh

still nothing

goin on day four I believe.

I just want my computer to work

there is NO hardware problems

I have tried everything.

I don't know what to do

right now I am going to make 100% sure I have the newest bios, and then I am going to start over.

OH MY GOD SUCCESS!

It took four days of headaches (spread out, I wasn't sitting here 24/7) but It works!

the trick: I followed fernando's advice and made a floppy with the raid drivers from the 6.53 nvidia set, and somehow that was the only floppy I ever made that worked! and trust me I tried dozens of them. OKay so Richatard is a happy camper.

Maybe someday down the line I will attempt to create a slipstream disc with full unatended install, and that doesn't require a floppy, but for now my system works, and I am happy as hell.

GOODNIGHT!

and fernando... I want to have your babies.

Congratulations, that you got it!
Within DFI-Street forum I saw some more details about the possible reason of your problem:
So at least it probably was a hardware issue.
I would do everything for you, but I won't do that! (Meat Loaf)

actually it was not a hardware problem. that was an attempt, even after switching the connecter ends, it didn't help, the only thing that worked were those older 6.53 drivers.
thanks!

P.S I feel like I abused this forums considering it has nothing to do with helping me install windows, its for nlite, oh well!

No, you didn't abuse this forum and I am happy that I could help!

CU
Fernando

FAILED x 12+...I have tried the drivers on the CD, the 9.16 drivers, MEI driver collection of the 9.34 version, all with the same result. Windows installs but I can not start it!!! So now I have about 12 coasters (until I found out that my burner can read CD-RW as a boot disk or it would be a whole lot more).

So these are my specs and I am at my wits end. I know the RAID array works and the hardware is fine since I have been able to install XP and Vista without RAID and more importantly with RAID0 Fedora Core 5 installs AND RUNS flawlessly!!!

AMD 64 x2 3800+ socket AM2
MSI K9N Platinum with nForce570, RAID 0,1,0+1,5
2 GB DDR2-800, PC2-6400 RAM (4-4-4-12 @ 2.2V)
ATI Radeon x1600 Pro 512MB PCIe
2 x 250GB Western Digital SATA-II HDD in RAID 0
Plextor 750-a DVD-RW/DL/RAM

Please, this is driving me NUTS - it's been a week already and I still haven't gotten XP up and running. Oh there's more too, when I try to install Vista with RAID enabled it doesn't even install. the little gray bar says Windows is loading files then just as it switches over to the little triple activity bar the system hangs. Doesn't matter if it's 32-bit or 64.

What exactly happened after the installation? Did you get reboot loops or BSOD's?
How did you install XP onto your Raid? Did you use an nLited CD or did use the F6/floppy method?
Did you do a LOW FORMATTING of both hdd's before you created the RAID array (to erase all datas from previous non-Raid tests)?

This is a known issue of Vista and not yet solved by NVIDIA/Microsoft. You can't get Vista installed onto an nForce Raid system by booting off the DVD, but you succeed, if you start Setup from a XP partition (for Vista x86) or from a running XPx64 (for Vista x64).
I have written an installation guide for owners of an nForce SataRaid system. Look here:
http://www.nforcershq.com/forum/1-vt66299....d2327f04623825e

Whithin the "Advanced BIOS Features" of your BIOS you should find the option to change the "Hard Disk Boot Priority". Set your RAID at first position and then try again to set your Raid as bootable.

I'm failing at this too. I'm using the DFI Lanparty Expert, and the Expert driver package from here:

http://us.dfi.com.tw/Support/Download/driv...G=A&SITE=NA

The NF4 RAID F6.zip

It allready has the "missing" files in the right directories.

I made sure that both my mobo was set to ACPI (or whatever the hell it is) and that nlite was. It goes all the way through to the GUI mode, but when it finishes it restarts and then I get a stop error. Currently I get IRQ IS LESS THAN EQUAL.

Background: Motherboard works but the floppy connector does not, ergo I can't use disks.

Should I try another version of Nlite or another Raid package?


Specs: 3500+ Clawhammer
DFI Lanparty UT NF4 SLI-DR Expert
Corsair TwinXP platinum (2gb's)
2 WD250gb Caviars
MSI cheapy Video card.

I'm running into a brick wall with the tutorial in the first post. It's very informative, but I can't see what is going wrong. In my first attempt I slipstreamed drivers from the file motherboard_driver_raid_nvidia_ck804_bootdisk_xp.exe, which is specifically for the Gibayte K8N-series of motherboards (mine is a GAK8N-SLI) and integrated as TEXTMODE in nlite. I got through all stages of installing Windows, but when it reboots for the final time I get the BSOD with the following stop error

"0x0000007B (0xBACC3524, 0xC0000034, 0x00000000, 0x00000000)"

I know that this stop error means an inaccessible boot device.

On my second attempt (which included deleting the partition, creating a new partition and formating to NTFS), I created a new slipstreamed disc, this time using drivers from the package nForce4_x16_6.85_winxp2k_english.exe from the NVIDIA site, drivers taken from the legacy folder. Same story, same stop error.

I know that at least the first stage of the windows install is loading these drivers because I can see it doing so at the bottom of the screen. The only thing I can think of is that Windows is still treating these drivers as unsafe (because they're not digitally signed) and over-writing them with its own default. However, I thought that that was precisely what the method in post#1 was supposed to solve.

Any help would be greatly appreciated.

P.S. This is a new source that already has SP2 integrated (by Microsoft) and I have also integrated the latest NVIDIA Forceware drivers (91.31) for my GeForce 6600 graphics card, as well as slipstreaming hotfixes from this page (v1.0.5a). Could any of that be causing a conflict? I doubt it, but it's always worth mentioning.

P.P.S. I should also point out that I have been able to install windows on this computer before (I'm doing a reformat just to start fresh), but that was using an old Gigabyte drivers package that is no longer available from their site (and I can't find the floppy). The file in question is driver_sata_nf4_boot disk_xp.exe. If anyone has it, I'd be grateful if they could email it to me so I could test it out to see if it will work where the newer package won't.

EDIT: I should also add that this is for a single SATA drive, arranged in a RAID array that is set to spanning and that my nVRaid BIOS version is 4.84

I get the exact same BSOD as zulu9812 with my new nLite CD

I've gotten one of my previous nLite CD's to work but I can't remember what drivers I used on it for my RAID 0 setup

Just to update my progress, I used nlite to delete the SCSI/RAID drivers from a fresh windows source, integrated the drivers from 6.86_nforce_win2kxp_international_whql.exe and burned a new winlite CD. This time, I couldn't even enter setup.

Bugger.

EDIT: Okay, I created a new slipstreamed disc, this time taking out the SCSI?RAID driver and all the IDE drivers. I was able to install Windows but, again, on final reboot I got that **** stop error. I'm at a dead end now, I've tried everything that I can think of.

My suggestions:
1. Check your RAM sticks by doing a memtest (the "IRQ_Not_Less_or_Equal" error mostly is caused by bad RAM or unstable RAM settings).
2. Unplug the floppy cable from your motherboard and disable the FDD Connector within BIOS (this is better than to work with a FDD without function).
3. Recreate a new nLited XP XD, but this time
a ) take the RC8 version of nLite (some users reported about problems with the final version by integrating TEXTMODE drivers) and
b ) integrate the nForce SataRaid drivers I suggested within my guide (post 1 of this thread). Don't take the nForce RAID drivers from the DFI web site you have used (they are very old, although they are presented by DFI this year).

Suggestions:
1. You should always use a clean original OS CD as source, when you start creating an nLited CD.
2. The nForce SataRaid drivers off the 6.85 package LEGACY folder should work for your chipset.
3. Maybe you should try to use the RC8 and not the final version of nLite 1.0 (some users reported about problems with the final version by integrating TEXTMODE drivers).
4. Don't remove any IDE/SCSI drivers by nLite, when you want to integrate the nForce SataRaid drivers.

Try nLite 1.0 RC8 and report here, if you succeed this way.

Okay, I went back to basics. Used my ordinary, original, unslipstreamed Windows XP Pro disc and put my nForce drivers on a floppy. Installed Windows the normal way. No problems whatsoever.

Looks like the problem was caused by nlite not integrating the drivers correctly. Or the drivers can't be integrated correctly. One of the two.

Which driver version did you take? Check the properties of the NVATABUS.SYS or NVRAID.SYS.

This is a very important question.
You would help yourself and a lot of other nLite users, if you would do the following:
Create an nLited XP CD with integrated LEGACY drivers from the 6.85 package by using nLite 1.0 Final. Take the original XP CD as source!
If this method fails, create another CD by using nLite 1.0 RC8.
Please report here about the results.
Thanks!
Fernando

I actually found the nForce CD that came with my 'puter. I've attached the drivers I got from that so you can look at it.

EDIT: can't attach, too big apparently. Can I email it to you?



Both 1.0f and 1.0 rc8 were complete failures, in the same manner described in my first post in this thread (i.e. installation was successful but crashed to BSOD after final reboot, indicating that the nForce drivers were being overwritten).

If you cannot find the driver version number, you may attach the NVATABUS.INF file.

I don't believe that.
Maybe your problems have something to do with the fact, that you don't have a real Raid array. Why did you build a Raid, although you have only 1 hdd?
When your installations have failed, did you try to boot in safe mode by using F8?

Fernando, I'm having the same problem as Zulu. I have 2 WD Caviar SE16's in RAID 0 on the nvidia controller. i've used both nlite 1.0f, and 1.0rc8, and still get the same problem. I have a legitimate copy of XP Pro, with SP1, I slipstream the network install version which has a build of 2180. Normally on machines that get SP2, it's build 2160. Could this be the problem???

Also, Safe mode doesn't work, especially when it restarts the computer after making a choice at the menu...

Yes, you should either take an XP CD with integrated SP2 or you have to integrate SP2 into an original CD before you start integrating the nForce SataRaid drivers.
An integration of the nForce SataRaid drivers into an XP SP1 version does not work.

Hi all

Thanks Fernando for this hell-thread


My mobo is MSI K8N Platinum with nvidia RAID BIOS version 4.84
ACPI set in nLite to auto
I'm getting a Blue screen when running Windows Setup

***STOP: 0x00000024 (0x00A902FE, 0xF7CAA6DC, 0xF7CAA3D8, 0xF7440F81)


*** ntfs.sys - address F7440F81 base at F73F1000, Datestamp 41107eea

I'm pretty sure this is the exact same error I was getting before creating the slipstream CD. Before, when I booted with the Windows XP CD (no service packs) and did the F6 thing, Windows Setup would load to the point where the menu would come up. If I pressed 'R' for repair it would then crash with this blue screen.

The RAID0 array is quite old and has worked ok in the past. But I've been asked to reinstall WinXP. Fortunately the OS is on a seperate PATA drive. I'm starting to think maybe my problem is different and it's the data on the hard drives thats causing the crashes, or maybe when I initially set up this PC the drivers I used from the included CD's were older nForce drivers that worked.... it doesn't bluescreen when I leave the 2 SATA drives unplugged

HELP!

Now, this is interesting. As I said, I can install Windows using an original, non-slipstreamed disc and nForce drivers on a floppy. This lead me to think that nlite was not integrating the nForce drivers correctly. When I created a slipstreamed disc (a hotfix pack, .NET 2.0, Acrobat Reader and Open Office 2.03, with WMP, IE, Messenger, Windows Messenger, MSN Explorer, System Restore, Automatic Updates, Imapi, Fax Services, Tour, Help, System Error Reporting, Event Dump Log, Security Center and Service Pack Messages all removed - NO DRIVERS INTEGRATED) and tried to use that in conjunction with my floppy, then I would run into problems.

I would be able to boot from CD into setup mode, press f6 to say that I wanted to install 3rd party SCSI/RAID drivers, be able to load the nRAID Controller and the nForce Storage Controller (they're not called exactly that, but something similar) and Windows would then start copying files (this is all before the GUI part of windows install). The installation would then tell me that it couldn't load these nVidia drivers, even if I hit Enter to retry.

This leads me to think that there is something in the nlite slipstreaming process which is interfering with installing nForce RAID drivers, no matter of they're integrated or on a floppy.

As zulu9812 said, I've also tried my nLite CD without any integrated raid drivers and I got the same results as him where it kept saying "Setup cannot copy the file:". I've wasted almost 10 CD's trying to fix the problem and I've had no success so far

You obviously have a problem with your hdd's and/or with different boot sectors (MBR's).
Check your hdd's by using Checkdisk and look into your BIOS for the Hard Disk Boot Priority (there you can choose, from which hdd you want to boot, that is something else as the Boot Drive Sequence). Which of your hdd's is drive C? Do you have more than 1 MBR?
When you want to install XP onto a non-Raid-hdd, you should neither hit F6 nor integrate any nForce SataRaid drivers. Just install XP and - after having done it - install the nForce chipset driver package suitable for your chipset by executing the SETUP.EXE. Then XP will see your Raid partitions.

1. You can't do the F6/floppy method with new nForce SataRaid drivers (from a chipset driver package 6.65 or higher). For F6 nForce SataRaid driver installation you should take the 6.53 package.
2. The nForce SataRaid driver integration method by using nLite or CD Creator is proved by thousands of users with different systems. It works for all of them and will work for you too. Maybe your burner is not OK or your burning speed was too high.

You obviously have a CD/CD Burner problem. Check your CD Burner or burn a new CD with lower speed.

@ all nLite 1.0 Final users with problems integrating the nForce SataRaid drivers:

If you get a message like "Setup can't find/copy file xyz", this might be caused by an issue of the Final version of nLite 1.0.
For details look here: http://www.msfn.org/board/Nlite-Final-TEXTMODE-Dr-t77510.html
My suggestion: Take nLite 1.0 RC8 until Nuhi has fixed the problem.

Hi Fernando, thanks heaps for your reply.

I wanted to run Windows setup & install the RAID drivers via F6 so I could do a chkdsk on the RAID0 array in question. The C: drive is a non-RAID IDE drive (PATA) and works fine by itself. The RAID0 drives are simply a large storage area (that I can't lose )

I tried to create your integrated driver CD simply to see if I could run chkdsk on the RAID0 array

When XP is installed and the drivers installed via Setup in Windows, the computer does the Bluscreen/restart thing


Many thanks


Vinny

There is no need to install Windows XP, if you want to check the integrity of your hdd's. DOS sees all your disks.
Can you boot in safe mode? If yes, uninstall the NVIDIA drivers again und reinstall the 6.53 driver package (just to allow XP to see the RAID array).

FYI Version 6.86 is out for the nForce4 AMD

Thanks for your notice.
I know about the new nForce driver package, but I have not tested it yet.
Furthermore the chipset driver package 9.34 and the nForce package for Vista Beta2 do contain newer IDE drivers (v. 667), which are compatible to all nForce4 chipsets too.

6.86 didn't work for me (endless reboots), however 6.70 is working great. My mainboard is Gigabyte K8NXP-SLI which uses nforce4 SLI chipset with nvraid bios 4.84.

Successful with MCE 2005 using nLite 1.0 RC8 for ASUS A8N-SLI Premium into nvraid.

Thanks to all who built up this thread.

--Greg

OK, I'm not sure wot you mean here. How does DOS read a RAID0 array??

Maybe you're talking about running a diagnostic tool to check the drives?? My understanding is that any low-level tests aren't going to bring back the data & the only way is to get something to diagnose the file system and I don't know any other way to do this other than to load the appropriate drivers.



XP won't boot at all, Safe Mode or not, if the RAID drives in question are connected

Last night I tried booting with another RAID0 set and it was fine


THANKS AGAIN FERNANDO
much appreciated

I wasn't using any package from the nvidia site. I used the package from the motherboard site.



No. My burner is fine, as proved by my next point.



I considered this in light of what you said to me. I copied my original Windows disc to my computer, recreated it as a bootable ISO and burned that disc. The same scenario repeated. To summarise so far:

1. If I integrate nForce drivers via nlite to make a slipstreamed Windows XP disc, Windows setup will complete, but crash to BSOD after final reboot, and continue to crash to BSOD every boot thereafter. This implies that the initial installation is using the nForce drivers, but that they are being overwritten with 'safe' windows drivers during the GUI part of the install.

2. If I put those nForce drivers on a floppy and install the drivers manually in conjunction with an original Windows CD by pressing f6 and then specifying the location of the drivers, I get a successful Windows installation and subsequent usage, with no Device Manager issues.

3. If I use the method in #2, but replace the original Windows CD with a 1:1 copy I burned myself, I get a successful windows installation as in #2. This implies no problem with my CD burning capabilities.

4. If I use the method in #2, but replace the original Windows CD with one I slipstreamed using nlite, Windows setup will not load the drivers from the floppy. This implies a problem created by the slipstreaming process.

I feel very secure in saying that it is not a problem at my end. Simply put, if I don't slipstream I can install the drivers and thus can install Windows. If I do slipstream, I can't.

I've managed to fix my problem now, I used the nVidia chipset driver disk from Asus's site which was version 6.82 and copied the contents for the new nLite 1.0.1 beta and it works fine!

Hi,
i have a Gigabyte GA-K8N Pro-SLI , nforce4 sli and have done everything in the guide. When i installed everything and finished finalising windows and reboots, it goes to the windows loading sign and then shows the blue screen with error message:
0x0000007B
please help

Edit:
dont worry about it.. i did what ferando told zulu9812 to do. And i worked! After 3 days of suffering! WOOT WOOT
i used the nLite 1.0 RC8 and used 6.85 even though my version is 4.81
thanks Fernando 1!

OK, now I'm convinced it's a problem with me hard drives

On another NF4 machine (Albatron K8SLI) runing RAID BIOS 4.81 it bluescreens on WinXP bootup & restarts
This PC's OS runs off another RAID0 array
If I connect the problematic RAID0 array while Windows is running, it also crashes

Does anyone have any ideas as to how I might be able to save the data that's on these drives ??


Cheers


Vinny

I hope, that you didn't always have used nLite 1.0 Final. This version had an issue regarding the TEXTMODE driver integration (see some postings above).
Did you get the same results with nLite 1.0 RC8 or nLite 1.0.1 Final?

If you can get acces to your datas, you should burn a CD or a DVD with all your important files.

I can't access the data ! That's the problem ! XP just bluescreens when I connect the drives

Have you even read my posts? ah whats the use
.

I read every post, although there are a lot of them from different users.

Now back to your question:
Before you decide to create a RAID, you should know, that you can't save datas from a broken or corrupt RAID0 array. That is the wellknown risk with RAID0.
As I understood your posts, you were not able at all to install an OS onto your corrupt RAID0 array. Why do you want to save datas from a fresh install, which you never got running?

No no no Fernando Obviously you can't read
I never said I installed an OS on the RAID0 array *sigh*

The 400GB RAID0 array has no OS, is full of data only, a seperate PATA hard drive has the OS. This is the third time I've mentioned that fact right there!

I know the risks with RAID0, however I believe there is software out there that could fix my problem. Has anyone used R-Studio to deal with a RAID0 array?

I can read, but I don't understand you.
What has your problem to do with this thread? I am not a data recovery expert and I doubt, that such a person will read your posts within this thread.

Yes yes, good advice, thanks, I'll post elsewhere. Cheers

Fernando 1,

I'm about to attempt an ISO for a nForce 590 raid setup, but I'd just like to clarify one thing based on some confusion from reading different threads:

Should the contents of the $OEM$\$$\OemDir folder contain ONLY inf files from the SATARAID folder, or every file from that folder, or just specific files?

I ask because I dont plan on using nLite. I've never used it and I don't want to start (nothing against it I just like knowing what happens under the hood so I do it all manually). I've included three other massstorage drivers manually and I wanted to do the same for the nForce 590 RAID.

The confusion on the contents of the OemDir folder comes from a different thread that suggests the only thing that should go into the OemDir folder is files other than .inf .sys or .cat. In other words, only .dll .vxd .cpl or other files should go in OemDir.

Does that hold true in the case of nForce raid drivers or in light of the [OemInfFiles] section which was not part of the do-it-yourself massstorage guide.

I have some important news for the unworking gals...
Since I got the RAID hdds...yey finally...it seems that my VIA SATA 64bit integration isn't working properly, no hdds detected. I fixed it manually and will put to next nlite, so that may fix some others too, who knows.

I'm talking here about 64bit, 32bit worked great for me.

Seems to be a good reason to publish one more stable 1.0.x release before going alpha, or?
Maybe some other fixes could be included too into a possible 1.0.2...