Fernando 1

@ RickSteele: Thanks for the details about your system. I am waiting for your next report. CU Fernando

This is really interesting. I just have checked it on different partitions of my system (nForce4 Ultra chipset with 2 SATA2 drives as Raid0). Unless I have used the same nForce IDE drivers as you did (v. 552), the NVATABUS.SYS and the NVRAID.SYS is presented as not WHQL-certified within the device manager of my system. The same thing with the nForce IDE drivers v. 621. But I have other Controllers than you have: 1 NVIDIA nForce RAID Class Controller as "SCSI and RAID Controller", 1 NVIDIA nForce4 Parallel ATA Controller and 2 NVIDIA nForce4 Serial ATA Controler as "IDE ATA/ATAPI Controller". Conclusion: The nForce SataRaid drivers NVATABUS.SYS and NVRAID.SYS are WHQL-certified for some, but not for all nForce systems. That might be the reason, why you didn't have these big problems with bluescreens and endless reboots after the install of the new nForce SataRaid drivers.

This popup message is not an issue. I think it is due to the fact, that you mixed the nForce SataRaid files, before you integrated them as TEXTMODE drivers. Normally no file changes or transfers are necessary, when you take the driver subfolder I proposed (PATARAID with 6.66, LEGACY with 6.67).

You are right, that was my fault. I have tested a lot of prebuilds of RC1 and those prebuilds did not contain this entry within the WINNT.SIF. Nuhi must have put the [OemInfFiles] section into the final version of nLite 1.0 RC1. I do not know the reason why he did it, because the OemInfFiles method needs a path $OEM$\$$\OEMDIR. If you look into your device manager and open the properties of the NVIDIA nForce4 Serial ATA Controller (device group IDE ATA/ATAPI Controller) and look into the driver details, you will see that the NVATABUS.SYS is not WHQL-certified.

As I understand your post, your experiences using the new method using nLite 1.0 RC1 were the following: The integration of the nVRaid drivers succeeded (no BSOD, no endless reboots), but after the installation of Windows XP by your nLited CD you have problems with your power management and with your sound. Is this correct? If yes, I will give this information to Nuhi. I don't understand, what you have written. The new version RC1 of nLite 1.0 does not use the OemInfFiles method. EDIT: Nevertheless the final version contains an [OemInfFiles} section. AFAIK there is still no NVATABUS.SYS, which is WHQL-certified. Although some NVIDIA driver packages are proposed as WHQL-certified, the special nForce Sata Raid drivers are not. Exactly this is the main reason for most of the difficulties. This is the moment, when the Windows XP Setup detects your Raid array. I have seen this popup only with nLite 1.0 Beta6, when I used the OemInfFiles method. CU Fernando

The RC1 version of nLite 1.0 has brought some important changes, which make it easier than ever to integrate the x64 nVRaid drivers into a bootable Windows XP x64 Edition CD. That is the reason why I have just edited the new method within post No 1 of this thread. CU Fernando

The RC1 version of nLite 1.0 has brought some important changes, which make it easier than ever to integrate the nVRaid drivers into a bootable Windows XP CD. That is the reason why I have just edited the new method within post No 1 of this thread. CU Fernando

Hi Stephane, thank you very much for having taken the time for several tests and postings within this thread, because it is very important for other users to know the exact reason, why someone succeed with a special method and others have BSOD's or endless reboots. The short interruption of the hardware installation during Windows Setup showing a popup window "New Disk Drive Detected" is very common for me. It is the moment, when the Windows XP setup routine is going to install the correct NVIDIA driver "NVATABUS.SYS" instead of the (wrong) MS driver for the PCI Standard IDE Controller. I have always seen this popup window, when I used the "fullunattended" method and both INF-files (NVATABUS.INF and NVRAID.INF) were integrated into the OemInfFiles section of the WINNT.SIF. It did not bother me at all, because this event supplied evidence, that the installation will succeed without endless reboots due to wrong Sata/Pata drivers. Just a little correction: It does not matter at all, which INF file you are choosing, when you are going to integrate drivers by nLite, because all files - inclusive all other INF-files - are copied by nLite and the hardware detection of the OS will take the correct INF file during installation. The only important thing is to choose the correct folder (with a suitable INF-file within it). Your contribution was very helpful for us all! Thanks! Fernando

Double post! Sorry.... Fernando

I am really all on edge about your results.... By the way I have 2 questions: 1. Have you ever tried the "Drivers Removal Method" that I described in post 1? If yes, how were the results with your system? 2. Why did you build a Raid array, although you have only 1 hard disk drive? CU Fernando

Hi Stephane, it is very interesting, what you have written. As far as I can see, you have modified the OemInfFiles method (that I described within post No 1 of this thread) only by these 2 points: 1. instead of copying the whole SATARAID subfolder content into the OEMDIR directory you took only the files NVATABUS.SYS and IDECOI.DLL and 2. you removed the "NVRAID.INF" from the OemInfName line within the WINNT.SIF. It is hard for me to unterstand, that these small changes, which only can have an effect within the GUIMODE part of the installation, have prevented the crashes of your system within the first (TEXTMODE) part of the installation. The only explanation for me is what you have written within point No 7. Is that true, that you did not take both mass controller drivers nLite proposed to integrate, but only the NVRAID.INF? Please give us an exact answer, because this might be important for other users witth similar systems as yours. CU Fernando

Thank you very much for the perfect description of your nVRaid problems and your thoughts about their reasons, but I see causes to point out the following: The experiences of Jayhall0315 were done with an ASUS A8N-SLI and cannot be automaticly transferred to users with other mainboards. Same thing: This is only a problem for users with an ASUS mainboard and has nothing to do with the integration of the nForce SataRaid drivers into a bootable Windows XP CD. That would be great! All users with an nForce SataRaid system wish you good luck! CU Fernando

If you have only S-ATA and no IDE (P-ATA) hard disk drives, then you did something wrong this time.The first pic looked much better. Each user has his own preferences. You can include what you want, but you have to remove the IDE bus drivers (see my first post within this thread).

What is your problem? Everything is fine within your device manager! The only little thing you have to search for is your "Unknown Device". (My tip: Google for "Asus A8N-E" +"Unknown Device"!) Everything else is totally OK. As you can see within the pictures, your NVIDIA Raid Controller and the nForce4 SATA Controller have their correct NVIDIA drivers. It is totally normal, that the "device" NVIDIA Stripe shows MS drivers (disk.sys and PartMgr.sys). CU Fernando EDIT: I found something about your "Unknown Device" in an ASUS newsgroup::

The 6.66 package is complete, whereas the 8.12 packages contains only SATARAID, Ethernet and SMBus drivers. Both driver packages were built by NVIDIA. The driver package 6.66 was already officially presented by NVIDIA, whereas the brandnew package 8.12 was leaked first by the french website "station-drivers", but now already presented as "official" nForce4 driver package by ASRock: http://www.asrock.com.tw/support/Download/...8NF4G-SATA2.htm Users with an nForce4 system should take the SataRaid drivers from the new package 8.12. They are really better than the older ones. CU Fernando

It is not the question of the driver, but of the Raid Controller. Most of the users who have both Raid Controllers (nVRaid and Sil3114), prefer the nForce Raid controller. The best drivers for the nForce4 SataRaid Controller will certainly be the brandnew ones from the NVIDIA chipset driver package 8.12 (look here:).

The method I have described is only suitable for NVIDIA nForce Sata or Raid Controllers. If you have a Serial ATA Controller from Silicon Image, you may not use the NVIDIA nForce chipset package 6.66, but the SATA drivers from Silicon Image for integrating the correct Sata drivers for your board. For all other Controllers you have on your nForce2 board (IDE, LAN, GART etc), you can use the NVIDIA driver chipset package 5.10 (don't try the package 6.66 for these controllers, they don't work with nForce2 boards).

Although I have no nForce2 motherboard in use, I think, that you can take the PATARAID subfolder. The nForce2 Serial Ata Controller is supported by the NVATABUS.INF.

What kind of motherboard do you have? Is it an nForce3 or nForce4 board? Did you install XP x64 onto a clean, formatted partition? To verify if your RAM is ok, make a memtest!

1) When you install Windows XP or Windows XP x64 on a system with firewire and ethernet ports, it is not unusual, that it takes a few minutes after the last reboot until you can work with your computer. You can prevent this behaviour, if you deactivate all network options (Microsoft Network etc.) of all firewire and LAN ports during the installation. 2) I don't know the reason for your low speed. What shows your Device Manager (everything OK there?)? 3) When you delete your Raid array, you cannot boot anymore, because the system looses the Master Boot Record (MBR). You have either to reconfigure your Raid array or to install a new MBR. If you have a system, which is overclocked to the limit, it might be possible, that you get trouble after the installation of a 64-Bit OS, because it needs some more resources. If you want help, please answer the following questions: 1. Did you install XP x64 into a seperate partition? 2. Have you formatted this partition, before you installed XP x64? 3. Which NVIDIA driver package did you use? 4. Is your BIOS up-to-date? 5. Are you sure, that your mainboard, your hard disk drives and your RAM don't have any issues?

By updating your mainboard BIOS. The Raid BIOS is a part of it.

Important information for all users, who want to integrate the nForce Sata/Raid drivers into a bootable XP x64 CD by using nLite: There is no need any more to take the nLite version Beta4, which had an issue with the installation of the Internet Explorer (32-Bit and 64-Bit). I found an easy method to integrate the nVRaid drivers by using nLite Beta5. Look into the first post of this thread! Cu Fernando

This was an important information for all users of a NVIDIA Sata/Raid system It really makes sense to let nLite remove those IDE drivers, which are causing the problems with the nVRaidSata drivers, because in this case there is no need for creating an OEMDIR folder and no need to edit something within WINNT.SIF. The only handicap of this method is, that the removal of too many or the wrong drivers may cause new yellow questionmarks within the Device Manager. Meanwhile I have tested this "Driver-Removal-Method" on my nForce4 SataRaid system - and I have got it to work without any problems (no endless reboots, no yellow questionmarks, no error popups! As a consequence I have added this new method into post 1 of this thread. So there are at least 2 easy methods to integrate the nVRaid drivers into a bootable CD by using nLite. Thanks to Dale and Metalljens for their posts. They gave me the push to try this method. CU Fernando

I can understand your reaction. It is really frustrating to spend such a long time and at least to be unable to install a correct working OS. But there is a reason to be optimistic. In the very next future, maybe within the next days, we will get a new version of nLite´with - full XPx64 support and - full integration of the nVSataRaid drivers (no "handmade" changes necessary). Pay attention to this forum within the next days! CU Fernando @ TeamMCS: The problem for you is to find the best driver combination and TXTSETUP.OEM entries to let the system correctly identify your PataRaid system within the first (TEXTMODE) part of the installation. If you have a floppy disk drive, you don't need to create and burn a lot of CD's. Just start booting with your original XPx64 CD and try to integrate different driver combinations via F6 method. When your Raid0 array has been correctly detected (as 1 hard disk drive), then you have gotten the right driver combination suitable for the integration of these drivers into a bootable XP x64 CD by nLite.

Dale, as we already know, you are a lucky man, but there are a lot of others in the world. I got the information about the correlation between the nForce Raid driver version, the nVRaid function and the Raid BIOS version from a lot of people. Look here: http://www.msfn.org/board/index.php?showto...ndpost&p=385843 and here: http://www.planetamd64.com/lofiversion/index.php/t10928.html and here: http://forums.nvidia.com/index.php?showtop...t=0entry44505 That is why I have put this information into post 1 of this thread. CU Fernando