Whats your order of integration????

AxlRose-RX · Post by **AxlRose-RX** » Fri Sep 12, 2008 1:54 am

Whats your order of integration??

I ask you guys this, because after december 2007, I am ready to make my new unnatended xp cd with:

sp3 and
RyanVM Post-SP3 Update Pack 1.0.1 - Released 2008-09-09
Windows media player and updates
Internet Explorer 7 and updates
All .Net Frameworks plus SPs and updates

Funny thing is I don't even remember what order I did, but was something like this:

1. Slip... my xp cd to sp-2
2. RyanVM Post-SP2 Update Pack don't remember what version but was a beta, the last one on december 07.
3. Boooggy's Slipstreamer for Windows Media Player 11 + updates
4. Don't remember which IE7 addon it was or if it was before or after WMP 11 heh

5. A .NET AIO switchless installer pack I made for RunOnceEx.cmd

Could any of you guys that have successfully integrated this addons or yours, tell me in what order and what versions of them used???

basically what I want is an XP cd with SP3 and:

1. RyanVM Post-SP3 Update Pack 1.0.1 - Released 2008-09-09
2. to Integrate Windows Media Player 11 + updates and which one worked for you best.
3. to integrate IE7 plus all updates and which one worked for you best and if was before WMP11 or after.
4. The last one u used for .NET AIOs with updates, if it worked for you well as integrated, or it installed after first logon to windows like I did with RunOnceEx.cmd.

Wesmosis · Post by **Wesmosis** » Mon Sep 22, 2008 5:44 pm

I suppose the answer is :
1- Slipstream SP3
2- Integrate Post-SP3 Hotfixes
3- Xpizing
4- Nliting
5- DriverPacks of bashrat

plz correct me guyz

crashfly · Post by **crashfly** » Mon Sep 22, 2008 5:57 pm

I might as well throw my integration order into the mix. It goes something like this:

1. Start with base SP2 install.
2. Slipstream SP3 into source.
3. Update/remove certain misc files as explained on another forum.
4. Use/Integrate WMP 11 into source (boogy's WMP slipstreamer)
5. Integrate Ryan's Integrator specific addons (kal's quicklauch tool, setup resolution size, BVProSvcDescriptions addon)
6. Use nlite to add updates, add multiple addons, make setting changes, remove windows components, etc) * includes update pack here
7. Make iso from nlite and test on virtual machine.

mr_smartepants · Post by **mr_smartepants** » Tue Sep 23, 2008 12:53 am

Basic methodology:
Add everything first
Removals next
Tweaks
DriverPacks last, just before build ISO.

If you add...remove...add, then you're asking for problems.

code65536 · Post by **code65536** » Tue Sep 23, 2008 1:04 am

crashfly, I assume that your step 2 (slipstream SP3) includes the Update Pack? One important thing about the order is that the RVM Update Pack should be applied *before* using the WMP11 slipstreamer (you can use the WMP11 slipstreamer prior to the RVMUP, and that's actually what I prefer doing, but in order to do that, you will have to make some manual adjustments to txtsetup.sif in order to avoid conflicts with the MUI directory IDs).

crashfly · Post by **crashfly** » Tue Sep 23, 2008 7:59 am

Actually no. My update set comes at step 6. So far I have not had to manually adjust the txtsetup.sif. However, if this causes some problems, I would like to know what "potential" problems I could run into.

yumeyao · Post by **yumeyao** » Tue Sep 23, 2008 8:03 am

so any description in detail for your step 3, crashfly?

code65536 · Post by **code65536** » Tue Sep 23, 2008 9:00 am

The RVMUP adds a number of location IDs to txtsetup.sif to handle the MUI files being installed for Windows installer. RVMUP hard-codes these additions. In the case of XP Pro, this will result in the addition of IDs 732-737, which should be free. The WMP11 slipstreamer also needs to add a location ID to txtsetup.sif, but it does so by taking the first available slot, which means that if the WMP11 slipstreamer is run prior to the RVMUP, it will have taken up a location ID that the RVMUP expects to be empty. The solution to this is to edit txtsetup.sif and to add the extra location IDs that the RVMUP was going to add. That way, the WMP11 slipstreamer will pick an ID outside of the range used by the RVMUP, and the RVMUP will still be okay.

And for anyone curious, my order goes like this:

Prerequisites:
* Slipstream SP3 (ideally, slip it onto SP0 if you have that)
* Post slip-stream cleanups (delete SP1.cab, etc.)
* Edit txtsetup.sif
* Create base ISO image for future use (so these steps are done only once; highly recommended)
* Create a WINNT.SIF (optional, of course)

Integration:
* Extract ISO image to working dir with 7-Zip
* WMP11 slipstreamer (if you didn't fix txtsetup.sif, move this to after Integrator)
* Integrator to add RVMUP, ALL addons, and switchless installers all in a single run.
* Fix timestamps (e.g., make sure that the timestamp for crypt32.dl_ matches the timestamp of the crypt32.dll file found inside; when decompressing, Windows setup sets the timestamp to the outer timestamp and not the inner time stamp, which really annoys me because I don't want files modified in 2001 to have a 2008 timestamp!)
* Copy over my WINNT.SIF and any other custom files (like my self-extracting 7z driver pack invoked through WINNT.SIF)
* Make ISO using OSCDIMG 2.54 from the latest WAIK using the boot sector bin from the latest WAIK.

I keep nLite out of the picture because I'm a control freak and nLite has this nasty habit of going in and doing "helpful" things that I did not explicitly approve of. The entire integration is itself unattended, as everything is invoked command-line by a script.

Nameless Mofo · Post by **Nameless Mofo** » Tue Sep 23, 2008 12:29 pm

Just for grins my order is:

1. Start with clean SP2 source
2. Slipstream SP3 using either a) nlite or b) /integrate switch to SP3 fullfile installer from MS
3. Integrate a) Ryan's update pack, b) addons for IE7, WMP10/11, Windows Defender, plus Zacam's syssetup.dll hack
4. Nlite to tweak stuff and remove junk - I'm not very aggressive, just unused languages, plus obviously useless crap like tour, msn, messenger, etc. I also remove drivers because I install drivers after Windows is up & running. I leave almost all services intact, and if in doubt I leave it. Even being conservative I still knock like ~150MB off the source.
5. My own custom tweaks to specific inf files.
6. Nlite 1.0.1 (a really ancient nlite) to make the iso. I use 1.0.1 because all versions 1.2.x and later upcase every filename on the iso, which I don't like.

crashfly · Post by **crashfly** » Tue Sep 23, 2008 9:53 pm

yumeyao wrote:so any description in detail for your step 3, crashfly?

Honestly, I would ... except I cannot bloody remember where I got the information from in the first place. I believe it was a forum, however I cannot for the life of me remember which one I visited at the time. I will try to investigate further and get that information for you.

From what I remember though, it was an update to some of the items not directly covered by a SP3 update. Deployment tools and some other minor files where what was updated to make the CD "completely" updated (at least as much as possible).

crashfly · Post by **crashfly** » Wed Sep 24, 2008 2:24 pm

Well, I had to search specific words to finally find what I wanted. As an update, step #3 should contain information pointing from here: http://www.msfn.org/board/Windows-XP-SP ... 18781.html

Removing specific obsolete files and updating these components dropped the "original" installation CD down by approx 30mb.

beats · Post by **beats** » Wed Sep 24, 2008 6:16 pm

For what it's worth, my order is:

1) A clean XP/SP0 VLK source with SP3 already integrated.

I only use the i386 folder, which already is cleaned up (see crashfly's post above), and the required root folder files. The basic layout looks like this:

I386
AUTORUN.INF
README.HTM
SETUP.EXE
SETUPXP.HTM
WIN51
WIN51IP
win51ip.SP3

Keep this pre patched and cleaned up source in 7z or rar format (whatever you prefer) for easy reuse.

2a ) Integrate update pack of choice with nLite. Personally, I use Red's and Xable's update packs, depending on the variant I'm preparing. Xable's for uber minimalistic and specialised +/- 100MB XP cd's, and Red's for full blown - albeit still stripped - winxp + applications dvd's.

2b ) Red's DirectX addon, Xable's HashTab and WGAN addons, Kel's Runtimes addon, and a few of my own addons.

* 2a+b can be done in one run.

3 ) Windows Media Player 11 + all updates with Booogy's WMP11 Slipstreamer.

4 ) nLite tweaks and stuff. Important! Never start hacking your source with nLite tweaks and stuff, always do this after integrating your update pack, third party addons and stuff like WMP11 and IE7.

5 ) Driver packs with BTS own integrator. Important! Driver packs should really be the final step.

6 ) After all the integrations, I copy my own i386 template/skeleton with various modified INF's, CAB's and stuff like WINNT.SIF, cmdlines.txt etc. + my $OEM$ folder layout.

7 ) Nero Uber Lite 6 (a self made custom version) to burn the final image (or nLite when creating an ISO for testing in virtual machines).

Notes:
If you want to integrate Internet Explorer 7 as well, do it after step 3) WMP11.

For all other applications (about 120 in total in both English and Dutch), I use Windows Installation Helper Utility (WIHU). It's comparable to WPI but its not maintained anymore. Yet, I still like WIHU better, in combination with silent installers for maximum flexibility on my DVD's. On first boot after the installation, it enables you to change to computer name, add user accounts, etc. as well. Of course this can also be predefined. I've also predefined a minimal default application set; this can be changed during the T13 stage, but if nothing is changed within 60 seconds, it will install the predefined set. WIHU can also be run after the installation is finished, at any time, on any win2k, winxp or win2k3 machine. Same applies to all driver packs, with DriverForge you're able to add any missing drivers to already installed - alien - systems. Everything runs and installs directly from the CD/DVD.

DjKilla · Post by **DjKilla** » Fri Sep 26, 2008 9:31 am

When is the ideal/best time to copy my WINNT.SIF to my i386 directory? Here's my setup (EVERYTHING done through RyanVM Integrator):

1) A clean XP/SP0 source with SP3 already integrated. (Used Autostreamer 1.0.33)

2) Integrate RVMUpdatePackSP3_1.0.1.7z

3) Continue integrating (after step 2) the following:
DirectX_9.0c_End-User_Runtime_AddOn_0.5.1_-_redxii.7z
DotNetFx_All_In_1_Addon_v2.2.7z
NR_IE7en_Addon_2.0.2.7z
xable_MicrosoftUpdateEngine-v1.3_addon.cab
xable_OUE-OGA-v1.7_addon.cab
xable_WGAV-v1.3_addon.cab

4) Windows Media Player 11 + all updates with Booogy's WMP11 Slipstreamer.

5) Copy WINNT.SIF to i386

6) Driver packs with BTS own integrator.

7) Make ISO, test using VMWare Server, install!

Post by **5eraph** » Fri Sep 26, 2008 11:12 am

WINNT.SIF can be copied into I386 any time before the DriverPacks. I include it before an Update Pack as part of my source.

DjKilla · Post by **DjKilla** » Fri Sep 26, 2008 11:25 am

5eraph wrote:WINNT.SIF can be copied into I386 any time before the DriverPacks. I include it before an Update Pack as part of my source.

Thanks for the reply! I wanted to make sure I was following the right flow to make a good slipstreamed OS.

crashfly · Post by **crashfly** » Fri Sep 26, 2008 12:30 pm

DjKilla wrote:When is the ideal/best time to copy my WINNT.SIF to my i386 directory? Here's my setup (EVERYTHING done through RyanVM Integrator):

1) A clean XP/SP0 source with SP3 already integrated. (Used Autostreamer 1.0.33)

The best time is right after you have your "source" ready. Although few, if any, addons modify the winnt.sif file, it is good to keep it with the install should something need it (to modify).

As an addendum to my above post, I actually have a batch file prepare my source and make necessary changes to have addons be ready to be added. Takes about 5 minutes, but it simplifies my process. This weekend, I will modify my first post and be more detailed about it.

runningfool87 · Post by **runningfool87** » Mon Sep 29, 2008 11:24 am

step 1: nLite

the end.

crashfly · Post by **crashfly** » Mon Sep 29, 2008 1:55 pm

code65536 wrote:The RVMUP adds a number of location IDs to txtsetup.sif to handle the MUI files being installed for Windows installer. RVMUP hard-codes these additions. In the case of XP Pro, this will result in the addition of IDs 732-737, which should be free. The WMP11 slipstreamer also needs to add a location ID to txtsetup.sif, but it does so by taking the first available slot, which means that if the WMP11 slipstreamer is run prior to the RVMUP, it will have taken up a location ID that the RVMUP expects to be empty. The solution to this is to edit txtsetup.sif and to add the extra location IDs that the RVMUP was going to add. That way, the WMP11 slipstreamer will pick an ID outside of the range used by the RVMUP, and the RVMUP will still be okay.

And for anyone curious, my order goes like this:

Prerequisites:
* Slipstream SP3 (ideally, slip it onto SP0 if you have that)
* Post slip-stream cleanups (delete SP1.cab, etc.)
* Edit txtsetup.sif
* Create base ISO image for future use (so these steps are done only once; highly recommended)
* Create a WINNT.SIF (optional, of course)

Integration:
* Extract ISO image to working dir with 7-Zip
* WMP11 slipstreamer (if you didn't fix txtsetup.sif, move this to after Integrator)
* Integrator to add RVMUP, ALL addons, and switchless installers all in a single run.
* Fix timestamps (e.g., make sure that the timestamp for crypt32.dl_ matches the timestamp of the crypt32.dll file found inside; when decompressing, Windows setup sets the timestamp to the outer timestamp and not the inner time stamp, which really annoys me because I don't want files modified in 2001 to have a 2008 timestamp!)
* Copy over my WINNT.SIF and any other custom files (like my self-extracting 7z driver pack invoked through WINNT.SIF)
* Make ISO using OSCDIMG 2.54 from the latest WAIK using the boot sector bin from the latest WAIK.

I keep nLite out of the picture because I'm a control freak and nLite has this nasty habit of going in and doing "helpful" things that I did not explicitly approve of. The entire integration is itself unattended, as everything is invoked command-line by a script.

Hmmm .... I see your point. I wonder if that could explain the occasional fubar I have with WMP11 on startup (during a VM session). Thanks for that information code65536. I am going to make "WMP11" modifications and see what happens then.

dav532000 · Post by **dav532000** » Thu Oct 09, 2008 9:49 am

Put this in the wrong place so I have copied it to here.
Hi Ryan. I am new at attempting anything like this, but thought you might like to no how I did. Affter a few attempts with NLite, I decided to give your Integragetor a try.I started by:-
Merging SP3 into XP-Pro SP2
Slipstreaming WMP11 with Boooggy&n7Epsilon slipstreamer.
RMV Integragetor for Addons-Update Pack SP3 1.0.1
WGAN_1.8.31.0
DirectX_9.0c
Addon Pack 1.9.0- Integragate.
Restart RMV Integragator:-
JD976_Stimpy.DotNet
WGANotify-Integragate
Restart RMV Integragator:-
Finished with your Alternative IE7 Pack, Integragate again.
Started NLite:-removed Language,Keyboard and a few other things.
Unattended Install and made ISO.
Testing on Virtual Machine as I write this.
The only problems I came across was that Setup asked me to Install
WGA, could that be that I added it again at the same time I added DotNet.
I then went to Windows Update, and the only Updates that I needed were
Hotfix For Windows Format 11 SDK KB929399
Hotfix For Windows Media KB939683, which were Slipstreamed but had to be reinstalled and Update For Root Certificates.
So all in all not to bad really,will try to add some applications and Drivers
to my next Build, so thanks for you fantastic Application,made it easy but rewarding.
Dave.