Jump to content

Welcome to MSFN Forum
Register now to gain access to all of our features. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more. This message will be removed once you have signed in.
Login to Account Create an Account


Photo

Integration of NVIDIA's nForce RAID and AHCI drivers

* * * * * 4 votes

  • Please log in to reply
1989 replies to this topic

#76
dale5605

dale5605

    Member

  • Member
  • PipPip
  • 231 posts
I was trying to suggest things to make it work for others.

And yes I am very happy that it works for me :D

If others are unlucky that is their problem :blushing:


How to remove advertisement from MSFN

#77
ronmanp

ronmanp

    Lazy Hyperactive

  • Member
  • Pip
  • 53 posts
im having problems integrating my sata drivers on my XP pro 32bits windows
Ive read the instructions by fernando but the nvraid drivers I need are for Nforce3 so I dont have any pataraid folder so how do I integrate Nforce3 sata drivers for XP Pro 32bits?

Sorry if it has been asked before :unsure:

Thanks in advance

#78
Fernando 1

Fernando 1

    Easy RAIDer

  • Member
  • PipPipPipPipPipPipPipPip
  • 2,021 posts
  • OS:Windows 7 x64

im having problems integrating my sata drivers on my XP pro 32bits windows
Ive read the instructions by fernando but the nvraid drivers I need are for Nforce3 so I dont have any pataraid folder so how do I integrate Nforce3 sata drivers for XP Pro 32bits?

Do you have a Raid array?
If yes, you can do it as I explained it in post 1 of this thread. There is even something said about users with an nForce3 chipset mainboard.
You can take the SATARAID drivers from the nForce chipset driver package v. 6.66. nForce3 Sata controllers are supported by that drivers.
CU
Fernando
My current system:
ASUS P8Z68-V | Intel Core i5 2500K | 2x4 GB Corsair XMS3 DDR3-1600 | 2x128GB Crucial M4 SSD as RAID0 in SATA3 mode | Seasonic M12II-520 Modular 520W | ATI Radeon HD6850 1 GB GDDR5
My old system:
DFI nF4 Ultra-D (BIOS: 2006/04/06) | AMD Athlon64 4000+ San Diego | 2x512 MB OCZ PC3200 CL2 Rev.2 Platinum | 2x200 GB Samsung S-ATA II as Raid0 | beQuiet!Titan BQT P5-470W-S1.3 | MSI GeForce NX6600GT-TD128E

#79
ronmanp

ronmanp

    Lazy Hyperactive

  • Member
  • Pip
  • 53 posts
sorry I dont understand ...
No I dont have a raid array I just have one sata drive but everytime I try to integrate the sata drivers from Nvidia the harddisk is not detected (I dont have a floppy drive :( )
Please explain me how to integrate the drivers for Nforce3

Thanks for your help

Edited by ronmanp, 05 September 2005 - 08:27 AM.


#80
Fernando 1

Fernando 1

    Easy RAIDer

  • Member
  • PipPipPipPipPipPipPipPip
  • 2,021 posts
  • OS:Windows 7 x64

No I dont have a raid array I just have one sata drive but everytime I try to integrate the sata drivers from Nvidia the harddisk is not detected (I dont have a floppy drive :(  )
Please explain me how to integrate the drivers for Nforce3

Have you tried it with the PATARAID subfolder (from the nForce chipset package 6.66)?
Although you have no Raid, there is a SATA driver (nvatabus.sys) within that folder, which is suitable for nForce3 chipsets.

Please post here the result of your work. This way you can help other users with an nForce3 SATA system.
My current system:
ASUS P8Z68-V | Intel Core i5 2500K | 2x4 GB Corsair XMS3 DDR3-1600 | 2x128GB Crucial M4 SSD as RAID0 in SATA3 mode | Seasonic M12II-520 Modular 520W | ATI Radeon HD6850 1 GB GDDR5
My old system:
DFI nF4 Ultra-D (BIOS: 2006/04/06) | AMD Athlon64 4000+ San Diego | 2x512 MB OCZ PC3200 CL2 Rev.2 Platinum | 2x200 GB Samsung S-ATA II as Raid0 | beQuiet!Titan BQT P5-470W-S1.3 | MSI GeForce NX6600GT-TD128E

#81
willdoicu

willdoicu
  • Member
  • 3 posts
Yeeehaw !!!

Thanks a lot Fernando 1, works everithig fine with Asus K8N (Nforce3), I just folow your first post. Great job !!!

#82
Fernando 1

Fernando 1

    Easy RAIDer

  • Member
  • PipPipPipPipPipPipPipPip
  • 2,021 posts
  • OS:Windows 7 x64

Yeeehaw !!!

Thanks a lot Fernando 1, works everithig fine with Asus K8N (Nforce3), I just folow your first post. Great job !!!

<{POST_SNAPBACK}>

Hi Willdoicu,
thank you very much for your posting.
Your comment verifies, that the method described in my first post works even with mainboards, which have an nForce3 chipset.
For other users with an Nforce3 SataRaid or PataRaid system would it be very helpfull, if you would answer the following questions:

1. Do you have an nVRaid array with S-ATA drives or P-ATA drives?
2. Which nForce chipset driver version did you use?
3. Which subfolder (SATARAID or PATARAID) did you use, when you integrated the textmode drivers?
4. Did you change something within the TEXTSETUP.OEM file? If yes, what?

CU
Fernando
My current system:
ASUS P8Z68-V | Intel Core i5 2500K | 2x4 GB Corsair XMS3 DDR3-1600 | 2x128GB Crucial M4 SSD as RAID0 in SATA3 mode | Seasonic M12II-520 Modular 520W | ATI Radeon HD6850 1 GB GDDR5
My old system:
DFI nF4 Ultra-D (BIOS: 2006/04/06) | AMD Athlon64 4000+ San Diego | 2x512 MB OCZ PC3200 CL2 Rev.2 Platinum | 2x200 GB Samsung S-ATA II as Raid0 | beQuiet!Titan BQT P5-470W-S1.3 | MSI GeForce NX6600GT-TD128E

#83
willdoicu

willdoicu
  • Member
  • 3 posts
[/quote]
[quote name='Fernando 1' date='Sep 6 2005, 08:28 AM']Hi Willdoicu,
thank you very much for your posting.
Your comment verifies, that the method described in my first post works even with mainboards, which have an nForce3 chipset.
For other users with an Nforce3 SataRaid or PataRaid system would it be very helpfull, if you would answer the following questions:

1. Do you have an nVRaid array with S-ATA drives or P-ATA drives?
2. Which nForce chipset driver version did you use?
3. Which subfolder (SATARAID or PATARAID) did you use, when you integrated the textmode drivers?
4. Did you change something within the TEXTSETUP.OEM file? If yes, what?

CU
Fernando

<{POST_SNAPBACK}>

[/quote]


my answers :
1. I have a nVRaid array with S-ATA drives
2. I've used nForce Win2K/XP driver package 6.66 for SATARAID,PATARAID and Sataide. I was integrated also nForce drivers from package 5.10 for Ethernet, Gart, MemCtl, SMBus.
3. I've use subfolders "sata_ide" and "sataraid" to integrate and "pataraid" in \$OEM$\$$\OEMDIR.
4.yes I-ve changed "inf = d1, nvraid.inf" with "inf = d1, nvatabus.inf" on "[Files.scsi.BUSDRV]" section from SATARAID subfolder.
That is all. Thank you again !!!

Edited by willdoicu, 06 September 2005 - 12:02 PM.


#84
Tweakin

Tweakin
  • Member
  • 6 posts
I am really stuck with this guys and need some help. I have tried Fernando_1's way twice and dale5605's way once. All three attempts have ended in repeated bluescreens.

I have,
ASUS A8N-SLI Deluxe (BIOS 1011 / nVraid v4.81)
A64 3500+ Venice
2x Western Digital 74gb Raptors

I have tried using the 6.66 package of nForce4 drivers, included the pataraid directory contents in the OemDir, integrated the sataraid and sata_ide drivers with nLite (1.0 b6), etc. I can't figure out what I could be doing wrong.

I can't believe how hard it is to get a stripe working with my raptors, I have never had so much trouble with a raid array before.

#85
Fernando 1

Fernando 1

    Easy RAIDer

  • Member
  • PipPipPipPipPipPipPipPip
  • 2,021 posts
  • OS:Windows 7 x64

I am really stuck with this guys and need some help. I have tried Fernando_1's way twice and dale5605's way once. All three attempts have ended in repeated bluescreens.
I have,
ASUS A8N-SLI Deluxe (BIOS 1011 / nVraid v4.81)
A64 3500+ Venice
2x Western Digital 74gb Raptors
I have tried using the 6.66 package of nForce4 drivers, included the pataraid directory contents in the OemDir, integrated the sataraid and sata_ide drivers with nLite (1.0 b6), etc. I can't figure out what I could be doing wrong.
I can't believe how hard it is to get a stripe working with my raptors, I have never had so much trouble with a raid array before.

<{POST_SNAPBACK}>


You can't install the nForce Raid drivers from the chipset package 6.66 with an nVRaid Bios v. 4.81. What you need is a Raid Bios version 4.84!

If Asus has no newer Bios version, you have to take drivers from an nForce package lower than 6.66.
My current system:
ASUS P8Z68-V | Intel Core i5 2500K | 2x4 GB Corsair XMS3 DDR3-1600 | 2x128GB Crucial M4 SSD as RAID0 in SATA3 mode | Seasonic M12II-520 Modular 520W | ATI Radeon HD6850 1 GB GDDR5
My old system:
DFI nF4 Ultra-D (BIOS: 2006/04/06) | AMD Athlon64 4000+ San Diego | 2x512 MB OCZ PC3200 CL2 Rev.2 Platinum | 2x200 GB Samsung S-ATA II as Raid0 | beQuiet!Titan BQT P5-470W-S1.3 | MSI GeForce NX6600GT-TD128E

#86
Tweakin

Tweakin
  • Member
  • 6 posts

I am really stuck with this guys and need some help. I have tried Fernando_1's way twice and dale5605's way once. All three attempts have ended in repeated bluescreens.
I have,
ASUS A8N-SLI Deluxe (BIOS 1011 / nVraid v4.81)
A64 3500+ Venice
2x Western Digital 74gb Raptors
I have tried using the 6.66 package of nForce4 drivers, included the pataraid directory contents in the OemDir, integrated the sataraid and sata_ide drivers with nLite (1.0 b6), etc. I can't figure out what I could be doing wrong.
I can't believe how hard it is to get a stripe working with my raptors, I have never had so much trouble with a raid array before.

<{POST_SNAPBACK}>


You can't install the nForce Raid drivers from the chipset package 6.66 with an nVRaid Bios v. 4.81. What you need is a Raid Bios version 4.84!

If Asus has no newer Bios version, you have to take drivers from an nForce package lower than 6.66.

<{POST_SNAPBACK}>


Ahh ha, I wasn't sure exactly what you meant in your first paragraph (on the first post), now it makes sense. Cool, I will update the BIOS now, I was just avoiding it because my BIOS is so heavily tweaked I hate to clear the CMOS :( It's worth it though if it means being able to get this fricken raid working!

#87
Fernando 1

Fernando 1

    Easy RAIDer

  • Member
  • PipPipPipPipPipPipPipPip
  • 2,021 posts
  • OS:Windows 7 x64

Ahh ha, I wasn't sure exactly what you meant in your first paragraph (on the first post), now it makes sense. Cool, I will update the BIOS now, I was just avoiding it because my BIOS is so heavily tweaked I hate to clear the CMOS  :(  It's worth it though if it means being able to get this fricken raid working!

<{POST_SNAPBACK}>

Please post the result of your work within this thread.
Good luck!
Fernando
My current system:
ASUS P8Z68-V | Intel Core i5 2500K | 2x4 GB Corsair XMS3 DDR3-1600 | 2x128GB Crucial M4 SSD as RAID0 in SATA3 mode | Seasonic M12II-520 Modular 520W | ATI Radeon HD6850 1 GB GDDR5
My old system:
DFI nF4 Ultra-D (BIOS: 2006/04/06) | AMD Athlon64 4000+ San Diego | 2x512 MB OCZ PC3200 CL2 Rev.2 Platinum | 2x200 GB Samsung S-ATA II as Raid0 | beQuiet!Titan BQT P5-470W-S1.3 | MSI GeForce NX6600GT-TD128E

#88
dale5605

dale5605

    Member

  • Member
  • PipPip
  • 231 posts
Umm Fernando, I am on 3/10 bios with 4.81 nvraid and 6.66 drivers.

Odd?

What BIOS are you running that got you 4.84 nvraid?

#89
Fernando 1

Fernando 1

    Easy RAIDer

  • Member
  • PipPipPipPipPipPipPipPip
  • 2,021 posts
  • OS:Windows 7 x64

What BIOS are you running that got you 4.84 nvraid?

I have a DFI Lanparty UT NF4 Ultra-D with the Bios from 06/23/05. This Bios includes the Raid Bios version 4.84.
My current system:
ASUS P8Z68-V | Intel Core i5 2500K | 2x4 GB Corsair XMS3 DDR3-1600 | 2x128GB Crucial M4 SSD as RAID0 in SATA3 mode | Seasonic M12II-520 Modular 520W | ATI Radeon HD6850 1 GB GDDR5
My old system:
DFI nF4 Ultra-D (BIOS: 2006/04/06) | AMD Athlon64 4000+ San Diego | 2x512 MB OCZ PC3200 CL2 Rev.2 Platinum | 2x200 GB Samsung S-ATA II as Raid0 | beQuiet!Titan BQT P5-470W-S1.3 | MSI GeForce NX6600GT-TD128E

#90
Tweakin

Tweakin
  • Member
  • 6 posts

Ahh ha, I wasn't sure exactly what you meant in your first paragraph (on the first post), now it makes sense. Cool, I will update the BIOS now, I was just avoiding it because my BIOS is so heavily tweaked I hate to clear the CMOS  :(  It's worth it though if it means being able to get this fricken raid working!

<{POST_SNAPBACK}>

Please post the result of your work within this thread.
Good luck!
Fernando

<{POST_SNAPBACK}>


Updating the BIOS did the trick. I have 4.84 NV RAID now, and it worked on the first try using your method on the first post.

Thanks!

#91
FatalSaviour

FatalSaviour

    Newbie

  • Member
  • 13 posts
Could someone please clarify what errors they're actually getting when they try to slipstream SATA NVRAID array drivers into an WinXP SP2 (32-bit) cd. Without making any text-mode modifications, simply using nlite to integrate the drivers, windows appears to have installed fine, and I can run apps, games etc. all day long. However, upon leaving it, sometimes immediately after booting, sometimes 3 hours after...it randomly reboots. Is this the constant rebooting that people are having problems with, or is it straight after booting XP that most people find their PCs flaking out?
Cheers

#92
Fernando 1

Fernando 1

    Easy RAIDer

  • Member
  • PipPipPipPipPipPipPipPip
  • 2,021 posts
  • OS:Windows 7 x64

Could someone please clarify what errors they're actually getting when they try to slipstream SATA NVRAID array drivers into an WinXP SP2 (32-bit) cd.  Without making any text-mode modifications, simply using nlite to integrate the drivers, windows appears to have installed fine, and I can run apps, games etc. all day long.  However, upon leaving it, sometimes immediately after booting, sometimes 3 hours after...it randomly reboots.  Is this the constant rebooting that people are having problems with, or is it straight after booting XP that most people find their PCs flaking out?

I don't know, if somebody could successfully integrate the nVRaid drivers into Windows XP by using nLite Beta6 without any "handmade" changes. All my tests failed at the end of the installation procedure by endless reboots of my computer, even when I rebooted in safe mode.
So the answer is: The issue appears straight during the installation of the OS, there is no chance to use it.
The reason for this issue is, that the Windows XP setup routine installs the wrong driver (Standard PCI IDE Controller) during the GUIMODE part of the installation.
The [OemInfFiles]-method, which is able to prevent this strange behaviour, has not been completely implemented into nLite Beta6.
My current system:
ASUS P8Z68-V | Intel Core i5 2500K | 2x4 GB Corsair XMS3 DDR3-1600 | 2x128GB Crucial M4 SSD as RAID0 in SATA3 mode | Seasonic M12II-520 Modular 520W | ATI Radeon HD6850 1 GB GDDR5
My old system:
DFI nF4 Ultra-D (BIOS: 2006/04/06) | AMD Athlon64 4000+ San Diego | 2x512 MB OCZ PC3200 CL2 Rev.2 Platinum | 2x200 GB Samsung S-ATA II as Raid0 | beQuiet!Titan BQT P5-470W-S1.3 | MSI GeForce NX6600GT-TD128E

#93
mjswooosh

mjswooosh

    Newbie

  • Member
  • 14 posts

Could someone please clarify what errors they're actually getting when they try to slipstream SATA NVRAID array drivers into an WinXP SP2 (32-bit) cd.  Without making any text-mode modifications, simply using nlite to integrate the drivers, windows appears to have installed fine, and I can run apps, games etc. all day long.  However, upon leaving it, sometimes immediately after booting, sometimes 3 hours after...it randomly reboots.  Is this the constant rebooting that people are having problems with, or is it straight after booting XP that most people find their PCs flaking out?

I don't know, if somebody could successfully integrate the nVRaid drivers into Windows XP by using nLite Beta6 without any "handmade" changes. All my tests failed at the end of the installation procedure by endless reboots of my computer, even when I rebooted in safe mode.
So the answer is: The issue appears straight during the installation of the OS, there is no chance to use it.
The reason for this issue is, that the Windows XP setup routine installs the wrong driver (Standard PCI IDE Controller) during the GUIMODE part of the installation.
The [OemInfFiles]-method, which is able to prevent this strange behaviour, has not been completely implemented into nLite Beta6.

<{POST_SNAPBACK}>


Hi there Fernando~

First of all, let me say THANK YOU SO MUCH for your contributions to helping all of us figure this out. I believe it is very irresponsible of nVIDIA to release such an obviously *broken* NVRAID driver, but thanks to you and other users there is a chance that many of us will actually get to use the wonderful RAID features on our nForce3/4 motherboards.

Unfortunately, I must report the [OemInfFiles]-method does not work for me yet.

I have tried re-doing the entire process 6 or 7 times (I've lost count now!): I re-transferred 2 different XP SP2 source CDs, re-did the nLite process multiple times, re-typed the [OemInfFiles]-method into the WINNT.SIF file many, many times just as you said to do, etc...

Unfortunately, I keep getting multiple errors during the install process. The main problems occur during the initial file install phase right after the drive formats (before it gets to the WinXP GUI). The primary problems are "missing .dll" errors in which I am instructed to hit [enter] if I want to keep going or [esc] to abort the install. Of course, I always hit [enter]. In some cases the install will get "stuck" on a particular missing .dll and I am forced to abort the install. In other cases, the file install will successfully finish at 100% but then at the very end the machine will BSOD with mention of some problem with a particular file.

I just tried Dale's method (no OemInfFiles) and was able to get the system to boot into windows. At first I thought the install was totally successful, but unlike Dale's personal experience my install did *not* successfully find or install the NVRAID files once WinXP loaded up. In other words, device manager shows the typical question marks for missing drivers and when I try to force the system to look for system changes it just brings up the same dialogue box that tells me the system had a problem finding the correct drivers for the nFORCE4 RAID device, blah blah.

In short, the [OemInfFiles]-method does not work for me (yet). If you (or anyone else here) can give me some insight as to what might be causing the repeated "missing .dll" and BSOD errors during install I'd greatly appreciate it.

Dale's method of simply integrating the files will at least let me get into windows, but for now it appears I'll have to manually install all drivers once I get there. This isn't too bad of a solution if it truly activates NVRAID (am still not there yet).

I'll keep tweaking and working to see if I can get things to work. Any further help with the [OemInfFiles]-method will be greatly appreciated!

Of course, it'd be nice if nVIDIA would pull their heads out of their collective butts and give us a RAID driver that actually works so we don't have to waste our time doing this kinda crap...I'm not real happy that I've had to waste TWO DAYS messing with RAID which is advertised to work as an "out-of-box" feature... :realmad:

#94
Fernando 1

Fernando 1

    Easy RAIDer

  • Member
  • PipPipPipPipPipPipPipPip
  • 2,021 posts
  • OS:Windows 7 x64

Unfortunately, I keep getting multiple errors during the install process. The main problems occur during the initial file install phase right after the drive formats (before it gets to the WinXP GUI).  The primary problems are "missing .dll" errors in which I am instructed to hit [enter] if I want to keep going or [esc] to abort the install.  Of course, I always hit [enter].  In some cases the install will get "stuck" on a particular missing .dll and I am forced to abort the install. In other cases, the file install will successfully finish at 100% but then at the very end the machine will BSOD with mention of some problem with a particular file. 


Before I can help you, I need some informations:

Are you really sure, that Windows Setup missed DLL-files? Or is it possible, that the system asked for CAT-files?
Did the setup always ask for the same or for different files?
What is your system (nForce3 or nForce4 chipset, PataRaid or Sataraid)?
Which nForce chipset driver package version did you use?
My current system:
ASUS P8Z68-V | Intel Core i5 2500K | 2x4 GB Corsair XMS3 DDR3-1600 | 2x128GB Crucial M4 SSD as RAID0 in SATA3 mode | Seasonic M12II-520 Modular 520W | ATI Radeon HD6850 1 GB GDDR5
My old system:
DFI nF4 Ultra-D (BIOS: 2006/04/06) | AMD Athlon64 4000+ San Diego | 2x512 MB OCZ PC3200 CL2 Rev.2 Platinum | 2x200 GB Samsung S-ATA II as Raid0 | beQuiet!Titan BQT P5-470W-S1.3 | MSI GeForce NX6600GT-TD128E

#95
mjswooosh

mjswooosh

    Newbie

  • Member
  • 14 posts

Unfortunately, I keep getting multiple errors during the install process. The main problems occur during the initial file install phase right after the drive formats (before it gets to the WinXP GUI).  The primary problems are "missing .dll" errors in which I am instructed to hit [enter] if I want to keep going or [esc] to abort the install.  Of course, I always hit [enter].  In some cases the install will get "stuck" on a particular missing .dll and I am forced to abort the install. In other cases, the file install will successfully finish at 100% but then at the very end the machine will BSOD with mention of some problem with a particular file. 


Before I can help you, I need some informations:

Are you really sure, that Windows Setup missed DLL-files? Or is it possible, that the system asked for CAT-files?
Did the setup always ask for the same or for different files?
What is your system (nForce3 or nForce4 chipset, PataRaid or Sataraid)?
Which nForce chipset driver package version did you use?

<{POST_SNAPBACK}>


1. Yes, the system asks for various "missing" .dll files, *not* cab files.
2. Setup seems to ask for different, random .dll files each time.
3. A couple of times install totally stopped due to a "missing .dll" file and hitting [enter] did nothing. Those 2 times I had to hit [esc] to abort install. However, most of the time hitting [enter] resumes install. This is very strange since most of the time it seems as if the system is saying, "I can't find this file...OH, NEVER MIND, now that you hit the [enter] key I just found it!" :rolleyes:
4. My motherboard: BFG "BFGRNF4U" nForce4 Ultra
5. BIOS: 0719 = nVRAID 4.84
6. nFORCE drivers = 6.66

**********************
Since I last posted I have re-tried Dale's method 2 more times, adding more drivers each time. Initially, I thought this method to be successful since I could boot into WindowsXP right after finishing install. However, after re-booting the system reverts to continual re-boots. :no:
**********************

Further Information Regarding Dale's Method:

My last effort successfully loaded the nForce sound drivers & ATI Catalyst 5.8 drivers in the *first* boot up sequence.

However, when WinXP starts the "Found New Hardware Wizard" pops up. The message reads:

"Cannot Install this hardware. There was a problem installing this hardware: NVIDIA nFORCE RAID Class Controller. An error during the installation of the device. The installation source for this product is not available. Verify that the source exists and that you can access it. Click Finish to close the wizard."

There is no option to do anything but click "Finish".

Since Windows seems to have successfully loaded the nForce/Ethernet drivers, Device Manager shows all of the question marks are now gone.

Device Manager/Disk Drives *correctly* shows I have "NVIDIA STRIPE 372.61G"

However, SCSI and RAID Controllers shows "Unknown Device", which correlates to the aforementioned "Found New Hardware Wizard". If I scan for new devices, the same wizard pops up time after time. None of the NVIDIA RAID drivers available seem to work.

In short, this method does not work for me since it does the continual re-boot process. :no:

#96
Fernando 1

Fernando 1

    Easy RAIDer

  • Member
  • PipPipPipPipPipPipPipPip
  • 2,021 posts
  • OS:Windows 7 x64

1. Yes, the system asks for various "missing" .dll files, *not* cab files.
2. Setup seems to ask for different, random .dll files each time.
3. A couple of times install totally stopped due to a "missing .dll" file and hitting [enter] did nothing.  Those 2 times I had to hit [esc] to abort install.  However, most of the time hitting [enter] resumes install.  This is very strange since most of the time it seems as if the system is saying, "I can't find this file...OH, NEVER MIND, now that you hit the [enter] key I just found it!"   :rolleyes:
4. My motherboard: BFG "BFGRNF4U" nForce4 Ultra
5. BIOS: 0719 = nVRAID 4.84
6. nFORCE drivers = 6.66

I am nearly sure, that your problem has nothing to do with nLite or the method how to integrate the "ugly" nForce SataRaid drivers.

My suggestions:
Change your cd player and create a new unattended install CD.
If this doesn't change anything, there is something wrong either with your RAM (check them) or power supply (strong enough?), with the temperatures within your pc case (maybe the 2 hard disk drives are too close together) or you are an overclocker, which has reached the limits (take Bios defaults settings).

Edited by Fernando 1, 07 September 2005 - 02:28 PM.

My current system:
ASUS P8Z68-V | Intel Core i5 2500K | 2x4 GB Corsair XMS3 DDR3-1600 | 2x128GB Crucial M4 SSD as RAID0 in SATA3 mode | Seasonic M12II-520 Modular 520W | ATI Radeon HD6850 1 GB GDDR5
My old system:
DFI nF4 Ultra-D (BIOS: 2006/04/06) | AMD Athlon64 4000+ San Diego | 2x512 MB OCZ PC3200 CL2 Rev.2 Platinum | 2x200 GB Samsung S-ATA II as Raid0 | beQuiet!Titan BQT P5-470W-S1.3 | MSI GeForce NX6600GT-TD128E

#97
willdoicu

willdoicu
  • Member
  • 3 posts

I am really stuck with this guys and need some help. I have tried Fernando_1's way twice and dale5605's way once. All three attempts have ended in repeated bluescreens.

I have,
ASUS A8N-SLI Deluxe (BIOS 1011 / nVraid v4.81)
A64 3500+ Venice
2x Western Digital 74gb Raptors

I have tried using the 6.66 package of nForce4 drivers, included the pataraid directory contents in the OemDir, integrated the sataraid and sata_ide drivers with nLite (1.0 b6), etc. I can't figure out what I could be doing wrong.

I can't believe how hard it is to get a stripe working with my raptors, I have never had so much trouble with a raid array before.

<{POST_SNAPBACK}>



Tweakin, pay attention you have ASUS A8N-SLI Deluxe no DFI !!!

Edited by willdoicu, 07 September 2005 - 02:33 PM.


#98
Fernando 1

Fernando 1

    Easy RAIDer

  • Member
  • PipPipPipPipPipPipPipPip
  • 2,021 posts
  • OS:Windows 7 x64

I am really stuck with this guys and need some help. I have tried Fernando_1's way twice and dale5605's way once. All three attempts have ended in repeated bluescreens.
I have,
ASUS A8N-SLI Deluxe (BIOS 1011 / nVraid v4.81)

Tweakin, pay attention you have ASUS A8N-SLI Deluxe no DFI !!!

That is right, but he succeeded even with an ASUS board. Haven't you seen this reply by Tweakin?

Updating the BIOS did the trick. I have 4.84 NV RAID now, and it worked on the first try using your method on the first post.
Thanks!


My current system:
ASUS P8Z68-V | Intel Core i5 2500K | 2x4 GB Corsair XMS3 DDR3-1600 | 2x128GB Crucial M4 SSD as RAID0 in SATA3 mode | Seasonic M12II-520 Modular 520W | ATI Radeon HD6850 1 GB GDDR5
My old system:
DFI nF4 Ultra-D (BIOS: 2006/04/06) | AMD Athlon64 4000+ San Diego | 2x512 MB OCZ PC3200 CL2 Rev.2 Platinum | 2x200 GB Samsung S-ATA II as Raid0 | beQuiet!Titan BQT P5-470W-S1.3 | MSI GeForce NX6600GT-TD128E

#99
mjswooosh

mjswooosh

    Newbie

  • Member
  • 14 posts

1. Yes, the system asks for various "missing" .dll files, *not* cab files.
2. Setup seems to ask for different, random .dll files each time.
3. A couple of times install totally stopped due to a "missing .dll" file and hitting [enter] did nothing.  Those 2 times I had to hit [esc] to abort install.  However, most of the time hitting [enter] resumes install.  This is very strange since most of the time it seems as if the system is saying, "I can't find this file...OH, NEVER MIND, now that you hit the [enter] key I just found it!"  :rolleyes:
4. My motherboard: BFG "BFGRNF4U" nForce4 Ultra
5. BIOS: 0719 = nVRAID 4.84
6. nFORCE drivers = 6.66

I am nearly sure, that your problem has nothing to do with nLite or the method how to integrate the "ugly" nForce SataRaid drivers.

My suggestions:
Change your cd player and create a new unattended install CD.
If this doesn't change anything, there is something wrong either with your RAM (check them) or power supply (strong enough?), with the temperatures within your pc case (maybe the 2 hard disk drives are too close together) or you are an overclocker, which has reached the limits (take Bios defaults settings).

<{POST_SNAPBACK}>




I think you are probably correct to some extent. It crossed my mind it could be a problem with my CD-RW media (Sony 4X) or possibly the DVD burner I'm using on the other system (Pioneer), or maybe even the DVD-RW players on my new system (NEC). There are LOTS of possible problems! ;) And since it seems "random" I thought the same thing you do.

However, the only thing that doesn't make sense to me is why would the CD-RW burns of WinXP using Dale's method work just fine and get all the way through the install process without showing the same "missing .dll" errors? I used the same equipment, even the same media (I just wrote over the top of the same 3 CD-RWs for all 9 attempts so far...).

If it really is a problem with my equipment you would think that the problem would occur using both the OemInfFile method -AND- Dale's integrated method, correct?

But the errors only occur when using the OemInfFile method. :wacko:

PS: All of my equipment is running at normal spec, not overclocked.

#100
dale5605

dale5605

    Member

  • Member
  • PipPip
  • 231 posts
mjswoosh, I also get those errors when I tried it the one time I did it that way. However after I installed those drivers I did not experience that reboot problem you are speaking of. Usually that problem only occurs after windows installs and you never make it into windows in the first place. I would recommend only adding in the nvatabus.inf and raidtool folder into your sataraid directory and leaving out the other stuff. You won't get the device manager errors that way, I really only suggested that as a *possible* solution to people having lots of problems. But I would just stick with the aforementioned. :P

Fernando you mentioned that windows is install the wrong ide driver being the cause for the problem.

I know I remove ALL drivers with nlite, this includes all the various ide drivers and the scsi/raid drivers.

Does this have anything to do with it?

I'm just curious as to what is causing these different results to be achieved.


Again, I can get my raid array working fine with nlite 1.0 b6 with no "handmade" changes.

Some things that may or may not be significant.

-Using nvidia 6.66 drivers
-Using nvraid 4.81 drivers loaded on my mobo
-Remove ALL drivers with nLite and integrate all my own
-Do not check "oem preinstall" box
-Use DefaultHide unattended method
-Integrate RVM1.3.1 + WMP10 + Addons


Oh and I didn't realize the 6/23 BIOS has the newer nvraid version because I didn't see it mentioned anywhere in the changes. I am considering flashing to that BIOS but everything is working the way it is now and I don't really feel like messing it up. :D

Edited by dale5605, 07 September 2005 - 02:53 PM.





0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users



How to remove advertisement from MSFN