JP1 Remotes

These RDF's are compliant with both IR V4.xx and RemoteMaster(RM) V0.9x or greater
NOTE: KM does not require RDF's
RDF's for RM and IR

Full set of RM Maps and Images
Due to significant activity with RDF's and Images I have also added a full set of RM Maps and Images.
NOTE: If you are using the above set of RDF's with RM you will need this full set.
All Maps and Images for RemoteMaster V.9x or greater

CHANGES:

• 1) Most RDF's updated to support alternate PID's in RM
  2) Some RDF's updated to add aliases
  3) Some RDF's updated to include support for IRtoWAV
  4) Some newer images added
  5) Updated Maps & Images to support changes in some RDF's
  6) ZIP files set up to create subdirectories (RDF & Images) under a root folder of JP1

You can selectively add the RDF's, Maps and Images you need however, if you choose to replace all, first remove and backup your old ones to eliminate conflicts with name changes

Nils_Ekberg wrote:Some RDF's updated to include support for IRtoWAV

The new RDF's for the URC-881x_801x_601x (6_80*.rdf) remotes contain the WAVUpgrade=Yes line, but these remotes don't have WAV support.

Oooops Mark, your right. I guess I just got carried away and don't know what I was thinking. I will fix it.

Fixed... I just reloaded the 1.17 since it was a minor fix and does not impact the functionality of the RDF's unless tries using the IRtoWAV for the URC-881x_801x_601x which obviously won't work anyway.

RDF's version 1.17 has been reloaded with some changes outlined in other threads related to IRtoWAV support, elimination of old Millennium RDF's and the elimination of old Replay RDF's

I just downloaded the Images/Maps zip, then extracted it into my "Images" folder, but Winzip created a JP1/Images folder under my images folder. Could you possibly re-create the zip without saving the full path info. Thanks.

Your wish is my command.....Done

Oooh, can you feel the POWER!!!

Remember power corrupts.......... 8)

Hey, I'm open to bribes!

I think you have this in reverse..you need to bribe us....beer usually works fine for me

Nils,

I've been thinking that it might be nice to have a version identifier included with the RDFs (and Images), other than just the name of the .ZIP file. This way IR and RM can display the version number on the About panel. I'm thinking something as simple as a text file called version.txt or version.dat. Whatever text is in this file would be the version.

Let me think about this a little Greg. I have a little bit of a problem with a version file since it is Dependant on me keeping them in sync which is probably not a big deal with one entry. It would however require the user to unzip the version file also or there would be nothing for RM or IR to look at. Maybe the message in the version then would be "Unknown" or something like that.

Been tied up with something else so have not had a chance to do much of anything here the last couple of weeks.

Nils,

I don't know about how you generate your ZIP files, but I use a .bat file and pass the version number to that .bat file, and it creates the .zip file using that version.

Here's a snippet of my .bat file: You could add the following as the first line of this .bat file: This would replace the contents of rdf\version.dat with whatever parameter you pass to the .bat file.

Nils' point is still valid. Having a seperate version file in the zip doesn't guarantee that the end user will keep things in sync.

For example, let's say that they download zip file version 1.17, then they download a few RDFs from somewhere else, but it turns out that these are old versions, IR would still display them as being 1.17 version RDFs because of the file.

It would be a better idea to have the version number in each RDF, but that would be a TON more work for Nils, so I'm not actually suggesting it.