speedyz

Thanks Fernando, again... Re NVIDE, I am loading burning software to see what the effects are (will report). I have reloaded the 6.70 driver pack (after successful windows install) to install the NVRAID tools software, about 70 dlls and 2 exe's, as well as making sure everything else is the way it should be. During Windows setup the RAID started sychrnoising as soon as Windows setup loaded the driver; pretty neat- as I was able to do the unattended install without any hassles whilst this was happening. Having horrible experiences with sophtware RAID (silliconimage, etc.) and hacking Linux kernels prior to the newer modules, I was not so keen about this and was glad to have got down to building a CD with the appropriate drivers- now I can boot the Recovery Console and access the array should I ever need to! Without you I couldn't have done this- and unfortuantely Shuttle has been shipping bad SATA cables on my box, resulting in a lot of bad posts all over the place about the 6.53 RAID not working. Researching that led me here and now I know enough to be happier- ie not just that 6.53 was probably ok after all but that my DRP will work so that is good. Plus I don't have a floppy drive in this new box anyway, so Windows setup's ancient F6 driver load routine was a PITA to do also . More soon...

Well it worked... the bloody thing worked. Absolutely brilliant stuff; the nlite devs, fernando, Rick- you guys are absolutely unbelievable... I'll report back with my findings in terms of array reliability, etc.I am not 100% sure it was the nvide.nu file I needed added in, but if you need to know Fernando I can try it again... So far, I have boot, all items installed, healthy raid, disks partitioned the way I want... and very nice perfromance indeed...

Thanks Rick, am trying this now. Your case didn't sound like BSODs though... are you using NF4 on AMD?

After windows loads mup.sys it loads the registry. If one of your hives is corrupt, it may reboot at this point without an error message. I have had this happen before due to bad SATA cables causing a machine to reboot at (roughly) weekly or bi-weekly intervals, and not working out the cause before this was happened.I'd bet your registry is not being built correctly during install. Try other options in nlite perhaps, but it could be a driver problem for all I know...

Heh, Fernando- the beer in Australia is better than the beer in America (But the beer in Germany beats anyone's I know...) This thread has been very interesting to me as I am using a Shutle SN25p w/AMD-64 (Nvidia NForce4c chipset)... and hope to run RAID 0. The motherboard in this machine should not be very different from any other NF4-based mobo. I know of noone else using this combination successfully until I got onto msfn.org, and wish I could report success, or gather more of a clue from the msfn forums (pls excuse my ignorance)- I have only just started using nLite! The problem I have, after following the instructions (thank you *very much* Fernando) which took me through using nLite to create an XP unattended install disk, is that (trying the fresh disk out) Windows setup does not enter the second stage, it simply finishes the 'loading files' part (the first section where it prompts for additional floppy-based drivers), displays 'Starting windows' and then a few seconds later blue screens. Have not even got to the user agreement or the drive utility- so think this must be driver related. I am using nForce 6.70, made the changes specified in Fernando's first post exactly. Should I try using nlite RC1.05 or 1.06? I believe my version (RC1.04) is the current release as there is nothing mentioned about later versions than this I can find (but I haven't gone looking for a CVS on this yet). I am unsure if the text (txtsetup.oem) file changes discussed with Fernando and others a little way back in this thread could be part of the problem? I can't seem to find clear (to me) details, but am re-reading all that for the 3rd time... Perhaps posters are talking about RyansVM when saying these versions? AFAIK the only drivers reported working on my rig (as reported on this forum are the manufacturer supplied ones; v6.53 (I think) - as reported by the member Q-Fireball in this thread http://www.msfn.org/board/lofiversion/index.php/t51244.html) Many thanks for any pointers... I'm pretty stumped trying to work out what text file changes are necessary, or if I should be using RC1.05, RC1.06 or just give up and use the old driver (which is 'reported as unstable' in the Shuttle forums)