or Connect
AVS › AVS Forum › Gaming & Content Streaming › ReplayTV & Showstopper PVRs › New software clobbers CA in modified 55xx units
New Posts  All Forums:Forum Nav:

New software clobbers CA in modified 55xx units - Page 3  

post #61 of 655
Quote:
Originally posted by Jeff D
I'm all for sharing, but in this case it had a negative result. Next time no one talks. ;)
It's really premature to draw that conclusion. First of all, I dont' think it's even been definitively proven that the new software disables the work-around for CA / IVS.... I won't be convinced until a seasoned Replay veteran gets his / her hands on the software and verifies it.

I'm skeptical of any claims that DNNA actually gives a cr@p about this stuff, frankly. They have other things to worry about -- there is no litigation on this matter, nor any settlements with which to comply that would motivate them to make this change.

And if they did care about the miniscule portion of their 55xx users who took advantage of this, it would be much easier and effective to send out a pause ad or some other notice to these users. This would also cover their legal butt alot more effectively than pushing the new software (which utimately will also be cracked anyway).

Don't let's get parnoid. Even if the new software forces us to change our approach, I'm willing to bet the price of a 5040 that it had very little to do with the hacks discussed here, and was instead an inadvertent change.
post #62 of 655
Quote:
Originally posted by DarkScreen

...
BTW, although I've been distracted with wirns and worms, I've not noticed any functional differences with the new RTV software.

I'm curious to see if the CA and IVS features go away on 50xx units when they are infiltrated with the new software. This could make things really difficult.
...
Closed Captioning is improved.

b144 does not affect the availability of CA and IVS on 50xx, meaning they
are still available.
post #63 of 655
Thread Starter 
Quote:
b144 does not affect the availability of CA and IVS on 50xx
This is good news!

Keep in mind that my failure (and others?) to get CA and IVS working on a 55xx could very well be pilot error. See post 56 for further details.
post #64 of 655
I've got a 5504 coming my way that I had intended on using the Wirns method on. Needless to say, I'm very interested in this topic.
post #65 of 655
Quote:
Originally posted by Jeff D
The fact that it was open shouldn't have been a liability if the users do stuff after the sale it's not really the fault of the developer. But... that's open to argument I guess. I would think it's up to DNNA and folks running around in suits.

as for the suggested method above about updates, I can't report any success. I've tried a few things and can seem to get the registry to take my changes. I'm asking for help from the higher powers... =)

If someone can sue a firearms manufacturer because they built a product and somebody misused it and killed someone else and have the mfgr be found liable or a family member can sue a automobile manufacturer because their now injured/deceased relative used one of their vehicles in a manner inconstant with that under which it was sold and again, the mfgr is found liable == then I don't see how this can be any different - although I do agree with you that, ultimately, it's up to a bunch of self-serving a-holes that are commonly known as attorneys.
post #66 of 655
I'm in NJ and have a 5504. I confirm I've lost my IVS and CA (that I enabled via WiRNS originally).


My replay must have just gotten the new sofware. I'm very sad.

EDIT: I forgot to mention, that I tried using WiRNS to put it back on and NOTHING. It did not come back.

My IVS and CA was on there for about 2 months (as soon as I got the Replay, i did the wirns trick to turn it on).
post #67 of 655
Thread Starter 
Quote:
I forgot to mention, that I tried using WiRNS to put it back on and NOTHING. It did not come back.
Greg, thanks for further validating that this is a genuine problem with the new software. And one that the current version of wirns does not resolve.

Guess we'll have to reduce our quality of life a little and put a little extra wear on the right arrow key on the remote.... until the software wizards figure things out. I'm confident that they will. :)
post #68 of 655
Quote:
Originally posted by rm -rf *.*
If someone can sue a firearms manufacturer because they built a product and somebody misused it and killed someone else and have the mfgr be found liable or a family member can sue a automobile manufacturer because their now injured/deceased relative used one of their vehicles in a manner inconstant with that under which it was sold and again, the mfgr is found liable == then I don't see how this can be any different - although I do agree with you that, ultimately, it's up to a bunch of self-serving a-holes that are commonly known as attorneys.
Thank the lord that most states have outlawed such suits. If YOU misuses a product, the manufacturer of that product can't be liable. Imagine if you could sue BIC lighter company because it set fire to your house when you tried to burn off a pan full of gasoline in your garage?
post #69 of 655
Quote:
Originally posted by rm -rf *.*
although I do agree with you that, ultimately, it's up to a bunch of self-serving a-holes that are commonly known as attorneys.
Niiiice . . .
post #70 of 655
So is it official... there is no current way around this? Or is it strictly on the QT... the hush hush... etc.? :)

My theory is that NBC paid them to remove it during the Olympics. There's a commercial every 3 minutes, then 3 minutes of someone's life story, and then 30 seconds of event time... rinse and repeat.
post #71 of 655
Quote:
Originally posted by rm -rf *.* ultimately, it's up to a bunch of self-serving a-holes that are commonly known as attorneys.
oh snap
post #72 of 655
Quote:
Originally posted by j.m.
However, try setting "SysConfig/Tweak/DisableSoftwareDownload" to "TRUE" as it ostensibly should work.
Does this look about right?
regedit setval SysConfig/Tweak/DisableSoftwareDownload 1

I feel like I'm missing a keyname in there. Other commands look like:
regedit setval <Path> <Keyname> <Boolean> and this one is just
regedit setval <Path> <Boolean>.

Clarification before full roll-out would be most appreciated. Thanks.

EDIT: I should mention that I've been through the Molehill site and I don't see mention of an appropriate keyname.
post #73 of 655
regedit setstr SysConfig/Tweak DisableSoftwareDownload "TRUE"

This may or may not work. Use at your own risk! YMMV.
post #74 of 655
It's a value not a string and you want it set to 1 to disable the check.

Conspiracy was right, at least that's worked for me and I've been able to disable the pending update with this method on my 5k box.

Software/Apps/Setup AllowSysUpdate seems to have no affect on anything.
post #75 of 655
So Jeff, I take it that would be:
regedit setval SysConfig/Tweak/DisableSoftwareDownload 1
NOT
regedit setval SysConfig/Tweak DisableSoftwareDownload 1

Twiki seems to indicate the first one is the right one.
post #76 of 655
Quote:
Originally posted by moyekj
So Jeff, I take it that would be:
regedit setval SysConfig/Tweak/DisableSoftwareDownload 1
NOT
regedit setval SysConfig/Tweak DisableSoftwareDownload 1

Twiki seems to indicate the first one is the right one.
How does one do this process? I have a 5040 basically virgin hard disk here, and a 5504 that's about to land via the Fed X guy....

John
post #77 of 655
Quote:
Originally posted by johnmagee4
So is it official... there is no current way around this? Or is it strictly on the QT... the hush hush... etc.? :)

My theory is that NBC paid them to remove it during the Olympics. There's a commercial every 3 minutes, then 3 minutes of someone's life story, and then 30 seconds of event time... rinse and repeat.
So if they could sneak this past the experts in this forum any chance they might try something similiar and disable dva streaming.

That would be pretty stupid, but I've seen a lot of stupid stuff happending lately.

Question: I would think if you droped an image on the 5504 it would restore ca until the next software push.
post #78 of 655
Quote:
Originally posted by Jeff D
I've been able to disable the pending update with this method on my 5k box.
Allow me to play devil's advocate here for a minute: it appears that DNNA is now checking the serial number at net connect time and disabling CA and IVS on 55XX machines if those features are enabled. I would guess there's also some sort of software version check at net connect time as well, so their server knows whether to push a software version to a given machine or not. IIRC, there's some language in the user agreement that the software cannot be altered or reverse engineered. So what's to stop DNNA from no longer providing service to a machine that has been altered to not accept a software update?
post #79 of 655
First pure speculation, then more speculation. If the WiRNS trick isn't turning CA back on even for a short period of time, then I suspect that the software is no longer checking the registry value to determine if CA should be on or not. I would imagine that they check the serial number instead. You can't fiddle with the serial number (at least not in an easy way--anything is possible I suppose) so this would make the CA issue for 55XX machines set in stone.

Correct me if I am wrong, but isn't WiRNS already able to filter communications between ReplayTV and mothership? Couldn't WiRNS simply tell the mothership that you already have the latest software so it doesn't send it down the pipe? In this way, the DNNA server wouldn't know that the machine wasn't running the latest software. No modification issue to worry about because as far as they are concerned, you are up-to-date.

I think odds of losing DVArchive capability are remote at best. First of all, there has never been a hint of legal issues with the in-home video sharing which is what DVArchive is taking advantage of. Second, DVArchive has to be considered a selling point by DNNA. They aren't likely to just up and decide to abandon a strong feature that costs DNNA nothing to maintain and improve.

And that's my gems for the day ;-)

Richard
post #80 of 655
Quote:
Originally posted by richierich
First pure speculation, then more speculation. If the WiRNS trick isn't turning CA back on even for a short period of time, then I suspect that the software is no longer checking the registry value to determine if CA should be on or not. I would imagine that they check the serial number instead. You can't fiddle with the serial number (at least not in an easy way--anything is possible I suppose) so this would make the CA issue for 55XX machines set in stone.

Correct me if I am wrong, but isn't WiRNS already able to filter communications between ReplayTV and mothership? Couldn't WiRNS simply tell the mothership that you already have the latest software so it doesn't send it down the pipe? In this way, the DNNA server wouldn't know that the machine wasn't running the latest software. No modification issue to worry about because as far as they are concerned, you are up-to-date.

I think odds of losing DVArchive capability are remote at best. First of all, there has never been a hint of legal issues with the in-home video sharing which is what DVArchive is taking advantage of. Second, DVArchive has to be considered a selling point by DNNA. They aren't likely to just up and decide to abandon a strong feature that costs DNNA nothing to maintain and improve.

And that's my gems for the day ;-)

Richard
I think the vast majority of replaytv users do not use dva. And I hope your right but it seems to me all they would need to do is change the guideparser and thats all she wrote.

On the other hand, tivo is starting to offer similar features (and Ivs) so they could potentially harm themselves.

I don't care too much about ca but I'd hate to lose dva streaming. The impact for me is I would probably go to windows mce before I considered Tivo.
post #81 of 655
Thread Starter 
Richierich said:
Quote:
Couldn't WiRNS simply tell the mothership that you already have the latest software
Richierich has some good points. Sounds like Conspiracy (message #72) and JeffD (#74) have already successfully tried the "leave me alone, my software's ok" tactic.

This may be a somewhat fragile stopgap solution. Here's why:

Through no evil intent of DNNA, it's possible that they may have made changes to this latest version of the software (or future ones) that will handle mothership guide and other information transfers, protocols, and processing differently. A legitimate reason for this would be to make their guide database more compatible with their new/future line of products or maybe just to add features or improve the service.

If the mothership starts sending out this newly structured data and they get confirmation from an RTV that it's software is up-to-date (and therefore compatible), then there could be serious data corruption issues. Analogous to saying, "Sure. Go ahead. My engine's been modified. Fill 'er up with diesel."

Under this speculative scenario, it may be more likely that the DNNA server actually reads the software version from the RTV before sending out the new style of data. In this case, their server might try to force a software update (even if DisableSoftwareDownload 1 set the registry to report that it's already up-to-date), not initiate the data transfer (so why is the schedule on my RTV not updating?), or display an error message. I'm actually a little surprised that they don't already read the actual software version in the unit (vs looking at the registry) to determine if an update is required.

Progress thru paranoia!
post #82 of 655
Quote:
Originally posted by Jeff D
It's a value not a string and you want it set to 1 to disable the check.
Okay, I had just guessed that it was a TRUE/FALSE string based on some of the other regedit entries. When an entry doesn't already exist in the registry by default, it is hard to tell (without trying it) whether it should be created as a 0/1 value or T/F string. ReplayTV uses both in the registry, seemingly without rhyme or reason. Doesn't make a lot of sense if you ask me, but that's the way it is.
post #83 of 655
Quote:
Originally posted by moyekj
So Jeff, I take it that would be:
regedit setval SysConfig/Tweak/DisableSoftwareDownload 1
NOT
regedit setval SysConfig/Tweak DisableSoftwareDownload 1

Twiki seems to indicate the first one is the right one.
No,
regedit setval SysConfig/Tweak DisableSoftwareDownload 1
is the correct format. See my previous post as to why it takes a wild guess sometimes to determine whether the entry requires setval 0/1 or setstr TRUE/FALSE.

From the regedit usage info:
Code:
Usage: regedit show    "keyname"
      regedit showall "keyname"
      regedit create  "keyname"
      regedit delete  "keyname" [valuename]
      regedit setstr  "keyname" "valuename" "string"
      regedit setval  "keyname" "valuename" value
      regedit save    "keyname" "filename"
      regedit load    "keyname" "filename"
      regedit init
      regedit flush
post #84 of 655
Quote:
Originally posted by richierich
Correct me if I am wrong, but isn't WiRNS already able to filter communications between ReplayTV and mothership? Couldn't WiRNS simply tell the mothership that you already have the latest software so it doesn't send it down the pipe? In this way, the DNNA server wouldn't know that the machine wasn't running the latest software. No modification issue to worry about because as far as they are concerned, you are up-to-date.
There was a NoSoftwareUpdate.dll plugin for WiRNS 0.7, but I do not believe that kjac has updated it for 1.x yet.
post #85 of 655
Quote:
Originally posted by DarkScreen
Through no evil intent of DNNA, it's possible that they may have made changes to this latest version of the software (or future ones) that will handle mothership guide and other information transfers, protocols, and processing differently. A legitimate reason for this would be to make their guide database more compatible with their new/future line of products or maybe just to add features or improve the service.

If the mothership starts sending out this newly structured data and they get confirmation from an RTV that it's software is up-to-date (and therefore compatible), then there could be serious data corruption issues. Analogous to saying, "Sure. Go ahead. My engine's been modified. Fill 'er up with diesel."

Under this speculative scenario, it may be more likely that the DNNA server actually reads the software version from the RTV before sending out the new style of data. In this case, their server might try to force a software update (even if DisableSoftwareDownload 1 set the registry to report that it's already up-to-date), not initiate the data transfer (so why is the schedule on my RTV not updating?), or display an error message. I'm actually a little surprised that they don't already read the actual software version in the unit (vs looking at the registry) to determine if an update is required.

Progress thru paranoia!
While DNNA could do this...it is unlikely that this is happening currently....if they did, it would likely be a bigger software release than just a new 5.1 version for 5000 & 5500 owners.

Plus there are those people that want software updates, but for whatever reason...their box won't update. I had a box that had trouble taking updates....found out later when I was trying to upgrade it...that there were disk errors in the system partition (don't know about the rest...wasn't any point in trying to preserve the MPEG partition...)

Now hopefully, it'll update...I want the CC fix.

Strange that I didn't encounter disk errors on the other boxes, each came from a different online site. The one with problems...I picked up from Radio Shack. I'm sure how I bought it doesn't have anything to do with it though :D

The Dreamer.

Though they did make changes in 5.0/5.1 that weren't compatible with older software versions on 5000's....but the 5.0 ReplayGuide could cope with 4.5 units.
post #86 of 655
Anyone who has a Bld 143 image has the Holy Grail for 55xx owners, at least for the forseeable future.
post #87 of 655
Quote:
Originally posted by adone36
Anyone who has a Bld 143 image has the Holy Grail for 55xx owners, at least for the forseeable future.
how? why? more data please.
post #88 of 655
Tony is onto something. This has been my thinking too.

As for what dreamer said about the version numbering I think this is pretty true too. I suspect that the replay software is doing what it always has. The difference is on the server side as such theres no need to change any replay software and not a larger change.


moyekj, j.m. gave you the info. The way I look at it is...

regedit cmd grouping tag value
where cmd, grouping, tag and value are alll seperated by a space. Grouping is to tell regedit where to place the tag in the files.


At the current moment I have one box that has gone from build 19 (140) to 144 all my other boxes are still at the old software. I've been disconnecting the ethernet cables until I find a better solution. =)
post #89 of 655
Quote:
Originally posted by Bigjohns
how? why? more data please.
Since we have reports on 143 and 144 here and on Planet Replay, it looks like the only difference in 144 is the 55xx whammy.
post #90 of 655
Quote:
Originally posted by Jeff D
At the current moment I have one box that has gone from build 19 (140) to 144 all my other boxes are still at the old software. I've been disconnecting the ethernet cables until I find a better solution. =)
Now you have me confused... maybe I just haven't got enough sleep lately. I thought you had verified that enabling DisableSoftwareDownload would prevent a software update? Or is the problem that the setting is not sticky and is reset by the mothership (which doesn't make much sense as it makes the setting useless)?
New Posts  All Forums:Forum Nav:
  Return Home
  Back to Forum: ReplayTV & Showstopper PVRs
This thread is locked  
AVS › AVS Forum › Gaming & Content Streaming › ReplayTV & Showstopper PVRs › New software clobbers CA in modified 55xx units