Your Universal Remote Control Center
RemoteCentral.com
One For All & Radio Shack Forum - View Post
Up level
Up level
The following page was printed from RemoteCentral.com:

Login:
Pass:
 
 

Original thread:
Post 14 made on Saturday February 12, 2000 at 04:29
Cico
Historic Forum Post
> Response by Gerard J. Pinzone on 02/11/00 14:53.47
>
> Gerard:

> Ok, that makes more sense. However, the notation that seems to be
> prefered (since the first device key push can be omitted if the Cinema 7
> is already in that mode) for this to be given as:
>
> [device2] [SETUP**] 994 [device1] [SETUP] ### [key1]

Ok, that makes less sense. I don't mind if you prefer a different
notation to the one I described, but I feel I should point out that
your version won't work.

> Now, remember all that hubbub regarding clearing a shifted key?

Hmmmm.... vaguely....

> The sequence you gave was:
> [SETUP**] 994 [key1] [SETUP] [key1]**

> The point is that all this may do is copy back the original function
> of key1 to SHIFT key1 rather than freeing up the memory taken by an
> advaced code assignment. I say this because all shifted buttons are
> programmed by defualt with the same function as the non-shifted
> button.

What the sequence does is remove the advanced code assignment from a
shifted key. That frees up the memory taken by the advanced code
assignment. The result is that the shifted key reverts back to its
original function, which as you say, is the same as the normal-mode
function. I can't find any reason to think it would also, at the same
as it is removing the bits from memory, it is adding a 2nd
"overlapped" copy of the original function to the key's shifted mode,
which presumably can not be cleared by standard protocol. Maybe if I
thought about it long enough... Er, no, it doesn't make sense to me
that it would perform two assignments when you've only asked it to do
one, or that a single key would hold 3 copies (if not more) of the
same function in the memory bank, unless it's being programmed with a
macro sequence.

But in the name of science and the hordes of C7 owners out there that
might be concerned about this and perhaps hesitate to program a
shifted function on account of this concern, I did test the theory
out, as I happen to be very close to maxxing out my C7 anyway... I
followed the instructions you described to test it out (after making
sure I could no longer program a code into my C7), and had no problem
assigning an advanced code to a non-shifted button, after clearing out
the key with the shifted EFC.



Hosting Services by ipHouse