Fernando 1

Yes, you should try it once again from the beginning. Remember, that Windows XP x64 is very sensitive with unknown hardware and "bad" drivers (as the NVIDIA ones).Did you enable ACPI (within BIOS and nLite)? Your system should make no problems as it is very similar to the mine. Good luck! Fernando

I suppose, that you have an nForce Raid array. If you want help, more informations are necessary:What sort of system (nForce3/nForce4, SATA or PATA) do you have? Is your system overclocked? Did you check your RAM sticks my MEMTEST? Do you have an nForce RAID BIOS version 4.84? Has your raid array been correctly detected within the first (=textmode) part of the installation? Did you try to unplug all unneeded hardware (modem, printer scanner etc.) or one of your RAM sticks during the installation of Windows XP x64? Cu Fernando

Trust me, you don't need to copy any file, if you just integrate the LEGACY folder of the package 6.70. You might be confused, because NVIDIA did not create LEGACY and PATARAID subfolders within their new packages as in v. 6.82 and furthermore they changed some file names, which makes it more difficult to pick up the right and necessary ones for the correct driver integration(NVATA.INF has the some function as NVATABUS.INF, NVATA.SYS has the same content as NVATABUS.SYS, CAT files are not really needed, when you take the LEGACY folder).CU Fernando

I have never tried the 6.82 driver package (because I don't have a SLI 2x16 mainboard), but I suppose, that you should do the following:Copy the files NVATA.INF, NVATA.SYS, NVCOI.DLL and NVATA.CAT from the SATA_IDE into the SATARAID subfolder. Then you can integrate the content of the SATARAID subfolder as Textmode driver by using nLite. If you are a little bit anxious, put the content of the SATARAID subfolder (with the added files) onto a floppy disk and try to install Windows XP by using the F6 method. If your Raid array is correctly detected, you can stop the installation and create your bootable XP CD with integrated nForce SataRaid drivers by using nLite. Good luck! Fernando

Congratulations!CU Fernando You are right, the 6.66 nForce chipset package does not contain a LEGACY subfolder (users with a SataRaid system should take the PATARAID subfolder). I meant the 6.67 package - my bad. Fortunately you have taken the right one nevertheless.

It is not as difficult as you mean and you don't need to understand the "OemInfFiles" thing, because it is already implemented into nLite.I suppose to do the following: Create a bootable XP CD by using nLite RC3. If you have trouble with this version, use RC1. Take the nForce driver package 6.70 or 6.67 and integrate the content of the LEGACY subfolder as textmode driver (see post No. 1). All the other things within nLite don't matter, but if you are anxious, do nothing else than integrating these nForce SataRaid drivers. At least create the ISO file and burn it. Then try the installation of XP from your nLited CD. If the installation fails, unplug both Hitachi drives and try again the installation. If you still have problems (BSOD), you should try to enhance the RAM voltage a little bit (0,1 V) and try it again. Good luck! Fernando EDIT: The tip from rnielsen151 was a good idea. Try it with one of your nLited CD's, before you begin the new nLite processing.

I will try to help you, unless it's not easy, because I believe, that some of your problems have more to do with your system (especially with your RAM-settings or with your 4 hard disk devices) than with nLite.Before I can give you any advices, I need to know the following: 1. Do you have an overclocked system? If yes, is the memtest OK? 2. Is your Raid array connected to the nForce Raid Controller or to the Silicon Image Raid Controller? 3. Which of your hard disk devices are connected to the nForce Raid controller? 4. Which hard disk device (single drive or Raid array) is your boot device? 5. On which hard disk device is your partition C (boot partition)? 6. Is your Raid array "healthy"?

I don't have any experience with mediashield, because I have a mainboard which supports only Raid0 and Raid1.AFAIK you need a board with Raid5 and at least minimum 3 Sata2 hard disk drives. Here are the details: http://www.nvidia.com/object/feature_raid.html If your system is ready for NVIDIA mediashield and if you have confgurated a healthy Raid5 array, you should be able to integrate the SataRaid drivers as I have described in post No 1. CU Fernando

I know that. My suggestion to go back to nLite RC1 and .NET 1.1 was only dedicated for users, who still get a freezing nLite although having uninstalled all nLite and .NET versions and reinstalled both (nLite 1.0 RC3 and .NET 2.0).

The nLite pop-up message like "If you want to install nForce Raid drivers, be aware to copy the file NVATABUS.INF into the folder you point at for integration", is nonsense in your case, if you are creating a bootable AMD64 OS like XPx64 or W2k3x64, because 1. the needed INF file for the 64-Bit Satabus driver is called "NVATAX64.INF" and 2. all needed files inclusive the NVATAX64.INF is already included the LEGACY nForce driver subfolder. If you really have problems with nLite RC3 in combination with .NET 2.0, try to go back to .NET 1.1 and nLite RC1. CU Fernando

I suppose, that you have taken a wrong driver package (a 32-Bit one), because the new 64-Bit SataRaid drivers don't have files named "NVATABUS.SYS" or "NVATABUS.INF". The names of the 64-Bit files are "NVATAX64.SYS" and "NVATAX64.INF". If you want to install the SataRaid drivers from the W2k3x64 nForce driver package 6.67, you should download them here: http://downloads.guru3d.com/download.php?det=1179#download After having unzipped the package, you have all SataRaid drivers and files you need for the integration within the folder Setup\IDE\WinXP\legacy. Point nLite to that folder named"legacy" and integrate both proposed drivers as Textmode drivers. Good luck! Fernando

I postulate, that you have no nForce Raid array and only 1 S-ATA hard disk drive.If you really want to integrate the nForce SATA drivers by using the F6/Floppy method, you should take the x64 SATA_IDE drivers from the package 6.25 or 6.56. My suggestion is nevertheless the integration of the SATA_IDE drivers from the x64 package 6.67 as textmode driver by using nLite 1.0 RC3. That should work. In each case you have to keep in mind, that you have to take the other x64 nForce drivers (for Ethernet, SMBus, GART etc.) from the package 6.25. CU Fernando

I have never had such an error message. Nuhi has written, that he fixed this error with RC3. If not, please write a post within the sticky thread about RC3 experiences, because Nuhi will not read all posts within this thread.

Thanx for your reply and the clarification concerning the CAT files. I will test your special driver remix.To take the content of the LEGACY folder for the integration of the nForce SataRaid drivers is maybe not the best, but certainly the easiest method. If you take the SATARAID subfolder, you have to copy the NVATABUS.INF and the NVCOI.DLL file (and maybe the both CAT files) from other subfolders into the SATARAID folder prior the integration procedure. According to my experiences you get the same (good) results by using the easier LEGACY method without any copying. CU Fernando

Important message for all users with nForc4 SataRaid systems: Don't use the new official x64 nForce4 driver package 6.69, when you want to integrate new SataRaid drivers into a bootable CD! It's better to take the SataRaid drivers from the 6.67 package. After a lot of frustrating tests (I always got endless reboots at the end of the install again) I found the reason: NVIDIA now gave the Satabus driver different names within the same package (NVATAX64.SYS and NVATA64.SYS) and they renamed the Satabus information file from NVATAX64.INF to NVATA64.INF. So if you copy the INF file from the SATA_IDE into the SATARAID subfolder, the Windows XPx64 Setup will not find the correct nForce Satabus driver. The installation even fails, when you just rename the NVATA64.INF file to NVATAX64.INF. As a consequece of this I have re-adjusted the text of my Post No 1. CU Fernando

That is a good message!Anyhow I would like to know the following: Which driver package version and which subfolder did you take? Did you copy any file into that folder before you integrated the driver? I have never seen such message. What did you change? My suggestion: Burn a new CD from the Image and lower the burning speed.

If I would not have seen the other new thread in this forum, I would have been helpless.I just have successfully created a Windows XP CD with integrated nVRaid drivers from the package 6.70 by using nLite 1.0 RC2. What might have been important is, that I have removed all Bus IDE Drivers within the section "Hardware Support". No! Yes, that is really very suspect.EDIT: Maybe it is worth to mention, that I already use .NETFramework v. 2.0.

As long as I try to integrate the nForce SataRaid drivers I have never seen such a message.Within German nLite Forum some users had posted the same thing and the answer was, that it was an issue in earlier nLite versions and should have been gone with RC1. After having googled I found this discussion about the message you got: http://www.webdeveloper.com/forum/archive/...hp/t-24691.html Have you done any changes within TXTSETUP.OEM, TXTSETUP.SIF or WINNT.SIF? Did you integrate just the content of the LEGACY subfolder as textmode driver or did you something else?

Which nLite version did you use?

Congratulations, that you succeeded at least.It makes me happy, when I detect the reason for an issue and when I can help somebody else. If you like, you can repeat the successful install by using nLite. A perfect integration of the nForce SataRaid drivers is not the only advantage of this tool .... CU Fernando

These 2 points seem to be the critical ones. If you really use 2 different Sata Controllers at the same time, you will get trouble.My suggestion: Unplug your Sata hard disk from Port 1 und try to install the OS only by using the Ports 3 and 4. If you succeed, you can add the third Sata hard disk. After having googled, I found this: Utility Image for nVidia and Marvell SATA RAID for NF3 board under Windows XP. Remarks: 1. Installation at booting stage is required if you intend to boot from SATA RAID. Please check user's manual for installation. 2. This image is not required if you just take SATA HDDs as non-RAID devices. 3. If you need SATA RAID but don’t take SATA RAID as booting device, please install RAID driver from driver CD under Windows operating system. This utility is not required.You can find it here: http://www.dfi.com.tw/Support/Download/dri..._FLAG=A&SITE=US CU Fernando EDIT: Thank you for your help and the download link for your special driver mix, unless I don't think, that the missing WHQL certificate of the NVATABUS.SYS is the reason for Mekrel's problem. My system (nForce4+2xSata2 as Raid0) is working flawlessly without any WHQL-certified NVATABUS.SYS.Nevertheless answers to the following questions might be interesting for us all: Is your special driver mix suitable for all nForce chipsets (nForce2, nForce3 and nForce4)? How is it possible to copy the NVATA.CAT into the NVATABUS.CAT? I have never seen a file named NVATABUS.CAT. (EDIT: Now I have seen this file NVATABUS.CAT within your driver package. The correct name is NVATA.CAT)

Thank you for the flowers! I appreciate each post, where the user succeeded with my guide. Now to your questions: 1. The nForce driver package 6.69 has the same SataRaid drivers as the packages 6.66 and 6.67. So it makes no sense to update these drivers by using 6.69. I don't recommend to use the new package 6.69, because there is no LEGACY folder. If you want to integrate the SataRaid drivers, you have to copy some files (NVATAX64.INF, NVCOI.DLL and NVATA.CAB) into the SATARAID subfolder prior to the integration procedure. If you really want to update a Sata or a Raid driver, you should do it by using safe mode booting (F8). 2. The latest official BIOS for your mainboard (dated 23th June) includes the actual NVIDIA Raid Bios version 4.84. You can verify it, when you are booting. The second screen shows your Raid array and the Raid Bios version. CU Fernando

I don't know exactly what you want to say with your post. Did you succeed with the integration of the nForce SataRaid drivers by using your special mix? Do you have an nForce SataRaid or an nForce PataRaid system?If you want to help Mekrel, you should explain, what you have done before you integrated the SataRaid drivers. Important may even be, what you have done with the SATA_IDE.INF and where you have got all those different drivers from.

Thank you for your post.New questions: 1. Do you only have 2 hard disk drives? If you have more, what sort (SATA/IDE)? 2. Which sort of controller is used by these hard disk drives (nForce Sata controller or nForce IDE Controller)? 3. Have you enabled these controllers within your BIOS? 3. Did you select both required drivers nLite proposed to integrate as textmode drivers (NVIDIA nForce Storage Controller and NVIDIA RAID CLASS DRIVER)?

Hi Mekrel,you have copied the whole content of your SETTINGS.INI with all removed languages into your post (a simple file attachment would have saved a lot of space), but you did not mention at all what happened during the install of the nLited XP CD. If you want help, you should answer to the followng questions: 1. Is your Raid array "healthy" (look at the second boot screen)? 2. At which part did the installation fail? 3. What happened exactly? 4. Has your Raid array been detected correctly during textmode part of the installation? Now a few words to the "brandnew" nForce3 driver package 5.11 you have used: The IDE drivers are exactly the same as within the 5.10 package NVIDIA had published last year. The only new component within the 5.11 package are the ethernet drivers and they have nothing to do with Sata and Raid drivers. CU Fernando