Fernando 1

I am sorry, I didn't remember that.Your problem has obviously nothing to do with the driver choice and integration method, but with nLite's processing itself. Maybe it's a bug of version 1.3 RC2. Please try nLite 1.2.1 Final. You will get it here: http://nuhi.olmik.net/old/nLite-1.2.1.installer.exe Good luck! Fernando

Thanks for the clarification.Here I found the description of a similar problem: http://www.msfn.org/board/index.php?showto...mp;hl=Parameter It obviously has something to do with your driver choice. Did you use the multiple driver or the single driver integration method during the driver integration part of nLite? Try to integrate just the LEGACY subfolder of the 6.85 chipset driver package (no SATARAID and no SATA_IDE) and report, if you get the same message.

You should never nLite a Cd which was already nLited or modified by another tool.Take a clean OS source and copy the CD content into a directory of your hard disk drive, then create an nLited CD with integrated drivers etc.

Did you get this error message while creating the nLited CD or did you get it during MCE setup?Maybe your problem is caused by the fact, that your MCE CD is already modified. If you want to create an nLited CD, your source should be a clean OS CD.

Look here: http://www.msfn.org/board/index.php?showtopic=82459

I don't know.When you tried to boot off the W2k3 SP1 CD, did you press any key when you were prompted to do it? After having disabled your P-ATA RAID array, did you readapt your BIOS settings, especially the RAID settings and the boot order of your hard disk devices? What about the MBR? Is it healthy and still on your first IDE hdd? My suggestion, when everything else fails: Unplug all not needed hdd's during the W2k3 installation and reconnect them, when you got a perfect running OS.

Use the XP folder. XP and W2k3 have a similar kernel.

Did you realize, that you have written post No 1000 of this thread (what an amazing interest!)? So you will succeed!Please report here, if I am right. CU Fernando

What you probably need is a driver package, which has an nForce4 Parallel ATA Controller driver.Try the LEGACY subfolder of this one: ftp://download.nvidia.com/Windows/nForce/...p2k_english.exe Alternatively you can take the 6.70 chipset driver package. My suggestion: Test the packages by booting off the original (not nLited) XP CD and presenting the content of the LEGACY folder by F6/floppy method. If the XP Setup routine detects your P-ATA RAID this way, create a new nLited CD by integrating the successfully used nForce aRaid driver version. Don't try to continue the XP installation by using the F6/floppy method - you may get endless reboots at the end.

Which mainboard, which chipset and which nForce Sata-/Pata-Raid drivers are you using?

Insert the ASUS mainboard CD, when you try to install the drivers of your "Unknown Device". It's propably the ACPI device.

Right click at the "Start" button > "Properties" > "Taskbar" , then enable "Show quick launch bar".

Did you integrate the correct VIA RAID drivers as TEXTMODE drivers? If yes, don't press F6 during the installation.

Even if you use the "Single Driver Integration" method, you get all drivers of a driver directory. Although you see only one single INF file within the driver integration window of nLite, this tool will integrate all INF, DLL and SYS files of the directory you pointed to. This is not a bug, but a feature. No matter which INF file you point at and no matter if usable for your hardware or not, nLite will integrate all possible drivers files, which are present within that driver directory. The "Multiple INF Files Option" is designed for chipset driver packages with different driver subdirectories (IDE, SMBus, Ethernet, Audio etc.). By using this driver integration method you can pick up all needed drivers at once.

You obviously found the solution yourself: http://www.msfn.org/board/index.php?s=&amp...st&p=614421If you are going to work with nLite, you must have administrator rights. As a consequence of your trouble I have added this point into my guide (post 1 of this thread).

This pop-up message has nothing to do with the driver integration, but with tweaking.It's done by the Windows System File Checker (SFC), who obviously found a system file, which has been modified (either by nLite or by prior modding of the XP source files). The System File Checker wants to replace the tweaked files by the original ones and asks for the installation source ("WinXP Pro SP2 CD" means your nLited CD with integrated drivers, hotfixes, tweaks etc.). If you want to keep the tweaked file(s), do the following: When the pop-up comes up, don't insert the CD and hit "Cancel", then you will be asked, if you want to keep the changed file. Answer "Yes" and the annoying message will disappear. If you want to restore all original MS Windows system files, you should do the follwing: Run: "sfc /scannow" and insert the original Windows XP SP2 CD (not the nLited one you used for installation purpose).

It is not a good idea to nLite an already nLited CD. Suggestion: Create a new nLited CD from scratch and use the original OS CD as source.

1. Check your RAID configuration (healthy? set as bootable?) and BIOS settings (no overclockung, set RAID as first bootable hard disk device).2. Check your memory sticks or remove one after the other, if you have more than 1 stick. 3. Unplug all unneeded devices. 4. Slipstream SP2 into your XP CD. Then try again to install XP by using F6 method. If everything fails, you should think about to RMA your mainboard.

Hi Theo,why didn't you try the drivers Gigabyte offers for your mainboard? Here is the link to the GA-M51GM-S2G driver page: http://www.gigabyte.com.tw/Support/Motherb...me=GA-M51GM-S2G Gigabyte recommends to take these nForce RAID drivers for Windows XP: http://www.gigabyte.com.tw/Support/Motherb...amp;FileID=2693 Create a driver floppy and use it via F6 or integrate the content of the driver floppy with nLite. Good luck! Fernando

I don't know. Why don't you just try it?to point 4: The 6.53 package is an old package and was primarily designed for nForce4 chipsets. The better choice for the integration of nForce3 compatible SataRaid drivers would be either Mei's Unified Driver Package (as proposed within my guide) or - as an old but safe option - the special nForce3 chipset driver package v. 5.11. Unfortunately I forgot to mention the "official" nForce3 chipset driver packages v. 5.10 and 5.11 within my guide. In this respect I agree with you, that my guide is not clear enough for users with an nForce3 RAID system. I will modify this point within my guide (UPDATE: Done!). to point 5: I proposed to use the "Single Driver" method to avoid the integration of wrong drivers. You should trust the tool nLite. There is nothing to warry about the WINNT.SIF.

1. You should not read all the pages of this thread, which is really confusing. As I have written in my first post, all important things are layed down there.2. The integration of actual nForce SataRaid drivers into a bootable OS CD is not as easy as you think. It is impossible to create something link a patch usable for everyone, because different chipsets, different mainboards, different hdd combination and even different BIOS versions may need different drivers or driver combinations. 3. If you want an easy and perfectly working method to get Windows XP installed onto your nForce3 RAID system, use the F6/floppy method and take the nForce chipset driver package v.5.10 or 5.11. But if you want to integrate the newest (and probably better) nForce SataRaid drivers into a bootable CD, you should do what is written within my first post.

no go with even just sataraid driver--still get two "Parameters Incorrect" messages during driver integration stage and "insert disc 2" when i try running a burned cd of it...Thanks for your reply.If you took a clean XP CD as source and didn't edit any SIF or OEM file, I see only 2 possibilities for your issue: Either nLite 1.3RC or NVIDIA's brandnew driver package is buggy concerning your special hardware configuration. As next step I suppose to create a new nLited CD without integrating ryan's 2.1.5a. If you don't succeed, you have 2 options left: 1. Try to install XP by using the original source and loading the new nForce 11.09 drivers via F6/floppy method. If you get the same error, I suggest to try the nForce SataRaid drivers from this driver package. 2. Build a CD by using this version of nLite. Please report here about the results.

Please try to integrate just the SATARAID subfolder of the new nForce driver package and report here if you succeed this way. Your experience with this brandnew nForce chipset package might be useful for other users with a similar hardware configuration. As I have written within my first post, the driver combination method (SATARAID+SATA_IDE) is not useful for all nForce SataRaid systems.

Open the device manager and look into the section "IDE ATA/ATAPI Controller". There you can find the running IDE/S-ATA Controllers and the drivers which they currently are using. I am nearly sure, that you only will find the following hardware components: MS Standard Dual Channel PCI IDE Controller and the Channels of your IDE ports, all of them using the MS standard ATAPI drivers.If you want any further help, you should give us some details about the RAID chipset your system is using (nForce, Silicon Image, Intel etc.).

If you don't have a RAID array, there is no need for any third party driver to get Windows XP installed onto a S-ATA hdd. XP is able to recognize all S-ATA disks without any third party driver. You should have or create a slipstreamed XP SP2 CD and set the correct Hard Disk Boot Priority within the BIOS. Furthermore it would be a good idea to partionate and format the S-ATA hdd you have set as first bootable hdd before you begin with the installation of the OS.