Fernando 1

Nuhi is a workaholic. So you can be confident, that you have not to wait for a long time.

Thanks, Banshee!Your test verifies, that option No 1 does not work the easy way (without editing the SIF files). Did you try one of the other options? If yes, did you succeed?

Maybe you are one of the users who should wait for the next version of nLite. On some systems people have problems with nLite 1.0 RC3. That's right. Wait for nLite 1.0 RC4 or Final and try a new clean install. That should be a good idea. The more important question is which is the better as boot hard disk. I personally prefer to boot from the Raid array. Yes, take one of the tweaking tools. All the best to you! Fernando

You should test all your hardware devices step by step!Good luck! Fernando

OK What was the result? Did you succeed with the LEGACY folder?

I am pretty sure, that it will work with the 6.70 package, if you put all extra needed files (NVATABUS.INF, NVATA.CAT and NVCOI.DLL) into the SATARAID subfolder prior to the integration. This would even be better than the easy method with the LEGACY subfolder, because you have the CAT files present, which enforce the correct installation of the drivers (SYS files). If you want to do the same with the package 6.82, there is only one problem: Within the newest nForce chipset driver packages you won't find a file named NVATABUS.INF (but a very similar file named NVATA.INF within the SATA_IDE subfolder). If you copy this file into the SATARAID subfolder, the necessary driver NVATABUS.SYS - although it is present in the SATARAID folder - will not be found by the installation routine, because the NVATA.INF points to a driver named NVATA.SYS, which is not present within the SATARAID folder. In this case you have 3 options to get a correct installation of all needed SataRaid drivers: 1) You copy both NVATA files (NVATA.INF and NVATA.SYS) from the SATA_IDE into the SATARAID subfolder (I am not sure, if it works, because the "normal" name for the nForce Sata Controller driver layed down in the SIF files is "NVATABUS.SYS"). 2) you open the NVATA.INF with the editor, search for "NVATA.SYS" and rename it to "NVATABUS.SYS" or 3) you take a NVATABUS.INF from chipset package 6.67 (32bit), it contains the same SataRaid driver version 5.52. Hope, that this is help enough. CU Fernando

Im using windows installed on another hdd, later I installed sata drivers and the sata drive, sorry I didnt explain this very good...You are right, it is not easy to help you because you give very little and rather unclear informations. Why didn't you answer to my questions? As far as I understand your posts, you did not even reach the step to install Windows XP by using an nLited CD with integrated nForce Sata drivers, because you have difficulties to create an nLited ISO image with integrated nForce Sata drivers.If this summary is correct, then your problem is nLite and not the execution of my guide. In this case you should open a new thread within the nLite forum and explain your problem, because otherwise Nuhi would not get knowledge about this nLite problem. By the way: Have you ever tried just to integrate the SATA_IDE subfolder of the nForce driver package 6.70 as "normal" (not as textmode) driver? Because you have no Raid system, there is no need for the raid drivers as mass controller drivers. I would like to help you, but you should give me a chance to do it......... CU Fernando

Does that mean, that you can install Windows XP with the nLited CD, but without the nForce Sata drivers? Or do you have a break within the installation?Which nForce driver subfolder did you integrate? EDIT: Which nLite version did you use? How did you manage the installation on this working partition?

How do you mean that?What exactly happened and at what step of the installation? EDIT: If you are not able to install a clean Windows XP, you possibly have a hardware problem. Did you enable the SATA ports within the BIOS? Are the SATA HDD's recognized within BIOS?

If you have no Raid, it should be very easy, because no driver integration is necessary for the complete Windows XP install. But what you need is an integrated SP2.So try just to slipstream SP2 into Windows XP, burn that CD with integrated SP2 and boot with it. You can install the nForce Sata drivers later (when the installation is completed). If you want an nLited CD with integrated nForce Sata drivers, be aware to slipstream XP SP2 as first step of the nLite processing.

If you want help, I need some more informations.What kind of system to you have (chipset, Sata/Pata, Raid etc.)? What have you done? What happened?

If you are starting to create a bootable XP CD by using nLite, don't start with a "modded" system.Begin with the original XP CD and add or remove all things later by nLite. Otherwise nLite may get problems. The same thing happens, when you change driver integrations or removals after the end of the nLite processing. In all these cases it is better to begin a new nLite processing with a clean OS.

Because a 64bit OS is more demanding than a 32bit OS. It depends on your RAM sticks. Some of them need lower voltage (from 2,6 V up to 2,8 V), but others need more electricity power, especially when they are forced by a 64bit OS. Ask the RAM manufacturer, if you are not sure.

As a first step I would propose to increase the RAM voltage per 0,1 Volt within your BIOS and to try again to install XP x64 using your nLited CD.If this fails, you may try to install the "old" 64-Bit nForce Raid drivers out of the package 6.56 Beta by simply using the F6/floppy method. According to my tests are these drivers the latest Raid drivers which can be installed by F6 and floppy. You can download the 64-bit driver package 6.56 here: http://downloads.guru3d.com/download.php?det=1068 Good luck! Fernando

I am pretty at a loss with your problem, but I am nearly sure, that the origin is a hardware issue.What about your power supply unit (enough power? all proposed connections to the mainboard set?) and your CD-ROM device (error-free? with correct IDE connection?)? Do you have any additional PCI Cards built in? If yes, did you try to remove them during the install of XP x64? EDIT: Are you sure, that your RAM sticks get enough power? If not, try to enhance the voltage per 0,1 Volt steps.

Normally nLite should work with regional versions of Windows XP (in your case: Spanish Edition).What do you mean with "modded"? Maybe is this the reason for the issue with nLite. You should do the following: 1. Copy the content of the original XP CD (Spanish Edition) into a folder of your HDD. 2. Prepare or download SP2 (Spanish Edition) for Windows XP. 3. Then start nLite again. Begin with slipstreaming SP2 and continue with integrating the nForce SataRaid drivers according to my guide. CU Fernando

The CAT files (as NVATA.CAT) only have the function to verify, that the associated driver (in this case: NVATAX64.SYS or NVATA64.SYS) is digitally signed by Microsoft. So the file is not really needed, when you want to integrate the drivers by using nLite 1.0 RC1 or higher. But when you are doing the F6/Floppy method, you may need the 2 CAT files (NVATA.CAT and NVRAID.CAT).As long as I do my tests integrating new nForce SataRaid drivers (v. 6.66 and higher) I have never had such a message about missing CAT files. If you want to prevent the message, you have to copy the NVATA.CAT from the SATA_IDE and the NVRAID.CAT from the SATARAID subfolder into the driver folder, before you are going to integrate the content of that folder as textmode driver.

The integration of the driver for this Sil IDE Controller Card by using nLite should be easy, but what has this Card to do with nForce and Raid?

I am not an expert in the deep processing structure of nLite (you have to ask Nuhi himself), but AFAIK this popup means, that there has been an error within step 13 of the nLite processing.Did you open and edit any SIF file (WINNT.SIF or TXTSETUP.SIF)? You have written, that nLite continued the processing unless the error message. What was the result?

No, this guide is only useful for NVIDIA nForce Raid systems.

You are welcome.I love such a post, because normally users only give a comment within this thread, if they have a problem. But more than 33.000 viewers cannot been mistaken. CU Fernando

That is a good idea. Windows XP x64 is more pretentious than Window XP in any case (drivers and system).

The procedure is rather complicated. When you have used the older Beta versions of nLite, you had to do some extra hand-made changes to get the SataRaid driver integration to work (either you had to remove all IDE Bus drivers within the section "hardware support" or you had to add special folders and to edit some lines within the WINNT.SIF), but since the RC1 version of nLite this is not necessary anymore. Now the suppression of the wrong MS IDE Controller driver is fully implementated.Your report about the BSOD's indicates, that you should have done something wrong or that you have a problem within your system. Please check your XP CD, your CD drive device and your RAM sticks, before you continue. If you try tomorrow a fresh CD, read and do exactly what I have written within my guide (post No 1). This method should work with your system! CU Fernando

The integration of the nForce4 Raid drivers from the package 6.70 into a bootable XP CD is not as difficult as you mean.Look here: http://www.msfn.org/board/index.php?s=&sho...ndpost&p=356029 CU Fernando

Section "Unattended Setup" > "General" > "Computer Type": Let it as it is as default ("automatic") Whithin my tests I mostly have chosen "FullUnattended" or "DefaultHide" as "Unattended Mode" and let the "Oem Preinstall" enabled, but other users have reported, that you should disable "Oem Preinstall", when you are doing an unattended install.