Fernando 1

The Raid BIOS is a part of the mainboard BIOS. So the easiest way to get an uptated Raid BIOS v. 4.84 is to check, if there is a new mainboard BIOS. Theoreticly the integration of a new Raid BIOS into a mainboard BIOS can be done by the user (you only need the new nVRaid BIOS and a special tool), but the consequences in the case of the failure are so great, that I would never give the advice to do it yourself. You have either to wait for a new mainboard BIOS or to take an nForce chipset driver package lower than v. 6.66. CU Fernando

Why did you integrate all IDE\WinXP subfolders (PATARAID, SATARAID, SATAIDE)? If you have S-ATA drives, but no Raid system, you only will need the SATARAID subfolder for the Textmode driver integration. nForce3 S-ATA systems are supported by NVATABUS.INF. But before you integrate the drivers from the SATARAID subfolder you should open the file txtsetup.oem from the folder SATARAID with the editor, go to the section [Files.scsi.BUSDRV] and replace the name nvraid.inf by the name nvatabus.inf. Within the OEMDIR subfolder you should only copy the files from the PATARAID subfolder. All the other drivers (Ethernet, Gart etc.) have to been taken from nForce chipset packages suitable for nForce3 systems.

Yes, if you remove the critical drivers, which are favoured by MS during installation, it is possible to integrate the nVRaid drivers without using the [OemInfFiles] method. I tested it and it worked with my system (nForce4) too. The problem is, that you might get "Unknown Devices", because some other needed drivers may not be installed. CU Fernando

There will not be so many people with exactly your system trying to install XP x64. Try it again with the manipulated textsetup.oem file. Maybe this will work.

People with an nForce4 SataRaid system will need only those 3 files you have left within the OEMDIR folder. The other files are just copied, because it's easier than to pick up special files and maybe people with other Raid/Sata systems need other files. AFAIK these not needed files do don't influence the integration of the nVRaid drivers. EDIT: Mjswoosh, it is not easy to explain, why you succeeded this time. Fact is, that you succeeded by creating the $OEM$\$$\OEMDIR folder as I have described in post 1 of this thread. The simply removal of some files out of the OEMDIR folder has not been the solution. I just tested it again. The removal of these files do not influence anything. Please give uns an answer to the following questions: 1. Have you made any changes concerning your BIOS (new version, new ACPI-settings etc.)? 2. What was your nLite setting within the section "Unattended Install", when nLite asked for "Computer Type"? Did you leave it as Default ("automatic") or did you choose a specific computer (ACPI-) type? 3. Is it possible, that you made - concerning "Computer Type" - another setting than before? Thanks!

Congratulations, this is totally correct.

I did not know, that you have a PataRaid system. In this case take the PATARAID subfolder. As the changes within the txtsetup.oem file were only reported for SataRaid owners, I would propose to let the txtsetup.oem file as it was. So reverse the changes you have made within this file.

Do the following: 1. Take the nForce package 6.66 for WinXPx64 (yes, you can use these drivers for nForce3 systems!) 2. Open the subfolder SATARAID within the path IDE\WinXP. 3. Open the file txtsetup.oem with the editor, go to the section [Files.scsi.BUSDRV] and replace the name nvrdx64.inf by the name nvatax64.inf 4. Store and close the changed file. 5. Now begin to work with nLite 6. Integrate the folder SATARAID from the package 6.66 as TEXTMODE drivers (both drivers which are presented by nLite, should be integrated). 7. Then integrate the other needed nForce3 drivers (SMBus, LAN, Gart etc.), but you have to take these drivers from the package 6.25! The rest can be done as I explained in the first post of this thread. If you have any trouble or if something is not clear, please ask. I will try to help you. Good luck! Fernando

Look here: Good luck! Fernando

Thank you for posting these details. It might encourage other users with similar hardware to install XPX64 or W2k3X64 by using nLite. This might be an issue within nLite Beta4. Try the following: Boot into W2k3x64, put the original CD (not the nLited one) into your cd player, open start > run and edit the following: sfc/scannow Good luck! Fernando

Mjswoosh, you have done everything correctly. The reason for your "Unknown Device" should lay somewhere else. After having googled with your mentioned ID string, I found this: http://forums.guru3d.com/showthread.php?th...goto=nextnewest What is about your BIOS (is it actual, correct settings)? What is about ACPI (activated or not)? Did you make any ACPI presettings by nLite section "Unattended Install"? EDIT: Within the DFI-Street Forum I just found something, with might be very interesting for us all:

I cannot find a special option to remove the IDE drivers by nLite. There was only a combination of SCSI drivers and something else and I removed that combination.

What is your problem? I did not really unterstand you. Please try to explain it as clear as possible (I am a German). Then you have to take the PATARAID subfolder. CU Fernando

1. As long as I integrated the nVraid drivers by [OemInfFiles]-method, I have never had any yellow question mark or an "Unknown Device" within the Device Manager. The Device Manager always showed the correct NVIDIA nForce4 Serial ATA Controller and the correct NVIDIA nForce Raid Class Controller. 2. Today I have tested to integrate the nVRaid drivers with nLite Beta6 without any "handmade" changes posted within post 1, but with the removal of the standard SCSI/Raid drivers by nLite. Result: Endless reboots. So this is not the trick for an easy nVRaid integration for everyone. As a second test I just deleted the ATAPI.SYS (as atapi.sy_) from the I386 folder and the standard SCSI/Raid drivers. Result: Endless reboots again. So the search for the exact combination of removing special drivers and doing special settings to prevent any "handmade" changes is not yet finished.

Within the next days I will try to find out the driver or driver family which has to be removed by nLite to prevent the conflict with not WHQL-certified NVIDIA Raid drivers. But to make it clear: The removal of all or a lot of the standard drivers from the Windows CD would not be a good idea for everyone. If Mjswoosh really removed MS standard drivers, he should not be surprised, that the Windows setup routine has interrupted the installation by asking for several DLL-files and that he has seen yellow question marks in his hardware device manager. The best solution for our problem is to find an easy way for everyone to integrate the not WHQL-certified nVraid drivers into a bootable complete Windows XP CD with the option, that it contains all standard drivers and all standard features. People, who are using tools like nLite, want to be free in their decision, what they want and what they don't want, and a lot of people change their mind about these things......... CU Fernando

Important information for all users, who want to try the method I have described in post 1 of this thread: nLite 1.0 Beta4 is back on the download page: http://www.nliteos.com/download.html Thanks, Nuhi!

Please help us and others to find the reason for the different handling of nVRaid systems by the Windows Setup routine on different systems and/or different nLite settings. Very interesting are the following details: 1. What sort of Raid system do you have (nForce3/nForce4, Sata/Pata)? 2. Did you remove any drivers by nLite? If yes, which ones? 3. Which version of the nForce chipset driver package did you use? 4. Which driver subfolder (SATARAID/PATARAID) did you integrate as Textmode driver? 5. Have you made any modification within the driver subfolder (by editing the TXTSETUP.OEM or copying other files into the folder), before you used it? 6. You have written, that you integrated SATA and RAID. Did you integrate them by choosing the both required drivers after pointing to the SATARAID /PATARAID subfolder or did you integrate them within 2 different steps?

The raidtool folder will not be necessary. But now to the driver removal by nLite: The longer I think about what Dale has written the more I believe, that the removal of certain drivers could be a very easy way to solve a couple of nVRaid problems. Tomorrow I will test these things.

There are only small differences between that, what Dale did and that, what works for me and a lot of other people. We all used the [OemInfFiles] method, which was integrated the first time into nLite by version Beta6. The problems Mjswoosh was writing about, occured during the first (TEXTMODE) part of the installation. During this setup part the installation procedure of Dale and me is nearly identical, because we have very similar hardware. It really can have something to do with it, if you removed the Microsoft STANDARD-IDE-ATA/ATAPI-CONTROLLER, because this wrong driver is installed by Windows Setup instead of the correct NVIDIA nForce IDE Performance driver NVATABUS.SYS. Is it really possible to delete this driver by nLite? If yes, that would be a good idea anyway.

Tweakin, pay attention you have ASUS A8N-SLI Deluxe no DFI !!! That is right, but he succeeded even with an ASUS board. Haven't you seen this reply by Tweakin?

I am nearly sure, that your problem has nothing to do with nLite or the method how to integrate the "ugly" nForce SataRaid drivers. My suggestions: Change your cd player and create a new unattended install CD. If this doesn't change anything, there is something wrong either with your RAM (check them) or power supply (strong enough?), with the temperatures within your pc case (maybe the 2 hard disk drives are too close together) or you are an overclocker, which has reached the limits (take Bios defaults settings).

Before I can help you, I need some informations: Are you really sure, that Windows Setup missed DLL-files? Or is it possible, that the system asked for CAT-files? Did the setup always ask for the same or for different files? What is your system (nForce3 or nForce4 chipset, PataRaid or Sataraid)? Which nForce chipset driver package version did you use?

What do you mean with these words? I don't really understand. If you have a mainboard with an nForce3 chipset, you can use the 64-bit nForce chipset package 6.25: http://www.nvidia.com/object/nforce_udp_winxp64_6.25 If you have a mainboard with an nForce4 chipset, you can use the v. 6.66 CU Fernando

Here is the link to the latest official 64-Bit drivers for nForce4 AMD platforms from NVIDIA: http://www.nvidia.com/object/nforce_nf4_wi...4_amd_6.66.html

Thank you very much for this Downloadlink, because a lot of people asked me already for this file. 1. Do you mean, that you have files like NVATABUS.XXX instead of NVATAX64.XXX and NVRAID.XXX instead of NVRDX64.XXX? Then you have either wrong (32-Bit) or old (not native 64-Bit) driver packages. 2. nLite Beta5 did not work for me for successfull integration of the nVRaid drivers, nLite Beta6 does not work at all with Windows XP x64. 3. I tried a lot of driver versions, they were all working with nLite Beta4 and the "handmade" changes described in post 1 of this thread. The best nForce SataRaid drivers for me (nForce4 chipset) are actually the ones from the chipset package 6.66.