I've built and released RemoteMaster v0.96
Changes for v0.96
- Fix Device Combiner support. Requires RDFs version 1.16 or later.
Links:
RemoteMaster.v0.96.zip
Release Notes and Change Log (also included in the ZIP file)
Installation Instructions (also in the Readme.html included in the ZIP file)
The RemoteMaster project home page.
RemoteMaster v0.96 now available
Moderator: Moderators
RemoteMaster v0.96 now available
Last edited by gfb107 on Fri Mar 19, 2004 11:46 am, edited 1 time in total.
-- Greg
Original RemoteMaster developer
JP1 How-To's and Software Tools
The #1 Code Search FAQ and it's answer (PLEASE READ FIRST)
Original RemoteMaster developer
JP1 How-To's and Software Tools
The #1 Code Search FAQ and it's answer (PLEASE READ FIRST)
Just to expand a little on the "Requires RDFS version 1.16 or later" statement.
RDFs 1.16 will be available tomorrow.
Rm will still work with RDFs v 1.15, but Device Combiner will not be listed as an available protocol until you use v1.16 of the RDFs.
RDFs 1.16 will be available tomorrow.
Rm will still work with RDFs v 1.15, but Device Combiner will not be listed as an available protocol until you use v1.16 of the RDFs.
-- Greg
Original RemoteMaster developer
JP1 How-To's and Software Tools
The #1 Code Search FAQ and it's answer (PLEASE READ FIRST)
Original RemoteMaster developer
JP1 How-To's and Software Tools
The #1 Code Search FAQ and it's answer (PLEASE READ FIRST)
Strange. The changes for v0.96 are very specific to DeviceCombiner, so this doesn't make much sense.
Try deleting/renaming your RemoteMaster.properties file.
Try deleting/renaming your RemoteMaster.properties file.
-- Greg
Original RemoteMaster developer
JP1 How-To's and Software Tools
The #1 Code Search FAQ and it's answer (PLEASE READ FIRST)
Original RemoteMaster developer
JP1 How-To's and Software Tools
The #1 Code Search FAQ and it's answer (PLEASE READ FIRST)
Your suspicions were right. Deleting the properties file and letting RM regenerate a new one solved that problem.
I compared the old and new properties file. The only difference that appeared to be of any significance (other that for my specific configuration, of course) was the Look& Feel line which, in the old file was "javax.swing. ..." and in the new one "com.sun.java.swing. ...". However, I made the substitution in the new file and it still worked. I've posted my old properties file here should you want to look at it.
But, then, upon trying change to the remote type to URC 8911, I received a whole page of error messages, the first of which was "java.lang.Exception: Syntax error at line 13 in CPTOCPx1(URC-9910_8910 Extender 1).rdf". Even though your message above indicates that 0.96 would run on the old version of RDFs, I downloaded the new RDFs that Nils poster earlier today. Same problem.
Incidentally, I downloaded all the RDFs to a new directory. Previously, I had been keeping only a few in the base directory, but updating is "becoming a pain". Since RM doesn't seem to have a RDF-path specification capability, other than at installation, I manually modified the properties file in order to specify the new loaction of the RDFs to RM. Still the same error messages. To make sure that RM was not, somehow, still looking at the old RDFs, I also renamed them. No change.
What am I doing wrong?
Don
I compared the old and new properties file. The only difference that appeared to be of any significance (other that for my specific configuration, of course) was the Look& Feel line which, in the old file was "javax.swing. ..." and in the new one "com.sun.java.swing. ...". However, I made the substitution in the new file and it still worked. I've posted my old properties file here should you want to look at it.
But, then, upon trying change to the remote type to URC 8911, I received a whole page of error messages, the first of which was "java.lang.Exception: Syntax error at line 13 in CPTOCPx1(URC-9910_8910 Extender 1).rdf". Even though your message above indicates that 0.96 would run on the old version of RDFs, I downloaded the new RDFs that Nils poster earlier today. Same problem.
Incidentally, I downloaded all the RDFs to a new directory. Previously, I had been keeping only a few in the base directory, but updating is "becoming a pain". Since RM doesn't seem to have a RDF-path specification capability, other than at installation, I manually modified the properties file in order to specify the new loaction of the RDFs to RM. Still the same error messages. To make sure that RM was not, somehow, still looking at the old RDFs, I also renamed them. No change.
What am I doing wrong?
Don
OK, I found the problem. It isn't you, it is a bug in RM. I'll make a new release shortly.
As it turns out the problem wasn't directly related to the properties file. Your properties file happened to show that the default remote to load should be the 8910 Extender 1, and RM had a little problem parsing that RDF.
As it turns out the problem wasn't directly related to the properties file. Your properties file happened to show that the default remote to load should be the 8910 Extender 1, and RM had a little problem parsing that RDF.
-- Greg
Original RemoteMaster developer
JP1 How-To's and Software Tools
The #1 Code Search FAQ and it's answer (PLEASE READ FIRST)
Original RemoteMaster developer
JP1 How-To's and Software Tools
The #1 Code Search FAQ and it's answer (PLEASE READ FIRST)
-
Nils_Ekberg
- Expert
- Posts: 1689
- Joined: Sat Aug 02, 2003 2:08 pm
- Location: Near Albany, NY
Greg
I took a look at this and line 13 is the XShift=$C0 entry. I removed this and it opened fine. I re-added the entry to the RDF and RM would not open until I removed the last remote entries as it was holding the 8910 extender rdf..
I tested further and any RDF that has the XShift=$C0 entry like the 9960 ex2 RDF fail also.
I took a look at this and line 13 is the XShift=$C0 entry. I removed this and it opened fine. I re-added the entry to the RDF and RM would not open until I removed the last remote entries as it was holding the 8910 extender rdf..
I tested further and any RDF that has the XShift=$C0 entry like the 9960 ex2 RDF fail also.