The day the HV-20 came out, there was a person on the dvinfo bb who completely trashed the camera.....some mechanical problem or such.....turned out to be complete BS. The guy was out cause problems.

I'm skeptical anytime a highly negative article, bb post, etc. surfaces on or about the launch of a product. MOST corporations have learned from these previous launches and vett their products rather well.

A lot of mischief makers out there.

from what I understand the original release had an issue. it was fixed in less then a day or so. i haven't had any issues with it. first major update I don't think I've ever had issues with.

Good, then maybe I'll take this leap of faith now.

There is some upside potential if it works OK (the roll-up of so many old patches may actually create a cleaner XP on an old system that's been very active).

I installed SP3 about 3 weeks ago, with no problems, except on one pc that had a USB external hub that lost the mouse ( not on the hub) but was able restore the mouse by re-arranging the USB. Normally I wait a little longer till some old friends at IBM give its a thumbs up, but with IE and player removed, ---- ;-)

Losing an USB mouse is also quite possible under XP Sp2 with all the last updates :-)
Unplug and plug into another USB-slot also improves the problem there without restart.

There is some upside potential if it works OK (the roll-up of so many old patches may actually create a cleaner XP on an old system that's been very active).

it also has new updates that aren't released seperatly. :/

I installed XP SP3 and I died.

...and went to heaven?

:O)

Installed on 2 systems at home ,XP Pro, XP Home, no problems at all...It will probably be blamed on Vista at some point, It gets blamed for everything else!!!!! 9 out of 10 problems are user related, they tweek, overclock, or just downright FUBAR their installs and then blame everyone else for their problems....

Here's Ballmer's take on the XP SP3 problems (that were deemed to be "mostly OEMs' fault"):



:O)

Here's Ballmer's take on the XP SP3 problems (that were deemed to be "mostly OEMs' fault"):
==========
Welcome to America

John

wait... isn't MS the OEM of SP3?

From http://www.infoworld.com/article/08/05/12/Microsoft-faults-OEMs-for-some-XP-SP3-endless-reboots_1.html?source=NLC-DAILY&cgd=2008-05-12InfoWorld[/link]

Microsoft blames computer makers for some of the problems users have encountered after updating to Windows XP Service Pack 3 (SP3), according to a company support document.

The document also showed that the "endless reboot" problem some users have reported after installing XP SP3 was neither unanticipated or new; Microsoft updated the document the same day it released the service pack, and indicated that the same thing happened nearly four years ago when it rolled out Windows XP SP2.

Knowledge Base document 888372, last updated May 6, spelled out an error message that stops a PC's boot process -- and, depending on the machine's settings, may make it repeatedly reboot -- after installing SP3. The fault, said the Microsoft document, is in the Windows XP image originally installed on the PC by the computer manufacturer, or OEM.

"The problem may occur if the original Windows XP Service Pack 1 (SP1) Sysprep image is created on an Intel-processor-based computer and if the Sysprep image is then deployed on a non-Intel-processor-based computer," said Microsoft.

"Under this configuration, after the computer is upgraded to Windows XP SP2 or SP3, the Intel processor driver (Intelppm.sys) may try to load because an orphaned registry key remains from the original Sysprep image," the document continued. "This issue may also occur if the original Windows XP SP2 or Windows XP SP3 Sysprep image is created on an Intel-processor-based computer and if it is then deployed onto a non-Intel-processor-based computer. Again, the Intel processor driver (Intelppm.sys) may try to load because an orphaned registry key remains from the original Sysprep image."

Installed XP SP3 into 3 computers, one Intel and two AMD and there were no problems.
JJK

Unless you are doing a clean install, I think you still need to manually clean the registry up if you are trying to optimize your computers performance. Just installing SP3 still leaves you with a registry full of junk.

I don't want the new version of media player for some compatability and DRM issues or I would install SP3. There is no way to roll back to older MS application versions once you install SP3 (including IE and a few other apps).

I like to see what Im getting before I get it too.

"There is no way to roll back to older MS application versions once you install SP3 (including IE and a few other apps)."

to try and be a little more clear - the order does matter. For instance, if you have IE8 in SP2, and then install SP3 - you will not be able to uninstall IE8. But if you uninstall IE8 in SP2 first, then install SP3, then IE8 - you can uninstall IE8 in the future.
The behaviour is well documented in the overview - very much worth reading before jumping in.

I think SP3 broke my system environment variables. I went to use "inconfig" in command two days ago & it would always say the file didn't exist. I check the environment variables & they had the shortcut for the system root for the system folder but it wouldn't work. I had to manually add my windows, system, sys32, etc. folders for DOS commands to work again.