MSFN Forums > Integration of nvRaid drivers into XPx64 and W2k3x64

Full Version: Integration of nvRaid drivers into XPx64 and W2k3x64

MSFN Forums > Member Contributed Projects > nLite

Pages: 1, 2, 3, 4, 5, 6, 7, 8

Fernando 1

Jul 13 2005, 02:46 PM

Attention:

Recently I have totally revised and unified my instructions and tips regarding the integration of the nForce RAID and S-ATA drivers. Instead of 2 different guides for 32bit and 64bit Operating Systems you will get all needed informations within one single guide usable for XP, XP x64, W2k3, W2k3 x64 and W2k.

You will find the actual pooled guide here.

If you have any questions or comments regarding the integration of nVRaid drivers into XP x64 or W2k3 x64, please post it into the linked thread.

Thanks!
Fernando

Here is the old guide, which will not be updated anymore:

QUOTE

Integration of the nVRaid drivers into
Windows XP x64 or Windows Server 2003 x64

Introduction:
Many users with a NVIDIA Raid system on their computer know about the problems, when they try to install Windows XP x64 or W2k3 x64:
Even if they have a floppy drive and integrate the newest nForce SataRaid or PataRaid drivers by the F6-method, they get bluescreens or endless reboots at the end of the installation. The reason for this strange behaviour is the fact, that the actual NVIDIA Raid drivers are still not correctly digitally signed with the consequence, that the XP installation routine does not trust them. During the second (GUIMODE) part of the installation the correct (but uncertified) NVIDIA drivers are replaced by wrong (not working) Microsoft PCI-IDE standard drivers.
The only chance to prevent these problems is to create an Unattended Install CD with integrated nVRaid drivers using a method to enforce the installation of the correct NVIDIA drivers.
After a lot of tests with nLite I have found 2 different methods to enforce the installation of the correct x64 nForce Raid and nForce S-ATA drivers und to prevent endless reboots at the end of the XP setup:
1. Method by directly enhancement of the x64 NVIDIA drivers (OemInfFiles-Method)
and
2. Method by suppression or removal of other interfering drivers (Driver-Suppression/Removal-Method)

New and very easy method with nLite

The actual versions of nLite (v. 1.0 or higher) offer the safest and easiest way to integrate the nVRaid drivers.
Advantages:
- fully automaticly method (without creating new directories or editing SIF or OEM files)
- without restriction of any kind during the use of nLite

Here is the way to do:

Attention: The following guide is only useful for users with an nForce Raid array!

Description of the Driver-Integration-Method
by using nLite

(valid for v. 1.0.1 or higher)

Important Requirements:

You only will succeed with the integration of the nForce SataRaid drivers, if you have
- an up-to-date mainboard BIOS (actual nVRaid drivers may need a Raid Bios v. 4.84 or higher)
- a stable system (proper RAM modules and stable BIOS settings, no overclocking!)
- an original or perfectly created Windows XP x64 or Windows Server 2003 x64 CD
- a proper working IDE-connected CD or DVD drive
- an enabled ACPI power management (within BIOS, don't disabe it by nLite settings).

Tips:

You can see the nVRaid BIOS version of your system on the second boot screen. If you can't get a Raid BIOS version v. 4.84 or higher unless having flashed the latest mainboard BIOS, you might get problems with the integration of the latest nForce SataRaid drivers. In this case you should take the old 64-bit nForce chipset driver package 6.56, which is not native 64-bit and usable with an older RAID BIOS.
It is a good idea to unplug all unnecessary extern hardware devices during the install of the OS with integrated nVRaid drivers.
If you have any hard disk drive outside your RAID array or a plugged-in USB stick, you may get the problem, that the MS Setup routine tries to install the master boot record (MBR) onto that non-RAID device, although you have set the RAID array as first bootable hard disk drive within BIOS. The only possibility to prevent this is to unplug these non-RAID devices during the installation of the OS. After the successful installation they can be reconnected without any problems.

Brandnew method:

Integration of the actual WHQL certified 64-bit nForce SataRaid drivers

The above mentioned and approved methods to integrate the nForce SataRaid drivers into a bootable XP x64 or W2k3 x64 CD were primarily documented by me in July 2005. Meanwhile NVIDIA has released a lot of new 64-bit nForce chipset driver packages with WHQL certified nForce Sata and Raid drivers. You can find them within the SATARAID and SATA_IDE subfolders. The problem was, that users with an nForce SataRaid system obviously could not use them during the installation (to avoid BSOD's or endless reboot loops at the end of the OS installation). They had to take the not digitally signed LEGACY drivers.

After a lot of new tests with the current version of nLite I figured out, that I got the newest WHQL certified 64-bit nForce SataRaid drivers installed onto an nForce SataRaid system, when I used a special combination of the nForce SataRaid driver integration:

Integration of the SATARAID subfolder (from the suitable 64-bit nForce chipset driver package) as TEXTMODE driver and additionally

Integration of the SATA_IDE subfolder (from the same nForce chipset driver package) as PnP driver!

At the end of the successul OS installation I had a flawlessly running XP x64 or W2k3 x64, all nForce IDE drivers (the SATA and RAID ones) were WHQL certified.

Advantages of the WHQL driver integration method:

A running Windows XP x64 is optimally prepared for a later upgrade with Vista, when it has WHQL certified SataRaid drivers from scratch (The WHQL stamp is a must for Vista x64, the Setup routine looks for the drivers which were installed first of all during the XP x64 installation).

By using this new method you will get the MS IDE drivers installed instead of the NVIDIA P-ATA (=IDE s/w) ones (A lot of nForce users have reported about troubles with the NVIDIA P-ATA driver). Remark: If you don't want the MS IDE drivers, you can easily replace them by the NVIDIA IDE driver after the end of the OS installation.

These findings might be a big step forward for all users with an nForce SataRaid system, but - as I could only test it with my nForce4 system - the new method has to be confirmed by users with other nForce chipsets. Nevertheless I am very optimistic, that the method works with every nForce chipset (maybe except nForce3).

1. nVRaid Driver Choice and Preparation:

Although nLite allows the correct integration of the actual nForce SataRaid drivers and prevents the installation of the wrong MS IDE standard drivers, the biggest problem is the creation of the optimal nVRaid driver prepackaging. The choice of the best driver version and combination depends on the system (Chipset details and Raid BIOS version). NVIDIA has complicated all this, because they often change the composition of their driver packages and even the names of the files for not understandable reasons. Nevertheless I found solutions, which should enable nearly everyone to get XP x64 or W2k3 x64 installed onto their nForce SataRaid system.

A. Preparation for the WHQL driver integration method:

Normal option for mainboards with an nForce4, nForce4xx, nForce5xx or nForce6xx chipset:
The preparation is very easy, because all you need is the actual 64bit nForce chipset driver package, which NVIDIA has designed for the specific nForce chipset of your motherboard. If you don't know the exact name of the chipset, look into your mainboard manual or google for it. Then go here, search for the nForce chipset driver package suitable for your chipset, choose the 64bit OS you want to install, download the driver package and unpack it by using a tool like WinRar or 7-zip.
That is all you need for the later nForce SataRaid driver integration.
Warning: Users, who want to integrate the nForce4 chipset drivers v. 6.69 into Windows 2003 x64, should pay attention, that they get the correct driver package named "nForce4_amd_6.69_winserver200364_english_whql.exe". NVIDIA additionally offers a package named "nForce4_amd_6.69_winserver2003_64_english_whql.exe", which is not usable for W2k3 x64, because it doesn't contain any 64bit drivers.

Brandnew alternative option for mainboards with an nForce4 (SataRaid and PataRaid), nForce4xx or nForce5xx chipset:
Users, who want to install XP x64 or W2k3 x64 with the newest 64bit WHQL signed nForce S-ATA and Raid drivers v.6.99 dated 05/15/2007, can take the SATARAID drivers from here and the SATA_IDE drivers from here.
Unpack both packages and store them somewhere. You will need them both for the later driver integration. The extracted "SATA_RAID F6 driver disk 64Bit" folder contains the SATARAID textmode drivers (has a TXTSETUP.OEM file), whereas the "SATA DRIVER 64Bit" folder is similar to the "SATA_IDE" folder (contains just the nForce S-ATA driver as PnP driver).

B. Preparation for the traditional LEGACY driver integration method:

Brandnew:Get the newest 64bit nForce IDE drivers even with nForce3 chipset mainboards:
It is possible to get the newest 64bit nForce SataRaid drivers v.6.99 even with an "old" nForce 3 chipset mainboard, if you take the actual 64bit nForce Unified Remix package 11.16 built by nForcersHQ forum member squall_leonhart69r (for a detailed description of Squall's Remix package and a download link to the whole package look here). Squall's latest nForce chipset driver Package contains the customized brandnew 64it nForce SataRaid drivers v.6.99 dated 05/15/2007 (identical with the above mentioned WHQL signed drivers), but with customized INF files to make them usable with nForce3 chipsets. To reduce the size of the package and to make the preparation of the nForce IDE drivers (as LEGACY folder) easier for you, I have extracted Squall's package, revised and repacked just the LEGACY mode 64it nForce IDE drivers and uploaded them to RapidShare. You can download this special packagehere.
Unzip the package by using a tool like WinRar or 7-zip and store the LEGACY folder somewhere.

If you have an nForce3 or nForce4 SataRaid system and get problems with the integration of WHQL certified drivers (endless reboots at the end of the installation, even after booting in safe mode), you should take one of the available x64 NVIDIA nForce chipset driver packages v. 6.67. For the integration into an XP x64 CD you should take the one you get here, whereas users, who want to create a W2k3 x64 CD, should take the one, which is specially designed for W2k3 x64 (you may download it here). Just unzip the suitable package. Fortunately NVIDIA has established within both packages a subfolder named LEGACY. This subfolder contains all necessary files for a successful integration, no other files or IDE subfolders are needed.

Users with an nVRaid BIOS version lower than 4.84 may have to take the old and not natively 64-bit nForce package 6.56 (downloadable here). Just unzip the package.

Users with an nForce3 mainboard, who get problems with the 6.99 and 6.67 drivers, should take the nForce chipset package v. 6.25, which you can download here. Just unzip the package for the later driver integration.

2. Processing with nLite:

Open nLite and do what you want, but you must choose the button "Integrate Drivers".
During the "Integrate Drivers" part of nLite you have to integrate the suitable nForce SataRaid drivers as textmode drivers (depending on the driver integration method you are going to use).
If you are using the new WHQL driver integration method, you have to integrate the SATARAID subfolder of your prepared nForce chipset driver package as textmode driver and additionally the SATA_IDE subfolder of the same package as PnP driver. You will find them within the IDE\WinXP directory of the package.
Don't be astonished if nLite gives a message, that it is already done. nLite v. 1.2 adds the content of the SATA_IDE subfolder automaticly, if you present the SATARAID subfolder of a complete nForce chipset driver package. This is not an error, but a new feature of nLite to make it easier for you!
Users, who are using the traditional LEGACY driver integration method, have to integrate the LEGACY subfolder of their prepared driver package (see above). They should not integrate any other IDE subfolder (neither SATARAID nor SATA_IDE).
Attention: nLite v. 1.2 adds automaticly the content of the SATA_IDE subfolder as PnP driver, if you integrate the LEGACY subfolder of a complete chipset driver package. You should prevent this by copying the LEGACY subfolder to a place outside the chipset driver package prior to the integration (so nLite will not find the SATA_IDE subfolder). Alternatively you can delete the wrongly integrated PnP driver within nLite's "Driver Integration" section before you start the nLite processing.
If you are going to use one of the the old packages 6.56 and 6.25, you have to integrate just the content of the IDE\WinXP directory (these packages don't have any subfolders).
During the integration of the textmode drivers you have to take all nForce Sata/Raid Controller drivers nLite shows within a popup window as "required". To make it easier for you, nLite has already enabled both needed drivers.
Since nLite v. 1.0 RC7 you have the choice between a single driver or a multiple driver folder integration. You should integrate the nForce SataRaid drivers with the single driver option. Only this way you can be sure, that nLite integrates the correct driver subfolder which you have prepared earlier.
Then you can integrate the other nForce drivers (SMBus, Ethernet etc.) as "normal" PnP drivers. In most cases you can take them out of the same NVIDIA chipset package you have used for the integration of the SataRaid drivers. Users with an nForce3 system may search for better or newer drivers (inclusive GART) than those NVIDIA offers within their 6.25 package.
Tip: If you want to integrate any graphic adapter driver, take a WHQL-certified version.

3. nLite Finishing and CD-Creation:

Create the ISO file by nLite und burn it as a bootable Image with a burning software as Nero (just choose "Recorder" > "Burn Image" and point to your just created ISO file).

At the end you will have a bootable Windows XP x64 or Windows Server 2003 x64 CD with integrated NVIDIA Sata/Raid drivers - no F6 and no floppy will be necessary.

That's all!

Tips for the Installation of the OS:

Make sure, that your BIOS settings are ok. You only will be able to install the OS by booting off your nLited CD, when the CD-ROM device with your nLited CD is set as first bootable device.
Before you begin with the installation of the OS by using your nLited CD, make sure, that there is no floppy within your floppy drive, no USB stick within any USB port and no Memory Card within your Card Reader.
Don't hit F6 and don't insert a driver floppy, if you install an OS by using a CD with integrated nForce SataRaid drivers!

Good luck!

CU
Fernando

dale5605

Jul 14 2005, 08:32 AM

Has anyone tested this yet? Could be very useful to me.

Fernando 1

Jul 14 2005, 01:21 PM

QUOTE (dale5605 @ Jul 14 2005, 03:32 PM)

Has anyone tested this yet? Could be very useful to me.

I just have tested it again with different drivers. In this case I used the NVIDIA chipset package 6.66. The result: It works like a charme.
This time I did not do any changes in TXTSETUP.SIF. So it seems to be easier than I described above.

Can anybody certify this?

dale5605

Jul 14 2005, 01:53 PM

Ok I'm not sure if I have the same drivers as you. These are the chipset drivers I have to integrate.

Audio driver version 4.62 (WHQL)
Audio utility version 4.51
Ethernet NRM driver version 4.82 (WHQL)
Network management tools version 4.85
SMBus driver version 4.48 (WHQL) with updated uninstaller files
Installer version 4.77
WinXP RAIDTOOL application version 4.82
WinXP IDE PATARAID driver version 5.33
WinXP IDE SATARAID driver version 5.33
WinXP IDE SATA_IDE driver version 5.33

I am pretty sure they are most recent, perhaps could you test these and see if they work?

Fernando 1

Jul 14 2005, 03:12 PM

QUOTE (dale5605 @ Jul 14 2005, 08:53 PM)

The NVIDIA 64-bit chipset driver package v. 6.66, that I just testet, contains the following components:

Audio driver version 4.62 (WHQL)
Audio utility version 4.51
Ethernet NRM driver version 4.82 (WHQL)
Network management tools version 4.85
SMBus driver version 4.48 (WHQL)
Installer version 4.77
WinXP IDE PATARAID driver version 5.34
WinXP IDE SATARAID driver version 5.34 (WHQL)
WinXP IDE SATA_IDE driver version 5.34 (WHQL)
WinXP RAIDTOOL application version 4.82

So they are a little more recent.

Nevertheless you can try those you have. You only have to look, if they are the right ones for the chipset you have on your motherboard (nForce3 or nForce4).

EDIT: The chipset driver package you have seem to be the v. 7.12 Intel Editition.

dale5605

Jul 14 2005, 04:45 PM

Sorry about that, those were the wrong ones.

These are the latest versions that I now have.

NForce4 x64 Chipset v7.13

Audio driver version 4.62 (WHQL)
Audio utility version 4.51
Ethernet NRM driver version 4.82 (WHQL)
Network management tools version 4.85
SMBus driver version 4.48 (WHQL) with updated uninstaller files
Installer version 4.77
WinXP IDE PATARAID driver version 5.35
WinXP IDE SATARAID driver version 5.35 (WHQL)
WinXP IDE SATA_IDE driver version 5.35 (WHQL)
WinXP RAIDTOOL application version 5.35

So hopefully you can now test with these latest versions. Your work is very appreciated.

Fernando 1

Jul 15 2005, 10:01 AM

QUOTE (dale5605 @ Jul 14 2005, 11:45 PM)

These are the latest versions that I now have.

NForce4 x64 Chipset v7.13

Audio driver version 4.62 (WHQL)
Audio utility version 4.51
Ethernet NRM driver version 4.82 (WHQL)
Network management tools version 4.85
SMBus driver version 4.48 (WHQL) with updated uninstaller files
Installer version 4.77
WinXP IDE PATARAID driver version 5.35
WinXP IDE SATARAID driver version 5.35 (WHQL)
WinXP IDE SATA_IDE driver version 5.35 (WHQL)
WinXP RAIDTOOL application version 5.35

So hopefully you can now test with these latest versions. Your work is very appreciated.

Although the newest NVIDIA x64 chipset package v. 7.13 is specially designed for nForce4 boards with Intel CPU, I tested these drivers with my DFI Lanparty NF4 D-Ultra (with AMD Athlon64 CPU).
The integration of these drivers into a bootable CD with nLite 1.0 b4 works like charme, when you are doing, what I have written above.

Attention: The way to integrate these x64 Raid-drivers is easier than I thought, when I opened this topic. Meanwhile I certified by a couple of tests, that there is no need to make any changes in TXTSETUP.SIF!

dale5605

Jul 15 2005, 10:34 AM

QUOTE (Fernando 1 @ Jul 15 2005, 12:01 PM)

QUOTE (dale5605 @ Jul 14 2005, 11:45 PM)

It should work, the 7.13 package is for ALL nvidia nforce4 chipset, AMD and Intel!!!

Also thank you for figuring this out. I have done it and it appears to be running well on vmware virtual machine.

Fernando 1

Jul 15 2005, 06:11 PM

I have just tried to integrate the new WHQL-certified NVIDIA Raid drivers from the chipset package 6.66 into a XP x64 CD with the brand new version nLite 1.0 b5 without making any changes I described above.
The integration failed and ended with endless-reboots!

So the new version does not fix the problem with the installion of nForce x64 drivers on boards with a NVIDIA Raid array.

But the solution is on page 1 of this thread .............

CU
Fernando

dale5605

Jul 16 2005, 08:53 AM

Tried integrating the 32bit 7.13 drivers without doing any editing like you explained here. And windows install hangs on the "installing devices" part.

Fernando 1

Jul 16 2005, 09:46 AM

QUOTE (dale5605 @ Jul 16 2005, 03:53 PM)

Tried integrating the 32bit 7.13 drivers without doing any editing like you explained here. And windows install hangs on the "installing devices" part.

If you try to install 32bit drivers into a 64bit OS, that won't work!

dale5605

Jul 16 2005, 10:28 AM

QUOTE (Fernando 1 @ Jul 16 2005, 11:46 AM)

QUOTE (dale5605 @ Jul 16 2005, 03:53 PM)

Tried integrating the 32bit 7.13 drivers without doing any editing like you explained here. And windows install hangs on the "installing devices" part.

If you try to install 32bit drivers into a 64bit OS, that won't work!

On a 32bit OS. Do I need to do that same editing WINNT as I do for x64?

Fernando 1

Jul 16 2005, 10:55 AM

QUOTE (dale5605 @ Jul 16 2005, 05:28 PM)

On a 32bit OS. Do I need to do that same editing WINNT as I do for x64?

Normally those settings I described in the first topic of this thread are only necessary with 64-bit drivers. But you can try it neverless - you cannot do anything wrong with it, when you take the correct drivers for your system.
If you have an nForce4 chipset, I would recommend the new WHQL-certified official NVIDIA driver package v. 6.66.
To give you a more detailed answer I should know your hardware details (chipset, Sata or Pata drives, sort of Raid array etc).
CU
Fernando

noen

Jul 19 2005, 02:46 PM

This does not work on my SN95G5 Shuttle NForce 3 board.

I've been trying every method on this board.

This one gets the furthest, but I just get caught in a reboot loop after it finishes installing.

Fernando 1

Jul 19 2005, 03:13 PM

QUOTE (noen @ Jul 19 2005, 09:46 PM)

This does not work on my SN95G5 Shuttle NForce 3 board.
This one gets the furthest, but I just get caught in a reboot loop after it finishes installing.

Did you use the new nLite Version 1.0 Beta5?
If yes - try it with the "old" Version 1.0 Beta4!

Look here:
http://www.msfn.org/board/index.php?showto...ndpost&p=355895

noen

Jul 19 2005, 03:21 PM

Yes I have tried with both versions.

I have also done the manual installs by editing txtsetup.sif and winnt.sif, which didnt work either.

I am going to roll back to the official 6.25 drivers. I have been working with the 6.56 betas.

First im going to pop into the recovery console and see if I cant figure out what its dying on during bootup

Fernando 1

Jul 20 2005, 01:34 AM

QUOTE (noen @ Jul 19 2005, 10:21 PM)

Yes I have tried with both versions.
I have also done the manual installs by editing txtsetup.sif and winnt.sif, which didnt work either.

I suppose, that you have done something wrong.
You can make a lot of mistakes by editing the TXTSETUP.SIF. That is why I searched for an easier method.

Try it again with nLite 1.0 Beta4 and follow exactly the instructions given by me in the first post of this thread.

Good luck!
Fernando

noen

Jul 20 2005, 03:49 AM

Well I tried it again, it bombs out into eternal rebooting on acpitabl.dat

So I went and searched for it. Looks like only the 6.34 and 6.66 nvraid drivers will actually work (and the 6.34's give a nagging error during install)

So I am downloading the 6.66 even though it's for the NF4, hopefully I can rip the SATA raid drivers and they will function properly.

I'll report back in a bit

_______

Update: The nForce4 6.66 AMD drivers dont work either. Last hope looks to be the 6.34

Fernando 1

Jul 20 2005, 06:28 AM

QUOTE (noen @ Jul 20 2005, 10:49 AM)

Well I tried it again, it bombs out into eternal rebooting on acpitabl.dat
So I went and searched for it. Looks like only the 6.34 and 6.66 nvraid drivers will actually work (and the 6.34's give a nagging error during install)
So I am downloading the 6.66 even though it's for the NF4, hopefully I can rip the SATA raid drivers and they will function properly.
Update: The nForce4 6.66 AMD drivers dont work either. Last hope looks to be the 6.34

As I have written in first post, I have only tested this method with my nForce4 chipset, but I am nearly sure, that it works on nForce3 systems too. My tests with the integration of the Sata/Raid drivers from the NVIDIA driver package v. 6.66 (64-bit version) were without any issue.

Are you sure, that you have taken the 64-bit versions of the chipset driver package 6.66? I ask this, because NVIDIA gave the wrong download link for a while with the result, that many users tried to install 32-bit drivers onto a 64-bit system. That won't work!

Please let me know the results of your further tests.

CU
Fernando

noen

Jul 20 2005, 04:07 PM

Yes, the installation proces works completely.

It fails AFTER setup has finished (When the gui mode install completes and restarts to begin windows)

It hangs on loading acpitabl.dat, which after doing a lot of googling seems to be caused by loading an incorrect, corrupt or wrong driver set.

Actually I do have a question that isnt clear in your guide.

Yes I am 100% sure using the 6.66 64bit drivers.

I have the sata/pata folders as descrtibed.

However there is no nvatax64.inf file int he sataraid folder, and there are two copies of the nvatax64.sys folder.

Which do I use, and do I put them all in the same single OEMDIR directory?

Fernando 1

Jul 21 2005, 12:52 AM

QUOTE (noen @ Jul 20 2005, 11:07 PM)

Yes, the installation proces works completely.
It fails AFTER setup has finished (When the gui mode install completes and restarts to begin windows)
It hangs on loading acpitabl.dat, which after doing a lot of googling seems to be caused by loading an incorrect, corrupt or wrong driver set.
Actually I do have a question that isnt clear in your guide.
Yes I am 100% sure using the 6.66 64bit drivers.
I have the sata/pata folders as descrtibed.
However there is no nvatax64.inf file int he sataraid folder, and there are two copies of the nvatax64.sys folder.
Which do I use, and do I put them all in the same single OEMDIR directory?

1. It is clear, that there is no NVATAX64.INF file in your SATARAID subfolder. That is why you have to take this file from the PATARAID subfolder to put in into the OEMDIR directory.
2. I don't believe, that you have 2 NVATAX64.SYS folders. What you certainly mean is, that you have such a file in both subfolders SATARAID and PATARAID. These 2 files are totally identical.
3. I believe, that your problem has nothing to do with the integration of the Sata Raid drivers, but with the GART drivers. As you should know, systems with nForce3 chipset need a GART driver. This driver is missing in the NVIDIA chipset package 6.66, because it was designed for nForce4 chipsets, which do not need any GART drivers.

My tip for you: Integrate the Sata Raid drivers with nLite 1.0 b4 as textmode drivers and the SMBus drivers from the package 6.66, but integrate additionally the GART drivers from another 64-bit chipset package (for example 6.25).

Good luck!
Fernando

Metalljens

Jul 21 2005, 10:41 AM

Can someone confirm which is the latest drivers that works with nforce3, 32 - and 64, integrated or not.

I have tried to up date to the new 6.66 32bit but they dont seem to work for me.
and yes im aware that the gart driver dont exist, but i cannot even update the raid controllers manually, the latest that works for me is 6.53, that works like a charm when slipstreaming windows xp with nlite too.

Fernando 1

Jul 21 2005, 11:06 AM

QUOTE (Metalljens @ Jul 21 2005, 05:41 PM)

Can someone confirm which is the latest drivers that works with nforce3, 32 - and 64, integrated or not.
I have tried to up date to the new 6.66 32bit but they dont seem to work for me.
and yes im aware that the gart driver dont exist, but i cannot even update the raid controllers manually, the latest that works for me is 6.53, that works like a charm when slipstreaming windows xp with nlite too.

The situation for nForce3 user is really awfull - you don't have any official and WHQL-certified x64 drivers for your chipset at the moment and the last official 32-bit version is the old package 5.10.
As many users report, the driver package 6.66 (32-bit and 64-bit version) runs without any problems on nForce3 mainboards. The latest driver package version is 7.13.

Maybe you should wait a few days. NVIDIA seems to release a new (unified and certified?) driver within the next days.

P.S.: I would newer update a Raid driver on a running system. It may end with a loss of your Raid array.

Metalljens

Jul 21 2005, 12:52 PM

Yes, it really is awful.
But what i dont understand is how can some of the nforce4 standalone packages work with nforce3 while others dont?

As i said earlier updating manually wouldnt do it for me.

So i did like this, i copied the nvatabus.inf from pataraid to sataraid just like you said, then i ran the nvidia setup and just chosed to install smbus and ide, when it came to the part of installing the idedrivers, i choose to install the SW drivers it said that the existing files were newer than the ones i was installing, and asked if i wanted to overwrite them, (this is for the nvidia pata and the sata controllers) (the ones i had installed was from the 6.53, and the ones i tried to install are from the 7.13) i answered yes to overwrite them and it worked like a charm.

It seems as though i cant install the ethernet driver from anything newer than the 6.53 drivers, otherwise it just bsod when installing using nvidia setup program.
Havent tried to manually install it yet, it doesnt seem that important either.

Havent tried the audiodrivers though, because i use the realtek ones instead.

So i have now made a driver package with smbus- and idedrivers from 7.13
Ethernet drivers from 6.53 and gart drivers from, well dont remember which was the latest.

This is for Xp32! havent tried to slipstream these drivers yet i will try it soon.
as for Xp64 i shall try the same thing there.

Fernando 1

Jul 21 2005, 01:08 PM

QUOTE (Metalljens @ Jul 21 2005, 07:52 PM)

It seems as though i cant install the ethernet driver from anything newer than the 6.53 drivers, otherwise it just bsod when installing using nvidia setup program.
Havent tried to manually install it yet, it doesnt seem that important either.
So i have now made a driver package with smbus- and idedrivers from 7.13
Ethernet drivers from 6.53 and gart drivers from, well dont remember which was the latest.

The mixing of drivers from different packages is no problem, when you try to integrate them with nLite. You only may get difficulties, when you install them by setup.
Here you can find a lot of things about nForce drivers:
http://www.nforcershq.com/forum/latest-dri...-3-vt60240.html

When you try to integrate your driver mix with nLite, I would not integrate any ethernet drivers. As you have written, you have difficulties to find a working driver. It will be easy to install this driver later (may be with the one from the coming nForce version 8.03?)

Sucka

Jul 25 2005, 12:57 AM

Did it exactly as explained and got 2 BSOD's during the install. The problem i had before was a BSOD right when it's supposed to go the the desktop. Glad someone got it to work though

Edit: Got it to run all the way through, same exact problem as with floppy drivers. Instant BSOD before desktop loads. Sorry but no dice on this one folks.

Fernando 1

Jul 25 2005, 02:02 AM

@ Sucka:

What kind of hardware do you have (nForce3 or nForce4, Sata Raid or Pata Raid) and which nForce driver version did you use?

Sucka

Jul 25 2005, 02:03 AM

Found working F6 drivers for RAID 0.

http://www.planetamd64.com/index.php?download=266

Sucka

Jul 25 2005, 02:04 AM

Fernando:

DFI SLI-D 6/23-2
AMD X2 4400+
2x250 Hitachi 16mb NCQ RAID 0

Followed your guide all the way through and first two installs i got BSOD's and the third it fully installed, but i got that same old BSOD as it goes to desktop i had been getting before. I actually just found working drivers, so i'm all set!

Fernando 1

Jul 25 2005, 02:42 AM

QUOTE (Sucka @ Jul 25 2005, 09:04 AM)

DFI SLI-D 6/23-2
AMD X2 4400+
2x250 Hitachi 16mb NCQ RAID 0
Followed your guide all the way through and first two installs i got BSOD's and the third it fully installed, but i got that same old BSOD as it goes to desktop i had been getting before. I actually just found working drivers, so i'm all set!

You did not mention your mainboard and chipset, but only the BIOS version. But as I am an owner of a DFI UT Lanparty Ultra-D, I think, that we both have the same chipset (nForce4 Ultra).
It is clear, that you can install Windows XP x64 by F6/floppy method, when you use the NVIDIA chipset driver package 6.56 or older, the problems began with the drivers from version 6.66 and higher.
As I made my tests only with my Sata Raid board, I cannot give you a safe solution for your BSOD problem. It's maybe caused by other hardware (did you turned off all USB devices during setup?).

Sucka

Jul 25 2005, 04:14 PM

Sorry, the SLI-D is an NF4 (all SLI is NF4).

I couldn't even get the drivers from any version to work. It took that specific set to work properly. The BSOD wasn't a hardware issue, but a compatibility issue with x64 and RAID on the NF4.

I'm amazed Microsoft would release this and not know that RAID didn't work?! Not to mention the fact you need to jump through hoops to figure it out.

Fernando 1

Jul 26 2005, 02:32 AM

QUOTE (Sucka @ Jul 25 2005, 11:14 PM)

The BSOD wasn't a hardware issue, but a compatibility issue with x64 and RAID on the NF4.
I'm amazed Microsoft would release this and not know that RAID didn't work?! Not to mention the fact you need to jump through hoops to figure it out.

It seems to me, that Microsoft and NVIDIA don't like and don't trust each other. Maybe all our problems will be solved, when NVIDIA will present their first WHQL-certified 64bit SataRaid drivers for all nForce chipsets, that support 64 Bit.

jarky

Aug 3 2005, 02:48 PM

okay I know this thread has gone cold but i need some help. I went through the steps in the first thread exactly and the disk boots up fine and reads my drives as 1 goes through the install reboots and goes through the gui install and reboots. At which point I get a windows load failure with options to boot normal, safe etc. no matter what I choose the computer tries and reboots and takes me right back to that safe boot screen.
please help me out here i'm using nlite v4 most current xp 64drivers but no go. I got no other option but to get this disk to work since I can't get my fdd to post.

Fernando 1

Aug 4 2005, 01:52 AM

QUOTE (jarky @ Aug 3 2005, 09:48 PM)

I went through the steps in the first thread exactly and the disk boots up fine and reads my drives as 1 goes through the install reboots and goes through the gui install and reboots. At which point I get a windows load failure with options to boot normal, safe etc. no matter what I choose the computer tries and reboots and takes me right back to that safe boot screen.

As I have nearly the same hardware as you (DFI Lanparty NF4 Ultra-D as mainboard and 2 Samsung Sata2 hard disk drives), I am sure, that the [OemInfFiles] method is suitable for your system too.
Please have a look on your bootable CD and check, if you really have
1. a root folder named $OEM$ with a subfolder named $$ and a subsubfolder named OEMDIR,
2. the correct files within the subsubfolder OEMDIR and
3. the exactly correct changes of the WINNT.SIF file
as I described in post No 1.
Only a little mistake can be the reason for the issue you have described.

To help you, I need some more informations:
Did you integrate the files from the nForce SATARAID folder as TEXTMODE drivers?
Did you integrate other drivers than the nForce SataRaid ones? If yes, which drivers did you integrate by nLite?
Which NVIDIA chipset driver version did you use?
Did you disable the Silicon Image Raid controller?
Do you use any other problematic hardware devices?
Did you unplugg all USB devices during installation of the OS?

CU
Fernando

jarky

Aug 4 2005, 04:52 AM

QUOTE

Please have a look on your bootable CD and check, if you really have
1. a root folder named $OEM$ with a subfolder named $$ and a subsubfolder named OEMDIR,
2. the correct files within the subsubfolder OEMDIR and
3. the exactly correct changes of the WINNT.SIF file
as I described in post No 1.

Yup it's all right the 3 files you have listed in post 1 are at d:/$OEM$/$$/OEMDIR, I have typed out the new lines in the winnt.sif file at least 10 times I even copied directly from your post a few time just to be sure.

QUOTE

Did you integrate the files from the nForce SATARAID folder as TEXTMODE drivers?

YEs I did integrate as text mode drivers despite the pop up warning in nlite

QUOTE

Did you integrate other drivers than the nForce SataRaid ones? If yes, which drivers did you integrate by nLite?

No I didn't do any other drivers just the nvidia driver found in the SATA folder Which actually has nlite integrate 2 drivers

QUOTE

Which NVIDIA chipset driver version did you use?

6.66 for xp64

QUOTE

Did you disable the Silicon Image Raid controller?

Hmmm, Disable it? I didnt' know you could disable the SI controller. I never enabled it and have never had anything hooked up there. If it can be disabled I assume i'll find an option somewhere in the bios, I'll hunt for it.

QUOTE

Do you use any other problematic hardware devices?

My **** 3.5 fdd won't post, which is why i'm doing this.

QUOTE

Did you unplugg all USB devices during installation of the OS?

Yup the only thing pluged up is the HDs, 1 optic drive, keyboard and monitor

Fernando 1

Aug 4 2005, 05:29 AM

@ jarky:

Did you enable NCQ (for Sata2 hard disk drives)?
Is it possible, that you stress your RAM and CPU too much by overclocking your system (a 64-bit system needs more resources than a 32-bit system)?
What is the reason for your problem with your floppy disk drive?

I think, that you have a problem with your board.
Try to unplug the floppy cable and disable the floppy controller in the BIOS.

jarky

Aug 4 2005, 04:09 PM

I Don't know about ncq i only know how to enable it in windows. My HD are un jumpered straight out of the static bag. so that sata II enabled spead stream disabled, I have speed stream disabled in my bios as well. Should I activate those jumpers and enable in bios, I didn't think that would make a difference.

I don't think it's my oc settings the are not very extreme at this point and I tried reseting to optimum after my last reboot loop and got the same results.
I have A and B drives set to none at this point.
I hope it's not my mobo it would be a b***h to pull my water cooling rig out.

jarky

Aug 4 2005, 05:21 PM

One question since our bios is at least similar. you asked id I had the silicon image controller disabled, where do I find the option to disable this controller. I looked and looked and I'm not seeing it. IN the bios raid menu I have sata 5 - sata 8 disabled, is that what you mean?

Fernando 1

Aug 5 2005, 01:35 AM

QUOTE (jarky @ Aug 5 2005, 12:21 AM)

You are right: Our BIOS is nearly similar (I have the new official version 6-23), but our mainboard is different, because you have 2 RAID controllers (NVIDIA and Silicon Image). So there should be a possibility to enable/disable the NVIDIA or Silicon Image Raid controller within the BIOS. But I don't know where, because I don't have the SLI version of the DFI NF4 board.

dale5605

Aug 5 2005, 10:01 AM

SATA 4-7 is the SIL. So disabling those would probably do the trick.

jarky

Aug 5 2005, 11:26 AM

My bios doesn't even show me sata 5-8 since I have nothing hooked up to the silicon image controller. I'm really at the end of my rope, I can't get the fdd to work and can't get the slipstream disk to work (despite many attempts). Got ANY other ideas before I pull out the jack hammer so I can RMA this board.

rtruesdale

Aug 12 2005, 07:14 AM

preface, never have done this with install cd before.
nvidia nforce driver are the latest as of now 6.66:}

guys, maybe i'm missing somthing in the process but somthing is missing here. I don't see the winnt.sif file until after I create the install (not iso). then its created and can add the sections mentioned.

also when adding my nvidia sata raid drivers i first after add the ini file. there is 2: install and oem. I'm grabbing both not know which I should grab.

when I boot to this disk I get

NTLDR corrupt message

ideas?

Fernando 1

Aug 12 2005, 07:36 AM

QUOTE (rtruesdale @ Aug 12 2005, 02:14 PM)

nvidia nforce driver are the latest as of now 6.66:}
I don't see the winnt.sif file until after I create the install (not iso). then its created and can add the sections mentioned.
also when adding my nvidia sata raid drivers i first after add the ini file. there is 2: install and oem. I'm grabbing both not know which I should grab.

1. The latest NVIDIA nForce chipset driver package is v. 7.13 (unless it is specified for SLI Intel chipsets).
2. The WINNT.SIF is created by nLite, when you choose the unattended install. If you stop nLite before it ends the processing of all requested tasks (integration of drivers etc.), you will not see a WINNT.SIF.
3.When you are going to integrate the drivers, there is an option "OEM Pre-Install". Let it as it is (activated), when you want to integrate the SataRaid drivers.

rtruesdale

Aug 12 2005, 07:37 AM

rtruesdale

Aug 12 2005, 07:42 AM

This is for an AMD chip and specifically what I'm downloading is

nForce4 AMD Edition (6.66) - Windows XP Professional x64

Version: 6.66
Release Date: July 15, 2005
WHQL Certified

* Audio driver 4.62 (WHQL)
* Audio utilities 4.51
* Ethernet driver 4.82 (WHQL)
* Network management tools version 4.85
* SMBus driver 4.48 (WHQL)
* NVIDIA PATA RAID driver 5.34
* NVIDIA SATA RAID driver 5.34 (WHQL)
* NVIDIA SATA IDE driver 5.34 (WHQL)
* NVIDIA RAID Application 4.82
* Installer 4.77

Fernando 1

Aug 12 2005, 08:00 AM

Take these ones, if you have an AMD nForce4 chipset.
Before you start installing XP x64, be aware, that you have flashed the latest BIOS version, because the new nVidia Raid drivers need the nVidia Raid BIOS version 4.84.

dale5605

Aug 12 2005, 08:04 AM

I don't see what the problem with the winnt.sif is. Do all the steps in nLite except create ISO and after all that is done and winnt.sif is created then do the editing.

rtruesdale

Aug 12 2005, 09:11 AM

QUOTE (Fernando 1 @ Aug 12 2005, 08:36 AM)

QUOTE (rtruesdale @ Aug 12 2005, 02:14 PM)

I don't specifically see "OEM Pre-Install" option but I'll assume this is set. I am running the release of nLite you recommended (as opposed to beta 5) as an fyi.

Fernando 1

Aug 12 2005, 09:24 AM

1. You see the OEM-Preinstall option, when you open the section "Unattended Install".
2. Use nLite 1.0 Beta4.

rtruesdale

Aug 12 2005, 10:28 AM

finaly up:)!!!

i plugged in my data disk now that I'm installed (200 gig drive I install unplugged to get xp on my raid). drive is coming up empty!!! what could be wrong? i know the data should be there!!

This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.