Jump to content

Script -- SP slipstreamer for HFSLIP. Anyone game to test?


Recommended Posts

Posted (edited)

[Attachments removed]

This script slipstreams the service pack into a Windows source that's located in HFSLIP's SOURCE folder.

Instructions:

1) Put the CD source in HFSLIP's SOURCE folder

2) Create a folder called HFSPACK inside the HFSLIP folder and put your service pack file in it

3) Place one of the attached scripts in the HFSLIP folder and run it

4) Have patience :)

The difference between spslipA-060126-1.cmd and spslipB-060126-1.cmd is that "spslipB" blocks the slipstreaming process if the source has already been patched.

*** spslipA ***

Service packs supported:

- SP4 for Win2K

- SP1a for WinXP

- SP1 for WinXP

- SP2 for WinXP

- SP1 for Win2K3

You can have both SP1 and SP2 for WinXP in there, but only SP2 will be processed in that case.

Slipstreaming SP1, SP2 or SP3 for Win2K into any version of Win2K is not possible.

WinXP can be patched from Windows 2000.

*** spslipB ***

This one is supposed to become the final version.

The following table explains which service packs are supported for which OS version.

SOURCE		  HFSPACK
--------------------------------
Win2K Gold SP4
Win2K SP1 SP4
Win2K SP2 SP4
Win2K SP3 SP4
Win2K SP4 No SP supported

WinXP Gold SP2, SP1a or SP1
WinXP SP1 SP2
WinXP SP1a SP2
WinXP SP2 No SP supported

Win2K3 Gold SP1
Win2K3 SP1 No SP supported

The service pack versions are sorted by preference. If more than one service pack is included in the HFSPACK folder, the one with the highest preference for the OS version in the SOURCE folder is used and the others are ignored. For now, this only applies to "WinXP Gold".

WinXP can be patched from Windows 2000.

The following are not possible:

- slipstreaming SP1, SP2 or SP3 for Win2K into any version of Win2K

- slipstreaming SP1a for WinXP into a WinXP SP1 source

*** Technical details for spslipB ***

Stage 0

If the HFSPACK folder exists and there's at least one file in it, Stage 1 is called.

Stage 1a

Check if individual hotfixes have been integrated into the source before. If that's the case, display an error and EXIT immediately after the user clicked a key.

Stage 1b

Check if the source still needs to be patched. If not, display a message and stop the slipstreaming process. If the source DOES need to be patched, proceed with Stage 2.

Stage 2

Check if the service pack in the HFSPACK folder is accepted for the OS in the SOURCE folder. If it isn't, display an error and stop the slipstreaming process. If the service pack IS accepted, proceed with Stage 3.

Stage 3

Patch the source.

In spslipA, Stage 1 is skipped (Stage 0 calls Stage 2).

Revision 1: Changed the name of the SP folder and the script is now deleting "svcpack.inf" if it detects it. Use the new file with the description above.

Revision 060126-1: distinguish between XPSP1 and XPSP1a to fix a "collision"; created second version preventing unneeded SP slipstreaming

Revision 060126-2: removed an unneeded PAUSE command that was used for testing; solved issue leaving behind "svcpack.log" in the HFSLIP folder

Revision 060126-3: unbloated the scripts a teenie little bit; no functionality changes from rev. 060126-2

Revision 060127-1: added more "validity checks" (see "technical details")

Edited by Tomcat76

Posted

Very nice Tomcat76. For the future, can you rename the SPACK to HFSPACK? Reason? Because when I view directories I like to see the "extras" segregated from the SOURCE and SOURCESS. Yea, I know, call me anal retentive.

A little comment. If slipstreaming SP2 onto an OEM cd, you may need to delete the svcpack.in_ file. I ran into that problem a lot.

Once troubleshooting is complete with this, I'll incorporate this into HFSLIP.

Posted

So what's your middle name then? :P

Script updated. I opted to delete "svcpack.inf" instead of "svcpack.in_". I'd say let's see how this goes first...

Posted

At this point, I mainly need results from the following people:

- those with Windows Server 2003

- those who have problems with slipstreaming in general

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...