Jump to content

tufkal

Member
  • Posts

    2
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    United States

About tufkal

tufkal's Achievements

0

Reputation

  1. 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~
  2. Hi guys! I do alot of XP installs and I decided to work up a CD to use with my business and personal PCs. I wanted it to cover the widest range of PCs it can, without compromising any functions. This is the method I have come up with, but I feel like I am doing this the hard way cause it's a bit like spaghetti the way things layer on top of each other. Start with XP SP1 Volume License CD Slipstream SP2 (Manually) Remove unneeded components (NLite) Add RyanVM's Hotfix Pack (Nlite) Add Device Drivers (RTS Pack, everything, method 2) Add more drivers (Manually same way RTS method 2 does a.k.a drivers via CD method) Add some app installs on first boot WMP10/NETFX/ETC (Manually via cmdlines.txt) I have yet to setup some registry tweaking (I dont like the way nlite does it) and I chose not to do any unattended options to keep the F6 option available. Something I am missing in what I've gathered from this wonderful site?
×
×
  • Create New...