Fernando 1

Yes, it is possible to create a valid floppy disk with the nForce SataRaid drivers. But if you try to install the newest nVRaid drivers (off the package 6.66 or higher) by F6 method, you risk to get endless reboots at the end of the install (Reason: see post No 1 of this thread).According to my experiences you have the best results, if you do this: 1. Download the nForce package v. 6.53 from here: ftp://download.nvidia.com/Windows/nForce/standalone/6.53/ 2. Unzip the package and copy the whole content of the IDE\WinXP directory (without the RAIDTOOL subfolder) onto a formatted floppy disk. 3. During the install you have to integrate both required drivers. After the completion of the install you can update all nForce drivers inclusive the SataRaid ones by just executing the setup.exe of the nForce package v. 6.70. CU Fernando

Thank you for the information. I will check it and correct my guide regarding this point if necessary.CU Fernando EDIT: I checked the nForce driver package 6.82 and found, that there is no NVCOI.DLL within the SATARAID folder. For this reason I did not change the quoted text within my guide (post No 1).

Hi RickSteele,thank you for your interesting report. As a reaction of the discussion about the NVIDE.NVU file I have replenished my guide in that way, that it might be useful for some users to add this file too, if they take the SATARAID instead of the LEGACY subfolder. Concerning the ReinstallBackups directory I can affirm your discovery, but I found there even other drivers, which I had integrated by nLite too (for example the NVIDIA Forceware and the monitor drivers). So I think, that this is nothing to warry about. The differences of the designations of the "Local Area Connections" are only cosmetic. CU Fernando

These are very useful informations.Please report about your further findings. We should know, for whom the NVIDE.NVU is important and for whom not. EDIT: The NVIDE.NVU is neither a driver nor a coinstaller file. It contains the following informations (extracted from the 6.70 package): As the file contains only informations about the uninstall of other files, I am really surprised, that it might be necessary for the install of the SataRaid drivers. I have very often installed the 6.70 drivers by using the SATARAID subfolder (plus 3 files, but without the NVIDE.NVU) and never got any problem or "missing NVIDE.NVU" pop-up message during the install.Notice: The PCI device VEN_10DE is the NVIDIA Memory Controller.

I like VB and XXXX! The latest version is nLite 1.0 RC4. Why don't you integrate them? After you have succeeded with the install, you can try to update the drivers (if you have a Raid BIOS version 4.84 or higher). Other users had resolved their problems by deleting the file NVIDE.NVU (look here: http://www.hardwareforums.com/16279-post-5/ ).After having googled I found this interesting link for Shuttle SN25p users (maybe it is useful for you): http://forums.sudhian.com/messageview.cfm?...&threadid=83035 One of the advices is to raise the RAM voltage to 2.8 V. CU Fernando

Be aware, maybe I am coming someday... (and I am very thirsty!)CU Fernando

It looks like a hardware problem, which has nothing to do with the integration of the nForce SataRaid drivers.Look here: http://www.hardwareanalysis.com/content/topic/31874/ http://www.earthv.com/tips_detail.asp?TipID=63 Within another forum someone wrote, that the same problem was solved after updating the BIOS of the graphic adapter. Hoping that you will find the reason for your problem Fernando

As I just realized your Plextor is a Sata device.I bet, that the Plextor is the reason for your trouble. Look here: http://www.plextor.com/english/support/PX-...y%20listing.htm My tip: Remove the Plextor and use for the install of the OS an other CD drive device. After the successful install of Windows XP you can reinstall your Plextor. CU Fernando

I can understand you - I would be angry too!That fact, that you cannot set your Raid as bootable, is a severe thing. If you don't have done something wrong, this issue refers to a hardware problem (Raid Controller malfunction?). By the way: Asus recommends for your board to take the new nForce driver remix package 8.22, which you can download here: http://dlsvr01.asus.com/pub/ASUS/mb/socket...32nforce822.zip I have no experience with this driver package, but maybe it is useful for you. CU Fernando

TStein has pointed it out: It is very difficult to write a guide about the nVRaid driver integration, which is useful for everyone, easy to understand and simultaneously totally correct.As a result of his post I have made some changes within the "Driver Preparation" part of my guide (first post of this thread). I hope, that my guide has gotten more understandable and not too complicated. If you still find something misunderstandable or if you have a better idea for an easy guide, please let me know it - nobody is perfect! CU Fernando

Hi TStein,thank you for your post. The way you did it is not the easiest, but the safest method to get the nForce SataRaid drivers integrated. A little correction: In step No 2 you mean the NVCOI.DLL (and not the IDECOI.DLL, this file is already in the SATARAID directory). CU Fernando

Done (into the 32-bit thread)!CU Fernando

Congratulations! How did you do it (F6 or with nLite? That will be difficult - you have to wait for a new RAID BIOS for your Shuttle. It is evident, that your Raid Controller does not work with actual drivers.CU Fernando

It works, because the drivers (SYS files) of both packages have the same version 5.52. The DLL files are coinstallers and needed for a correct installation of the drivers (NVCOI.DLL is needed for the NVATABUS.SYS and "called" by the NVATABUS.INF) The CAT files contain only informations about the certification status of the depending driver (NVATA.CAT is responsable for the NVATABUS.SYS, NVRAID.CAT for the NVRAID.SYS). CAT files are not really necessary, but may be useful with weird drivers as the nForce SataRaid ones. Thanks again - I have already edited my guide! CU Fernando

You are right! I have just checked it. The link is correct to the 32-bit driver, but what you get is the 64-bit one (wrong link by NVIDIA). Thank you very much for your information. I will put the correct link into post No 1 within the next minutes. That was a very good idea too! Until now I did not propose to take the 6.69 package, because it is a bit complicated to take the correct files. I will mention this way within my guide (post No 1).Your post was very helpful - thanks again! CU Fernando

That might be the reason for your trouble. It seems to me, that you still have parts of the boot sector (made by your first test without Raid) on the start position of your Raid array.Tip: Do the formatting of both hdds and then try to enable the bootable option. Yes, that is the newest one. I have no experience with that version. That was a mistake. You should have taken the NVATABUS.INF off the LEGACY subfolder. Athough both files are very similar, the NVATA.INF has only informations to install the - not-existant - NVATA.SYS.

Yes, as long as your Raid is active, the first hdd (with the boot sector) shows 320 GB (the size of the Raid=2hdds), whereas the second hdd shows the rest (the size of 1 hdd). Between IDE and SATA I hdds there is not a big difference in speed.CU Fernando

Hi Mpastreich,before you can start with the install of an OS onto a Raid array, you have to ensure, that a. both Hdd's have not been used before (brandnew) or made "totally clean" by low level formatting, b. the Raid has been built as it should (Raid activation in BIOS, configuration of the RAID via F10 inclusive activating as boot disk) and c. that the RAID is the first bootable hard disk device (to do within BIOS). First sign of a successful configurated RAID is, when you see, that it is "healthy" on the second boot display. If you have a floppy drive, you can test the TEXTMODE part of the XP install via F6 (if you have a Raid BIOS version 4.84, you can take the files from the SATARAID subfolder of the 6.70 package, but you have to add the following 3 files: NVATABUS.INF, NVCOI.DLL and NVATA.CAT, you find them in one of the other 2 IDE\WinXP subfolders). If Windows Setup detects your Raid system as 1 disk, you can nearly be sure, that the driver integration method (post 1 of this thread) will work on your system too. Then you can start with the install of your nLited CD with integrated nForce SataRaid drivers. CU Fernando EDIT: 1. Don't touch your healthy Raid array by shutting off the Raid Controller and trying to install something on one of your Sata disks. 2. You should integrate SP2 into your nLited CD.

Hi Mike,on the Shuttle homepage I found the following guide for the installation of XP (32-bit version) onto a a SN95G5 with a SataRaid system: http://www.shuttle.com/share/fae/hq/faq/sf...N95G5%20XPC.htm Try that! If the install succeeds, please let me know, which version and which special combination of drivers and information files are needed to get the Shuttle SN95G5 to work with a SataRaid system. If the install fails, bring your Shuttle mainboard back to your vendor! In spite of your problems with your Shuttle I wish you a happy New Year Fernando

If I were you I would bring the mainboard to the dealer where I bought it and let him test the Raid Controller.

wow i really hate shuttle, and there is now way to hack it?Theoretically it's possible to integrate the 4.84 RAID BIOS into the actual Shuttle mainboard BIOS with a tool named CBROM, but 1. this is very dangerous if the procedure fails and 2. NVIDIA won't send you just the RAID BIOS. Good night! Fernando

Let it be, you will be disapointed again.I make the conclusion, that you can not install XPx64 on your Raid array with native nForce 64-bit Raid drivers as long as Shuttle don't offer a BIOS with integrated Raid BIOS v. 4.84. The reason for your trouble are the Raid drivers, because the nForce Raid Controller don't support them because of the lack of an actual Raid BIOS.What I don't understand is, that you even can't install XPx64 with the old SataRaid drivers off the 6.25 package. Have you ever tried to install them by F6 with a floppy (all files of the IDE\WinXP folder without the RAIDTOOL subfolder)? The only possibility I see is, that the Raid Controller is damaged. To verify this, you should try to install Windows XP (32-bit) onto your Raid array. We in Germany would say: I am at the end of my Latin! (That means: I am at my wits' end!) CU Fernando

The text is not so important and mostly points into the wrong direction.Interesting are the first numbers and letters from the stop message STOP: 0X000............(..........). If you can read it, post it to me. It seems to be the STOP: 0x0000007B message, which is described here: http://support.microsoft.com/default.aspx?...Ben-us%3B324103 The possible reason is a hardware or driver conflict. My tip: Try to enhance your RAM voltage within BIOS a little bit (0,1 V). Sometimes this has helped! By the way: Did you enable ACPI within your BIOS? Otherwise you can cancel your test. CU Fernando

I told you what to do to see the error message. What sort iof message did you get? Do the following:1. Create a new folder on your desktop and call it XPx64 (as example). 2. Copy the whole content of your original XPx64 CD into the just created folder. 3. Start nLite 1.0 RC4 (requires .NET Framework 2.0) and point at your just created folder. 4. Go forward until you get the big buttons with the different tasks. 5. Just choose "Integrate Drivers", "Unattended Setup" and "Create a bootable ISO". 6. Within the section "Integrate Drivers" just integrate the LEGACY subfolder of the 6.67 package as textmode drivers. nLite says, that 2 drivers are required - take them both by just clicking OK. 7. Within the section "Unattended Setup" on the "Information" side remove the check on OemPreinstall and choose "DefaultHide" as Unattended Mode. Within the "General" side just let the "Computer Type" as "automatic" and put your Cd key into the fields. 8. After the end of the processing and the creation of the ISO file burn it as bootable image with Nero. If this install fails try the following: 1. Recall nLite and point it again to your just nLited folder XPx64. 2. This time choose only "Remove Components" and "Create a bootable ISO". 3. Whihin the section "Remove Components" cancel the Compatability list and then open the part "Hardware Support". Remove all IDE Bus drivers (there are 5 of them) by clicking onto the small window in front of them. 4. After the processing of nLite create a new ISO file and burn it as bootable image. Good luck! Fernando WARNING: THIS NIGHT I WANT TO GO TO BED EARLY AND I WON'T STAND UP AT 03.30 am!

What means "nothing"? What happened? What sort of BSOD message did you get at what point of the install? Did you try the install with floppy (F6)? The 6.25 drivers should work by using the F6/floppy method too. Try the 6.67 (LEGACY subfolder without any changes).Good luck! Fernando EDIT: Take just the SataRaid drivers and nothing else until we solved the problem with these drivers!