You ask this in DriverPack MassStorage forum.
This topic will be moved to imaging forum, where syspreppers and so on hang out.

We are using RIS to install our desktops.  The installation works fine, drivers are loaded, etc...  However, if we try to ghost the machine to a new piece of hardware, the system gets stuck in a reboot loop.  From what we're able to determine, its due to the old machine not having the device information loaded for the new hardware.  Make sense?

This was attainable using Sysprep in an old image we've been using (DriverPacks were 5x series).  There were a handful of batch files that would generate the content for [MassStorage] section of Sysprep...  and when Windows was loading, it would load each device driver.  This would allow the ghost image, and even a working OS (one that a user had been using for a period of time, then ghosted to new hardware) to be reasonably portable.

Is there a way I can automate the inclusion of the MassStorage drivers for every boot?  Or maybe a way of loading all the drivers once the OS is up (since the machine can be installed RIS, the problem is moving the installation to a different piece of hardware)?

Am I even asking this the right way?

Thanks...