Page 2 of 2
Posted: Sun Jan 04, 2004 7:35 pm
by TimH
The cluster manager doesn't get loaded on a pc, it is located on the switch. You just connect to the switch with a browser and the cluster manager runs.
It's not really a big issue since I rarely have to run the cms (cluster manager software) from my laptop. I have access to other machines that do run the cms, and I actually had not been able to run a couple other java things since I was still on the older version. All in all, it's good to know that cms is broke on newer versions. Definetly better to find out this way than in a pinch when I need to setup a new vlan for the boss or something

Posted: Tue Jan 06, 2004 3:31 pm
by DGG
Just converted my extended 8911 KM files to RM. Encountered a few problems, including a crash, but was eventually successful. Details in a bug report on SourceForge.
Otherwise, its a "cool tool", especially since it incorporates several of the items in my IR/KM wish-list posted a day or so ago under JP-1 General Forum. I'll be using it from now on.
I just hope you plan on integrating ExtenderCodeCalc functionality into RM someday.
Don
Posted: Tue Jan 06, 2004 7:47 pm
by gfb107
Just read you bug report at SourceForge.
Many of your problems were caused by trying to use the RDF bundled with the extender instead of the RDF for the 8910 with extender from the RDF package in the Tools section at Yahoo.
There are some improvements that could be made to that RDF.
In the General section, the line XShift=$C0 should be added.
All the xs- button definitions from the Buttons section should be deleted, as they are made redundant by the above line.
The DEV_ and SET_ buttons should have the AllBind restriction.
These buttons are defined in sequential keycode order, so you just have to add :AllBind after each of the specified keycodes. This change will make it so IR and RM will not make these buttons available for assigning functions or macros.
Or you can just use the
one I've modified
Posted: Tue Jan 06, 2004 9:06 pm
by DGG
Thanks, Greg. I prefer the way RM displays xs buttons using the XShift command in the RDF file.
The main reason for the separate bug report was to provide details on the RM crash/failure to restart and external functions problem. Also, I can now duplicate the external function problem if its helpful.
Don
Posted: Tue Jan 06, 2004 9:11 pm
by gfb107
I've not been able to reproduce it, so please give detailed instructions.
Posted: Tue Jan 06, 2004 9:32 pm
by DGG
Just realized that the app hadn't hung. The "$s" in the hex string I copied from IR caused an error condition, and RM wouldn't let me move on until the "$" was removed. Unlike IR, RM doesn't seem to like "$s" in a hex string.
Don
Posted: Fri Jan 09, 2004 4:14 pm
by DGG
Greg, I've found another little difficulty. When I attempt to assign the function "power" to the xs-power key, the assignmwent does not appear as a keymove in the outpout code window. It does, however, appear normal under the "button" tab. It appears the only way to make that keymove effective is to program it from the keymove tab in IR.
Don
Posted: Fri Jan 09, 2004 5:43 pm
by gfb107
Yep, that's a bug. If there is no function assigned to the normal or shifted button, the x-shifted button won't be included.
There will be a new release with the fix in the near future.