JP1 Remotes

I haven't tried downloading the new stuff yet, but I have found this thread very depressing. Especially:

ElizabethD wrote:Vicky, you must be using IE. Stop. Forever stop. Or set it up to block everything. Best, change the browser to Opera or SeaMonkey.

Surely we haven't set up something that doesn't work with IE? IE may be a joke to Liz and others, but it is bread and butter to most ordinary guys, including me. I have neither a desire, nor any intention, of changing to anything else.

To give everyone a really big laugh, I actually LIKE Microsoft. I go back to the days of 8-bit processors and CP/M, where every manufacturer used a different disk format, and if you could somehow manage to read a disk of one machine on another, the programs on it wouldn't work as they had to be re-compiled with different OS settings for each machine. I feel that if it wasn't for the virtual monopoly of Microsoft then computers might never have left that nightmare scenario.
_________________
Graham

I finally see what is going on. Since I have a SourceForge account, I don't have to suffer through the advertisement to get to the download.

I moved the zip files over here.

xnappo

Thanks Chris, it really simplifies things to have it actually download the zip file when you click download.

- Merged RDFs from development area
I missed the fact that the 11781178 10820N wasn't in the beta zip. Since I'm nearly done with the extender, it would be nice if the base RDF was in the next zip file.


- Protocols sections updated to match PM
This should fix a lot of random errors that came up when using RM to create an upgrade.

- SetupCodes updated
This should help people avoid the pitfalls of uploading a bad setupcode and having the remote reset, or worse not reset, when an error was encountered. I ran into this error all the time.


- Map and Image filenames fixed for case-sensitives OSs
This should make life for Linux users much better. I remember what a pain that was in Windows when the file names were misspelled. RM was torturous. Nils had fixed that for us Windows users, but I guess that was still a problem in case sensitve operating systems.

- DevComb entries fixed/added to match KM
Good, did you PM unclemiltie about his extenders having bad information there.

- Added [Extender] section to all extenders, and added the OEMSignature entry
What exactly does this do for us?


Now we need to get Rob to fix the links in the MAIN section, if he hasn't already this should be good to go!

vickyg2003 wrote: - Merged RDFs from development area
I missed the fact that the 11781178 10820N wasn't in the beta zip. Since I'm nearly done with the extender, it would be nice if the base RDF was in the next zip file.

Sure - I will get that added - can you point me to the location so I make sure to get the right one?

vickyg2003 wrote: - DevComb entries fixed/added to match KM
Good, did you PM unclemiltie about his extenders having bad information there.

No - but I will. Do you mean whether to remove the RDFs that are currently in there? I don't want to remove any that are currently there - but I will update them if needed. I will not add any more of his without his permission.

vickyg2003 wrote: - Added [Extender] section to all extenders, and added the OEMSignature entry
What exactly does this do for us?

That allowed your tool to do all of the other updates on the extender RDFs.

xnappo

vickyg2003 wrote:- Added [Extender] section to all extenders, and added the OEMSignature entry
What exactly does this do for us?

IR.exe 8.02, and later, does not show extender RDFs in a choice list when there is a non-extender RDF that matches the same signature (unless you turn on the Advanced option "Always Show Extenders"). But its detection of extender RDFs is based on looking for features such as "ext" in the name, and is not perfect.

This was put in when WagonMaster was starting to update the RDF library. It was agreed then that putting an [Extender] section, even if empty, into the RDFs of extenders would provide a completely reliable way to identify them. This is one of the criteria used by v8.02 and so no change to IR.exe is needed to take advantage ot this improvement to the RDFs.
______________
Graham

xnappo wrote:

vickyg2003 wrote: - Merged RDFs from development area
I missed the fact that the 11781178 10820N wasn't in the beta zip. Since I'm nearly done with the extender, it would be nice if the base RDF was in the next zip file.

Sure - I will get that added - can you point me to the location so I make sure to get the right one?

https://www.hifi-remote.com/forums/dload ... le_id=7425

vickyg2003 wrote: - DevComb entries fixed/added to match KM
Good, did you PM unclemiltie about his extenders having bad information there.

No - but I will. Do you mean whether to remove the RDFs that are currently in there? I don't want to remove any that are currently there - but I will update them if needed. I will not add any more of his without his permission.

No, I didn't want you to remove them, but the base remote of the Atlas is one of the remotes that had bad information. So he needs to correct the RDF's for his extenders that are not in the main zip.

mathdon wrote:

vickyg2003 wrote: - Added [Extender] section to all extenders, and added the OEMSignature entry
What exactly does this do for us?

It was agreed then that putting an [Extender] section, even if empty, into the RDFs of extenders would provide a completely reliable way to identify them. This is one of the criteria used by v8.02 and so no change to IR.exe is needed to take advantage ot this improvement to the RDFs.

Thanks Graham

I have updated the links in the "Main" folder so that when you use the DOWNLOAD button, you will actually download xnappo's file (ie, the one in the RDFs folder).

I have removed the version number from the links in the Main folder as these could get out of date. To see the version number, you should either download the file (the version number is in the file name) or you can use the "click here" links which will take you to the files in the RDF folder where the version number is present.

Thanks Rob.

xnappo

I will stick with 1.28........

tennessee titan wrote:I will stick with 1.28........

I don't suppose that would hurt if you are not using RemoteMaster, but if you are using remotemaster you're just begging for problems that are difficult to diagnose. Once the rest of us move on to 1.30, it will be even more difficult to diagnose those pesky problems that come with the protocol variant information being out of date.

Why would you want RDF's riddled with mistakes?

tennessee titan wrote:I will stick with 1.28........

Please remind us of this when you post about problems.

tennessee titan wrote:I will stick with 1.28........

Gotta ask ... why?

Reading your post here:
https://www.hifi-remote.com/forums/viewt ... 7320#p87320

Every one of your remotes has errors in the RDF that have been corrected.

xnappo

Thank you for your good work. I will try not to post problems and annoy Rob....

xnappo wrote:Hello all,

I have released a new version of the RDF, maps, and images files.
....
Please let me know if you have any issues, or what you would like to see in the next release!

Hi, the new release looks great. Will it be possible to include this with the next release please?
https://www.hifi-remote.com/forums/dload ... le_id=8215
Thanks.

rem wrote: Hi, the new release looks great. Will it be possible to include this with the next release please?
https://www.hifi-remote.com/forums/dload ... le_id=8215
Thanks.

Will do.

Thanks,
xnappo