crayoxided

Excellent! Again, thanks for the reply.

lol. I did! http://support.microsoft.com/kb/912817 No where, that I could see, did it state that 912817 superceeded 902400. And if it is superceeding, why did windowsupdate not sense that when it scanned the base install? Very newbie questions, I know, and since I'm an RTFM guy myself ... it is killing me to behind on this learning curve. Is there a FAQ or a website somewhere that I can get up to speed on these types of questions?

Thanks for the reply. Outside of something, I guess, like WSUS, how does one find out about what is being superceeded?

Before I HFSlip'd my XP SP2, I searched the MSFN boards to try and understand why KB894391 and KB902400 were not in Tomcat76 dynamic list of updates to be downloaded. As best as I could determine, KB894391 was superceeded by KB902400 and it was superceeded by KB913580. However, when I run a fresh HFSlip'd install against windowsupdate.microsoft.com, it complains that 894391 and 902400 are missing. I left out these optional updates: KB896344 Cannot transfer from XPSP2 32-bit to XP 64-bit KB900485 "Stop 0x7E in aec.sys" error message KB904942 Issue with MSOE6 when installing MSIE7 KB909520 Update for Microsoft Base Smart Card CSP and I left out these because a base install of XP SP2 did not call for them: KB917537 Vulnerability in MS IIS using ASP KB912817 COM+ Hotfix Rollup Package 13 KB901190 Vulnerability in the Korean IME KB885626 Systems running Prescott C-0 w/o BIOS support Since I am so new to HFSlip, I am learning how to get windowsupdate happy before I tackle the options for bloat. Am I missing something?