A
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.
You should upgrade or use an alternative browser.
B
Barry Watzman
This is not really an adequate fix. What MS needs to do is issue a new
Security Update, PRONTO (Monday) that will be automatically installed by
anyone with Automatic Live Update turned on, that makes the fix (and
I'm not sure that the proposed fix is really adequate, but at least it's
a start). MS cannot expect 100 million+ mostly technically illiterate
users to use Regedit to fix this problem.
Security Update, PRONTO (Monday) that will be automatically installed by
anyone with Automatic Live Update turned on, that makes the fix (and
I'm not sure that the proposed fix is really adequate, but at least it's
a start). MS cannot expect 100 million+ mostly technically illiterate
users to use Regedit to fix this problem.
B
Barry Watzman
This is not really an adequate fix. What MS needs to do is issue a new
Security Update, PRONTO (Monday) that will be automatically installed by
anyone with Automatic Live Update turned on, that makes the fix (and
I'm not sure that the proposed fix is really adequate, but at least it's
a start). MS cannot expect 100 million+ mostly technically illiterate
users to use Regedit to fix this problem.
Security Update, PRONTO (Monday) that will be automatically installed by
anyone with Automatic Live Update turned on, that makes the fix (and
I'm not sure that the proposed fix is really adequate, but at least it's
a start). MS cannot expect 100 million+ mostly technically illiterate
users to use Regedit to fix this problem.
B
Barry Watzman
This is not really an adequate fix. What MS needs to do is issue a new
Security Update, PRONTO (Monday) that will be automatically installed by
anyone with Automatic Live Update turned on, that makes the fix (and
I'm not sure that the proposed fix is really adequate, but at least it's
a start). MS cannot expect 100 million+ mostly technically illiterate
users to use Regedit to fix this problem.
Security Update, PRONTO (Monday) that will be automatically installed by
anyone with Automatic Live Update turned on, that makes the fix (and
I'm not sure that the proposed fix is really adequate, but at least it's
a start). MS cannot expect 100 million+ mostly technically illiterate
users to use Regedit to fix this problem.
B
Barry Watzman
This is not really an adequate fix. What MS needs to do is issue a new
Security Update, PRONTO (Monday) that will be automatically installed by
anyone with Automatic Live Update turned on, that makes the fix (and
I'm not sure that the proposed fix is really adequate, but at least it's
a start). MS cannot expect 100 million+ mostly technically illiterate
users to use Regedit to fix this problem.
Security Update, PRONTO (Monday) that will be automatically installed by
anyone with Automatic Live Update turned on, that makes the fix (and
I'm not sure that the proposed fix is really adequate, but at least it's
a start). MS cannot expect 100 million+ mostly technically illiterate
users to use Regedit to fix this problem.
B
Barry Watzman
This is not really an adequate fix. What MS needs to do is issue a new
Security Update, PRONTO (Monday) that will be automatically installed by
anyone with Automatic Live Update turned on, that makes the fix (and
I'm not sure that the proposed fix is really adequate, but at least it's
a start). MS cannot expect 100 million+ mostly technically illiterate
users to use Regedit to fix this problem.
Security Update, PRONTO (Monday) that will be automatically installed by
anyone with Automatic Live Update turned on, that makes the fix (and
I'm not sure that the proposed fix is really adequate, but at least it's
a start). MS cannot expect 100 million+ mostly technically illiterate
users to use Regedit to fix this problem.
B
Barry Watzman
This is not really an adequate fix. What MS needs to do is issue a new
Security Update, PRONTO (Monday) that will be automatically installed by
anyone with Automatic Live Update turned on, that makes the fix (and
I'm not sure that the proposed fix is really adequate, but at least it's
a start). MS cannot expect 100 million+ mostly technically illiterate
users to use Regedit to fix this problem.
Security Update, PRONTO (Monday) that will be automatically installed by
anyone with Automatic Live Update turned on, that makes the fix (and
I'm not sure that the proposed fix is really adequate, but at least it's
a start). MS cannot expect 100 million+ mostly technically illiterate
users to use Regedit to fix this problem.
B
Barry Watzman
This is not really an adequate fix. What MS needs to do is issue a new
Security Update, PRONTO (Monday) that will be automatically installed by
anyone with Automatic Live Update turned on, that makes the fix (and
I'm not sure that the proposed fix is really adequate, but at least it's
a start). MS cannot expect 100 million+ mostly technically illiterate
users to use Regedit to fix this problem.
Security Update, PRONTO (Monday) that will be automatically installed by
anyone with Automatic Live Update turned on, that makes the fix (and
I'm not sure that the proposed fix is really adequate, but at least it's
a start). MS cannot expect 100 million+ mostly technically illiterate
users to use Regedit to fix this problem.
B
Barry Watzman
This is not really an adequate fix. What MS needs to do is issue a new
Security Update, PRONTO (Monday) that will be automatically installed by
anyone with Automatic Live Update turned on, that makes the fix (and
I'm not sure that the proposed fix is really adequate, but at least it's
a start). MS cannot expect 100 million+ mostly technically illiterate
users to use Regedit to fix this problem.
Security Update, PRONTO (Monday) that will be automatically installed by
anyone with Automatic Live Update turned on, that makes the fix (and
I'm not sure that the proposed fix is really adequate, but at least it's
a start). MS cannot expect 100 million+ mostly technically illiterate
users to use Regedit to fix this problem.
R
Rhonda Lea Kirk
Barry said:This is not really an adequate fix. What MS needs to do is issue a
new Security Update, PRONTO (Monday) that will be automatically
installed by anyone with Automatic Live Update turned on, that makes
the fix (and I'm not sure that the proposed fix is really adequate,
but at least it's a start). MS cannot expect 100 million+ mostly
technically illiterate users to use Regedit to fix this problem.
In microsoft.public.windowsxp.general, you'll find this:
http://groups.google.com/group/[email protected]&rnum=1#9660d27b5cf11c22
Granted, it's not what you're asking for, but it's better than nothing.
rl
R
Rhonda Lea Kirk
Barry said:This is not really an adequate fix. What MS needs to do is issue a
new Security Update, PRONTO (Monday) that will be automatically
installed by anyone with Automatic Live Update turned on, that makes
the fix (and I'm not sure that the proposed fix is really adequate,
but at least it's a start). MS cannot expect 100 million+ mostly
technically illiterate users to use Regedit to fix this problem.
In microsoft.public.windowsxp.general, you'll find this:
http://groups.google.com/group/[email protected]&rnum=1#9660d27b5cf11c22
Granted, it's not what you're asking for, but it's better than nothing.
rl
R
Rhonda Lea Kirk
Barry said:This is not really an adequate fix. What MS needs to do is issue a
new Security Update, PRONTO (Monday) that will be automatically
installed by anyone with Automatic Live Update turned on, that makes
the fix (and I'm not sure that the proposed fix is really adequate,
but at least it's a start). MS cannot expect 100 million+ mostly
technically illiterate users to use Regedit to fix this problem.
In microsoft.public.windowsxp.general, you'll find this:
http://groups.google.com/group/[email protected]&rnum=1#9660d27b5cf11c22
Granted, it's not what you're asking for, but it's better than nothing.
rl
R
Rhonda Lea Kirk
Barry said:This is not really an adequate fix. What MS needs to do is issue a
new Security Update, PRONTO (Monday) that will be automatically
installed by anyone with Automatic Live Update turned on, that makes
the fix (and I'm not sure that the proposed fix is really adequate,
but at least it's a start). MS cannot expect 100 million+ mostly
technically illiterate users to use Regedit to fix this problem.
In microsoft.public.windowsxp.general, you'll find this:
http://groups.google.com/group/[email protected]&rnum=1#9660d27b5cf11c22
Granted, it's not what you're asking for, but it's better than nothing.
rl
R
Rhonda Lea Kirk
Barry said:This is not really an adequate fix. What MS needs to do is issue a
new Security Update, PRONTO (Monday) that will be automatically
installed by anyone with Automatic Live Update turned on, that makes
the fix (and I'm not sure that the proposed fix is really adequate,
but at least it's a start). MS cannot expect 100 million+ mostly
technically illiterate users to use Regedit to fix this problem.
In microsoft.public.windowsxp.general, you'll find this:
http://groups.google.com/group/[email protected]&rnum=1#9660d27b5cf11c22
Granted, it's not what you're asking for, but it's better than nothing.
rl
R
Rhonda Lea Kirk
Barry said:This is not really an adequate fix. What MS needs to do is issue a
new Security Update, PRONTO (Monday) that will be automatically
installed by anyone with Automatic Live Update turned on, that makes
the fix (and I'm not sure that the proposed fix is really adequate,
but at least it's a start). MS cannot expect 100 million+ mostly
technically illiterate users to use Regedit to fix this problem.
In microsoft.public.windowsxp.general, you'll find this:
http://groups.google.com/group/[email protected]&rnum=1#9660d27b5cf11c22
Granted, it's not what you're asking for, but it's better than nothing.
rl
R
Rhonda Lea Kirk
Barry said:This is not really an adequate fix. What MS needs to do is issue a
new Security Update, PRONTO (Monday) that will be automatically
installed by anyone with Automatic Live Update turned on, that makes
the fix (and I'm not sure that the proposed fix is really adequate,
but at least it's a start). MS cannot expect 100 million+ mostly
technically illiterate users to use Regedit to fix this problem.
In microsoft.public.windowsxp.general, you'll find this:
http://groups.google.com/group/[email protected]&rnum=1#9660d27b5cf11c22
Granted, it's not what you're asking for, but it's better than nothing.
rl
R
Rhonda Lea Kirk
Barry said:This is not really an adequate fix. What MS needs to do is issue a
new Security Update, PRONTO (Monday) that will be automatically
installed by anyone with Automatic Live Update turned on, that makes
the fix (and I'm not sure that the proposed fix is really adequate,
but at least it's a start). MS cannot expect 100 million+ mostly
technically illiterate users to use Regedit to fix this problem.
In microsoft.public.windowsxp.general, you'll find this:
http://groups.google.com/group/[email protected]&rnum=1#9660d27b5cf11c22
Granted, it's not what you're asking for, but it's better than nothing.
rl
B
Barry Watzman
It's an improvement, but since the "problem" was installed automatically
by Automatic updates, the fix needs to be "pushed" the same way.
by Automatic updates, the fix needs to be "pushed" the same way.
B
Barry Watzman
It's an improvement, but since the "problem" was installed automatically
by Automatic updates, the fix needs to be "pushed" the same way.
by Automatic updates, the fix needs to be "pushed" the same way.
B
Barry Watzman
It's an improvement, but since the "problem" was installed automatically
by Automatic updates, the fix needs to be "pushed" the same way.
by Automatic updates, the fix needs to be "pushed" the same way.