scstrato

Member
  • Content count

    4
  • Joined

  • Last visited

Community Reputation

0 Neutral

About scstrato

Profile Information

  • OS
    XP Pro x64
  1. I have good news and bad news to report. First, I downloaded a copy of DBAN to rid myself of that pesky partition where nvraid.sys was hiding. Problem is, there was no hidden partition. Even after doing this I still received the exact same error message. The good news is I now have a working OS installed with a healthy RAID. On a whim I decided to try another build using nLite, however, this time I did not use the direct burn method. I used the exact same method you described above, same drivers and copy of OS, but I created an ISO first then burnt the image to disk. Voila! I have no idea why this made a difference, or even if it was the issue to begin with, but I am very, VERY happy. Thanks for the patience!! Cheers!
  2. If you have done what I had recommended, there is only 1 explanation: The driver has been integrated into the XP x64 CD, which you had used as source.Questions: 1. Is there a file named WINNT.SIF within the i386 or AMD64 directory of your "original" XP x64 CD? If yes, which is the content of the file (open it with the Editor)? 2. Is there a file named NVRAID.SYS or NVRAID.SY_ within the AMD64 directory of the OS CD? 1. Confirmed. No WINNT.SIF file anywhere on the disk. This is a certified Microsoft windows installation disk, not a copy. 2. There is no file named NVRAID, period, on the disk. I even exported the .CAB files and unpacked them using winrar. Nothing. So, is it obvious that the NVRAID.sys file is still on the hard drive (not loading during installation)?
  3. No such luck my friend. After following these steps I received the exact same error message referencing "nvraid.sys". Obviously this file is the root of my problem, the question is where is this driver coming from? Originally I thought maybe GParted didn't actually format the drives properly but now I'm thinking the Win XP install disk is loading it during install. Is there a way through nlite (or other utility) to disable this driver altogether and force the use of the integrated drivers? Isn't that what nLite is supposed to be doing for me by creating the disk with integrated drivers?
  4. Hello. Newbie here. I've been following this posting for several hours now while I work on a friends machine and I simply cannot get past the following error msg: "The device associated with following device driver will not work correctly on this computer: nvraid.sys. The device driver is not compatible with the x64-based version of Windows your computer is running" First, forgive me for my inexperience with RAID setups. I have verified all the steps in your tutorial are correct; RAID enabled in BIOS, array cleared and healthy and unattended win xp 64b boot disc created with the driver from the "64bit nForce SATARAID drivers v9.99.09 mod by Fernando" using nlite. Some quick details about my issue. The PC was originally running with Vista but the owner has had problems since inception with corrupt arrays. He purchased this copy of Win XP Pro 64 bit and has asked me to load it for him. Obviously it does not have a floppy drive. So, If I am following your tutorial correctly, I'm guessing I have one of two problems, or both: 1. The Win XP 64b install disk is Service Pack 1. I have downloaded the SP2 installation file but when I try and incorporate that into the unattended installation setup thru nlite I get an error because the machine I am using is a Vista 32bit machine (only 64bit slipstreaming is supported from a 64bit OS). Is there any correlation to my issue here? -and/or- 2. As I have underlined and bolded above, the error msg specifically indicates the problem is with driver: nvraid.sys. Again, if I am following your tutorial correctly, shouldn't this driver be: nvrd64.sys? If this is the case I am guessing that deleting and clearing the array is not erasing, or allowing an over-write of, the old driver? Any and all help is greatly appreciated (even if it's some little stupid step I missed).