glugglug

The 64-bit NVRAID drivers FINALLY work properly as of the mid-late november version (6.25). They are not certified yet however. What needs to go on the floppy is everything in the IDE\WinXP directory from the nForce unified driver setup archive except the raidtool directory under that.

Does the windows installer automatically run the .INF files to add the registry keys for NvRaidService? Do SourceDisksFiles lines need to be added for NvRaidSvEnu.dll, NvRaidEnu.dll, and nvRaidService.exe or is putting these in the AMD64 directory of the install CD sufficient? Maybe this is why it fails after reboot? Do they each get "1,,,,,,4_,4,1,,,1,4" as the parameters on their SourceDiskFiles line? Edit: added these. The installer now completes, but when the XP 64-bit extended edition splash screen should show up after installation, the machine reboots. Also, the installer kept asking for the CD "SOURCEDISK", looking for the NVRAID.SYS or NVRAID.SY_ file. I pointed it at the file on the windows CD repeatedly, and even tried pointing it at the floppy, eventually just hit cancel and it continued with the rest of the install. It also screwed up the boot.ini, replacing the multi(0) or multi(1) on each line with a signature(hex digits), and the disk and rdisk numbers are reversed from how 32-bit XP uses them. Had to add another 32-bit installation to manually fix the boot.ini.

after reboot it gives an error message saying there was a problem with the disk configuration, on a black screen. If you press F8 before that point you get the boot menu and can boot your old OS. If you install onto a separate drive, it gets a blue screen about 5 minutes into the GUI part of the install.

Got them working during the text mode portion of the install. They don't yet work after reboot. The driver files are added to the AMD64 directory and the following lines are added to the TXTSETUP.SIF In [sourceDisksFiles] nvatabus.sys = 1,,,,,,4_,4,1,,,1,4 idecoi.dll = 1,,,,,,4_,4,1,,,1,4 nvraid.sys = 1,,,,,,4_,4,1,,,1,4 nvraidco.dll = 1,,,,,,4_,4,1,,,1,4 nvatabus.inf = 1,,,,,,,20,0,0 nvraid.inf = 1,,,,,,,20,0,0 In [sCSI.Load] nvatabus = nvatabus.sys,4 nvraid = nvraid.sys,4 In [setupData] DriverSigningPolicy=Ignore In [HardwareIDsDatabase] PCI\VEN_10DE&DEV_00E3 = "nvatabus" PCI\VEN_10DE&DEV_00E5 = "nvatabus" PCI\VEN_10DE&DEV_0065 = "nvatabus" PCI\VEN_10DE&DEV_0085 = "nvatabus" PCI\VEN_10DE&DEV_00EE = "nvatabus" GenNVRaidDisk = "nvraid" ACPI\_NVRAIDBUS = "nvraid" That last line seems to have made the difference. I got the idea of using ACPI\_NVRAIDBUS as the device ID from looking at the registry on my 32-bit installation. This still does not work after reboot. But then again, even copying the provided files onto a floppy and using F6 doesn't work for 64-bit. Maybe I should try it with the DriverSigningPolicy line in place (that wasn't there when I tried it before).

I have the 64-bit drivers which are linked above. After extracting all the files from that exe file archive, and putting those from the IDE directory onto a floppy, it gives me errors when the text mode part of the installer tries to load them.

I am attempting to get 64-bit windows set up on my RAID10 array, but the default windows install of course does not have the NVRAID drivers to see the array. I extracted the IDE directory with SATA and RAID drivers from the nForce Unified installer and put this onto a 1.68MB floppy, but it gives me errors when I try to use these, maybe because there are no .cat files? Also, the unattended 32-bit XP CD I made with the RAID drivers slipstreamed in says it is loading the RAID drivers but does not see the array. I had to use a floppy with the 32-bit drivers and do an attended install for this. The errors I get when trying to install the 64-bit drivers are: nvraid.sys caused an unexpected error (1024) at line 2283 in d:\srvidx01\base\boot\setup\oemdisk.c nvatabus.sys caused an unexpected error (1024) at line 2283 in d:\srvidx01\base\boot\setup\oemdisk.c

Anyone have experience with this? As far as I can tell, the list of included files is exactly the same as for the 32-bit NVidia IDE and RAID drivers, minus the 2 .cat files. All these files go into the AMD64\$OEM$\TEXTMODE directory, correct? Are the .cat files required for an unattended install? would this be the correct addition to UNATTEND.TXT? [MassStorageDrivers] "NVIDIA RAID CLASS DRIVER" = "OEM" "NVIDIA NForce Storage Controller" = "OEM" "IDE CD-ROM (ATAPI 1.2)/PCI IDE Controller" = "RETAIL" [OEMBootFiles] disk1 idecoi.dll nvatabus.inf NvAtaBus.sys nvcoi.dll nvide.nvu nvraid.inf nvraid.sys nvraidco.dll NvRaidEnu.dll NvRaidMan.exe nvraidservice.exe NvRaidSvEnu.dll NvRaidWizard.dll NvRaidWizardEnu.dll nvuide.exe RegRaid.bat txtsetup.oem

What changes would I need to make to the TXTSETUP.SIF or other files to slipstream in these Win64 NVRAID and nForce IDE drivers? These are a PITA more so than other drivers because they are too big to fit on a normal floppy, so you have to get Winimage to format it for 1.68MB. Also, too many files to fit on a DMF floppy. 7-zip archive of the driver files