[Fernando 1]

sadseh, on Jun 29 2006, 07:31 AM, said:

I've a laptop with a Turion 64 X2, an nVidia nForce 430/410 chipset, and a Windows XP x64 that I'm trying to install. I used nLite to re-compile the Windows with only the SATA_IDE drivers, from the .667 Legacy folder, in TXT mode. I also added the boot-mode option (no tweaks or anything else, to keep it simple).

The setup went fine, it gave me no error that it "can't copy nvraid.sys" during the DOS part, and everything went smoothly until it finished everything and rebooted me into the actual Windows environment. The Windows XP x86 splash image quickly flashed by, was quickly replaced by a blue screen, and the comp immediately restarted.

For any help I need some informations:
Do you use Raid or not? If yes, which nVRaid BIOS version do you see on second boot display?
How many and which sort of hdd's are connected to your mainboard?
Which nForce IDE driver package did you use?
Which SataRaid driver subfolder (SATA_IDE or LEGACY) did you integrate?
What do you mean with "It gave me no error that it can't copy nvraid.sys"? (the 64-bit driver package does not contain such a file, the correct name is NVRDx64.SYS)

[sadseh]

Fernando 1, on Jun 29 2006, 04:35 AM, said:

For any help I need some informations:
Do you use Raid or not? If yes, which nVRaid BIOS version do you see on second boot display?
How many and which sort of hdd's are connected to your mainboard?
Which nForce IDE driver package did you use?
Which SataRaid driver subfolder (SATA_IDE or LEGACY) did you integrate?
What do you mean with "It gave me no error that it can't copy nvraid.sys"? (the 64-bit driver package does not contain such a file, the correct name is NVRDx64.SYS)

Let me try to answer them as detailed as I can:

1. I don't think I use Raid. The laptop simply comes with an nForce 430/410 Chipset. As such, I don't try to include the RAID drivers in nLite, but it forces me to. When I select "nvatax64.inf" it gives me a menu asking me what mode to use (I choose TXT) and which of the two drivers in the menu to use (I pick both, as it says required on each, and the first post gave me the impression that I should pick them). But no, no Raid.

2. I have only one HDD, the details of which I couldn't give you right now as my laptop is dead right now, so I can't use system manager. All that the HP says about it is that it is "80 GB 5400 RPM SATA Hard Drive." If there's a way I can find out what it is without logging into Windows, I'll gladly try to do it.

3. There is a long and a short answer for this. In short, I used the \IDE\Win64\Legacy folder found in the 6.67 driver package that the first post linked to.

In long, before finding this thread, I have tried the latest nForce 430/410 package found on nVidia's site at the moment, which is called "8.26_nforce_winxp64_international.exe." I don't know why it says international as I got it off the English main download link, nor can I explain the 8.26 version number, when the first post has been discussing various packages starting with 9. This approach worked the same as the Legacy one--full install and then a BSOD at boot.

Before even that, I tried integrating the chipset drivers that came with my laptop, but they were 32-bit and so useless for this case.

4. Ignore that comment. I was simply trying to say that I got no errors during any part of the installation. I just threw in a .sys that came first to my memory, which apparently is the one from the 32-bit driver package to come with my laptop. Sorry for the confusion. I think the error message I referred to in the second paragraph of point 3 would be more fitting here.

Edit: I remember now. The reason I said nvraid.sys is because I also tried manually re-tagging the 32-bit drivers that came with my laptop originally to 64-bit. That didn't work, of course, because during the setup, it was still looking for the original filenames, including nvraid.sys.

Also, if I forgot to mention it, I've been using the latest nLite found on the site, the 1.0 final.

Lastly, I just looked at the nVidia page ( http://www.nvidia.com/object/nforce_nf4_43...nxp64_8.26.html ), and it says all the drivers are WHQL certified. Yet they refuse to work. Why is this?

This post has been edited by sadseh: 29 June 2006 - 12:00 PM

[sadseh]

Never mind. The guide on this page didn't work for me, but that was because of nLite. I found a guide you posted on VitaliGraf.de, http://board.vitalig...ead.php?tid=159 , and it worked perfectly with the Unattended Windows CD Creator and its "Bad Controller" option.

I thank you, my good man, for finally ending the 3-day misery that I've frenzied myself by trying to install the damnable Windows on my laptop.

Danke.

[Fernando 1]

sadseh, on Jun 29 2006, 11:13 PM, said:

Never mind. The guide on this page didn't work for me, but that was because of nLite. I found a guide you posted on VitaliGraf.de, http://board.vitalig...ead.php?tid=159 , and it worked perfectly with the Unattended Windows CD Creator and its "Bad Controller" option.

Thank you for posting how you fixed your problem.

CU
Fernando

[wizzbangca]

Setup cannot find:
nvraid.cat
nvraidco.dll
nvrdx64.inf
nvrdx64.sys

Don't know where nlite told the setup program to look for the files. I have them in all folders of the disc. I have all hard drives out except for the raid 0 drives. I press escape to bypass the files, I get bsod when windows tries booting to the gui portion of setup.

Using the latest nforce driver set. Any suggestions?

[Fernando 1]

wizzbangca, on Jul 11 2006, 06:43 AM, said:

Setup cannot find:
nvraid.cat
nvraidco.dll
nvrdx64.inf
nvrdx64.sys
Don't know where nlite told the setup program to look for the files. I have them in all folders of the disc. I have all hard drives out except for the raid 0 drives. I press escape to bypass the files, I get bsod when windows tries booting to the gui portion of setup.
Using the latest nforce driver set. Any suggestions?

You probably have done something wrong (for example using 32-bit drivers for XPx64 or pressing F6 during Setup).
Please give me some informations about your system (sort of nForce chipset,number and sort of hdd, sort of RAID etc.) and the nForce SataRaid driver package version you tried to integrate.

[wizzbangca]

Fernando 1, on Jul 11 2006, 02:07 AM, said:

You probably have done something wrong (for example using 32-bit drivers for XPx64 or pressing F6 during Setup).
Please give me some informations about your system (sort of nForce chipset,number and sort of hdd, sort of RAID etc.) and the nForce SataRaid driver package version you tried to integrate.

First of all, they're the 64 bit drivers. I'm not that lame. The write up mentions an inf file that no longer exists. I'm going to try to get the 6.67 drivers, slip those and then upgrade IF the slipping works. Crazy thing, all the other latest nforce drivers slip just fine.

Now the info: nforce 4 chipset, 2 80gb sata1 drives in raid 0. No floppy drive. Go to nvidia's site, those are the drivers I was using.

[Fernando 1]

wizzbangca, on Jul 11 2006, 05:20 PM, said:

Fernando 1, on Jul 11 2006, 02:07 AM, said:

You probably have done something wrong (for example using 32-bit drivers for XPx64 or pressing F6 during Setup).
Please give me some informations about the nForce SataRaid driver package version you tried to integrate.

Go to nvidia's site, those are the drivers I was using.

On NVIDIA's site are a lot of different nForce chipset packages. Which version did you take?
I ask this, because NVIDIA is presenting 64-bit packages on their FTP site without any 64-bit drivers. As a consequence these drivers do not work at all with XPx64 or W2k3x64. That is the reason for my warning within my guide:

Don't use one of the specially for W2k3x64 designed 6.69 packages NVIDIA has on their FTP-Server, they don't contain 64-bit drivers!

[Fernando 1]

@ all nLite 1.0 Final users with problems integrating the nForce SataRaid drivers:

If you get a message like "Setup can't find/copy file xyz", this might be caused by an issue of the Final version of nLite 1.0.
For details look here .
My suggestion: Take nLite 1.0 RC8 until Nuhi has fixed the problem.

[nuhi]

Just integrate that particular driver with rc8, otherwise final is better.

But it would be good to apply the fix yourself if you can figure it out from that topic.

[wizzbangca]

Found the answer. First off, started with a fresh x64, yet again. Integrated the drivers, but not the latest one. I used the motherboard cd. That's right, I tried integrating the drivers before the board came in. The manufacturer said Nforce 4, but in reality the drivers are nforce 4 sli. Might not make a difference, but the drivers on the cd slipped no problem using nlite final. Anyone using asus boards, use the drivers disc. All files are right where they belong for slipping.

Thanks everyone.

[Fernando 1]

@ all users with an nForce SataRaid system:

After a lot of new tests with the current version of nLite I figured out, that it is possible to get the newest WHQL certified nForce SataRaid drivers installed onto an nForce SataRaid system, when you do a special combination of the nForce SataRaid integration:

• Integration of the SATARAID subfolder (from the suitable 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 Windows XPx64, all nForce IDE drivers (the SATA and RAID ones) were WHQL certified, which is very important especially for Microsoft's 64-bit operating systems. Another advantage: Windows did install the MS IDE instead of the NVIDIA PATA (=IDE s/w) drivers (a lot of nForce users have troubles with the NVIDIA ones).

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 actual nForce chipset (except the nForce2 and nForce3 ones).

Please post a feedback of your results into this thread! This would be very helpful for all other nForce SataRaid users.

After having done some more tests I will modify the first post of this thread. Have a look at it for more details about the new nForce SataRaid integration method.

CU
Fernando

[stowe39]

Thanks for these instructions! The newer method worked brilliantly for me.

I have a asus m2npv-vm motherboard (430 chipset), am2 64 bit 3800+, 4gb ram and mirrored 320gb hdds.

I had tried the f6 and floppy disk method - but only got bsods.

I have now successfully installed 2003 svr x64 using the 8.26_nforce_winxp64_international drivers.

Cheers

Kym

[shodan]

is there anything new with the thread for win2k3 R2 x64 ?

[Fernando 1]

shodan, on Oct 16 2006, 01:21 AM, said:

is there anything new with the thread for win2k3 R2 x64 ?

As Stove 39 has written within the last post, the new WHQL driver integration method does work with W2k3 x64. So there is a good chance for you too.

My advice: Download the newest W2k3 x64 driver package suitable for your special nForce chipset and integrate the SATARAID (as Textmode) and the SATA_IDE (as PnP) subfolder into the first CD of your R2 CD pack.

Please report here about the result. If you succeed, I will update my guide.

CU
Fernando

[shodan]

Hi,

I have a nforce 570-based board (msi k9n platinum sli)
I downloaded 9.16_nforce_winxp64_international_whql.exe from nvidia (http://download.nvid...tional_whql.exe)

(this file is for nForce 570 SLI/570/550 chipsets, there is a separate file for 590 users http://download.nvidia.com/Windows/nForce/...ternational.exe
that file probably isn't whql'd)

I did integrate drivers , then insert-> single driver , then selected IDE\WinXP\sataraid and textmode
next I tried to add IDE\WinXP\sata_ide as pnp driver but it said can't add it's already there

I ended up with this in my "last session.ini"
[Drivers]
C:\Public\Downloads\9.16_nforce_winxp64_international_whql\IDE\WinXP\sata_ide\nvata64.inf,0
C:\Public\Downloads\9.16_nforce_winxp64_international_whql\IDE\WinXP\sataraid\nvrdx64.inf,BUSDRV
C:\Public\Downloads\9.16_nforce_winxp64_international_whql\IDE\WinXP\sataraid\nvrdx64.inf,RAIDCLASS

made my iso , put it in the drive , install went fine without a sataraid-related itch

well I had another problem but I'm not sure it's related to this driver

when I ran my nlited install, first I got the textmode part (properly detected the driver & partitions)
but after it rebooted it complained that "system root/system32/ntoskrnl.exe" was missing or corrupt
with a rescue disk I checked and the file was in the right place
by chanced I though of looking at my boot.ini file

it said
multi(0)disk(0)rdisk(1)partition(1)\SYSTEM\PROGRAMS\WINDOWS="Windows Server 2003 Enterprise x64 Edition" /noexecute=optout /fastdetect
but the entry of my previous install said
multi(0)disk(0)rdisk(0)partition(1)\USR\WINDOWS="Windows Server 2003 Enterprise x64 Edition" /fastdetect /noexecute=optin /usepmtimer

so I changed the entry of the new system to
multi(0)disk(0)rdisk(0)partition(1)\SYSTEM\PROGRAMS\WINDOWS="Windows Server 2003 Enterprise x64 Edition" /noexecute=optout /fastdetect

and it worked fine
I had a usb drive plugged in that could be the cause (but I would have expected a wrong disk() not rdisk() ?? well anyway there are other things wrong with this install so I'll have to reinstall anyways, I'll keep you informed)

[Fernando 1]

shodan, on Oct 16 2006, 08:29 AM, said:

I have a nforce 570-based board (msi k9n platinum sli)
I downloaded 9.16_nforce_winxp64_international_whql.exe from nvidia (http://download.nvid...tional_whql.exe)
(this file is for nForce 570 SLI/570/550 chipsets, there is a separate file for 590 users http://download.nvidia.com/Windows/nForce/...ternational.exe
that file probably isn't whql'd)
I did integrate drivers , then insert-> single driver , then selected IDE\WinXP\sataraid and textmode
next I tried to add IDE\WinXP\sata_ide as pnp driver but it said can't add it's already there
I ended up with this in my "last session.ini"
[Drivers]
C:\Public\Downloads\9.16_nforce_winxp64_international_whql\IDE\WinXP\sata_ide\nvata64.inf,0
C:\Public\Downloads\9.16_nforce_winxp64_international_whql\IDE\WinXP\sataraid\nvrdx64.inf,BUSDRV
C:\Public\Downloads\9.16_nforce_winxp64_international_whql\IDE\WinXP\sataraid\nvrdx64.inf,RAIDCLASS
made my iso , put it in the drive , install went fine without a sataraid-related itch

Hi Shodan,
thank you very much for your report, because it might be very helpful for other users.

As you can see within the "last session.ini", nLite has integrated not only the SATARAID, but also the SATA_IDE subfolder. This is a new feature of nLite. Since v. 1.20 nLite will take automaticly both subfolders, if you present the SATARAID subfolder of an nForce chipset package. This explains why nLite "said", that the content of the SATA_IDE folder is already there.

shodan, on Oct 16 2006, 08:29 AM, said:

well I had another problem but I'm not sure it's related to this driver
when I ran my nlited install, first I got the textmode part (properly detected the driver & partitions)
but after it rebooted it complained that "system root/system32/ntoskrnl.exe" was missing or corrupt
with a rescue disk I checked and the file was in the right place
by chanced I though of looking at my boot.ini file
it said
multi(0)disk(0)rdisk(1)partition(1)\SYSTEM\PROGRAMS\WINDOWS="Windows Server 2003 Enterprise x64 Edition" /noexecute=optout /fastdetect
but the entry of my previous install said
multi(0)disk(0)rdisk(0)partition(1)\USR\WINDOWS="Windows Server 2003 Enterprise x64 Edition" /fastdetect /noexecute=optin /usepmtimer
so I changed the entry of the new system to
multi(0)disk(0)rdisk(0)partition(1)\SYSTEM\PROGRAMS\WINDOWS="Windows Server 2003 Enterprise x64 Edition" /noexecute=optout /fastdetect
and it worked fine
I had a usb drive plugged in that could be the cause (but I would have expected a wrong disk() not rdisk() ?? well anyway there are other things wrong with this install so I'll have to reinstall anyways, I'll keep you informed)

This error message came because you had not removed your USB drive during the installation of your nLited CD.
The Windows setup routine always tries to install the OS onto another drive than a RAID one, if it finds one. That is the reason why I suggest to unplug all other drives during the OS installation onto a RAID array.

[gdogg]

please tell me the old method, is still hidden somewhere.
no method on the first post has worked for me, since beta 1.0 final.
anyone able to help me?

I havn't been able to install windows, for months.

I get bsod, on first boot after install every time, every method I try.

only thing that works, is a pre 1.0 final, cd I found, using old intergration method.

ive tried, old drivers, custom drive packages, offical drivers, vista drivers, bsod on all

This post has been edited by gdogg: 28 October 2006 - 08:57 AM

[Fernando 1]

gdogg, on Oct 28 2006, 04:54 PM, said:

please tell me the old method, is still hidden somewhere.
no method on the first post has worked for me, since beta 1.0 final.
anyone able to help me?
I havn't been able to install windows, for months.
I get bsod, on first boot after install every time, every method I try.
only thing that works, is a pre 1.0 final, cd I found, using old intergration method.
ive tried, old drivers, custom drive packages, offical drivers, vista drivers, bsod on all

The "old" method is to integrate just the LEGACY subfolder as TEXTMODE and not to integrate any other IDE\WinXP subfolder. Your problem might be the following:
As the big majority of users with an nForce SataRaid system have the best results by integrating the SATARAID and additionally the SATA_IDE subfolder, Nuhi had built into his nLite (since version 1.2) a new and automaticly running nForce SataRaid driver integration routine. If you offer nLite a complete nForce chipset package and point to the SATARAID or LEGACY subfolder, nLite integrates not only the content of the folder you pointed to, but additionally the content of the SATA_IDE subfolder. Exactly this combination might be not good for your nForce Raid system. You should prevent, that nLite additionally integrates the SATA_IDE subfolder.

The solution: Look into my guide to see which nForce chipset driver package is the best for you. It should have a LEGACY subfolder. Copy this LEGACY subfolder somewhere, but outside the chipset driver package (so nLite will not find the SATA_IDE subfolder).
The rest is easy: Just integrate the LEGACY subfolder as TEXTMODE.

Please report here, if you succeed this way. In this case I will give a message to Nuhi to remove the automaticly running additional integration of the SATA_IDE subfolder with the next nLite version and to substitute it by a popup window asking "Do you want to additionally integrate the SATA_IDE subfolder?"

[gdogg]

Thanks

I will be testing this today for sure, I need a clean install, bad.

I just lost 512MB of ram, so thats why it took so long to reply

edit
I don't think I am ever gonna be able to make an nlite cd that will actually install anymore, unless I don't remove a single item.

I am trying to test this, but I cant, cause I want a nlite cd with components removed like all my other installs, but that just causes a uregmp2 something or other error, then the install crashes at completing install.

So now I will try a full xp, with integrated drivers, so I can somehow get mwx 3.0 out, if that is even possible anymore.

This post has been edited by gdogg: 30 October 2006 - 07:47 AM