After reading http://www.msfn.org/board/index.php?showtopic=12566 i understand Method 2, and it is exactly what I want to use. The thing is I want to created an automated way to create a unatended CD Yeah you read that right. An unattended install CD is great for my line of work, but I need to keep it up to date all the time. I am working on a script to take a folder full of .reg, .cmd, the .7z files, and create the final product itself. To do this, I need to understand better exactly what is going on when I install RTS's wonderful driver packs. I see quite a few files modfied in the i386 directory (most of them from the DriverpackMassStorage i assume) that I would like to understand what happened. Most of the actual work gets done by dynamiclly created batches files that I havent had a chance to analyze. Can someone break this down for me? 1) New setup, driver policy, and dirver path tools are put in place 2) txtsetup, hivesomething, driverblah, get updated with new masstorage entries 3) mass storage drivers get cab'd into i386 4) this happens 5) this happens Something like that... From my nice XP SP2 folder and a set of DriverPack.7z files, to the integrated method 2 slipstreamed copy, behind the scenes~
