Fernando 1

This thread was started within the nLite Forum and is dedicated for home users, who want to create their special Windows XP or XPx64 CD with integrated nForce SataRaid drivers by using nLite. The integration of Driver Packs and especially MassStorage Driver Packs into a Windows CD has primarily nothing to do with nLite. There is a special forum "DriverPack MassStorage" within the MSFN Board. That forum is dedicated for pc system administrators, who want to create a Windows CD useful for nearly each mass storage combination. Cu Fernando

You can prevent the reboot by hitting F8 and choosing "no reboot at system failure". Then you have plenty of time to read the error message.By the way: Is there a MBR on your 3rd (non-Raid) hdd, for example from earlier installation tests? If yes, you should delete it.

Thanks for the reply.When you got the BSOD after reconnecting the 3rd hdd at the end of the installation, did you try to boot in safe mode? If yes, did it fail? Could you read the error message?

Please explain a little bit more detailed what you have done.As I understand you have 3 SATA hdd's. 1. They are all connected to nForce SATA ports. Two of them are put together to an nForce RAID array, the third is a single SATA hdd. 2. Before you start with the install, you unplug the non-Raid hdd (to prevent, that the XP setup puts the MBR files onto this hdd). 3. After the end of the TEXTMODE part of the install you shutdown your pc, connect your 3rd hdd and then you continue with the install. 4. This works with XP x64, but doesn't with XP x32. Is this what you did and what happened? What happened, when you reconnected your 3rd hdd after the successful end of the install? EDIT: As nLite puts the driver files all together into the same OEMDIR folder, you would get the same effect, if you copy all files of the SATA_IDE into the SATARAID subfolder prior to the integration.

That is a very interesting variation for the installation of XP x64 with integrated nForce SataRaid drivers (but the wrong thread!).Please give us answers to the following questions, because they might be helpful for other users: What was the result with XP (32-bit)? Which nForce driver package did you take for the successful install of XP x64? Did you integrate the NVIDIA standard SATARAID subfolder or the one with the added files (NVATAX64.INF etc.)? CU Fernando

I'm hoping with you, that it isn't the mainboard which should be repaired or changed.Before you bring it back to your vendor, check your cables (SATA and IDE) and your PSU. These hardware components are very often the reason for errors. Good luck! Fernando

You can try it, but I'm sure, that you will not be happy with a very low CD-ROM speed. I bet, that you will get trouble if you try to replace the nForce4 Serial ATA Controller by the Standard Dual Channel PCI IDE Controller, although the MS device manager shows them as "compatible". That is exactly the error during the install of XP which causes the endless reboots at the end.I would recommend to give the systray icon a chance (you may hide it with the task manager).

If your CD drive is OK, you should try to replace the nForce P-ATA Controller by the MS Standard Dual PCI IDE Controller.Look here: http://www.msfn.org/board/index.php?s=&sho...ndpost&p=453294 Here you can get informations about how to troubleshoot CD or DVD devices: http://support.microsoft.com/default.aspx?...b;EN-US;q218617 CU Fernando

I am nearly sure, that this error (never have seen or heard about such message before) has nothing to do with nLite or especially with the integration of the nForce SataRaid drivers.My tip: If you google for "unknown hard error Systemroot\system32\ntdll.dll" you will find a lot of discussions about that error, for example here: http://www.annoyances.org/exec/forum/winxp/r1047757657 CU Fernando

Is one of the hdd's an IDE one or are all of them SATA connected?If yes, did you use the NVIDIA Sata ports for all of them? Did you put the Raid as first bootable hard disk device within BIOS (maybe the system tries to boot from your Western hdd, when it is connected)? What is about the drivers you tried to install after you had reconnected the Western hdd?

Either I did not really understand your reply or you did not read the question within my last post.Now I have even more of them: Before you reconnected your 3rd hdd, did you have a look into your device manager? Everything OK there? Why did you need separate drivers for your 3rd hdd? What sort of drivers did you install for the 3rd hdd? Did you install them in safe mode? What error message did you get? Can you please give some informations about your system (mainboard and chipset, hdd details etc.)?

Do you get a BSOD even when you reconnect the 3rd hdd after the successful installation of Windows XP?By the way: I have mentioned this behaviour of non-RAID hdd's during the install within my guide in the first post of this thread ("Tips" at the beginning).

I don't think, that you can get a fresh install without that icon within the systray, but there should be a possibility to remove it after the end of the install.In an other forum I have read, that the "Safely remove hardware" icon disappears, when the nForce P-ATA Controller is replaced by the MS Standard IDE Controller. If you really want to try this, do the following: a ) Go to the device manager and open the IDE ATA/ATAPI Controllers. b ) Now open the"Properties" of the NVIDIA nForce4 Parallel ATA Controller and go to "update driver". c ) Don't use the Internet and the automaticly search for the driver , then point to "not searching, but choosing yourself". d ) Within the following window you should see 2 hardware devices, if you enable the option "show compatible devices". e ) Choose the "Standard Dual ChannelPCI IDE Controler" and go to "next". After a reboot the NVIDIA P-ATA Controller should be replaced by the MS Standard IDE Controller. If the icon has not been removed and you want the nForce P-ATA driver back, replace the MS IDE driver by doing the same as above. CU Fernando

Is it possible, that you did not enable the Sil Controller within BIOS (because you don't use them actually)? In this case it is clear, that the driver has not been installed.CU Fernando

No, if you integrated them correctly.

That is totally normal! All devices with hot-plugging capacity are shown in systray as "safely removable hardware".Look here: http://www.planetamd64.com/index.php?showtopic=14090 My answers:1. The nForce Raid controllers will have the better performance than the Silicon Image ones. 2. You can take the nForce SataRaid drivers off the 6.70 package (see my first post), but you have to take the other nForce drivers (GART, SMBus etc.) from another driver package. Although I didn't try it yet, you should also be able to take all drivers - inclusive the nForce SataRaid ones - off the new 8.22 Remix driver package. Important is, that you integrate all needed drivers and files (look into the driver package structure and compare it with my guide). If you don't have an actual nVRaid BIOS (v. 4.84 or higher), you should take the SataRaid drivers off the package 6.53. 3. Yes! CU Fernando

The first post is up-to-date. I did not describe a correct and a wrong way, but 2 different ways to integrate the nForce SataRaid drivers. If you have an nForce4 mainboard (with a Raid BIOS version 4.84 or higher) and if you want to use the easiest method, just integrate the IDE\WinXP\LEGACY subfolder as textmode driver (no preparations at all necessary!). The first part of the Windows installation is called "TEXTMODE" (like DOS, that means without any GUI). Mass storage (= "textmode") drivers, which are not present within the OS CD, have to be loaded within this TEXTMODE part of the installation (i.e. by F6/floppy). Otherwise Setup will not detect the unknown mass storage devices (in this case: your RAID array).Remark: If you are integrating a driver by using nLite, you should not "insert" a folder, but just point to the content of a driver folder. I totally agree with you. Exactly this is the reason why I have written this guide (to make it as easy as possible for you!). CU Fernando

Hello RickSteele,I have to thank you a ) for the correction of your earlier comment about my guide concerning the use of the 6.82 driver package on SLI X16 systems and b ) for your notice, that the Windows setup asks for the NVIDE.NVU file, if you integrate the SATARAID driver subfolder (As a result of your post I have clarified this point within my guide). CU Fernando

So you succeeded finally?How did you do it (F6 or nLite)? Which nForce SataRaid driver version did you install?

@ RickSteele:That is interesting. As I don't have a SLI X16 mainboard, I cannot test it. My tip: Try to integrate the nForce SataRaid drivers off the 6.70 package and update the drivers after the successful install. That should work. Please give a feedback! EDIT: I assume, that your DVD-RW device, where you are booting from, is connected to an IDE port. Otherwise you have a known problem. The CD/DVD booting device should be IDE connected, otherwise you can get conflicts with the fresh installed Sata drivers. @ all users with a SLI X16 mainboard: Please report about your experience with the 6.82 driver package. CU Fernando

Done!CU Fernando

@ Securite:Thank you for the summary of what you have done to get a successful XPx64 CD with integrated PataRaid drivers. These instructions may help other users with an nForce3 mainboard and a PataRaid system. @ all: Don't be confused. There are no important differences between the instructions of Securite and my guide (first post of this thread). He took the 6.25 nForce RAID floppy drivers, I recommended to download the whole 6.25 driver package (just to have the other needed nForce drivers at the same time), which includes exactly the same RAID drivers. CU Fernando

Thank you very much for this comment.That is a bad, but wellknown behaviour of the Windows Setup. If you have a hard disk drive outside the Raid array, it tries to install the OS on this device, even if you have set the RAID array as first bootable device. The only possibility to prevent this is to unplug the extra hdd(s) during the install of the OS. I think, that I should mention this in my guide (first post of this thread). CU Fernando

Although I didn't test it with the Sil RAID drivers, I don't see any difficulties with these drivers similar to the nForce or VIA RAID drivers. Just integrate them as textmode drivers by nLite.CU Fernando

Hi Mariokart,try to boot in safe mode. If you succeed, look into the device manager for yellow question marks. If you cannot boot in safe mode, choose the F8 boot option "no restart at system failure" and look onto the error message. If you use the actual nForce SataRaid drivers (off the package version 6.66 or higher), you should have a Raid BIOS version 4.84. Have a look onto the second boot display. There you can see the version number of your Raid BIOS. If you can't get a new mainboard BIOS with integrated Raid BIOS v. 4.84 or higher, you have to create a new nLited CD. Instead of the new nForce SataRaid drivers from the nForce package 6.67 you should take them off the package 6.56. You can download this package here: http://downloads.guru3d.com/download.php?det=1068 CU Fernando