Comments

rs170a wrote on 8/26/2004, 5:39 AM
The response from SonyEPM in this thread was:

There shouldn't be any problems with the release version of XP SP2 and current SF/Sony apps. We've been testing for quite a few months with various SP2 betas, so if your apps are current all should be good.
The only gotcha is, potentially, 3rd party drivers for your sound card, video display etc- those are beyond our control. As of this writing we aren't seeing any problems there either but there's always a chance so be aware of that... worst case you could do a rollback.
If we do find an app problem caused by the released version of XP SP2, we'll jump right on it- if you find something yourself we'd like to know about it.

Mike
wombat wrote on 8/26/2004, 4:51 PM
Seems OK so far - no obvious problems
Flack wrote on 8/27/2004, 11:23 AM
Yep no problems with mine just updated and installed it on two of my rigs...

Flack...
Jsnkc wrote on 8/27/2004, 12:12 PM
IT runs fine with Vegas, but there are a lot of other issues to watch out for...I just posted one problem I was having yesterday with websites.
Flack wrote on 8/27/2004, 12:14 PM
You should check the setup of the firewall...


Flack..
mhbstevens wrote on 8/27/2004, 6:55 PM
I can report no problems running Vegas 4e under XP2, which is good as we are going to wait another two years for Longhorn.

donp wrote on 8/27/2004, 7:18 PM
Ijut read an article from CNET that the SP2 for XP has a conflict with AMD 64 bit processors.
BillyBoy wrote on 8/27/2004, 8:29 PM
I downloaded SP2 last night. A giant 98MB file, which took about 15 minutes to download with my broadband connection. Took over 20 minutes for Windows to install it, because it makes all kinds of changes and replacements and "improvements" to Windows core files.

So far no problems with Vegas, or Microsoft Office, Photoshop, Flash, etc..
PeterWright wrote on 8/27/2004, 8:40 PM
Interesting - just received a circular email from the Vegas supplier here in Perth (who uses Premiere himself) saying that SP2 is not qualified for Premiere Pro or Avid, and using it will void their (the local supplier's) warranty.
kentwolf wrote on 8/27/2004, 9:15 PM
>>...SP2 is not qualified for Premiere Pro or Avid...

It would seem that the reverse would actually be true: Premiere Pro or Avid is not qualified for SP2.

It would seem that the OS-Owner (MS) would get to say what's qualified for what. MS holds all the cards, so to speak.

Sounds like your local supplier just doesn't want to have to troubleshoot people's PC's since warranty service makes no money, for the most part (but it keeps customers).

If "SP2" isn't qualified, will that be the case forever? If not, when will it change? If the policy changes for a release incarnation of SP2, which one? How will you know which SP2 incarnation is the one your supplier will "OK?"

Since the SP2 cannot forever void warranties (especially since I believe it is shipping on new PC's), you ought to ask him to clarify the policy. It's probably along the lines of "I want to see if everything is OK first." That's a lot different than SP2 not being "qualified."

...oh well...enough now... :)
efiebke wrote on 8/27/2004, 10:14 PM
Yesterday, I updated my older computer to SP2. I'm having problems with the Windows Firewall engaged and my two networked computers working well with each other. I THOUGHT I selected the correct options within the new Firewall so that the two computers can network with each other the way I had them before the upgrade. Sadly, it just ain't working. Don't know if it's the new firewall associated with the SP2 or if it's just me????

For now, my solution is to turn off the firewall feature. When I do this, all is fine.

But because of this, I'm reluctant to upgrade to XP SP2 for my new computer which has all of the audio/video programs with associated hardware. Maybe I'll upgrade later once I learn more how to control SP2.

Ted
apit34356 wrote on 8/28/2004, 12:27 AM
efiebke, SP2 firewall is the problem for most app programs. MS site has a large list of known programs that will not work with SP2. Check the MS knownledge about your lan, they address issue with a couple of different approaches.