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.vitaligraf.de/showthread.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.

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?

Hey all, I'm having an issue with this too. 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. Any ideas of what I did wrong or how to fix it? I've been torturing myself over installing WinXP64 on my new lappy for the past two days (as long as I've had it) with no luck. By the way, I couldn't tell you anything about my BIOS aside from that it is the one to come with the HP dv2000z laptops. It has no option to disable native SATA support or anything like that. The BIOS menu says it is "PhoenixBIOS Setup Utility," version F.06

Whoooops, sorry; wrong thread.