2008-09-08, 15:29 | Link #3 | |
Thinking outside the box
Graphic Designer
Join Date: May 2007
Location: The Netherlands
Age: 37
|
Quote:
And i agree with martino about using FF or Opera
__________________
|
|
2008-09-10, 17:55 | Link #9 |
Senior Member
Join Date: May 2006
Location: California
|
If that was in response to me, you took my reply out of context. I wasn't talking about SP3, I was talking about Internet Explorer 8. Service Pack 3 isn't the problem, Internet Explorer 8 beta is the problem.
__________________
|
2008-09-13, 04:44 | Link #10 | |
All Hail Lelouch!
Author
Join Date: May 2008
Location: In His Majesties Service.
Age: 40
|
Quote:
Theirs 4 types of beta's IMO: 1.The "released to the public to to iron out the last few small glitches" kind. 2.The "will cause generally odd behaviour for some users" kind. 3.The "cause complete and utter chaos no matter what hardware or OS you use" kind. 4.The "why the hell did MS release this piece of bug ridden crap in the first place?" kind. |
|
2008-09-15, 09:48 | Link #12 |
Tech Bloke
|
I think the main issue I've heard about with XPSP3 and IE is that if you install SP3 you cannot uninstall whatever version of IE you have installed at the time. So for example if you have IE8 Beta on, you won't be able to uninstall it, which will cause problems when the full version comes out.
__________________
|
2008-09-22, 03:54 | Link #14 |
I have arrived on time!
Join Date: Dec 2006
Location: Austalia
|
Like everyone else suggested, use a different browser, IE is horrible. The most popular choices are FireFox, Opera and Safari, all three have similar options and functions so why not try them all and keep the one you like?
__________________
|
2008-10-04, 00:07 | Link #17 |
Senior Member
Join Date: May 2006
Location: California
|
The current issue is you won't be able to uninstall Service Pack 3 if and only if you install the Internet Explorer 8 beta.
The only other major problem with SP3 I have heard of is the issue with AMD OEM built PCs where installing SP3 really messed them up because the OEM custom image was loading Intel cpu drivers after the update. This is in no way, shape, or form Microsoft's fault though.
__________________
|
|
|