Fernando 1

Hi Chuck,more interesting than your mainboard BIOS version is the version of your NVIDIA Raid BIOS (look onto the second bootscreen).You may need v. 4.84, if you want to install the new nForce Raid drivers. Answers: 1. Right! 2. You may remove all IDE Bus Drivers within the section "Hardware Support", but normally this is not necessary with nLite 1.0 RC1. 3. If you have integrated the LEGACY subfolder during textmode driver integration, you will find all files of this folder within the I386\NLDRV folder of your ISO CD, but the files are compressed (NVATABUS.INF is named NVATABUS.IN_). 4. No, there is no need to create a special OEMDIR directory, when you use nLite 1.0 RC1. Good luck! Fernando

Because the chipset driver packages 6.66 and 6.67 are not designed for nForce3 chipsets. You can see it, when you have a look onto the the drivers included. The GART driver, which is necessary for nForce3 boards, is missing in both packages.Nevertheless you can use the nForce SataRaid drivers from the package 6.66 and 6.67 for nForce3 systems. They are much better than the ones from the package 5.10. If you want to see the latest usable nForce3 chipset drivers, look here: http://www.nforcershq.com/forum/latest-dri...-3-vt60240.html CU Fernando

Take the SataRaid drivers from the chipset driver package 6.67 (LEGACY folder) and the other drivers (SMBus, GART etc.) from the package 5.10.

You can do it, but I am not sure, if you need to do it. CAT files are not really necessary in this case. You may even skip the files during the installation process and the drivers will be installed nevertheless.

There is no reason to warry about that. You can point nLite to any INF file you want - nLite copies all files whithin the driver folder and Windows XP x64 Setup will install the correct one. But I am not sure, if the Ethernet and SMBus drivers from the nForce chipset package 6.66 or 6.67 are suitable for nForce3 systems. It may be safer to take the ones from the 64-bit nForce chipset driver package v. 6.25. If you have an nForce3 board, you will need the GART driver. Take it from the 64-bit nForce chipset driver package v. 6.25.EDIT: You will find the NVATA.CAT within the SATA_IDE folder, but this file is not necessary.

Why have you not tried to integrate the new 64-bit nForce SATA drivers (LEGACY folder from the 6.67 package) as I have described in post No 1 of this thread? There is no cause to warry about the missing Raid array. Windows XP x64 Setup will not install any Raid driver, if it does not detect an activated Raid Controller.

Congratulations for your success! Concerning your question about driver upgrading I would give you the advice to wait until Gigabyte presents a new BIOS for your board with a Raid BIOS v. 4.84. Otherwise you will risk new problems. Be happy, that you can work with Windows XP x64. CU Fernando

Have a look at this thread: http://www.planetamd64.com/lofiversion/index.php/t11324.html Maybe it will help you with your Gigabyte K8N-Ultra-9.

Hi Ergo,I can understand, that you are frustrated. As you can imagine, it took me much more time than you to find at least a way to get the nForce SataRaid drivers installed with nearly each SataRaid system. Very often I was close to throw my computer out of the window. There are thousands of possible reasons for the issue you described. A computer is much more complicated than an egg-timer and you only can solve a computer problem with patience. If you cannot get a BIOS with a Raid BIOS v. 4.84, I would recommend to take an nForce chipset driver package lower than 6.66, for example the 6.56. If you were able to boot into safe mode after the installation of XPx64, your problem has likely nothing to do with the NVIDIA nForce SataRaid drivers. The 64-bit version of Windows XP is very choosy concerning all drivers (more than the 32-bit OS Windows XP). So look into your device manager, if the NVIDIA nForce Sata/Ide and Raid Controllers are correctly integrated. If this is the case, you can be quite sure, that your problem cannot be resolved by changing the SataRaid drivers or the method to install them. Some weeks ago I got a BSOD each time, when I tried to install Windows XP. This issue had gone at once after I had set the voltage of my RAM a lttle bit higher (2,7 V instead of 2,6 V), but it took me 2 full days to find this simple way to resolve my problem. This example may demonstrate how complicated things are. CU Fernando

Just have a look into post No 1 of this thread. There you can find all what you need. The guide is up-to-date and incorporates especially the use of nLite 1.0 RC1. It is not necessary at all to read all posts of this thread. CU Fernando

It is very easy to prevent the autostart of nwiz and other not needed programs: Start > Run >enter "msconfig" > OK The window "System Configuration Program" opens. Within the section "System Start" you can deactivate "nwiz".

This is the thread for the integration of the nForce SataRaid drivers into the 32-Bit OS Windows XP. If you really want to install Windows XP x64, you should discuss your problems within the XPx64 thread:http://www.msfn.org/board/index.php?s=&sho...ndpost&p=352404 If you want help, you should give some more informations: What did not work for you? What happened during the install? At which point of the installation did it happen? Did Windows Setup recognize your hard drives or your Raid correctly? Do you have a Raid array or only Sata drives? Which drivers (version and subfolder) did you integrate as textmode drivers?

I have never tried this. Ask Bashrat the Snaky himself. He is the expert concerning the BTS driver packs.

I am not an expert in manipulating boot managers and MBR's trying to combine several Operating Systems laying on different SATA (as Raid) and IDE hard disk drives, but AFAIK your problems have nothing to do with your mainboard and nothing to do with the integration of the nForce SataRaid drivers into a bootable CD. The boot order is layed down in your BIOS (first boot device: X, second boot device: Y etc.). According to those BIOS settings your system searches for the first hard disk device with a Master Boot Record (MBR), which normally is the partition with the letter "C:\". It is impossible to have 2 MBR's onto 2 different partitions named C:\ parallel and to switch from the one to the other. If you want to use your 2 Raid array HDD's (which should always be detected as 1 HDD!) with the option to switch via Windows Boot Manager to your IDE HDD's, you should do the following: 1. Configure your Raid array as you want and take the Raid array as first bootable hard disk boot device (or as the second, if you take the CDROM as the first one) . 2. If you cannot boot into your Raid array (as active boot partition C:\), repeat the installation of the OS onto the Raid array using your nLited CD with integrated nForce SataRaid drivers. After the successfull installation of the OS your IDE HDD's should be detected as well. 3. Now you have the possibility to create as many partitions as you want onto your IDE HDD's (but no disk device C:\) and to install the OS you want onto the newly created partitions of your IDE HDD's. At the end of the procedure you have 1 MBR (on C:\, which is within your Raid array) and several partitions within and without your array. Everything clear? If not, please ask an expert within an ASUS newsgroup or google around. CU Fernando

Send me a PM with your eMail address and I will send you the TXTSETUP.SIF (543 KB) of my nLited x64 CD. The drivers and all other needed files (INF and DLL) are stored as compressed files in X:\AMD64\NLDRV (X is the letter of the CD-ROM drive), but the textmode drivers are additionally copied into the AMD64 directory. EDIT 1: Obviously you are not sure, which version of Windows XP x64 you have (just copied somewhere). Put the original CD into your CD drive and look into the README.HTM, which you find within the root of the CDRom drive. There you can see, what you got. EDIT 2: Stinart, you are saving a lot of time, when you first do that: If you are sure, that you have the original english version of Windows XP x64, try to install it using the F6/floppy method. Take the driver package 6.25 (for x64) and copy all files (not the subfoder raidtool) from the folder WinXP onto your floppy. If you succeed this way, you can try it with nLite.

I have never heard about similar problems, but I am rather sure, that it is not an issue of nLite. Please answer to the following questions: 1. Do you have an original version of Windows XP x64? 2. When you have copied the content of the original XP x64 CD onto your hard disk device and pointed nLite to that path, did nLite recognize the content of that folder correctly as Windows XP x64 Edition? 3. Are you sure, that it was a "Pe" type error? Yesterday you wrote, that it was a "P11" type error (no idea, what this error message means, just to verify, if you got the same message or not). EDIT: I just googled and found this: Do you have an english or an other version of Windows XP x64? Did you try to integtrate the Multilingual User Interface (MUI)?

I thank you both for your post! CU Fernando

1. The 6.25 driver package don't have native 64bit drivers. That is the reason why they have names as the "normal" 32bit drivers (NVATABUS.SYS and NVRAID.SYS). On the other hand the new packages as 6.67 have native 64bit SataRaid drivers (NVATAX64.SYS and NVRDX64.SYS). That is the reason, why the TXTSETUP.OEM from the 6.25 package asks for the NVATABUS.SYS and the TXTSETUP.OEM from the 6.67 package wants the NVATAX64.SYS, and the reason, why you don't find a NVATABUS.SYS within the 6.67 package. Is it possible, that you have mixed the TXTSETUP.OEM files between the 6.25 and the 6.67 packages? That would explain your issue. 2. No, I don't think so. You have done something wrong during the textmode driver integration. These are the 2 drivers which nLite proposes to integrate: RAIDCLASS = "NVIDIA RAID CLASS DRIVER (required)" BUSDRV = "NVIDIA nForce Storage Controller (required)" The first one is the Raid driver NVRDX64.SYS (real 64bit) or NVRAID.SYS (32/64bit), the second is the Sata driver NVATAX64.SYS (real 64bit) or NVATABUS.SYS (32/64bit). You have to take both. At the end of the processing nLite will copy all driver files into the folder AMD64\NLDRV and the 2 just mentioned SYS-files addtionally into the AMD64 root. You should repeat your work and be carefull during the textmode driver integration part.

If the drivers NVRDX64.SYS (the compressed form is NVRDX64.SY_) and NVATAX64.SYS (compressed: NVATAX64.SYS_) are not copied by nLite into the AMD64 folder, you cannot build a bootable XP x64 CD, because the Setup cannot find your Raid array. I believe, that you have done something wrong within the driver integration part of the nLite processing. Did you really integrate the content of the LEGACY subfolder as TEXTMODE drivers? Did you take both drivers which were proposed by nLite to integrate?

Take a look into the AMD64 folder of your nLited CD using the 6.67 driver package. Is there a file named "nvrdx64.sy_"? Are you sure to have not corrupted files, when you downloaded and unzipped the driver packages? If both answers are "Yes", try the following: Create a new CD by using nLite 1.0 RC1, but this time use the SATARAID subfolder of the package 6.67. Before you integrate the SATARAID subfolder you should do the following: 1. copy the NVATAX64.INF (from the LEGACY folder) into the SATARAID subfolder and 2. make the changes within the TXTSETUP.OEM file (see above). I am really sorry, but I cannot try it myself, because I have only a PC with an nForce4 chipset. Please report about your results. Goodluck! Fernando

The Raid Bios version might be a problem, when you use the 6.67 driver package. New Raid drivers need a new Raid Bios (v. 4.84 or higher). As you have an nForce3 chipset, I suppose, that you have edited the TXTSETUP.OEM file. This was reported by a user with an nForce3 board, but he used the PATARAID subfolder from the6.66 package. Maybe the TXTSETUP.OEM files are different. Which chipset driver package and which subfolder did you use?

If you use nLite 1.0 RC1, there is no need any more to edit something or to choose "unattended install" etc. For details look into post No 1 of this thread. My tip is to take the LEGACY subfolder of the nForce chipset driver package 6.67 for the Textmode Driver integration. If you still have any troubles, post it here. But without any details about your current system (chipset of your board, Sata or Pata hard disk drives, Bios version etc.) it will not be easy to help. CU Fernando

Either you are in the wrong thread (the theme here is the integration of the nVRaid drivers into the 32bit OS Windows XP) or you have taken the wrong driver package (the file NVRDX64.SYS is a 64bit driver and only dedicated for Windows XP x64 Edition). If you want to see the method how to integrate the drivers into a Windows XP x64 CD, look here: http://www.msfn.org/board/index.php?s=&sho...ndpost&p=352404 Since I started this thread, my only intention was to give all users with an nForce SataRaid system an as-easy-as-possible guide how to integrate these weird drivers into a bootable CD without BSOD and reboot loopings at the end. The main thing is the result (that the integration succeed and the OS works) and not the way to go. Maybe your method (copying a lot of files into the SATARAID subfolder instead of just using the PATARAID subfolder) is better for you or shortens the installation time of the OS (I need 7-10 minutes with my system), but this might not be important for other users and especially for newbies. Your jpegs in your previous posts are made after the complete installation of the OS (and a safe mode manual reinstall of the drivers?), but the problem occurs during the hardware detection at the beginning of the GUIMODE part of the installation. MS does not trust the NVIDIA drivers (look into the SETUPAPI.LOG). @ RickSteele: Let us stop this academic and totally useless discussion. Be happy with your special and maybe better way to integrate the nForce SataRaid drivers and enforce your efforts to find a way to integrate the Creative Audio drivers. But this is another theme and has nothing to do with this thread. Good luck! Fernando P.S.: If you want to answer by quoting, you only have to cklick on the "Quote"-button with the yellow balloon on the right hand bottom place of the post.

As you have seen yourself, there is no reason to copy these files into the SATARAID subfolder prior to integration. It is easier and at least safer to integrate just the LEGACY (package 6.67) or the PATARAID (package v. 6.66) subfolder without any changes. With no kind of mixture of these files you will manage it, that the Windows XP Setup routine accepts the NVATABUS.SYS and NVRAID.SYS as WHQL-certified drivers. You can verify this at the end of the installation, when you have a look into the file SETUPAPI.LOG (you find it within the Windows folder) and search for those nForce drivers. CU Fernando

Where do you have a folder called "NVRAID"? Do you mean the SATARAID subfolder?