Ok, this is really pissing me off!

Vertigo1 · Post by **Vertigo1** » 2003-04-30 10:33pm

After installing 10 megs worth of updates from Symantec for Systemworks 2002, I can't play any DVDs on my computer!

PowerDVD bitches at me for having TV-out ability, and even MP8 complains that it can't play it because of copyright protection. I own the damn movie legitimately, and now I can't play it? FUCKERS!

This is the very reason I did a full re-install of XP! Anyone have a clue of getting around this?

Quick specs:

Duron 700 (not overclocked, and I have it watercooled so temps isn't even an issue)
Asus A7V (running 4-in-1 v4.38)
Visiontek Geforce 3 Ti200 64MB DDR running 43.45 dets.

Vertigo1 · Post by **Vertigo1** » 2003-04-30 10:36pm

Note: I tried disabling auto-protect, but that didn't do a damn thing. Also, I'm completely up-to-date as far as WindowsUpdate is concerned. (I only get the critical updates). My DVDs played fine after running WU so that has nothing to do with it either. I also tried re-installing PowerDVD.

Hamel · Post by **Hamel** » 2003-04-30 10:41pm

Is your region setting correct?

Vertigo1 · Post by **Vertigo1** » 2003-04-30 10:44pm

Hamel wrote:Is your region setting correct?

Yeah. All my DVDs are region 1, and its set to region 1. If I reboot into Win98 and run PowerDVD, it plays just fine. I know it has something to do with what Symantec released. I just don't know how to get around it.

Post by **Darth Wong** » 2003-04-30 10:49pm

Vertigo1 wrote:
Hamel wrote:Is your region setting correct?
Yeah. All my DVDs are region 1, and its set to region 1. If I reboot into Win98 and run PowerDVD, it plays just fine. I know it has something to do with what Symantec released. I just don't know how to get around it.

Why don't you just uninstall Symantec and lodge a bug report?

Vertigo1 · Post by **Vertigo1** » 2003-04-30 11:02pm

I'll give that a shot. However, knowing my luck it'll still stick around afterwards...

Vertigo1 · Post by **Vertigo1** » 2003-04-30 11:23pm

It still errors out! Argh! I'm starting to really loose my confidence in Symantec.....

Vertigo1 · Post by **Vertigo1** » 2003-05-01 10:31pm

Well, I've got good news and bad news.

The good news is, that I was able to fix the problem by rolling back to the 40.72 dets. The bad news is....I've fucked up Systemworks 2002 so bad that I'll have to do yet ANOTHER re-install anyways.

Its a damn good thing I don't have jack shit to backup this time.

Apparently the updates from Symantec and the dets past 40.72 fight. I did lodge a bug report like you said Mike, but the morons are dead set on it being a corrupted LiveUpdate download. (which wouldn't cause this)

Ohh well....I'll be sure to backup the WUTemp dir so I won't have to download 35MB of updates next time.

Einhander Sn0m4n · Post by **Einhander Sn0m4n** » 2003-05-01 10:46pm

Look for a Cdilla (can be spelled Cdilla, C-dilla, or c_dilla) folder or mentions of it in the Registry.

It's corporate name is Macrovision Safecast. Look for those words in your filesystem or Registry as well.

I think SpybotSD can kill this, as it's known spyware as well as being a DRM Trojan.

EDIT: And Boycott Symantec and install AVG!

Vertigo1 · Post by **Vertigo1** » 2003-05-01 11:03pm

The only CDilla I had on my system was the software "dongle" for 3D Studio MAX 5. (yes, I checked it to be sure it wasn't the spyware version)

This XP install is completely clean of spyware. Thats one of the first things I checked for after I installed SP1.

Einhander Sn0m4n · Post by **Einhander Sn0m4n** » 2003-05-01 11:07pm

Vertigo1 wrote:The only CDilla I had on my system was the software "dongle" for 3D Studio MAX 5. (yes, I checked it to be sure it wasn't the spyware version)

This XP install is completely clean of spyware. Thats one of the first things I checked for after I installed SP1.

Hmm I coulda sworn you were describing a C_Dilla infection...

Only thing I can recommend is uninstalling Systemworks and getting AVG.

Vertigo1 · Post by **Vertigo1** » 2003-05-01 11:15pm

Dude, read the whole thread. I *did* uninstall it and it still happened. The only thing that fixed it was rolling back to an earlier version of nVidia's dets.