Fernando 1

And you are sure, that you have an nForce Raid array and not a Sil3114 Raid array?EDIT: You have 2 different sorts of Raid Controllers on board (the nVRaid and the Sil ones). Check within your device manager, which controller your Raid uses.

No, that will not be ok. There are some important files missing within the SATARAID subfolder. You have to take either the LEGACY folder or the SATARAID with some extra files in it (see post No 1 of this guide).You have written, that you have an AN8 SLI Premium, but who is the mainboard producer (ASUS or Abit)?

Thank you for this clarification, Rick.My guide is already customised to your findings. Best wishes! Fernando

I know, that users of some Asus boards have an "unknown device" within their device manager. You have already pointed it out. The problem can be resolved by putting the Asus mainboard CD into the CD drive. The missing driver will currently be found. But this has nothing to do with the integration of nForce SataRaid drivers.With my DFI mainboard I normally have no trouble at all with "unknown devices", unless I have removed too many drivers by nLite. Thank you for posting the driver details. If you think I should change my guide regarding this special point, please let me know. CU Fernando

Please let us know, which files you used from the LEGACY and the SATARAID subfolder. There is no reason to install the old drivers or to reinstall XP:1. The icon "safely remove hardware" is totally normal (it is shown for hot plugging devices). 2. You can easily install the missing "unknown" devices by giving them the correct nForce drivers. Look into the properties and write here what you see (example: DEV_0057 is the NVIDIA Network Bus Enumerator as a part of the nForce Ethernet controller). CU Fernando

Before you gave your old raptor away, did you correctly remove your Raid array? If not, you really should clean your hard disk drives by low level formatting. Good luck! Fernando

Do you mean it stops after the install of the setup files and before the hardware installation begins?Is the cursor on left hand top of the screen blinking? Did you change anything else unless you have a new raptor? Is your PSU strong enough? Have you tested your RAM sticks (memory test)? Do you have the correct voltage for your RAM? My tip: Set BIOS timings at default (no overclocking), unplug all unnecessary hardware devices and try it once more. Maybe you should test it with a little enhancement of the RAM voltage (0,1 V).

New dated download links on the homepage of a mainboard producer does not mean, that the drivers are really new.Can you give me the link to the drivers and the details of your system?

On the right hand bottom of each post you find 2 buttons: a "Quote+" and a "Quote" one. Just click on the "Quote" button, then you have the quoted text like here. If you want to answer at once to more than one post, you have to hit the "Quote+" button of each post and then the Reply button at the site bottom. That would be fine. Before you start, please verify, that you have a Raid BIOS v. 4.84 (official BIOS 623-3 has it included).Good luck! Fernando

Thanks!CU Fernando

You are right, that was my bad. I had it already corrected before you have written this. Thank you for this statement. I am very curious about your test results.As I know, that you like testing, I would like to stimulate you to test the nForce SataRaid driver integration by using another tool named Windows Unattended CD Creator. This tool is rather simple and cannot be compared with nLite according the options, but has fully integrated a special method to prevent the substitution of the correct nForce driver by the wrong MS driver without any manipulations on the IDE controller drivers. It would be interesting to know your experience with this tool and its alternative method. If you want to use the WUCD Creator: The link to my guide in english language is here. CU Fernando

Hi Rick,thank you for this information, but I already knew it (I started this thread: http://www.nforcershq.com/forum/1-vt64530....er=asc&&start=0) There is no big difference betweeen the older 6.82 and the new 6.85 package concerning the version of the various drivers, but one thing is brandnew: The 6.85 package has a LEGACY folder, which contains all necessary files. So the integration of these drivers will be much easier than before. As a consequence I will adapt my guide regarding this point. Hi Thornsword,thank you for the flowers! You are right - I have very similar hardware as you have (my DFI Lanparty NF4 is the best board I ever had). What was it, what you have edited by hand? It's a while ago, that people needed to do some "handmade" editing. Since nLite 1.0 RC1everything works automaticly, if you follow my guide. At least a tip: The Raid driver you have downloaded from DFI homepage is a very old version from 2004. You should update the SataRaid drivers by a newer version (off the 6.70 package). CU Fernando

Not really, unless you had downloaded a corrupted driver package. Maybe you should redownload the 6.53 package.If you find the file NVATABUS.SY_ within the i386 folder, you probably did not choose both required drivers nLite propose to integrate as textmode drivers. For the moment I propose the following tests: 1. If you have a floppy disk drive, try to install Windows XP by F6 method, by using the old Shuttle RAID driver disk. 2. If the install succeeds, try the same with the SataRaid drivers off the 6.53 package (copy the whole content of the IDE\WinXP folder exepting the RAIDTOOLS subfolder onto an empty floppy). After these tests take the best driver for the integration by using nLite. Do nothing else, just integrate these **** nForce SataRaid drivers. Don't change anything within the nLited folders and files (as I have seen on your pics, you have created an $OEM$ folder and an OEM subfolder). Good luck! Fernando

Your first picture shows the files inside the folder "Raidtools" (which youdo not need at all), the second shows, that the only drivers you had integrated were the SataRaid ones. Which results do you mean? Why should I mention that within my guide? Important is the folder where the drivers come from before they are integrated. Users of nLite have nothing to do with the folder, where nLite stores the integrated driver files. By the way: nLite 1.0 RC4 and RC5 stored these files within a folder named "OEMDIR". So Nuhi changes the folder names if he wants, but this is without any influence on users who follow my guide. Tere is no reason for them to work on this folder.

Whom do you ask and which results do you mean?EDIT: I just had a look onto Shuttle homepage and found a special Raid driver disk for your SN85G4 V3: http://global.shuttle.com/Download/Downloa...tem=SN85G4%20V3. Users with an nForce3 250 chipset can use the 6.53 driver package, but now it seems to me, that you have an older nForce3 chipset, that is not compatible with the newer drivers. Maybe this is reason why no drivers could be integrated as textmode drivers. Normally it should be no problem for you just to integrate the old nForce Raid drivers from the Shuttle homepage, but I am not sure, if the integration works, because the TXTSETUP.OEM file is not in the same folder as the driver files. Maybe you have to copy the TXTSETUP.OEM into the RAID\WinXP subfolder of the Raid disk and to edit the first lines of the TXTSETUP.OEM file prior to the integration.

Congratulations, that you got it to work. Normally it is no problem to integrate drivers you don't need, because the MS setup routine will only pick the ones for existing devices.Contrary to that is the behaviour of some mass storage drivers and especially SataRaid drivers, which are not correctly digitally signed. These drivers may induce problems within the setup. It took me a lot of work and many weeks of time to find a way to successfully integrate the nForce SataRaid drivers. As you know, nLite has incorporated a sytem to prevent the preference of the MS IDE standard driver, but AFAIK this system does not work for VIA RAID drivers. If you really want to integrate several mass storage drivers into a Windows XP CD, you should look into this forum: http://www.msfn.org/board/index.php?showforum=107 . CU Fernando

The "Raidtools" are tools and no drivers. I have never used them. So you can leave the "Raidtools" folder as it is. I personally remove this folder, before I begin with the integration. 1. Why did you try to integrate all those Raid drivers at once? AFAIK your ABIT KN8 has neither a VIA nor a Sil Raid Controller. So I recommend to integrate only the nForce SataRaid drivers and to see what happens.2. You have to verify your nVRaid BIOS (look at your second boot screen). If your version is lower than 4.84, you should take the nForce chipset package 6.53 for the integration. 3. Don't manipulate the TXTSETUP.SIF and the WINNT.SIF. Good luck for you both! Fernando

The SataRaid drivers are only copied into the i386 folder, when you integrate them as "Mass Controller" (= textmode driver). If you integrate them as "normal" device drivers (pnp drivers), you will not find them within the i386 directory.EDIT: Which driver subfolder did you integrate for the SataRaid drivers? Did you get at this point of integration a pop-up window with the question, if you want the following 2 drivers to be installed: NVIDIA nForce Storage Controller (required) NVIDIA RAID CLASS DRIVER (required)? If not, you really missed to choose the integration as TEXTMODE DRIVER.

I think, that you have done something wrong.If you follow my guide, you will find the driver NVRAID.SYS within that folder, which you take for the nForce SataRaid driver integration (LEGACY or SATARAID). nLite will copy all files into the driver folder OEMDIR and additionaly the drivers as copressed files (NVATABUS.SY_ and NVRAID.SY_) into the I386 folder. Have a look, if you find them there. CU Fernando

Thank you, Rick, for this reply.I believe you, that this worked with your ASUS board, but I'm not sure, that people with other boards will succeed by just integrating the SATARAID subfolder. As a result of your posts I have modified my guide regarding the use of the 6.82 driver package by users with an Asus A8N32-SLI Deluxe. Big thanks again - your tests were very important! CU Fernando

Good, that you have added this information.I don't think, that your install would have succeeded without the additional integration of the SATA_IDE subfolder. Reason: There is no file named NVATABUS.INF or NVATA.INF within the SATARAID subfolder, but such an INF file is absolutely necessary for a successful installation of Windows XP onto an nForce SataRaid system. CU Fernando

Try the following:1. Take default BIOS settings (no overclocking). 2. Use only 1 RAM stick. 3. Unplug all not needed hardware components (audio card, usb devices etc.) 3. Try to boot with a normal (not nLited) XP CD with integrated SP2. Don't use F6/floppy method. What happens? Thank you for the clarification. I will mention your experience within post 1 of this thread. That is not totally correct. Within the SATA_IDE subfolder of the 6.82 package there is a file named NVATA.SYS. This driver is nothing else as the nForce IDE (P-ATA) driver.

Could you boot in safe mode?Have you integrated SP2 into XP?

My guide is dedicated for users with an nForce Raid system.As you have no Raid, you should not integrate the SataRaid drivers as textmode drivers. Try to install XP without any nForce Sata/IDE drivers (no F6, no integration of these drivers by nLite). CU Fernando

Hi RickSteele,I have to thank you for your post, because you pointed out the interdependency between the IDE drivers and the burning results of Nero Burnig ROM. As a consequence of your post I would like to correct my guide regarding nForce4 SLI x16 systems, but before I do this I have to crearify something. You propose to integrate the SataRaid drivers off the 6.82 package as it is (without NVATABUS.INF) and to replace the nForce PATA drivers by the MS ATAPI ones after the successful installation. My questions: 1. Is my summary of your findings correct? 2. Did you integrate just the original SATARAID subfolder of the 6.82 package or did you copy the content of the SATA_IDE subfolder into the SATARAID one prior to the integration? 3. How did you replace the nForce PATA by the MS ATAPI driver (real install or driver update within the device manager)? Thank you in advance for your answers. CU Fernando