• Content count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About mpastreich

  1. I'm not agry with you. I appreciate all the work you've done and the help you've given. I wonder if the RAID controller is having a problem with the SATA 300 disks (WD2500 Caviar SE16)? or the SATA DVDR? (plextor PX-716SA), or some combination of the two (I noticed when I loaded WindowsXP on an IDE drive and then was initializing the RAID array through the Windows interface, accessing the DVDR while the array was initializing, or synchronizing caused Windows to BSOD). I'll do some playing with the 8.22 driver remix package tonight. I'll also try playing around with a combination of removing the DVR and seeing how the RAID controller reacts. I'll let you know how it goes, and thanks again for your help.
  2. 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. Okay, I tried doing the formatting for both hard drives and then building the RAID array and trying to set it to bootable. No luck, still grayed out. I tried building the array, booting off a different hard drive, and then formatting the whole array. Then tried rebooting and seeing if I could make it bootable. Still no luck. Tried pulling the drivers from the Legacy folder as you suggested and using a CD with SP2 integrated. No luck. Tried tuning that installation into an "unattended installation, no luck. Tried pulling the files from the SATARAID folder, with the extra files you suggested, and putting them on a floppy to install during a WinXP2 install. No luck. Next I guess I'll try a fresh nlite build of SP2, the sataraid/ide drivers (with the legacy .inf), and the unattended and see what happens When I started making this machine last week, I was hoping to finish with it before I went on vacation. I spent 1/2 a day putting the pieces together, I didn't think I'd devote another week (or more) of my off hours time to getting the OS installed. :angrym:
  3. First off, thanks for the speedy reply. a. They are both brand new drives (although one of them was then used to test installing the OS without RAID) b. F10: The array is build, and shows up as "healthy", however no matter what I do the "" bootable option is greyed out, and the bootable column shows up as "N/A". I have however been able to set it as the first boot device in the BIOS boot menu. "MediaShield IDE ROM Bios Version 5.50" (assuming this is the Nvidia RAID bios) I tried the bootfloppy method since the machine currently has a floppy dangling out the side of it (yeah for 10 years of doing this sort of thing and having parts lying around ... even if I had to go to Radio Shack to get floppies) using both the whole of the "Legacy Directory" and the 6.70 directory with those files you listed added in from the sata_ide directory. Note: there isn't a NVATABUS.INF file in the sata_ide directory, just a nvata.inf file so I added that. In both cases I got a BSOD when it tries to start up the GUI portion of the installation (the bottom status line reads "Starting windows..." the keyboard lights flash once, the monitor goes to black, and comes back up with a BSOD stating "A problem has been detected and Windows has been shutdown to protect your computer. ... STOP 0x0000007B ( ... )" Suggestions? EDIT: tried integrating SP2 into the directory where nlite had integrated the Legacy drivers then burned the installation to an ISO. Same BSOD as above.
  4. Hi, My hardware is: motherboard: asus A8N-VM CSM processor: AMD 64x2 4400+ memory: crucial 1GBx2 DDRAM hd: western digital WD2500KS (250GB SATA300) x2 dvd: plextor PX-716SA I've been trying to install WindowsXP Pro onto the HDs in a RAID1 configuration. I've got the nvidia raid settings in BIOS, and i've configured it in the boot setup. When I don't install any extra drivers, the system finds no drives to install on (makes sense). When I try to install after shutting off the RAID controller, I can install onto any one drive (not what I want, but I'm almost ready to take it). When I try installing the nvidia drivers during setup, I always get a STOP: message (blue screen, no other text BUT the STOP code). When I try installing the nvidia drivers by following your instructions at the top of this thread (6.70 drivers, grabbing the Legacy Folder, WinXP PRO no service packs) I get a stop message, but with the full "Windows has stopped to protect your system ... yadda ... yadda ... yadda" and a different stop code. I'm getting a bit frustrated by this, and have recieved no help from ASUS (although I did notice they decided to use a different chip for RAID controller on their new A8N32 board). My current choices are: 1) boot from a spare PATA drive I have around. 2) use the SATA drives a single units (then why did I bother buying two?) 3) buy a SATA RAID controller to sit in a PCI or the PCIex1 slot (so I can leave the PCIex16 slot open for a graphics bump in the future). 4) pull my hair out getting this to install the way I want it to (and the way it should). Help and suggestions would be most appreciated.