RickSteele

Yup, it can, the HDD and IE7b2

All of you do yourselves a huge, unfanthonable favor and purchase Terabyte backup and partitioning software-garanteed the absolute best ever before and to come. Go here: http://www.bootitng.com/company.html

jcarle 4 74G Raptors in RAID 0 on an A8N32-SLI Deluxe........redifines fast I'm using IE 7 beta2 and am experiencing no problems but I do not like the layout. You can not cannot put the Toolbars all on one line up top for instance; and the way it handles "Favorites bugs me.....not impressed yet....am going to roll back.

troyquigley "i tried that it did not work" Extract all the files, remove the X64 folders as previously stated and use nlite 1.0rc5 to integrate as drivers. I have not tried this yet but am going to this weekend.

PhanTom Just installing VMWare again ..gonna test it there first...then prob a full fresh install...this first NLited install on new system seems to have some quirks I can't really figure out...sucvh as Windows Installer service not starting as it should (even when it's set to automatic) Firstly when nliting if you are slipsreaming sp2 into a previous winXP build, complete this first by itself and exit nlite; then relaunch nlite and slipstream all of the hotfixes/updates; exit nlite again and defrag/reboot. At this point slipstream WMP10 if you use it afterwhich launch nlite and slipstream all WMP10 updates; defrag and other than updating this folder with the new monthly hotfixes/updates, do nothing else with it and save it as "winXP....original" or whatever name you wish-sans quotes and backup to CD-RW/DVD-RW. Now you have an unmodified base os completely up to date. Create another folder and name it winXP... or whatever, copy all of the "...original" folder to here and nlite customizations in this one. Now, if an nlited custom install fails you at least have a fully updated os to install-albeit using F6. If you do not slipstream the sp alone I have found that the files-especially in gp-do not show as updated-no end to the grief-your concern was among my experiences. Also, follow fernando's driver integration guide using 6.82 and some files/one folder from 6.70. My ASUS A8N32-SLI Deluxe is running beautifully on a 4kb stripe...and fast.

Fernando 1 "So you succeeded finally? How did you do it (F6 or nLite)? Which nForce SataRaid driver version did you install?" Either way on either mobo using 6.65, 6.70 on the Premium and 6.82 on the A8N32..., with or without F6, or nlite. The driver concern only affects the ATAPI drives for me and their recognition/functionality during and immediately after setup. Also, I owe you an apology. I've just now completed a fresh install on the A8N32-SLI Deluxe modifying the sataraid folder in the 6.82 driver set as you outline in your guide, nliting winXP pro using these modified drivers and voila; here I am typing this with the NVIDIA ATAPI sw drivers installed. All went perfectly. The nvide.nvu must also be copied-setup looks for it-popup as before.......... I do not know what I did wrong before. I also had an issue with creating bootable DVD's. nuhi is working with me on this one in another thread so........I'm just wondering if this is gone too. The F6 method on this mobo I found very unstable for the ATAPI only; ie: the DVD-RW never seemed to operate smoothly as before on the Premium mobo. Possibly the MS drivers do not play well with nforce and the 6.82 contain no NVIDIA sw drivers even though manual installation in safe mode asks you if you wish to install....The MS ones remain on reboot. Thanks for your interest and patience; sorry again for my error. One last thing that might be of interest: no more "ReinstallBackups" sans quotes in system32 with this install; and upon entering Safe Mode to manually install the 6.82 on this A8N32-SLI Deluxe using the same folder I pointed nlite 1.0rc5 to during driver integration for my ISO, the NVIDIA sw drivers installed this time-I copied the entire "Legacy" folder to the 6.82 from the 6.70 and also copied the requesit files from there to the 6.82 sataraid folder; so go figure!

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! Migrated from A8N-SLI Premium and 6.70 drivers-4 WD 74G Rapters all installed in the correct sequence; ie: SATA 1, 2..etc..and the RAID array was recognized and valid. Endless reboots at logon; I would imagine due to the conflict in the ATAPI drivers-one using nforce switched and the other calling for default MS. 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. They are all IDE. Also, I'm not sure this belongs here but, on nuhi's web page in the FAQ section is a reference to 4KB stripes not bootable/working at all in winXP pro. That is how I run my array-4KB stripes ever since I was able to on the A8N-SLI Premium-BIOS update added this option; and right now I am typing this reply on an ASUS A8N32-SLI Deluxe, 4 WD74G Rapters in RAID 0 using a 4KB stripe. Never any problems and much quicker than 16 and up.

Users with an nForce4 AMD/Intel SLI X16 mainboard may take the SATARAID subfolder of the new nForce chipset driver package 6.82 (download it from here), but they have to add the NVATA.CAT and the NVCOI.DLL (from the SATA_IDE subfolder) and the NVATABUS.INF (from the LEGACY subfoder of the 6.70 package) prior to the integration. Does not work for me on A8N32-SLI Deluxe-Microsoft drivers for ATAPI still installed and DVD-RW recognition during setup is through command line only; ie: G:\....... or H:\......... Also, on one occasion only I got endless reboots after GUI finished.

rabidfan "Your method worked perfectly for me, save one detail" Learn something new everyday

WhiteWizard, "I tryed the floppy with the WinXP/Legacy folder from the 6.70 but keep reciving the error." nforce4, as with all of NVIDIA's chipsets, are very finnicky and compatability does not seem to be a consideration. Try this; enable the NVIDIA controller in the BIOS, enable RAID for only those drives you will connect, reboot saving changes on the SiiL controller. When up and running on the SiiL controller enter Device Manager and right click the "Unknown Device", hit update drivers, point to your F6 floppy disc and allow the drivers to be installed. Reboot, then reboot again; only this time enter BIOS setup and disable the SiiL controller. Reboot, saving changes, shut down your PC manually when it will boot no further. Move your drives to the nforce controller, power up your PC and turn it on. Make sure your HDDs are plugged into the correct SATA plugs; ie: SATA 1, SATA 2....so forth. If this works, reboot a final time into Safe Mode and run the 6.70 setup.exe. Also you must remember that the nforce4 F6 option shows 2 driver classes when you hit "S" for select; you must hit the first one and enter, then hit "S" again and select the second choice and hit enter again-then, continue on.

To WhiteWizard "Can anyone tell me is there's a way to make a functional NVIDIA nForce™ RAID Class Controller driver diskete whitout integrating in the XP CD" Download the 6.70 drivers from Nvidia's site, extract them and copy all of the IDE\WinXP\legacy files to an empty, freshly formatted floppy; just those in the "legacy" folder. this is your F6 diskette. After successful completion of install, reboot into Safe mode and run the setup.exe for these drivers.

So I think, that this is nothing to warry about. I agree but, just to close this up with a little footnote, I use Terabyte partition and backup software. When integrating using the Legacy folder Image for DOS performance-which translates to HDD performance-is very seriously impared until the nforce4 setup is run. This does not occur when using the sataraid folder with the files aforementioned copied. Oh, by the by, this is a great thread-much appreciated by all; thanks

"Please report about your further findings. We should know, for whom the NVIDE.NVU is important and for whom not. I've always included that file but missed doing so for the DVD image created for the erroneous install. I've extracted the ASUS 6.65 F6 drivers downloaded from their website for comparison and the nvu file is included. These drivers install and work error free also. One other anomoly I've noticed is at the end of any successfully integrated setup I always find the nforce 4 drivers integrated enumerated in system32\ReinstallBackups; as if they were uninstalled and reinstalled again during setup; yet no errors during setup, or any setup messages, and the windows setup error log is empty. Further, if I choose "hide default" in winnt.sif "Local Area Connection" in Network Connections, and in the registry, is labelled "Local Area Connection 2". When "Provide Default" is selected this does not occur; ie: only Local Area Connection is present. The internet works fine in both cases.

GUI looked for nvide.nvu-"could not copy...."- available in either the SATA or Legacy Folders-6.70-when using the sataraid folder for nlite txtmode integration. In addition to nvcoi.dll, nvatabus and nvata.cat one should also copy nvide.nvu to the sataraid folder before nlite integration. Without nvide.nvu my DVD-RW's were neither recognized or assigned a drive letter by PNP and the drivers had to be installed manually.

3 days and about 6 hours later; I'm still stuck on the silo trying to get through sniping the mortor teams-the closest I've come is 43seconds-what am I doing wrong? I'm playing at the most difficult level-Veteran

@Fernando 1 Let us stop this academic and totally useless discussion. OK

@ Fernando 1 As you have seen yourself, there is no reason to copy these files into the SATARAID subfolder prior to integration. Wrong; doing so integrates the NVIDIA sw drivers for my DVD/CDROM or ATA drives instead of allowing the generic MS ones-a performance bonus for me-and all ATAPI drives are properly recognized and useable within Windows Explorer during GUI setup and onwards-which was not the case before except through command line execution; also important for my personal setup routine; ie:during command file setup for app installs-mine is user attended and DVDROM recognition in Explorer is required. Finnally, these are not true SATA_RAID drivers and manual install does not install these for SATA drives. NVATABUS.SYS and NVRAID.SYS as WHQL-certified drivers... Refer the jpegs in my previous posts to you-they already are integrating the sata_raid folder as discussed-only the ATA/ATAPI are not showing signed, but, are stable and completely functional.

@dale5605 I have tried integrating the 2.08, the 2.05, and the 1.84 drivers.. I don't remove much using nlite-just the eye candy; screen savers, msn, colour schemes, images, display drivers etc. I use a common sense approach to spanking XP-pro sp2. For instance, I cannot remove sound devices in the drivers section; I forget why now-tried it once-way back-created all kinds of problems in many of my apps etc. The 2.08 drivers integrated correctly using nlite 1.0b6 with the exception of the ctac32K.sys file in the original SBA2_PCDrvBeta_LB_2_08_0002\Drivers\wdm\win2k_xp\i386 folder-nlite b6 did not even cab/copy this file or the win2k_xp\i386 folder during integration; resulting in a file copy error during GUI setup. I just cabbed it and created the folder in I386 in NLDRV\win2k_xp, then modified the dosnet and txtsetup accordingly to point to this driver and voila-for me anyways. Creative's 1.50 always integrated no problem, but the 1.55 had to be installed manually after setup and reboot was complete because the 1.50 was prerequisite. the manual update is done in Device Manager-right click and update driver, point to the extracted 1.55 folder...and so on-never using Creative's setup. nuhi even said not to integrate creative drivers.. new to me

@Fernando 1 I am waiting for your next report. Could not wait 'till Sunday and have just finished a complete fresh install. Copied the nvata.cat, nvcoi.dll and nvatabus.inf to the sataraid folder prior to integration with nlite and let nlite create the initial answer file in the process, using his own OEMinf customization. The ATA/ATAPI drivers only showed up unsigned still, all others show WHQL as before so, nothing changed; has to be something in the way setup.exe registers the files because, as before, manual install rendered all drivers WHQL. The Creative SBA2_PCDrvBeta_LB_2_08_0002 drivers still exhibit the same behaviour-no console, no sound, the older ones integrated successfully every time for me. Had to manually install the sound drivers again.

@dale5605 Creative drivers simply do not integrate properly.. Never had a problem with the others-only the SBA2_PCDrvBeta_LB_2_08_0002 just use the "legacy" folder from the 6.67 drivers, don't mess with the 6.66 or sataraid folders, it will only cause pointless problems... The inf's are different and reference different coinstallers etc., but I will make a fresh ISO and try with only the Legacy drivers integrated and try it on a fresh install. Keep in mind that this nvraid.inf references the cat file in the sataraid folder...which means only manual install will render them WHQL; until nvidia's setup routine is deciphered. this is unrelated to the nvidia integration... ????-never said different

@Fernando 1 Where do you have a folder called "NVRAID"? Do you mean the SATARAID subfolder? Yes

I think I'd agree with this........ I believe if you copy the nvata.cat, nvcoi.dll and nvatabus.inf to the nvraid folder prior to integration with nlite and let nlite create your initial answer file in the process, using his own OEMinf customization, then the drivers will show up WHQL because all of the inf's make reference to this same cat file in the SATA_IDE folder and coinstaller in the Legacy folder. I'll know better on Sunday. But, keep in mind that in order to have WHQL on all my drivers I must manually reinstall after setup in safe mode. Also, I only remove the eye-candy and things like MSN Explorer. What do you think? Only the ATA/ATAPI drivers show up unsigned; as before-manual install corrects this...so it did not work.

My System: ASUS A8N-SLI Premium, AMD FX-55 Clawhammer processor, ASUS EAX850XT PE 256mb PCIe, Audigy 2 ZS, Sony LCD SDM-HS95PS-DVI, Corsair TwinX1024XL 3200 Pro, 4*WD 74G Raptors in RAID0 on nforce4 chipset, Lian-Li PC-75 case, 1*LG 4163 and 1*Plextor PX-716A DV-RW, Panosonic floppy, Sycom 1000va UPS, Enermax EG701AX-VE SFMA 2.0 (600W) Power Supply, Labtech 580e 5.1 THX speaker system, HP Deskjet 940C, Logitech MX518 Gamers Edition mouse I believe if you copy the nvata.cat, nvcoi.dll and nvatabus.inf to the nvraid folder prior to integration with nlite and let nlite create your initial answer file in the process then the drivers will show up WHQL because all of the inf's make reference to this same cat file in the SATA_IDE folder and coinstaller in the Legacy folder. I'll know better on Sunday. But, keep in mind that in order to have WHQL on all my drivers I must manually reinstall after setup in safe mode. Also, I only remove the eye-candy and things like MSN Explorer.

This popup message is not an issue. I agree, never caused me grief.

If you look into your device manager and open the properties of the NVIDIA nForce4 Serial ATA Controller (device group IDE ATA/ATAPI Controller) and look into the driver details, you will see that the NVATABUS.SYS is not WHQL-certified. <{POST_SNAPBACK}> Not so, all nforce drivers are WHQL after manual install-refer the nforce SATA controller properties.jpeg attached below, the previous attachment was also from driver properties in device manager. At least this is the case on my system.