problem is, i can't flash bios (and my version doesn't support that), it's not my laptop and I don't want to risk someone else property... I had exactly the problem mentioned in your post, but I figured out by installing SATA_IDE /floppy both disk1 and disk2 (through external floppy). Then it worked, so I went through whole instalation (without doing that I couldn't even start installing because I'd get BSOD [screenshot])

So now im after installation, but everytime like 1second after the Windows Laoding screen appear my pc throw up BSOD and reset immidiatly (like half second after)

I downloaded chipset drivers from here MSI official web (as they are for my laptop, xp of course).


Thanks for help so far.


EDIT:
The BSOD says:
STOP 0x0000007B (0xBACCF524, 0xC0000034, 0x00000000, 0x00000000)

What do you mean with "both disk1 and disk2"? Did you integrate 2 different drivers?
If you have an nForce AHCI system, you should just integrate the SATA_IDE driver folder of a suitable nForce driver package. I recommend to integrate this driver. It is newer and better than that one from MSI home page.

I cant download your file:Invalid File. This error has been forwarded to MediaFire's development team.
Can you please reupload it?

I didnt exactly 'integrate' , i used external floppy to add drivers during installation by pressing F6. And in folder SATA_IDE/FLOPPY there are 2 folders - disk1 and disk2

The file is not invalid. I just successfully downloaded it from MediaFire.

Ok, the reason is the limited floppy size of 1,4 MB.
You should integrate the driver into the OS CD. That is always the better choice.

Thanks, after all the effort I finally made it running with your file. Thanks again. You've done great job, it took me about 10 hours to make it work, but thanks to you at least it do now.
Thanks again, have a nice day!

You are welcome.
It makes me happy, that I was able to help you.

If its in-box then i shouldn't bother trying to integrate it... Do you have any other ideas? I really don't want to change my hardware but its looking like my only option.

Thx,
Zak

I have them extracted, but you cannot use them from scratch with Windows XP, because the TXTSETUP.OEM file is missing.

Assuming, that you have already flashed the latest mainboard BIOS version, I see only the way to break the RAID and to use both SSD's as separate drives. Once NVIDIA has released an SSD compatible nForce RAID driver, you can recreate the RAID.

:(

So I got the bright idea of reformatting today.
I busted out my XP SP3 + RAID CD, which I used in the past, and I got nothing but fail.

I'm dealing with 3 drives in RAID 0 on an MSI P6N SLI Platinum (not V2) - an nForce 650i SLI board.

The first attempts resulted in the ol' 0x0000007B BSOD after the initial loading of drivers and such ("Setup is starting Windows" I think).
So I went about clearing my array and breaking it and rebuilding it and trying again. Still failed.

I played around a bit with Acronis to see if I could just restore my backup image, but since it would have taken ages, I figured I would continue working on the issue.

I then built another CD based on the existing CD - I just added the latest drivers I could grab from MSI's site.
I got past the first hurdle, and XP was able to see and partition and format my drive.

It then failed on the next reboot with some error about a bad disk configuration.
I checked out the boot.ini file (Acronis was able to see my array and partition, read from it, and write to it) and noticed some weirdness, which I attempted to fix. Didn't help.
I rebuilt my array again, and ran the installer from this new (XP + SP3 + old drivers + new drivers) CD again.

This time I got as far as setting up language options and entering the serial and such.
On the next reboot (what should have been the first real boot into Windows) I got a quick blue screen followed by a soft reboot.

I'm currently trying to restore my backup image with Acronis, but with the way things have been going today, I don't have high hopes.

I AM using a SATA optical drive, as it's the only optical drive I have.
I CAN'T set individual SATA ports to IDE/RAID mode (maybe I could in a previous BIOS version for my board?).

Any ideas? I'm currently hunting down a "fresh" XP + SP3 disc, and I'll drop the drivers recommended here on it and try again (though if the restore from the backup works, I may just quit while I'm ahead).
Does anyone know the keyboard shortcuts to enable hidden options in MSI BIOSs? I believe it was something like alt+F2, shift+F4. I dunno. Maybe that reveals the option to set SATA ports to RAID/IDE individually.

I'd hate to have to hunt down an IDE drive, but I may have to. (Curious - why does a SATA optical drive in RAID mode cause issues?)
I'll also run deep scans on my hard drives (they passed the quick scans), or try various combinations of 2 drives in RAID 0 (with the 3rd drive disconnected).

What really bothers me is that I used this disc before and everything went fine.

@ sexconker:
1. How much RAM are you using? If more than 3GB, remove 1-2 RAM sticks just during the OS installation.
2. Have you tried to connect your CD/DVD drive with the eSATA port of your mainboard while installing the OS? Maybe this will work, because the eSATA port is using a SILICON IMAGE and no NVIDIA nForce SATA Controller, but you have to change the boot device order within the BIOS.
By the way: Not all SATA connected optical drives do have problems with a RAID or AHCI enabled SATA Controller.

Thanks for the reply.

Acronis worked and I'm back on the afflicted machine with no problems (with yesterday's image).

2 GB of RAM.
I've got the P6N SLI-Fi, not the SLI Platinum I guess (so no eSata and no second SATA controller).
This is the optical drive I used to install the OS initially (onto my RAID array).

I'll try with the clean XP + XP3 retail disc, nLite the drivers (from here) onto it, and see what happens.
Now that I know Acronis works (never actually tested the restore before).

Perhaps this weekend / the next 3-day weekend. This was way too much drama for a Monday.

I'll update here with whatever happens.

Well I tried again yesterday.

Used the clean XP SP3 image, dumped the 10, whatever drivers (from the nForce 15.25 package) into it with nLite (as well as an update pack and a bunch of tweaks).

Worked like a charm.

@ sexconker:
Thanks for your feedback. It's fine, that you succeeded now.

Have fun with Windows XP running on your nForce RAID0 array!
Fernando

Can the txtsetup file be added into the win7 drivers? Or is modifying the driver a fruitless endeavor?

Vista and Win7 don't need and don't use the TXTSETUP.OEM file.

Sorry i didn't make that very clear. Are any parts of the win7 driver compatible or interchangeable with the XP driver?

The Win7 in-box nForce drivers may work with Vista, but I doubt, that they will be usable with Windows XP.

is it possible to integrate all textmode drivers (all nvidia and all intel) so as to have only one XP install CD?

You can integrate more than 1 textmode driver, but I do not recommend to integrate different textmode drivers from the same chipset vendor.
Reason:
The real drivers are the files with the extension ".SYS". Windows XP /32/64bit) Setup will only detect the SATA hdd's, which are set to RAID or AHCI mode, if the suitable textmode driver SYS file is present within the i386/AMD64 directory of the XP CD.
Problem: The chipset vendors (in your case: Intel and NVIDIA) have created and published many different textmode driver versions with completely different functions and compatibilities, but with the same names.
Examples: All 32/64bit Intel SATA drivers are named IASTOR.SYS, NVIDIA's 32bit SATA drivers are named NVATABUS.SYS/NVATA.SYS or NVGTS.SYS.
Bad consequence: If you integrate different Intel or NVIDIA textmode drivers into the same XP CD (32/64bit), the final OS installation may fail, because the correct SATA driver (SYS file) has been overwritten during the driver integration processing.

First up: thanks Fernando1 for your hard work and dedication on this for 86 pages!! Rather than trawl through that lot, I'll post my question here at the end!

I'm trying to put together a sysprep image that supports the diverse hardware in my organization. I've successfully integrated drivers from Intel, JMicron and Silicon Image but I'm having trouble with the nForce kit. We have a small number of systems based on nForce 1, 2, 3, 4 and 410/430, so I am using "Fernandos XP 32bit nForce LEGACY Remix Pack v5.5a" as it seems to support them all. Unfortunately, my 410/430 based system (an Asus A8N-VM CSM motherboard with SATA RAID 5) crashes with a BSOD 0x07B error on first boot.

I have three folders in my image's C:\Drivers\Storage folder:
nVidia1 (which contains the contents of the "sataraid" folder from the driver pack)
nVidia2 (files from the "sata_ide" folder)
nVidia3 (files from the "legacy" folder)

(The reason the folders are numbered like this is to get the sysprep process to try them in order (newest to oldest) and use the first driver it finds that works)

My sysprep.inf [SysprepMassStorage] section contains the following lines:

(There are other lines to support other mass storage controllers, I've just included the relevant ones for the 410/430)

First of all, am I using the correct drivers for what I want to accomplish?
Second, am I doing this the right way?

Thanks in advance for any help/guidance/ideas you can give me!!

@ beardy:
Welcome at MSFN Forums!

Here is my comment:
1. If you want to use 1 single driverpack for nForce2, nForce3, nForce4 and nForce 430/410 (MCP51) chipset mainboards, you have chosen the best suitable one. The included nForce IDE drivers v6.99 will fully support them all.
2. It is not a good idea to integrate all 3 IDE driver folders (SATARAID, SATA_IDE and LEGACY). My suggestion: Just integrate the LEGACY driver folder. This way nearly all possible hdd configurations (even PATA and PataRAID Controllers) will be supported.
3. The ASUS A8N-VM CSM motherboard is supporting RAID5, but you will need an appropriate mainboard BIOS and nVRAID BIOS version.

Good luck!
Fernando

Hi all - new member of the forum - found Fernando's post on NVRAID installs, read through many of the pages, and it looks fantastic. Couldn't find my solution exactly, though.

Before I kill data on my drives, I thought I'd ask for some advice. Though I've mastered plenty of weird XP quirks, this one's slightly beyond me.

System:
Asus nForce5 590SLI (M2N32SLI Dlx)
GeForce 8800GT
2x 74GB raptors (RAID 1) (Edit: fixed RAID type)
2x 160G Hitachis (RAID 1) (Edit: fixed RAID type)
1x 500G Seagate
1x 250G WD (fresh drive)

I was having some BSOD errors yesterday, so decided to upgrade drivers in case that was the problem. Went to NV nForce 15.25, and it killed the nV RAID. Drives are still there, but during POST, the pc hangs at "Detecting Array" if I try RAID-enabling the Raptors in BIOS. If I leave them as JBOD, but RAID-0 the Hitachis, POST says "Healthy" array, but WinXP Pro doesn't see them at all.

I've re-installed XPpro on the 250G, but didn't do the F6-install for drivers, just trying to see if all my data was on the HDDs. It is.

Now, the system's booting off one of the Raptors, but only in JBOD mode. DevMgr says the NVRaid controller's working properly, Ver 10.3.0.46. But no RAIDs visible.

Any ideas? I'm copying all data to the SG & WD drives in case I have to do a wipe, but I really, really want to avoid that.
Or, if I drop the Raptors to JBOD, and do a fresh XP install on one of them, then "rebuild" the array, can I tell it which directories to mirror from each drive? Or would I just be SOL?

TIA,
Jim/ByTor

@ Bytor:

Welcome at MSFN Forums!

Before I can give you any advice, I need some additional informations:
1. Before you installed Windows XP onto your single WD hdd, which OS were you running?
2. Do you have any additional OS installed?
3. On which hard disk drive is the boot sector (MBR)?
4. Is it possible, that you got more than 1 MBR within your system?
5. Which order did you set at the BIOS option "HARD DISK BOOT PRIORITY"?
6. Did you really create 2 RAID0 (=striped) arrays? I ask this, because you wrote about a "mirror", which would be a RAID1 array.

See embedded answers... I really appreciate the help.

I'm about ready to trash one of the Raptors with a LLFormat, and just build a new RAID array from the other drive. This may be the least painful solution, unless you've got some other ideas.

One additional note - I'm now able to see the Hitachis in RAID-1 within Windows - functioning normally. Registered the nvraidservice thru the .bat file, and that made them visible. Thought I'd try re-enabling RAID on the Raptors, and the system hangs again at "Detecting Array." I haven't gone back to clear CMOS yet, because I don't have the willpower to spend a few hours on the PC right now - that'll be a weekend job. Posting this now from the wife's lappy.

The Hitachi-Problem seems to be solved, so let`s look at your Raptors.

You got 2 of them, they were figured as RAID-1, so both HDDs have the full data on it.
If one of the HDDs crashes you`re able to REBUILD the RAID-0 with another spare HDD.

I would give this a try: Use your "1x 250G WD (fresh drive)" as spare drive and try to
rebuild the (former Raptor-) RAID-1. Try this with both Raptors to see if one causes the failure.

You misunderstood my question.
The "HARD DISK BOOT PRIORITY" is the order of the bootable hard disk drives and has nothing to do with the BIOS settings regarding the order of the bootable storage devices (CD/DVD>HDD>Floppy etc).
Since you have more than 1 hard disk drive (each RAID array is shown as 1 hdd) within your system, you have to give an information to the BIOS, which one of them should be booted at first.

I can set the new WD to be first priority, and boot into the new install of windows ok. I may have to reinstall that version and F6 the RAID drivers into it, unless there's a way to enable RAID w/o a new install.

Also, when I put even 1 of the Raptors as "RAID enabled" in BIOS, POST still hangs at "Detecting Array..."

The necessity of doing a fresh install of the OS depends on
a ) the SATA Mode situation during the previous OS installation (a fresh install is not necessary, if the RAID Mode was enabled) and
b ) the place, where the OS has been previously installed (no fresh OS install is needed, if the OS has been installed outside the RAID).

At first step you should enter the RAID BIOS Utility and check, if the RAID is shown as "healthy". As long as the BIOS does not detect the RAID correctly, you will not be able to get anything installed onto it.

If I RAID-enable even 1 of the 2 Raptors in the Setup utility, the boot sequence doesn't even get to the point where I can F10 to the RAID utility.
It will show the SIL driver (unused in my case), then go to "Detecting Array" and not even show 'healthy' or 'damaged' or 'failed.' It just hangs.

With neither of the Raptors RAID-enabled, BIOS only detects the Hitachi array, and that's listed as 'healthy.' Then I can boot into XPPro off either of the Raptors as C: (which functions identically to how the C:-RAID array used to), or off the new WD as C:. In either of those cases, both Raptors show up as discrete drives.

I'm really banging my head against the wall here.

@ Bytor:

It seems, that you got some problems due to the change of the RAID settings and the installation of Windows XP onto different drives resp. RAID arrays without checking the "HARD DISK BOOT PRIORITY" settings.
According to what you have reported, you obviously have installed Windows XP 2 times onto your system, 1 onto the Raptor hdd or RAID array and recently additionally onto the single WD drive.
I suspect, that you now have 2 boot sectors with 2 MBR's within your system. Since this is never a good idea, I wrote about the importance of the "HARD DISK BOOT PRIORITY" BIOS settings. After any change of the hdd and RAID configuration you should have verified, that the hdd/RAID array, where your MBR was set, is still at the first place of the HARD DISK BOOT PRIORITY settings. Otherwise you will get a new MBR within the hdd/RAID, which was just there by mischance.
Another possible issue: Each change of the RAID settings (enabling/disabling the RAID Mode and switching the RAID Array from RAID0 to RAID1 or vice versa) has a big impact on the usually unreadable "track 0" of the affected hdd(s), especially if there is a boot sector on it.
Since you obviously are able to boot into Windows XP off 1 single Raptor hdd set in non-RAID mode, you will not be able anymore to do it after having recreated the Raptor RAID array.
You may try to solve the problem by erasing the MBR off the Raptor hdd and by reparing the "track 0" entries, but this will be difficult and dangerous for your current datas. The better way will be a low level format of both Raptor hdd's and a clean recreation of the array without enabling the boot option.
The MBR of your non-RAID WD hdd should be the only one within your system.

EDIT:
Since your problem has nothing to do with the topic of this thread, you may search for further help somewhere else, were you probably will find a better support regarding the solution of your special RAID, MBR and Track 0 problems.

Good luck!
Fernando

Yep, thanks for the info. The reason I'd posted here to begin with was I saw the excellent info about the various NV drivers and the integration into the 5xx pkgs, and thought there might be some relevance to my situation. I do apologize for the thread hijack.

@ Bytor:

By the way: As long as you don't install Windows XP onto a RAID device, you don't need to integrate any RAID driver into the OS CD. Once the OS is up, you can run the installer (SETUP.EXE) of the suitable nForce chipset driver package. You will find it within the first post of this thread.

If you have any further question regarding the nForce SATARAID driver, please post it here.

Best wishes!
Fernando

@ all users with an nForce RAID or AHCI system:

Today I have updated my guide (first post) again.

Changelog:
- modified: nForce IDE drivers v9.99.09 mod by Fernando (now enhanced AHCI support)
- updated: "NF4-5 non-AHCI WHQL Packs" (32/64bit)
- updated: "Special WHQL Performance Packs" (32/64bit)
- updated: "MCP73 WHQL Driverpacks" (32/64bit)
- updated: "NF4-7 Performance Packs" (32/64bit)

Any feedback is much appreciated.

By the way:
It will not take long and my guide will have more than 1 million views - unbelievable for me. When I started this thread in June 2005, I did not expect, that my guide will be interesting for so many nForce users for such a long time.

Have fun!
Fernando

Hi All,

New member here and of course I have a problem with an nVidia nForce raid system.

I have a Dell XPS720 with 2x320GB drives in Raid 0 which contains my OS, Win Xp Pro. Unfortunately, a power cut resulted in being locked out of Windows on reboot. I tried safe mode etc to no avail. I then tried a repair using my Dell OS disk and got hung up in the infinite boot cycle with the Not Digitally Signed problem. So now I guess I have a corrupted version of WinXp on my c: drive. I have successfully installed a new Pata IDE drive and loaded the OS on that and all my original files etc are still there but it would be great if I could repair/recover my original system without having to re-install everything.

I think that I have implemented the nLite procedure correctly as specified in the excellent work by Fernando 1. I have tried both the legacy drivers provided by Fernando 1 and also the WinXP IDE SataRAID Driver (v6.91) "WHQL" directly from nVidia. In both cases, I get as far as accepting the Windows license agreement (F8) and then I get the BSOD with a message regarding IRLQ_NOT_LESS_OR_EQUAL.

I am unsure if I need to physically copy any files (ie outside of nLite) to the folder in which I placed the copy of my Dell OS disk. Or maybe I don't have the correct drivers for my XPS 720 system?

Any help really appreciated,

Many thanks.

@ Seanmick:
Welcome at MSFN Forums!

Questions:
1. Which nForce chipset does your Dell XPS720 have?
2. Did you save the exact BSOD error message? If you couldn't read it, hit F8 while booting/rebooting and choose the "Don't reboot at system failure" option.

Hi Fernando 1,

Many thanks for the prompt reply. I have an update:

1) I re-made an OS CD and included the sata_ide sub-folder as PnP as suggested and this enabled me to get to the install procedure after the license agreement page.

2) The system went into chkdsk and told me the "volume was dirty" and proceded to run chkdsk which reported that it was recovering orphaned files. These included files like system, sam, security etc.

3) Once chkdsk completed, the system then allowed me to enter setup mode. It tells me that it has already attempted an upgrade (done when I first had the problem) and so I allowed it to retry this repair.

4) This proceeds successfully and copies the files to the c: drive.

5) On re-boot, the Raid array is reported as healthy, I can enter its setup mode from the BIOS, the array is 0, helathy, stripe is reported etc. the black Windows Welcome screen then appears, then goes blank as normal prior to the blue WinXp logon screen, the keyboard is energised, the mouse pointer appears briefly but then the system goes into reset mode again and loops attempting to restart Windows.

Based on this behaviour, is it possible that I have loaded the incorrect drivers when I made the OS disk or is it a just that the damage is such that the XP repair will not work? The drivers I integrated were downloaded from nVidia, the enclosed Readme file is as follows:

This WinXP nForce (C55/MCP55) driver package consists of the following components:

Ethernet Driver (v60.24) "WHQL"
Network Management Tools (v60.26)
SMBus Driver (v4.57) "WHQL"
Installer (v5.17)
WinXP IDE SataRAID Driver (v6.91) "WHQL"
WinXP IDE SataIDE Driver (v6.91) "WHQL"
WinXP RAIDTOOL Application (v6.91) "Sedona"

I integrated the SataRAID (textmode) and the SataIDE drivers (PnP).

I can boot the system to XP normally from the pata drive, will I get full details on the actual nForce chipset under System Information?

Many thanks again for all your help, very much appreciated.

Regards.

@ Seanmick:

1. Try to get the exact BSOD error message, when the reboot loop is starting, because this may give you a tip where the issue is coming from. You will get the message, if you hit F8 while rebooting and choose the "Don't reboot at system failure" option.
2. I am not sure, if the drivers you used are the "suitable" ones for the nForce chipset of your mainboard.
If you can run any Windows OS, please open the Device Manager and look into the "IDE ATA/ATAPI Controllers" and "Storage Controllers" resp. "SCSI and RAID Controllers" sections for the exact names of the listed SATA and RAID Controllers. If possible, give me the HardwareID's of them (right click onto the Controller > "Properties" > "Details" > "Property" > "HardwareID's").
3. Have you ever tried to integrate just the SATARAID driver folder without additionally doing that with the SATA_IDE driver folder?

Hi Fernando 1,

Again, many thanks for the help. I am beginning to think that I should do a clean install but I am concerned that I will have the same issues even in this case since it might not correctly load the sataraid drivers on a complete reinstall either.

1) I tried using F8 to prevent the system reboot on failure but I do not get an error message and the system loops trying to restart windows.

2) I have started WinXp using the my IDE drive with the Sata Raid array active and I get the following information:

IDE/ATA/ATAPI controller
Driver: Microsoft atapi.sys/stopprop.dll.
Hardware Id: 10de-036e / Primary_IDE_Channel / *PnP0600

SCSI and Raid Controllers:

nVidia nForce 590/570/550 Serial ATA Controller 5.10.2600.0692
Driver: nVidia nvatabus.sys/idecoi.dll/idecoiins.dll
Hardware Id:
PCI\VEN_10DE&DEV_37F&SUBSYS_01E11028&Rev_A2 plus three others

nVidia nForce Raid Class Controller 5.10.2600.0692
Driver: nVidia nvraid.sys/nvraidco.dll/nvraiins.dll
Hardware Id:
ACPI\NVRAIDBUS / *NVRAIDBUS

3) The file information on the nVidia drivers I loaded with nLite tells me that they are version 5.10.2600.0691. However, I do not see either idecoiins.dll or nvraiins.dll in either directory, is this an issue?

4) I am still using 4 GB of RAM, I would prefer not to remove them if possible. Would this cause the type of behaviour I am experiencing?

Is is really possible that I would not be able to use my Dell OS disk to safely do a complete reinstall? By the way, if I am forced to implement a complete reinstall, I will not most likely not reactivate the RAID 0 array and I will use the disks as two separate sata disks, do you see any problems with this?

Many many thanks for all your help,

Regards,

You have to hit F8 while rebooting at the point where you get the system loops. Then you will get a message, because the reboots will stop.
Thanks for the details.
So you have an MCP55 chipset mainboard and will be able to use a lot of different nForce chipset driverpacks.
If you want the latest and best nForce drivers for your mainboard, you may look into the start post of this thread. For your system I recommend to take either the "NF4-5 non-AHCI WHQL Driverpack" (most stable drivers) or the "Special WHQL Performance Pack for XP" (stable with best performance).
If you are going to reinstall Windows XP onto your nForce RAID array, you should only integrate the SATARAID and not the SATA_IDE driver folder.
No, these are intern co-installer files, which are used by the OS. The original files are named IDECOI.DLL and NVRAIDCO.DLL.
Yes, it is possible, that something is written into your memory, but outside the 3 GB, which can be read by 32bit Operating Systems. The problem only can occur during the OS installation itself. Once the OS is up and running, 4 GB or even more is no problem for the 32bit OS (it cannot use the full memory size, but it has no negative impact on the system stability).
I don't know. Usually this should work, but I do not recommend to do it, because the drivers of the Dell OS CD most likely are outdated and not the best for your system.
No, I don't see any problem with the OS installation, but you certainly will be disappointed about the performance of your system when running in IDE instead of RAID mode.

i can't find out what mcp is for the nvidia 650i sli motherboards, i see it as the 430 mcp, but what does that mean? I'm trying to figure out if it has a mcp## format and if so, what it is.? =O

issue-
So basically xp32 pro is trying to be installed from scratch, SS-ed the nvidia drivers (10.3.0.46) pictured below** , onto a sp2 disc, because previously without any SS the drive was not detected. Now the drive seemingly detected, the installation proceeded; afterward on reboot after the gui setup there is a BSOD error screen which flashes by too quickly to catch an error code (restarts). The configuration is just a single Sata drive, so no raid. Afterwards, it was found out from the dell website (computer is an xps 630i) some other driver listed under 'mediashield' that seem related. Do you think this could be the problem? that the other driver (first one shown below) should be integrated instead?



any assistance is appreciated, thanks

**(not all of the drivers pictured were slipstreamed, just the last one, the picture is to demonstrate the differences between the drivers)

The nForce 650i chipset belongs to the MCP55 series.
I recommend to integrate just the SATARAID drivers v9.99.09 (download link). The nForce IDE drivers v10.3.0.46 are not designed for being used with non-AHCI capable RAID systems. Do not additionally take the SATA_IDE driver folder.

Good luck!
Fernando

this worked, thanks!!

Hi Fernando 1,

Just a quick email to say thanks for the help. I had to do a full re-install since the XP repair didn't work, too much damage I think. The modified OS disk with the drivers added worked fine so I'm now rebuilding my system.

Regards and thanks again,

Seanmick.

@ kurmud and Seanmick:
You are welcome! Fine, that you succeeded at least and that I was able to help you.

@ all:
This thread has now more than 1 million views - I am overwhelmed!
When I started it in July 2005, I did not expect, that it will be that popular.

Regards
Fernando

Hi Fernando, i wanna ask

I want to make xp pro 32 bit and integrate all driver intel, amd, and also nForce using nlite. i litte confuse with nForce driver. my question is which nForce driver should i added into nlite? because there is so many driver for chipset in your first post. your suggestion is just integrate nForce Legacy driver (32bit nForce LEGACY drivers v6.99 built by Fernando) is it right? is it include all driver and chipset for nForce SATA RAID, SATA IDE and Legacy? or i should add all of them?

here it is my preset, intel, amd, and nForce is it right or not?



thank you

zilan

@ zilan:
Welcome at MSFN Forums!
No, the v6.99 drivers will not work with all actual AHCI supporting nForce chipsets (MCP65 and up).
I do not recommend to do that, because the previously integrated textmode drivers, which have to be present within the i386 directory of the XP CD, might be overwritten this way.
If you want to create a Windows XP CD, which can be used with nearly all available AHCI/RAID systems, you should not do it by using a tool like nLite. In this case I recommend to take the Mass Storage package and use the DriverPacks integration method by using DP Base. For further details you may look here.
This will not work as you have thought.
It is not a good idea to integrate different textmode driver versions of the same vendor by using a tool like nLite. Since the Intel textmode drivers v5.5.1035, v7.8.0.1012 and v8.9.0.1023 all do contain the driver named IASTOR.SYS, only the last integrated one will be usable during XP Setup. All the other ones will be overwritten.

Links down (or at least the one I tried is)

32bit nForce IDE drivers v9.99.09 mod by Fernando (download link) - not working

I am sorry, but the hoster MediaFire is temporarily down.
Here is an alternative link to the requested driver: http://www.german-winlite.de/wbb/index.php...721ea11b301c0c7

Hi!

Upfront, my apologies if my concern has already being addressed. I tried several searches on the 59 pages of replies on this topic, but did not find enlightenment...

I am building a new system with old components, ASUS A8N-E with Athlon64 3700+, which uses NVIDIA nForce4 Ultra AMD chipset, the audio is Realtek ALC850. For graphics, I am using an ATI AIW 2006 PCIe. After

I updated the BIOS to 1013 (latest) and nRAID to 5.60 (latest that supports chipset). I connected two Seagate 7200.10 250GB disks as SATA 1 and 3. On the IDE side, I have three (3) optical drives. I setup RAID to make a striping (467 GB) of both SATA HDDs...

I made a working BartPE while using only the:

...\Fernandos_XP_32bit_nForce_LEGACY_Remix_Pack_v5.8\IDE\WinXP\sataraid

folder, because using sata_ide and/or legacy hung BartPE during bring-up. That got me thinking, and here I am with a question:

If I am only going to use SATA drives to make my RAID volume, which is the best package to add to nLite to make my custom WinXP Pro SP3 install CD??
A. 32bit nForce IDE drivers v6.99 WHQL
B. 32bit nForce IDE drivers v10.3.0.46 WHQL

And do I need to use the LEGACY folder, or can I use the SATARAID folder?
Of course, I always need to do the SATA_IDE as PnP driver.

With regards to Audio, should I install the AudioDrv folder in your package as well as the latest Realtek ALC850 drivers?

Thanks in advance!!

Take the v6.99 ones. The actual v10.x.xx series nForce IDE drivers do not run with NF4 systems.
You should never integrate the LEGACY driver folder, if you are going to additionally integrate the SATA_IDE driver folder. So the options are
a ) just LEGACY (as textmode driver) or
b ) SATARAID (textmode) and SATA_DE (PnP).
I always prefered the SATARAID + SATA_IDE combination, because only this way you will get WHQL certified drivers installed.
No, these are HDAudio drivers. What you need are the Realtek AC'97 Audio Codec drivers. You will get the latest ones from here: http://www.realtek.com.tw/downloads/downlo...etDown=false#AC