Page 2 of 2
Posted: Thu Oct 02, 2003 11:23 am
by johnsfine
The 1 byte version is in 15-2116, 15-2133, 8060, 8910 and 9960.
The 2 byte version is in 15-2103, 15-2104, 15-2107, rcu810, 4080 and 8011.
I think none of the other S3C80 models have PID 0111 at all. I have no clue about the non S3C80 models.
I would strongly prefer if you did NOT remove even useless protocols from the list in the RDF for remotes that have that protocol. Someone should put a varient name on the 0111 entries in the RDFs for models that have the 2 byte version. If you want to put some variant name like "obsolete" on them and then leave mention of that variant out of the protocols.ini file, you would get the same net result as removing 0111 from those rdfs.
Posted: Thu Oct 02, 2003 11:30 am
by gfb107
johnsfine wrote:I would strongly prefer if you did NOT remove even useless protocols from the list in the RDF for remotes that have that protocol. Someone should put a varient name on the 0111 entries in the RDFs for models that have the 2 byte version. If you want to put some variant name like "obsolete" on them and then leave mention of that variant out of the protocols.ini file, you would get the same net result as removing 0111 from those rdfs.
Fair enough.
Posted: Thu Oct 02, 2003 11:50 am
by gfb107
What about the URC-6131?
Posted: Thu Oct 02, 2003 12:26 pm
by johnsfine
gfb107 wrote:What about the URC-6131?
Oops!
It uses the 1 byte version.
Once again I THINK none of the OTHER S3C80 models have PID 0111, but I've just proven my unreliability in such matters.
Posted: Thu Oct 02, 2003 2:14 pm
by The Robman
johnsfine wrote:I would strongly prefer if you did NOT remove even useless protocols from the list in the RDF for remotes that have that protocol. Someone should put a varient name on the 0111 entries in the RDFs for models that have the 2 byte version. If you want to put some variant name like "obsolete" on them and then leave mention of that variant out of the protocols.ini file, you would get the same net result as removing 0111 from those rdfs.
I agree. My original suggestion to Mark for KM was to have two Tivo protocols:
1) Tivo - This would use the official $0111 protocol id, and would serve up a protocol upgrade for remotes that either don't have $0111 or have the 2-byte version.
2) Tivo 2-byte - This version would be exclusively for people with remotes that contain the 2-byte version of the $0111 protocol. While it would let you enter the functions using 1-byte OBCs or EFCs, it would generate the additional byte for you. (This would be the same as "Tivo Official" in the older versions of KM).
Mark didn't like this idea because converting the first option from being a "hacked" protocol to an "official" protocol would mean that the FAV/SCAN hack would no longer be supported.
My suggestion, if this was deemed an important issue, was to create a third option called "Tivo SCAN" which would be an exact copy of the old "Tivo Hacked", which lets you program functions to the FAV/SCAN button, when present on your remote.
Posted: Fri Oct 03, 2003 9:29 am
by mr_d_p_gumby
PID 0111 is also in the Atlas...
Posted: Sat Oct 04, 2003 12:24 pm
by gfb107
mr_d_p_gumby wrote:PID 0111 is also in the Atlas...
Would that be the 2-byte or 1-byte version?
Posted: Sat Oct 04, 2003 1:37 pm
by johnsfine
It's the new (1-byte) version.