--- In RMCEnhancer@yahoogroups.com, "Jay" <jay13178@y...> wrote:

> Um, there are all of _two_ of them. The reason this group died is
> because there is no accompanying documentation with rmcenhancer that
> actually helps the users (from whom the definitions should be coming)
> actually _learn_ how the protocols or whatever other technogeeky stuff
> works.
>
> You've got a great program man. It has the potential to be better than
> omniremote, or perfectremote, but it's _worthless_ if there's no one
> who can use it well enough to write any definitions.

Jay,

The documentation is there, in the research folder of the group. I
showed step by step how I wrote the Sony Satellite definition. It was
a laborious process, and most people recognize that it is easier to
just pay for Noviremote/Omniremote and use those instead of going
through a process that cannot guarantee a match and may end up being
wasted effort.

I had a goal of taking all of the UEI definitions from the JP1 group,
which were easily obtainable, and mapping them into the existing
protocols supported by Clie RMC. The RMCEnhancer program is the tool
to accomplish that. I've used a variety of methods to determine the
information from the protocols, and incorported my findings into the
protocol file on the way. But this is a job only a hacker, or someone
with the right equipment and knowledge of the IR protocols can do.
There are few here who have demonstrated that capability.

My incentive was what I would end up with: A Clie that had more
remote definitions than most universals, and would always be with me
when I needed it. Since then, my Clie has become unreliable, and is
now consigned to the dusty shelf. Sony has dicontinued not only the
Clie RMC program, but the entire Clie line. If I get another
handheld, my next one cannot use the work I've done. So I have lost
my incentive to finish the protocol research and start the mapping
process. Every now and again, I find myself with time and sudden
interest to finish what I started. And so every now and again, you'll
see something from me. That's my quirky behavior.

The latest update I put out puts everything in place to be able to
share definitions and skins with ease. Next time I suddenly get
interested in this, I may map a bunch of definitions out of the
devices spreadsheet (also in the research folder) into the program.
But in the meantime, everything necessary is there for anybody else to
work on it. And on occasion, somebody with extraordinary skills pops
their head in and figures this out, and then shares their work.

So to wrap up this long message with my point: Jay, building a
definition from scratch is really for the technically
minded who understand how the protocols work, or are willing to
experiment.