skinlayers can you email me at me so stinky at g mail dot com? You seem to be the only one here who got sysprep to play nice with driverpacks. Bashrats directions here, http://forum.driverpacks.net/viewtopic.php?id=768  apparently don't work right and your directions haven't been commented on by anyone else and I don't know if you have figured anything else out since your original post.

If you come by my post please email me. Thanks!

Thanks Overflow, I was having some problems last night and search was timing out on me. I'll have a look through those threads. I hope I can get this to work, if so I'm definitely donating to this project as it could potentially save me a lot of headache.

So I'm new to Sysprep and my eyes started glazing over at figuring out PCI identifier lines for various hardware and adding them to sysprep.inf.

The driverpacks seem to be a great solution for initial CD installs but but I'm not sure if they factor in to sysprep images?

My process would be -
take XP SP2 disc, add RyanVM hotfixes, add most of the driverpacks, burn my CD
do install on my "base hardware" PC along with my required apps
Run sysprep with a fully automated answer file ( will this catch and use the driverpacks?)
Image it and be ready to go

With sysprep its all about the image that is created of the drive. Driverpacks seems to modify it so that upon install from a CD Windows will find the extra drivers and use them. But in my case I'm doing a image of a hard drive.
If I sysprep it will those drivers be automatically available? I know this is a little out of the purpose of driverpacks but does anyone know how to do it so that future installs based on a image that used the KTD option will also find an use those drivers? Does that make sense?