MassStorage OEMSETUP.INF Files

Hi,
welcome to DriverPacks.

First thing I will say sounds like a shrug off.. Do not see this as a beratement.
You use the wrong order of doing it it to it.
Allow me to explain the absence of txtsetup.oem files.
We use DriverPack MassStorage INI to do the TXTmode (see the modify DriverPack MassStorage faq).
The sysprepper guru (and other anal(itic) users) figured that having 115 txtsetup.oem  files was a problem when they used DriverPacks for sysprep.

therefore, the answer to the Nlite scan question is NO.
(Since we do not keep the txtsetup.oem files, and the DriverPack MassStorage INI have been filtered and have VERY specific entries for those case where we use a driver with same HWID for different OS.)

We do not want to edit the driver INF files, and avoid it like the plague, but we had to do it to some.
(Some of our team members are sysprep users and they figured we should do it for many more, but the MAIN team want to keep sysfile rename and INF edits to the bare minimum.)

So, Brad, Nlite, then DriverPacks.
Please, DO READ THAT customise faq.

Last edited by Jaak (2008-05-21 14:02:41)

Thanks for your replies. I've spent the better part of the day trying to build an addon for nlite that will make the same changes in txtsetup.sif and dosnet.inf as well as copy the compressed drivers into the i386 directory. Being new to addons you can imagine I have been struggling and less than successful.

When nlite integrates the driverpacks the build only grows by 600MB. Granted that's compressed into the drivers.cab so I imagine your 1.2GB estimate is accurate. If I use KTD won't this effectively be the same?

My revised process is now:
1) Copy Source which includes my custom winnt.sif
2) Use Nlite to integrate hotfixes, drivers and tweaks
3) Use Driverpacks Base to integrate Textmode Mass Storage Driverpack
4) Create ISO using nlite

My ultimate goal is three fold:
1) Create a universal xp install cd complete with drivers for all hardware
2) Sysprep and ghost a single image that will be able to deploy over multiple Dell desktops from Optiplex GX620s to Optiplex 755s.
3) To do all this without having to do an administrative logon after the initial install. i.e. no runonce or additional programs to run.

Surely there is a way to integrate the drivers for initial setup, keep the drivers for future hardware changes, not break sysprep and not include a fake setup step or grossly huge OemPnpDriversPath.

Can you tell me if I'm heading down the wrong path here? I bow to your experience. Thanks for the help.

P.S. Reading the faq you mentioned...I'll be reading this well into tomorrow.

Brad

Thanks OverFlow. I'll check it out. Logic dictates that if MIcrosoft can do it, so can we. I'll join the crusade.

Getting people to see what can be done teaches those whom do not yet know what can be done.
My past experience says that we will see more tips and more easy solutions described in a not too distant future, and it all started by getting people like us asking you to help us help you.

for instance, I liked that ruby script a lot, but wished it was vbs.
(and it is not perfect yet, because it cannot yet supplant what we list as replaceifOS.)