Should I not using OEM?

[dottedquad]

Hello all, I would like to create an unattened edition of the winxp setup cd as follows: Install my raid drivers from a floppy and install software not using the $OEM$ way ex: office2003. The reasoning for this is I need a universal unattended xp install that will suite multiple computers. If possible could someone pinpoint what sections to read from the Unattended Guide to complete the cd? Much appreciated.

So far, I have slipstreamed all the hotfixes, created an install point for office2003, and created an unattended setup. My piority is to mainly install office2003 not using the $OEM$ folder since installing drivers via floppy won't be an option.

-Rich

Edited January 4, 2008 by dottedquad

[Arie]

I'm basically doing the same as you. I use HFSLIP to integrate all required updates and such. I install most applications via home brew, silent, self-extracting archives via SVCPACK.INF. I import Registry tweaks and such via SVCPACK.INF as well. I install Office 2003 from CD-ROM via RunOnceEx. Applications which are not SVCPACK.INF compatible are installed via RunOnceEx as well. And a short note on Microsoft .NET Framework, I install RogueSpear's silent installation packages for version 1.1 SP1 and 2.0 SP1 via SVCPACK.INF first, followed by any applications which depend on either, and I install RogueSpear's Lite version of version 3.5 first via RunOnceEx, also followed by any applications which depend on version 3.x. Oh, and I also use HFSLIP to integrate my own drivers, such as SATA, audio, et cetera.