Page 2 of 2
Posted: Sun Jan 02, 2005 10:42 am
by Mark Pierson
I fixed your link above. Take a look at the
posting links message to see how links to Yahoo have to be done.
Posted: Sun Jan 02, 2005 10:50 am
by mr_d_p_gumby
That's not a valid fix for the RDF, though it probably allowed you to get your upgrade to match KM in this one case.
Code: Select all
[DeviceTypes]
TV = 0
VCR/DVD = 1
Cable = 2
CD/Audio = 3
AUX = 4
This will cause other problems, as you've told it to use a fourth keymap for an AUX device type, neither of which exist in the remote. The AUX device uses the same keymap and device type as the VCR device in the Atlas. I'll try to look at this later if I have time available.
Posted: Sun Jan 02, 2005 11:45 am
by mr_d_p_gumby
The correct fix for this problem is to change only the [DeviceTypes] section as follows:
Code: Select all
[DeviceTypes]
TV = 0
VCR/DVD = 1
Cable = 2
CD/Audio = 3
VCR/DVD = 1,1
I've checked this in both RM & IR, and it will work properly with this change.
Do
NOT add an AUX entry to the [DeviceTypeAliases] section as you did in your "fixed" version. The above change is the only one you should make.
Some time back (
in this message), another user reported a problem with the checksum range. I haven't had time to test for this problem, but you might also have to change the [Checksums] section if you encounter the same problem:
The problem that user tonymorehen reported with the [FixedData] at $017 has not been mentioned by any other user, so I don't know if his case was unique or not. I would not change the fixed data yet, as it will require some time & experimentation to track down what's going on there.
P.S. Nils, this will need to be done for the next release of RDFs... 