I'm a bit new at this sysprep thing, so please be patient if I am overlooking something. I hope someone can help me. I have put an inordinate amount of time into this project and I don' know how much more I can spare right now.
We have an existing image at work that is intended to be modified and use as a base for custom images in our schools. I have decided to take it upon myself to create a more or less universal image since the existing one doesn't work out of the box on a lot of newer hardware (sometimes not at all).
I have modified our existing sysprep creation script to work Driverpacks.net drivers. I have added LAN, CPU, and Chipset drivers to the C:\D folder (added with devpath) and use the SAD M2 method for the rest of the drivers. I sealed the image without using the -BMSD option. Where my problem comes in is in injecting the Mass Storage drivers.
I created a LiveXP CD with OLSP and the sysprep version for SP3. I did not, as far as I know, change any other settings when creating it. I have gone through the OLSP process, making sure to check the box to not complete it with sysprep since I already did so. It does not appear to actually add the mass storage section to my sysprep.inf. I have tried it both with and without the mass storage section already existing.
I'm really not sure what I am doing wrong here. Should I instead be trying to use the gui mass storage injector that Zetup posted? Most of our systems are Intel based with a few AMDs here and there. Would using Zetup's solution allow me to integrate all of the DP mass storage text drivers without having to worry about running afoul of the ntldr memory limits?