HolgerDK

That did the trick - thank you very much. And that i should have known or be able to figure out for my self

I tried both method 1 and 2, but as it was the first time i used the driverpacks i'll try again to see if i did something wrong.

Is there someone out there who can tell me what im doing wrong ? - or is installing WinXP on my SATA drive a lost cause ?

If i remember correctly you need to change OemPreinstall = Yes to OemPreinstall = No

Yep - multiple times, and every time did windows tell me that the driver files couldn't be copied - i know the floppy drive works and i tried multiple working floppydiscs - same s***, different disc... And when i use install cd with the drivers slipstreaming into it and the floppy to see if it makes a difference, the install program asks me which drivers to load from the floppy and still it manages to NOT see the Raptor drive when the install proces reaches the choose-which-disc-to-install-to-point (or should i write - choose-which-drive-to-ignore...). Normally i'm a positive person with quite a lot of patience, but this s*** really gets on my nerve...

I'm trying to install (a danish) Windows XP Pro SP2 (Tried Win2k Pro SP4 as well - same result...) on a Western Digital 74 GB Raptor on my brand new A8V (updated the bios to 1009). So far without succes... (instead i got a lot of anger towards MS, Via and software in generel...) I have tried the following: 1) Slipstreaming the (4.10a) driver for the onboard Via RAID controller into the WinXP install CD with the "old" method (that worked perfectly on my Abit AN7 with the same SATA drive on a SATA controller as the only harddrive in the computer...) - making a "$OEM$\$1\drivers" folder, editing "txtsetup.sif"and "winnt.sif". WinXP loads the driver upon boot from the installcd, recognices the Raptor disc, proceeds to copy all the install files (apparently including the driver) on to the drive, reboots and crashes with this error message: "***STOP: 0X0000007B (0XFAF47528,0XC0000034,0X00000000,0X00000000).". If i boot on a PATA drive i can see that the RAID drivers apparently has been copied on to the SATA drive in a folder called "Drivers" (and the "viamraid.sys" file is in the "winnt\system32\drivers" folder but not installed... I added this to "txtsetup.sif": [SourceDisksFiles] viamraid.sys = 1,,,,,,4_,4,1,,,1,4 [HardwareIdsDatabase] PCI\VEN_1106&DEV_3249 = "VIA RAID" PCI\VEN_1106&DEV_3149 = "VIA RAID" PCI\VEN_1106&DEV_3164 = "VIA RAID" [SCSI.load] VIARAID_MULTIPLE_XP = viamraid.sys, 4 [scsi] VIARAID_MULTIPLE_XP = "VIA RAID Controller(Windows XP)" 2) Using Driverpacks Massstorage 5.0.3 methods 1 and 2 - Doesn't work. Windows doesn't recognise the SATA drive when the install program looks for drives in the computer... But im not sure i did this the right way. When i unpacked the Massstorage driverpack it put the files in a folder called "DP, i then moved the extracted driver into the "Driverpack" folder that Driverpack base created (was this wrong) 3) Walking away from the computer to let my temper cool down - thrice... The hardware used in the computer is: Athlon64 3200+ 90nm Asus A8V Deluxe (non WiFi) 2*512 TwinMOS Twister PC3200 CL2 Club3D X800 Pro ViVo Sony 19" E400P 74 GB WD Raptor Plextor PX-712A Antec TruePower 330W PSU And this hardware runs fine - im writing this on the computer (with a PATA drive and running Win2k) im trying to install WinXP on Im on the brink of selfdestruction with anger/frustration... - can someone please tell me what im doing wrong before that happens? rant==on; Why the hell can't MS write a f***ing barebone SATA driver that windows can use... - that would make this SO much easier. Its not like SATA drives were introduced to the market 2 months ago - but 2 years ago rant==off;