View Single Post
  #5  
Old June 23rd 03, 04:04 AM
Jay Sottolano
external usenet poster
 
Posts: n/a
Default

Brad,
The ASUS card has the Philips chip, but I haven't upgraded the
drivers yet, past the ones that came with the ASUS card (30.71??). I'm
on a different machine right now, so I'd have to look. If the purpose
was to block copying out the back ports, I think you make several valid
points (I have a Ti200 as well in another machine). I'm curious as to
whether the Philips chip eliminates the problem... Thanks for the
explanation...

Jay S,

Brad wrote:

My understanding is it depends on the TV chip on your card. A few people
have tried various macrovision-defeating apps/techniques with success, which
means they may not have had this particular problem in the first place. Most
who have one of the offending chips simply cannot play DVDs without
reverting to the 40.72 drivers, as was the case with me and my Visiontek
GeForce3 Ti200, which has an old Brooktree BT868 chip on it. In some cases
also, nVidia's measures are ineffective (ie, PowerDVD won't work, but WinDVD
will). If you have a newer TV-chip, possibly Phillips, you may have no
problem whatsoever if it supports MV protection.
Again, I don't know why they didn't just disable the TV-out during DVD
playback, instead of disabling DVD playback and ****ing everybody off. I
take it all future cards will be made with MV-conforming TV-out chips. Come
to think of it, my old ATI TV Wonder card used a BT868 chip, yet it had
Macrovision protection in the drivers (see, it can be done).
Its so irritating though, trying to copy a DVD thru TV-out is such a cheap
ritarded Mickey Mouse method, plus its just plain EASIER to rip a DVD even
with a bargain-basement DVD-ROM if you really wanted it that bad. You can't
stop the real criminals from copying them with bad drivers, so why ****
everybody else off? I can't do anything about the BT868 chip on my card, nor
did I even ask for it, and DVD playback/acceleration is one of the main
selling features of a decent graphics card, and now they're trying to take
that away from me? They want to disable functionality on a product I already
own, but I don't see nVidia or Visiontek or the assholes behind Macrovision
lining up to give me a prorated refund because my card now does less than
advertised.
For the time being I can deal with 40.72 drivers, since they're DX90, pretty
fast and all that, but what about a year from now if I'm still not ready to
upgrade and I'm stuck with outdated drivers? What then? This is total BS.
Brad
"Jay Sottolano" wrote in message
...
Brad,
So, for example, I have XP Pro, with Power DVD, and a new ASUS GF4 4200
8x AGP card. In this configuration, if I update to 43.45 for example, I
will/won't be able to watch a commercial DVD on my computer? I'm not looking
to send the signal out to TV or second monitor... Thanks...

Jay S.

Brad wrote:

It does not make DVDs unplayable, it makes them unplayable if your card's
TV-encoder chip is old (look most Brooktree/Conexant chips) and doesn't
support macrovision. Frankly I don't know why they didn't just make the
driver disable the damn TV-out when you play a DVD.


"Pepys" wrote in message
...

XP Pro, P4 2.4, Pioneer 106 s DVD player, GeForce 3 500 Ti, Power DVD 5

blah

blah blah


WTF is nVidia up to with their latest drivers?

There is apparently some sort of Macrovision detection function built in

to

the latest geforce drivers which disallows any DVD with copyright to be
played through a computer.

****, **** and double ****.

The only way I watch DVDs is through the computer on a flash new 19" TFT
screen, and now that has been denied me by some ****** deciding to
arbitrarily stop the watching of DVDs on computers.

If they think this is going to stop piracy - think again.

The only advice I have received so far to overcome this annoying problem,

is

to rip the DVD to my hard drive, hack out the macrovision element of the
show and take it from there.

If anyone knows of a fix for this problem I would be greatful.



Sam

PS Tried the old Remote Selector thingie and it simply did not correct the
problem.