if you used a source that has mass storage text mode integrated then oyou don't need to do anything else to add mass storage support

just create a SAD folder and run DP_Install_Tool.cmd when you deploy to add the rest of your drivers...

if you have not used a DriverPacks slipstreamed source then use offline sysprep to add support after the fact... pretty simple.

Details are all here in this thread... what is missing can be had at 911.

_________________
Call Center Software

Won't the mass storage controllers work just my setting the HDD controller to standard IDE before you shutdown
then when the system boots it will use txtsetup.sif to install the correct txtmode drivers.

If the mass storage drivers were available to minisetup then they would be replaced by the drivers in the mass pack.
so all you need to do is have the mass storage pack extracted somewhere and put the folders in the devpath entry.
except for some of the known issues with certain hardware requireing registry entries that woud be 90% effective and OSP more like 98% ?

Me and bro eXoRt will test it for you.

Thanks. Hopefully you'll find it working as expected.

Regards,
Galapo.

Galapo, does your program work with LiveXP and all its variants?

Yes, that's all I use it with these days. I haven't fired up pebuilder for two years now.

Regards,
Galapo.

Also, Ian I found something that you might find helpful.

Galapo, could you add an option to mount a VMWare image and use that for the target?

I guess I could but I don't really see the point. If one wants to use a VMWare image, then it should be up to the user to have the image mounted, and it's not difficult. There's various ways of doing so: either with VMWare's own supplied program, or vdk.exe, or ImDisk, etc.

New version is out also. Changes to OfflineSysPrep:
· Options which are run on first boot (driver-signing supression, generating new SID, auto HAL update) are now stored in case of re-running OfflineSysPrep before first run and when OfflineSysPrep starts the second (or third etc.) time then these options are selected by default if originally selected
· Original setup commandline is replaced if re-running OfflineSysPrep before first run

Regards,
Galapo.

Works like a champ!!!!!

Thanks Galapo, and of course everyone for support, ideas, driver help, and all the rest!  GREAT STUFF!!!

Ian

Warning The steps in the article are effective only on Volume License media. If you try these steps on OEM media or on retail media, you will not change the product key.

hmm, that's pretty odd, it seemed to work just fine, but I never ran Key Finder or anything to verify, it just went through the motions.  Maybe that's all it did, went through the motions......

Oh well, I'm minutes away from trying a test that went

Plain SysPrep with only Mini-Setup option selected and no MS textmode integration
OSP with HAL next boot, MS injection, no SID, fix keyboard//mouse unresponsiveness, couple other things...

I'll post back with results and full OSP options used at that time

Ian

Ian, you can change one number in the reg binary of the msoobe registry key and call the msoobe activation and it will ask for a new number.

http://support.microsoft.com/kb/328874

Unfortunately, that only works for VLK licenses.  Not OEM pre-activation.

Ian, you can change one number in the reg binary of the msoobe registry key and call the msoobe activation and it will ask for a new number.

Yup, I went that way at first, but felt that was too clunky.  (jeez, I love that word, huh??)  It worked fine, but having to say yes to activation, then telephone, then change key, then update, then phone in every time, what a pain! 

Ian

Galapo, could you add an option to mount a VMWare image and use that for the target?

Ian, you can change one number in the reg binary of the msoobe registry key and call the msoobe activation and it will ask for a new number.

http://support.microsoft.com/kb/328874

With sysprep.exe you can use -mini -reseal for re-entering the activation key.