RyanVM

Still a pain in the arse if you have a board with more than one controller like many new motherboards are these days (with RAID supporting south bridges such as ICH5R and an addon RAID controller such as the Promise 378). You'd have to hack up the txtsetup.oem file to include both. Yuck. And of course, things get even more complicated if you want to use your unattended CD on more than one machine.

What's with those folder names?

Does it work now?

It would certainly be cool if it worked.

*crickets chirping* It would be nice if possible because it would greatly cut down on size (uncompressed drivers take up so much more space it's ridiculous). However, I'm sure adding them to drivers.cab would add other unforseen complexities

If you used the pack I compiled, you do NOT need to press F6. The point of integrating these drivers is specifically so you won't have to press F6. In fact, it's normal that you will get errors if you try to copy RAID drivers from a floppy during unattended setup. This is due to OEMPreinstall being set equal to Yes in winnt.sif.

Look at any documentation that came with your motherboard and/or the manufacturer's website. The driver pack I compiled (theoretically) supports the onboard Promise 378 controller, so you should be OK on that end assuming you followed directions correctly. If the drivers are integrated correctly, you will see them on controller fasttx2k. If you have the drives attached to the Intel SATA controller, you can NOT do JBOD as it only supports RAID 0/1/0+1 modes. Also, there's really no performance gain from running in JBOD mode. The only advantage you get from it is that the drives are seen as one big drive rather than as separate drives. Again, IF YOU DON'T HAVE MATCHING DRIVES, YOU ARE PRETTY MUCH GUARANTEED TO SEE NO PERFORMANCE GAIN FROM RUNNING IN RAID.

Happens to the best of us

That was better English than many people I've seen for whom it's their native language And your point was VERY well put.

owned by typos

Good suggestion, I'll look into it

To make a RAID array, you really need to have two identical drives for best performance. If you're making an array from random hard drives like you are, you need to make a JBOD array. This need to be done in the RAID controller BIOS before you even start Windows setup.

Yes but this really isn't the forum to be discussing it in.

I haven't to date seen anybody successfully integrate the drivers through that method (though I seem to recall hearing about it now that I think about it). If you want simplicity, I'd just go with my little package linked in my sig (shameless plug I know ) as all you have to do is unpack the RAR archive to the CD root, run the batch file to make the necessary changes to txtsetup.sif, and copy/paste some stuff into winnt.sif.

When you slipstream a service pack on top of an older build, can you safely delete the older cd-ident files?

Are AGP drivers considered chipset drivers? Also, has anybody managed to figure out a way to extract the AMD K8 chipset drivers? Their installation package is a pain to work with.

I'm not sure what to tell you guys. Where are you getting the error? I just created a fresh XP install CD and applied the patch to a clean txtsetup.sif and the CD booted just fine and saw the SATA hard drive (Seagate 120GB) on the ICH5R controller just fine. Are you sure you extracted all the files properly? Did you make the needed changes to winnt.sif?

It sounds like he's saying that you boot from a floppy and execute a batch file which creates the winnt.sif file using echo commands then executes winnt.exe to start setup.

I've got an 875 board here at work that if I have time, I'll attempt the unattended install on. It's always possible there's a mistake somewhere in my little package. In the mean time, you can try following GreenMachine's method (start with a fresh txtsetup.sif) and try integrating only your relevant drivers instead of all of them. http://greenmachine.msfnhosting.com/READING/addraid.htm

Arablover - it turns out I had a typo in the text file . It should be fixed now. Re-download the RAR archive and see how the new one works.

What about subfolders within that directory scheme (say 000\nforce, 000\via, etc)?

I was under the impression that Windows detected hardware, then looked to those folders for matching stuff (so if the chipset drivers cause more hardware to be detected, it will just go back to those folders looking for compatible drivers), not looking the folders sequentially looking for matching hardware. Am I wrong?

If you're getting it on all systems, it might be a mistake on my end. I'll look into it tonight when I get home from work.

What build of XP are you using? And the CD works correctly with the 875 board still?

Most of those drivers can be slipstreamed individually (without having to run a setup CD). Check out some of the threads in the driver forum.