At all: How to slipstream Hotfixes manuel? by hand

[KNARZ]

Hi

First of all i worked with nlite and hfslip and maybe there's a method that i don't know or i didn't test (PatchChk). But at all, the tools and programs didn't satisfyed me.

nlite doesn't slipstream all hotfixes in the best way and all the comments in the end *urghs*

hfslip miss some hotfixes...

so i want do it manuel, can someone help me how which i shold choose? GDR or QFE and how to slipstrem the *.inf in the HIVE's of Windows?!

and so on...

please some post some information

(****, what bad english but i'm not able to do it better at this time and after that day, sorry)

Edited December 13, 2005 by KNARZ

[saugatak]

Why don't you use hfslip to slipstream what you can and then batchfile the rest?

[blinkdt]

I use HFSLIP for Windows 2000 installs (peerlessly integrates IE6, WPM9, and DX9 as well) and the SVCPACK method for WinXP. Search and you will find.

[maxXPsoft]

WindowsXP-KB901214-x86-ENU.exe /Quiet /Passive /integrate:C:\XPCD

Been awhile since I done it manually but I think thats close

If you open a Dos Prompt and paste the exe name in there and put a blank space and /? it will tell you these things

Edited December 14, 2005 by maxXPsoft

[KNARZ]

No, you understand me wrong.

I mean slipstream not integrate (SVCPACK)

slipstream (you know) means to replace the original files from the i386 folder. i tryed it with hfslip and nlite but both of them missed some KB's (normal kb's which doesn't make problems e.g. 885250 (or something like this)

i want repleace them. (slipstream) by hand

Edited December 14, 2005 by KNARZ

[Shamwari]

How about the following batch I found on http://www.nzgadget.com/ article posted Sunday, September 11, 2005:

"Put the following into a batch file (I called it IntegrateAll.bat). Execute the batch file with the command:

IntegrateAll C:\XP"

@Echo off
rem ////////////////////////////////////////////////////////////////////////////
rem // IntegrateAll.bat
rem // This Batch file integrates the hotfixes for Windows XP SP2
rem // Syntax:
rem //   IntegrateAll <DistributionFolder>
rem ////////////////////////////////////////////////////////////////////////////

if "%~1" == "-p" goto Process

rem ////////////////////////////////////////////////////////////////////////////
rem // Main routine
rem // %1 contains Options
rem //

rem //
rem // Verify that we are pointing to a distribution folder base
rem //
if exist "%~1\I386" goto FolderExists

echo -- "%~1" is not a distribution folder.
echo Syntax:
echo   IntegrateAll ^<DistributionFolder^>
goto END

:FolderExists

echo ::: Integrating Updates :::

set DISTDIR="%~1"
set HFINT="%~1\i386\svcpack\HFINT.DAT"
set HFINTTEMP="%~1\i386\svcpack\HFINT.TMP"

rem // 
rem // Do 885835 and then 885250 to start with. There is a conflict here. So
rem // we need to do some special processing. Note: 885835 is superceeded by
rem // 885250 but we want an entry so that the hotfix show as installed
rem //
call %0 -p KB885835 "WindowsXP-KB885835-x86-ENU.exe" 

rem // Modify the line mrxsmb.sys (change it to mrxsmb.sys.tmp)
for /f "usebackq" %%L in (%HFINT%) DO (
 if %%L==mrxsmb.sys (
  echo %%L.tmp>>%HFINTTEMP%
 ) else (
  echo %%L>>%HFINTTEMP% )
)
move /y %HFINTTEMP% %HFINT% > NUL

rem // Integrate 85250  
call %0 -p KB885250 "WindowsXP-KB885250-x86-ENU.exe" 

rem // Modify the line back (change the mrxsmb.sys.tmp back to mrxsmb.sys)
for /f "usebackq" %%L in (%HFINT%) DO (
 if %%L==mrxsmb.sys.tmp ( 
  echo mrxsmb.sys>>%HFINTTEMP%
 ) else (
   echo %%L>>%HFINTTEMP% 
 )
)
move /y %HFINTTEMP% %HFINT% > NUL

rem //
rem // Now integrate all the rest of the hotfixes.

call %0 -p KB888302 "WindowsXP-KB888302-x86-ENU.exe" 
call %0 -p KB887472 "WindowsXP-KB887472-x86-enu.exe" 
call %0 -p KB891781 "WindowsXP-KB891781-x86-ENU.exe" 
call %0 -p KB888113 "WindowsXP-KB888113-x86-ENU.exe" 
call %0 -p KB867282 "WindowsXP-KB867282-x86-ENU.exe" 
call %0 -p KB873333 "WindowsXP-KB873333-x86-ENU.exe" 
call %0 -p KB890175 "WindowsXP-KB890175-x86-ENU.exe" 
call %0 -p KB886185 "WindowsXP-KB886185-x86-enu.exe" 
call %0 -p KB885836 "WindowsXP-KB885836-x86-ENU.exe" 
call %0 -p KB873339 "WindowsXP-KB873339-x86-ENU.exe" 
call %0 -p KB887742 "WindowsXP-KB887742-x86-ENU.exe" 

call %0 -p KB883939 "WindowsXP-KB883939-x86-ENU.exe" 
call %0 -p KB890046 "WindowsXP-KB890046-x86-ENU.exe" 
call %0 -p KB890859 "WindowsXP-KB890859-x86-ENU.exe" 
call %0 -p KB893066 "WindowsXP-KB893066-v2-x86-ENU.exe" 
call %0 -p KB893086 "WindowsXP-KB893086-x86-ENU.exe" 
call %0 -p KB896358 "WindowsXP-KB896358-x86-ENU.exe" 
call %0 -p KB896422 "WindowsXP-KB896422-x86-ENU.exe" 
call %0 -p KB896428 "WindowsXP-KB896428-x86-ENU.exe" 
call %0 -p KB898461 "WindowsXP-KB898461-x86-ENU.exe" 
call %0 -p KB903235 "WindowsXP-KB903235-x86-ENU.exe" 
call %0 -p KB901214 "WindowsXP-KB901214-x86-ENU.exe" 
call %0 -p KB893803v2 "WindowsInstaller-KB893803-v2-x86.exe" 
call %0 -p KB896727 "WindowsXP-KB896727-x86-ENU.exe" 
call %0 -p KB899587 "WindowsXP-KB899587-x86-ENU.exe" 
call %0 -p KB894391 "WindowsXP-KB894391-x86-ENU.exe" 
call %0 -p KB899588 "WindowsXP-KB899588-x86-ENU.exe" 
call %0 -p KB896423 "WindowsXP-KB896423-x86-ENU.exe" 
call %0 -p KB899591 "WindowsXP-KB899591-x86-ENU.exe" 
call %0 -p KB893756 "WindowsXP-KB893756-x86-ENU.exe" 

echo.
echo ::: Done :::
echo.

goto END

rem ////////////////////////////////////////////////////////////////////////////
rem ////////////////////////////////////////////////////////////////////////////
:Process
rem //
rem // %2 will contain the KB number
rem // %3 will contain the Exe file name
rem //

echo Integrating %2
"%~3" /integrate:%DISTDIR% /passive

:EndProcess
goto END

rem ////////////////////////////////////////////////////////////////////////////

:END

Disclaimer: this is not my work, but it works a charm, and make updating a clean XP source a doddle.

Regards

[KNARZ]

Still wrong understanding...

I want: Extract the Hotfixes - replacing the i386 SP2 files with the new one - Add the QFE or GDR *inf information to HIV*.inf in i386 and all other information which i need to do so, e.g. txtsetup.sif dosinf...

replaceing i386 source files. - i don't want use the /integrate:X command, no SVCPACK folder.

in short: Hotfix files replaces the I386 Source files with all needed new information.

(I'm not that noob, that you could expect if you look in my avater)

Edited December 14, 2005 by KNARZ

[Shamwari]

OK, how about RyanVM's MSFN Files Page Post SP2 Update Pack?

[tommyp]

What hotfixes are not slipstreamed correctly with HFSLIP?

[Oleg_II]

KNARZ

slipstream (you know) means to replace the original files from the i386 folder. i tryed it with hfslip and nlite but both of them missed some KB's (normal kb's which doesn't make problems e.g. 885250 (or something like this)

HFSLIP doesn't integrate hotfixes - it slipstreams them. Check SVCPACK.INF after running HFSLIP - is there any Windows-KB***-ENU.EXE or such lines? And you won't find any hotfix files in i386 - they are "dissolved" among the source files

As for KB's, you can ask on HFSLIP forum. If the problem can be solved TommyP or other member will help.

[KNARZ]

OK, how about RyanVM's MSFN Files Page Post SP2 Update Pack?

i have/use a german windows version.

oleg_ii: i know

tommyp: i don't know how many and which but e.g. i know that the WLAN WPA2 patch from Windows wasn't slipstreamed and some other (patch with new msconfig.exe)

My Structure (october):

Verzeichnis von H:\NEW XP\hfslip\HF

07.10.2005 16:21 12.814.336 mp10setup.exe

09.10.2005 14:19 739.408 msxmlcab-x86-DEU.exe

03.10.2005 21:02 856.416 Windows-KB890830-V1.8-DEU-x86-DEU.exe

09.10.2005 13:21 4.601.824 WindowsUpdateAgent20-x86-x86-DEU.exe

15.12.2004 14:05 617.704 WindowsXP-KB873339-x86-DEU.exe

18.06.2005 11:14 4.677.872 WindowsXP-KB884883-x86-DEU.exe

31.03.2005 02:59 527.088 WindowsXP-KB885222-x86-DEU.exe

09.02.2005 22:36 791.784 WindowsXP-KB885250-x86-DEU.exe

02.11.2004 16:47 1.204.968 WindowsXP-KB885523-x86-DEU.exe

23.12.2004 04:41 471.272 WindowsXP-KB885626-x86-DEU.exe

15.12.2004 14:05 3.111.656 WindowsXP-KB885835-x86-DEU.exe

15.12.2004 14:05 534.760 WindowsXP-KB885836-x86-DEU.exe

02.11.2004 16:56 4.550.888 WindowsXP-KB885884-x86-DEU.exe

02.11.2004 19:35 780.008 WindowsXP-KB885894-x86-DEU.exe

15.12.2004 14:02 398.568 WindowsXP-KB886185-x86-DEU.exe

06.03.2005 14:40 597.224 WindowsXP-KB886610-x86-DEU.exe

20.11.2004 19:57 548.072 WindowsXP-KB886677-x86-DEU.exe

31.03.2005 00:37 944.880 WindowsXP-KB886716-x86-DEU.exe

09.02.2005 22:36 1.085.672 WindowsXP-KB887472-x86-DEU.exe

23.11.2004 16:30 462.056 WindowsXP-KB887742-x86-DEU.exe

25.12.2004 20:56 1.433.832 WindowsXP-KB887797-x86-DEU.exe

09.02.2005 14:21 374.504 WindowsXP-KB888113-x86-DEU.exe

09.02.2005 14:17 401.128 WindowsXP-KB888302-x86-DEU.exe

28.05.2005 15:40 3.659.016 WindowsXP-KB888656-x86-DEU.exe

06.04.2005 13:10 356.584 WindowsXP-KB889016-x86-DEU.exe

15.06.2005 14:34 528.624 WindowsXP-KB890046-x86-DEU.exe

13.01.2005 18:46 474.344 WindowsXP-KB890831-x86-DEU.exe

12.04.2005 20:43 6.107.888 WindowsXP-KB890859-x86-DEU.exe

28.05.2005 15:40 6.210.824 WindowsXP-KB891122-x86-DEU.exe

09.02.2005 14:20 410.856 WindowsXP-KB891781-x86-DEU.exe

11.05.2005 12:08 2.549.512 WindowsXP-KB892313-x86-DEU.exe

15.06.2005 16:23 796.912 WindowsXP-KB893066-x86-DEU.exe

12.04.2005 20:24 4.651.248 WindowsXP-KB893086-x86-DEU.exe

29.05.2005 12:15 1.253.616 WindowsXP-KB893357-x86-DEU.exe

15.08.2005 15:05 697.072 WindowsXP-KB893756-x86-DEU.exe

13.05.2005 16:05 2.584.848 WindowsXP-KB893803-x86-DEU.exe

21.05.2005 07:59 2.082.544 WindowsXP-KB894391-x86-DEU.exe

13.05.2005 19:25 4.637.936 WindowsXP-KB895200-x86-DEU.exe

14.10.2005 15:27 2.590.960 WindowsXP-KB896256-v3-x86-DEU.exe

15.06.2005 14:29 1.044.208 WindowsXP-KB896358-x86-DEU.exe

15.06.2005 14:29 726.256 WindowsXP-KB896422-x86-DEU.exe

15.08.2005 15:06 569.584 WindowsXP-KB896423-x86-DEU.exe

15.06.2005 14:35 531.184 WindowsXP-KB896428-x86-DEU.exe

14.05.2005 13:02 614.128 WindowsXP-KB896626-x86-DEU.exe

11.10.2005 20:48 4.971.248 WindowsXP-KB896688-x86-DEU.exe

03.10.2005 21:01 533.744 WindowsXP-KB897663-x86-DEU.exe

15.06.2005 14:36 1.036.048 WindowsXP-KB898458-x86-DEU.exe

29.06.2005 00:47 493.808 WindowsXP-KB898461-x86-DEU.exe

15.08.2005 15:06 743.664 WindowsXP-KB899587-x86-DEU.exe

15.08.2005 15:05 584.944 WindowsXP-KB899588-x86-DEU.exe

11.10.2005 20:47 545.008 WindowsXP-KB899589-x86-DEU.exe

15.08.2005 15:05 589.552 WindowsXP-KB899591-x86-DEU.exe

12.10.2005 20:18 5.221.104 WindowsXP-KB900725-x86-DEU.exe

18.06.2005 11:14 1.320.176 WindowsXP-KB900930-x86-DEU.exe

11.10.2005 20:48 1.053.936 WindowsXP-KB901017-x86-DEU.exe

12.07.2005 23:01 631.536 WindowsXP-KB901214-x86-DEU.exe

11.10.2005 20:48 4.940.528 WindowsXP-KB902400-x86-DEU.exe

29.07.2005 17:14 526.064 WindowsXP-KB903234-x86-DEU.exe

09.10.2005 10:51 538.352 WindowsXP-KB904412-x86-DEU.exe

11.10.2005 20:41 1.400.048 WindowsXP-KB904706-x86-DEU.exe

11.10.2005 20:47 627.440 WindowsXP-KB905414-x86-DEU.exe

11.10.2005 20:48 588.528 WindowsXP-KB905749-x86-DEU.exe

07.10.2005 14:30 567.024 WindowsXP-KB906569-x86-DEU.exe

03.10.2005 20:32 562.416 WindowsXP-KB907865-x86-DEU.exe

64 Datei(en) 113.079.232 Bytes

Verzeichnis von H:\NEW XP\hfslip\FDVFILES

14.10.2005 14:27 <DIR> .

14.10.2005 14:27 <DIR> ..

0 Datei(en) 0 Bytes

Verzeichnis von H:\NEW XP\hfslip\FIX

14.10.2005 14:27 <DIR> .

14.10.2005 14:27 <DIR> ..

13.11.2005 21:41 1.408 WINNT.SIF

1 Datei(en) 1.408 Bytes

Verzeichnis von H:\NEW XP\hfslip\HFCABS

14.10.2005 14:27 <DIR> .

14.10.2005 14:27 <DIR> ..

09.10.2005 13:21 355.629 LegitCheckControl.cab

09.10.2005 22:03 741.237 swflash.cab

2 Datei(en) 1.096.866 Bytes

Verzeichnis von H:\NEW XP\hfslip\HFSVPK

14.10.2005 14:27 <DIR> .

14.10.2005 14:27 <DIR> ..

14.05.2005 14:17 44.685 reg.reg

1 Datei(en) 44.685 Bytes

Verzeichnis von H:\NEW XP\hfslip\HFSVPK_SW

06.11.2005 15:36 <DIR> .

06.11.2005 15:36 <DIR> ..

05.01.2005 11:33 533.768 energyblissviz.exe

02.11.2004 16:48 696.792 scriptde.exe

02.11.2004 16:37 5.072.896 vm3810.exe

3 Datei(en) 6.303.456 Bytes

Verzeichnis von H:\NEW XP\hfslip\HFTOOLS

14.10.2005 14:27 <DIR> .

14.10.2005 14:27 <DIR> ..

27.03.2002 23:19 237.568 MSICabExtract.exe

28.03.2002 12:31 669 MSICabExtract.txt

2 Datei(en) 238.237 Bytes

[Bilou_Gateux]

Still wrong understanding...

I want: Extract the Hotfixes - replacing the i386 SP2 files with the new one - Add the QFE or GDR *inf information to HIV*.inf in i386 and all other information which i need to do so, e.g. txtsetup.sif dosinf...

replaceing i386 source files. - i don't want use the /integrate:X command, no SVCPACK folder.

in short: Hotfix files replaces the I386 Source files with all needed new information.

(I'm not that noob, that you could expect if you look in my avater)

I have already written two batch to do some parts of the job:

• 1st batch HF1.CMD integrate (HFINT.DAT is created in SVCPACK folder) HFs in i386 distribution folder
  
• actually done by hand: clean the i386\svcpack.inf file from all KB######.exe /q /n /o /u /z lines.
  
• 2nd batch use (HFINT.DAT) to repack updated binaries in i386 distribution folder
  
• actually done by hand: update TXTSETUP.SIF in case of new binaries. DOSNET.INF is already updated by previous integrate
  
• 3rd batch will (Insert (append) text into existing .inf file, batch file request to do it unattended) uses extracted infos from various HF update_SPxGDR.inf to update HIVESFT.INF and HIVECLS.INF using SED.
  

but haven't yet finished writing the 2nd and 3rd one contains only the basic. Still a lot of (typos) errors.

PS: All checks i have done are with Windows Server 2003 Standard or Web Edition Service Pack 1

Edited January 18, 2006 by Bilou_Gateux

[KNARZ]

Bilou_Gateux: Congratulations, you understand me =)

If you want you can send me the batches and MAYBE i can help, but i think i don't have enough knowlege about batch to help you in a good way.

but maybe

Why do you use GDR and not QFE? - (I read the MS KB, but it was no clearly answer for me)

Edited December 17, 2005 by KNARZ

[Bilou_Gateux]

Step 1 - Gathering the Needed Parts and Pieces

There are a few essential items necessary to successfully create the slipstreamed CD. You will need:

The original Windows 2003 Server installation CD ROM.

Windows 2003 Server Service Pack 1 - It will be necessary to either download SP1 or obtain it on CD. To slipstream, you need the full SP1 (Network Installation).

Step 2 - Building Directories

The first step is to build a directory structure to hold the files that will be used in the CD creation process. It's a simple structure, requiring nothing more than a few folders. It doesn't matter what names you use for your folders or where you locate them on your hard drive, but most users find drive C the easiest. I created the folders shown below, located on Drive C. Create whatever folders you are comfortable with or use the ones below if you want to copy and paste commands later in the tutorial.

C:\HFSLIP\WIN51IB.SP1

C:\HFSLIP\WU\Software\en\com_microsoft.windowsnetserver2003family\x86WinXP

Step 3 - Copying and Extracting Files

The first step is to insert the Windows 2003 Server CD and copy the entire contents into the WIN51IB.SP1 folder or the equivalent folder in your structure.

The second step is to navigate to where you downloaded the Service Pack 1 file. If you downloaded SP1 from Microsoft it should be named WindowsServer2003-KB889101-SP1-x86-ENU.exe.

Step 4 - Updating The Windows Share

Apply the Service Pack 1 to Windows Server 2003 in the WIN51IB.SP1 folder that were copied in the first step.

WindowsServer2003-KB889101-SP1-x86-ENU.exe /integrate:C:\HFSLIP\WIN51IB.SP1

Step5 - HF1.CMD and hivesft.cmd

My current batches script are located here

What does HF1.cmd: it integrates each HF KB######.exe /integrate:%source%

Why do you use GDR and not QFE? - (I read the MS KB, but it was no clearly answer for me)

Microsoft takes the decision for me.

This method uses update_SP1GDR.inf and binaries located in KB######\sp1gdr to update the source.

It also call a 2nd batch hivesft.cmd for extracting from update_SPxGDR.INF infos to later inject in HIVExxx.INF.

Cannot be used to integrate MSFT bloat (WMP, Messenger, .NET framework), only WindowsServer2003-KB######-x86-enu.exe HFs.

Step6 - HFINT.cmd

Step7 - HIVEsft.cmd

Step 8 - ???.cmd

Edited January 21, 2006 by Bilou_Gateux

[KNARZ]

the only interessting thing in the post was the info, that you have a batch (buggy/komplex) to injekt the GDR_inf's in the HIVE's.

i already know the steps

maybe i can optimize it.