SP2 for Australia WHEN ? its the 26th now and NO Sp2 in Windows Update ?

  • Thread starter Thread starter OCZ Guy
  • Start date Start date
O

OCZ Guy

(@@*(@* me off.

I waited for the right one yet they don't want me to have it ?

Thanks for any Help.

HELLO NURSE.
 
UMMM how long did they have testers testing this SP2 ?? that never
came up ?




The reason they haven't released it yet is due to security problems, plus a
bunch of bugs that people who downloaded the network install version have
discovered.

Like if you linger your mouse over an .avi file and windows tries to display
the file properties, the window freezes. Not with any other file type
though. Weird, no?

Just wait... the last thing you need are more bugs on your system; praise MS
for that :P

HELLO NURSE.
 
OzzieBloke said:
The reason they haven't released it yet is due to security problems,
plus a bunch of bugs that people who downloaded the network install
version have discovered.

HUH?!? I downloaded it a week ago and certainly haven't discovered "a bunch
of bugs". There is only one major bug and that concerns Prescott CPUs - and
there's a workaround for that

Like if you linger your mouse over an .avi file and windows tries to
display the file properties, the window freezes. Not with any other
file type though. Weird, no?

No, because it doesn't exist. Just because it happens on your system doesn't
make it a 'bug'. SP2, when installed on a properly maintained system
(Prescott issue aside) causes no problems whatsoever. The problems that do
exist are due to either third-party applications or PEBCAK errors.

Stop perpetuating nonsensical rumours.
 
Given that I do keep my system maintained, up to date with the appropriate
patches, don't install and deinstall programs willy-nilly (thus not piling
out the registry with leftover entries), and the *only* element that changed
on my system between my problem not existing and my problem currently
existing was the installation of SP2, I would have to say that it's an SP2
bug.

Granted, MS can't cater to every hardware/software combination out there.
But given that I'm not running any "cracked" programs, and the programs I do
run are all mainstream, I would assume that something so simple as a file
properties freeze trying to bring up the file properties of only one
particular file type is unlikely to be attributed to a file association
glitch with the program that executes it (given that it happens to be Media
Player).

People *are* finding bugs left, right, and center. It's not your call to
defend MS and say there is no problem, or accuse a user of not knowing how to
maintain a system. It *is* the right of the user to report bugs, as well as
read reputable online sources that have been in contact with MS techs who
have already admitted to there being not only bugs in the SP2 release, but
also security holes that still aren't being adequately addressed.

Please keep you "perspicacity" to yourself in future.

Ozzie.
 
(@@*(@* me off.

I waited for the right one yet they don't want me to have it ?

Thanks for any Help.

HELLO NURSE.

Don't panic! I see it in WindowsUpdate here in NZ.

Cheers,

Cliff
 
No, that's not true. It's release was staggered around the world to
reduce server load.

I see it here in NZ, approx 6:45pm on 28th.

Cheers,

Cliff
 
OzzieBloke said:
Given that I do keep my system maintained, up to date with the
appropriate patches, don't install and deinstall programs willy-nilly
(thus not piling out the registry with leftover entries), and the
*only* element that changed on my system between my problem not
existing and my problem currently existing was the installation of
SP2, I would have to say that it's an SP2 bug.

Granted, MS can't cater to every hardware/software combination out
there. But given that I'm not running any "cracked" programs, and the
programs I do run are all mainstream, I would assume that something
so simple as a file properties freeze trying to bring up the file
properties of only one particular file type is unlikely to be
attributed to a file association glitch with the program that
executes it (given that it happens to be Media Player).

People *are* finding bugs left, right, and center. It's not your
call to defend MS and say there is no problem, or accuse a user of
not knowing how to maintain a system. It *is* the right of the user
to report bugs, as well as read reputable online sources that have
been in contact with MS techs who have already admitted to there
being not only bugs in the SP2 release, but also security holes that
still aren't being adequately addressed.

Please keep you "perspicacity" to yourself in future.

Ozzie.

"Miss Perspicacia Tick" wrote:

And have you read the follow-ups to these "bugs" that are being found?! No
you have not. If you had you wouldn't have posted as you have. All of them
can be attributed to one of three things: -

1) Third party software for which the developer should issue an update.
2) A poorly-maintained system (riddled with spyware, viruses, etc)
3) PEBCAK errors.

So, like I said, there are NO BUGS (other than the Prescott issue) that can
be directly attributed to SP2. By that I mean SP2 installed on a clean
system with nothing other than Windows installed.

I beta tested SP2 extensively, and I stand by my earlier statements.
 
Back
Top