Hotfixes For Windows XP Professional SP2

[RyanVM]

so does this mean you are trying to update the file [TPC-IP.SYS]?

if so i'll wait a bit before i update my CD

What's TPC-IP.SYS?

[sixpack]

so does this mean you are trying to update the file [TPC-IP.SYS]?

if so i'll wait a bit before i update my CD

What's TPC-IP.SYS?

Sorry misspell TCPIP.SYS

[RyanVM]

so does this mean you are trying to update the file [TPC-IP.SYS]?

if so i'll wait a bit before i update my CD

What's TPC-IP.SYS?

Sorry misspell TCPIP.SYS

I already did patch it. Look back a page

[RyanVM]

%DATE:~4,14%

That should get the date without the "Sat".

EDIT: You can only use variable with REG.EXE, not REGEDIT.EXE.

I'm beginning to think an INF is a better way to do this.

[GreenMachine]

REG.EXE is really not bad, though not available in Windows 2000.

[RyanVM]

REG.EXE is really not bad, though not available in Windows 2000.

Here's what I'm thinking (and now's the best time to do it since there's only two real hotfixes for SP2 thus far): Keep track of and makecab all of the hotfixed files, which can be put directly in i386. Then keep an INF with the registry entries to be added for each hotfix (mostly just HKLM\blah\Hotfix and HKLM\blah\Updates entries) to be applied during setup. That way you've got all the newest files integrated into the install source, but you don't have to run all the EXEs during setup, saving time and space.

[sixpack]

@RyanVM

thanks

[GreenMachine]

@RyanVM: In that case, an .INF file is probably better suited. You could also use it to move/copy files. RaveRod did something along those lines long ago.

[RyanVM]

Yeah, I think I'm gonna do it. And starting from the beginning, it shouldn't be too bad to make and maintain. I wouldn't have wanted to start it 6 months ago with SP1 hotfixes, though

[GreenMachine]

So far it seems OK, but just wait till they release another Advanced Networking Package (a.k.a. 817778) type patch!

Still, it will certainly be faster then integrating the files, and running the fixes from SVCPACK.INF.

Let the RyanVM HotFix Pack fly!

[RyanVM]

So far it seems OK, but just wait till they release another Advanced Networking Package (a.k.a. 817778) type patch!

Still, it will certainly be faster then integrating the files, and running the fixes from SVCPACK.INF.

Let the RyanVM HotFix Pack fly!

Yeah, I was thinking about that kind of pack too (or HighMAT).

I agree, let it fly! (when the U of M game is done )

[GreenMachine]

I agree, let it fly! (when the U of M game is done )

Time for work! (Just don't put your knee down: you might get roughed!)

[RyanVM]

I agree, let it fly! (when the U of M game is done )

Time for work! (Just don't put your knee down: you might get roughed!)

Yeah no kidding

[XtremeMaC]

hi there

1st

which tells us that it can be integrated into the cd (which I just tested and, it works.)

it creates the svcpack folder and puts these in there

branches.inf

HFINT.dat

KB884020.cat

KB884020.exe

and here's what the svcpack.inf looks like

[CatalogHeader]

[Version]

BuildNumber=2600

MinorVersion=1

MajorVersion=5

Signature="$WINDOWS NT$"

[setupData]

CatalogSubDir="\I386\svcpack"

[setupHotfixesToRun]

KB884020.exe /q /n /z

[ProductCatalogsToInstall]

KB884020.cat

so after this stage of integrating the modified tcpip.sys could be replaced easily..

or better yet I could be dreaming...ok this post was useless.. just realized that this was for integrating the sys in the cd

so yes inf's way to go

Edited September 18, 2004 by XtremeMaC

[GreenMachine]

I still think that XPCREATE does a nicer job: they still run the update from SVCPACK, don't compress the files added to I386, and don't use the /O switch on the hotfix. That can get really slow when the number of fixes adds up.

However, I do think there is something to be learned from what the /INTEGRATE option does. (Like the BRANCHES.INF)

They should really talk to me before doing this stuff ...