New hotfixes?

[LeveL]

Today is that glorious monthly day when M$ releases hotfixes.

With HFSLIP, is it safe to just put any new hotfixes in the HF folder, or

does the HFSLIP bat file always get updated to support new hotfixes?

I know this question has probably been asked a million times, I couldn't

really find any info on it.

I assume if the hotfixes are standard, E.G. with a white icon /q /o /z it is OK?

This is for Windows 2000, apparently M$ is releasing hotfixes for all OS's (2000, XP and 2003) today.

Edited August 14, 2007 by LeveL

[Tomcat76]

No, I need to open them up and see if everything is OK. An installation switch doesn't say anything.

[LeveL]

I can test them out with the current HFSLIP if you want.

Windows 2000 SP4

(August 14th Hotfixes)

Windows-KB890830-V1.32.exe

IE6.0sp1-KB937143-Windows2000-x86-ENU.exe

IE6.0sp1-KB938127-Windows2000-x86-ENU.exe

msxml4-KB936181-enu.exe

msxml6-KB933579-enu-x86.exe

Windows2000-KB921503-x86-ENU.EXE

Windows2000-KB936021-x86-ENU.EXE

Windows2000-KB938829-x86-ENU.EXE

WindowsMedia9-KB936782-x86-ENU.exe

KB933579

Security Update for Microsoft XML Core Services 6.0 and Microsoft XML Core Services 6.0 Service Pack 1

KB890830

Windows Malicious Software Removal Tool - August 2007

KB921503

Security Update for Windows 2000

KB938829

Security Update for Windows 2000

KB937143

Cumulative Security Update for Internet Explorer 6 Service Pack 1

KB936782

Security Update for Windows Media Player 9

KB936181

Security Update for Microsoft XML Core Services 4.0 Service Pack 2

KB936021

Security Update for Windows 2000

KB938127

Security Update for Internet Explorer 6 Service Pack 1

The two MSXML hotfixes are MSI files, they need extracting out of the hotfix

and the /quiet /norestart switches are used. Its /q /o /z on all others.

[Tomcat76]

Those switches are not for extracting the hotfixes. They are used for regular installation which is not HFSLIP's purpose.

Either way, I checked them out and I can't see a problem. I am currently testing Win2K.

[LeveL]

Those switches are not for extracting the hotfixes.

Oh no I know im just saying, the only ones I had a problem with doing it the /q /o /z way

were the two MSXML ones, but I looked inside and they are MSI files.

I am also testing

I put all the hotfixes in the HF folder except with those 2 MSXML hotfixes, I extracted the

MSI files out and put the 2 MSI files inside the HF folder.

I will post back the results.

[Tomcat76]

2K is OK.

[LeveL]

eeeeeeeek!

Yeah everything went OK for me except this one:

Security Update for Microsoft XML Core Services 4.0 Service Pack 2 (KB936181)

Did you put the hotfixes directly into the HF folder?

I didn't, I extracted the MSXML ones (MSI files) and put the MSI files in the HF folder.

I thought HFSLIP was good but sheesh - you mean you don't even have to extract those MSXML MSI files out?

Nice one Tomcat76, indeed, just throw ALL the August hotfixes into HF as they are and it works!

Thanks man, HFSLIP is a force to be reckoned with!

Edited August 15, 2007 by LeveL

[Tomcat76]

There must've been a conflict somewhere. Did you remove the previous MSXML4 update?

[LeveL]

There must've been a conflict somewhere. Did you remove the previous MSXML4 update?

No, I unpacked the MSXML hotfixes and put the MSI files in the HF folder = mistake.

What I should have done was just put the hotfixes in directly, without extracting, then it worked.

[Tomcat76]

HFSLIP can handle MSI files for MSXML in the HF folder. It can be used to speed up the process (one extraction instead of two).

MSXML4/6 as EXE: extract EXE > extract MSI > process DLLs

MSXML4/6 as MSI: extract MSI > process DLLs

That's what HFSLIP is doing internally. If the first worked for you, I can't think of any reason why the second would fail because the MSI file is the same. You took it out of the MSXML4 EXE package but that's exactly what HFSLIP is doing too when you give it the EXE.

[LeveL]

When I extracted them (which I didn't need to do) of the two new August hotfixes for MSXML, only one of them didn't install, that was the "msxml.msi" which despite the short name, is the August one. When I left it alone and just put the EXE (white icon) hotfixes in, it worked. So extracting the MSI files out of the two new hotfixes, yes one of them did work but the msxml.msi one didn't. Nevermind, nice to know it doesn't even require any extracting, just dump all August hotfixes in the HF folder and it works! Can't thank you enough for HFSLIP, it makes things so easy. It even puts in all the new DirectX files like d3dx9_35.dll