To: FreeKeys
Steve doesn't address it on the webpage; perhaps it was in the program. How compatible will the hotfix be with the service update coming down the pipe from Microsoft? I'm leery about installing a fix that will lock up a later patch.
4 posted on
01/03/2006 5:27:05 PM PST by
kingu
To: kingu
You can just un-register the dll responsible for the flaw and turn it back on later when Microsoft does release a patch.
(Denny Crane: "I Don't Want To Socialize With A Pinko Liberal Democrat Commie. Say What You Like About Republicans. We Stick To Our Convictions. Even When We Know We're Dead Wrong.")
5 posted on
01/03/2006 5:30:53 PM PST by
goldstategop
(In Memory Of A Dearly Beloved Friend Who Lives On In My Heart Forever)
To: kingu
How compatible will the hotfix be with the service update coming down the pipe from Microsoft? I'm leery about installing a fix that will lock up a later patch.I don't know; I'm not a techie. It DOES tell you how to un-install it, however, so you should do that first anyway. I should point out that I'm not even sure this is the same horrible Windows security flaw; it IS possible for TWO (or even more) MS flaws to have just been discovered at the same time!
6 posted on
01/03/2006 5:35:50 PM PST by
FreeKeys
(Democrats play politics with national security.)
To: kingu
How compatible will the hotfix be with the service update coming down the pipe from Microsoft?There are instructions for removing the patch when MS comes out with their patch. IIRC, it's fairly painless.
7 posted on
01/03/2006 5:47:29 PM PST by
randog
(What the....?!)
FreeRepublic.com is powered by software copyright 2000-2008 John Robinson