MS Web Site lacks time saving ability

[MS_shady_in_KB]

Information about most KB searches are usually vague, if
you really want to understand a security patches actual
issue, get a shovel! After following several links, you
may find out. For example, I recently (i'm assuming that
there have been thousands of you tried same search) queried
KB [s/b dumb db] for the XP Pro Sp2 release date. Not to
get it yet, but to schedule myself time to review the
service packs fixes, paying attention to the compabitibilty
issues primarily. We're using legacy apps., intranet
clients w/ internet access are few enough to enable auto
updates, for our db on server. Short story long, I never
was able to find this info on
Microsoft.com/windows/xp/pro/sp2--Tree or within links
where any logical person would have posted this info. OR,
is that the problem itself, LOGIC?? I danderously 'assume'
that the shady game is a result of a lack in confidence on
behlf of MS. As you likely know, this XPsp2 release was
constantly pushed back. Again, lacking confidence seems
aparent. My opinion of the XPsp2 fixes, "this should be
called XP Pro sp0 (initial release of OS)!

 

[hermes]

Information about most KB searches are usually vague, if
you really want to understand a security patches actual
issue, get a shovel! After following several links, you
may find out. For example, I recently (i'm assuming that
there have been thousands of you tried same search) queried
KB [s/b dumb db] for the XP Pro Sp2 release date. Not to
get it yet, but to schedule myself time to review the
service packs fixes, paying attention to the compabitibilty
issues primarily. We're using legacy apps., intranet
clients w/ internet access are few enough to enable auto
updates, for our db on server. Short story long, I never
was able to find this info on
Microsoft.com/windows/xp/pro/sp2--Tree or within links
where any logical person would have posted this info. OR,
is that the problem itself, LOGIC?? I danderously 'assume'
that the shady game is a result of a lack in confidence on
behlf of MS. As you likely know, this XPsp2 release was
constantly pushed back. Again, lacking confidence seems
aparent. My opinion of the XPsp2 fixes, "this should be
called XP Pro sp0 (initial release of OS)!

Why would you expect their website to logical? You obviously have used
their operating system(s) before, do you consider them to be logical?

--
hermes
DRM sux! Treacherous Computing kills our virtual civil liberties!
http://protectfreedom.tripod.com/index.html
http://www.cl.cam.ac.uk/~rja14/tcpa-faq.html
http://anti-dmca.org/
http://www.eff.org/IP/DMCA/unintended_consequences.php

Windows XP crashed.
I am the Blue Screen of Death.
No one hears your screams

 

[Malke]

Information about most KB searches are usually vague, if
you really want to understand a security patches actual
issue, get a shovel! After following several links, you
may find out. For example, I recently (i'm assuming that
there have been thousands of you tried same search) queried
KB [s/b dumb db] for the XP Pro Sp2 release date. Not to
get it yet, but to schedule myself time to review the
service packs fixes, paying attention to the compabitibilty
issues primarily. We're using legacy apps., intranet
clients w/ internet access are few enough to enable auto
updates, for our db on server. Short story long, I never
was able to find this info on
Microsoft.com/windows/xp/pro/sp2--Tree or within links
where any logical person would have posted this info. OR,
is that the problem itself, LOGIC?? I danderously 'assume'
that the shady game is a result of a lack in confidence on
behlf of MS. As you likely know, this XPsp2 release was
constantly pushed back. Again, lacking confidence seems
aparent. My opinion of the XPsp2 fixes, "this should be
called XP Pro sp0 (initial release of OS)!

Was there a question in there, or are you just venting? You do
understand that this is a newsgroup offering peer-to-peer help for
Windows XP and not Microsoft tech support, right?

Here's how to find out absolutely everything:

http://www.google.com

Malke