And yes, Robman suggested the same thing. But at the time I was banging on the phone with cust. serv. rep from UEI.

I still say something is broken and needs to be fixed.

Now to the permanent fix. Will using jp1 and reprogamming these keys actually work? Is this a programmable fix or is it a little deeper in the software OS/eprom level?

Using JP1 for this problem, you probably would have just stored the same KeyMove into the eeprom that you already did without JP1. It's a little easier to do with JP1 (much easier once you're experienced with JP1) especially for key moves from alternate setup codes like this case. But once done, the resulting eeprom contents are the same as you already have.

If you happened to be short of KeyMove space, JP1 provides another way to get these results. You could completely redefine the 1058 setup code to rearrange and redefine keys however you want and that gets stored in a different part of the eeprom than the key moves. But you wouldn't normally go to that trouble to avoid just one key move.

With JP1 you can also examine learned signals from your orriginal remote and find their protocol, device number and command numbers and then put them back into eeprom as key moves or as part of rebuilt setup codes. This may save eeprom space and/or improve reliability over using learned signals.

With JP1 you can also try any of those Sony device and command combinations listed on RHM's pages, even if those combinations don't correspond to any setup code built into the 2116 (the way the command you wanted in this case corresponded to that Tape setup code).

But, none of that is a more "permanent fix" to the one missing function than what you already did (except that with JP1 you can backup your whole eeprom contents to a file on your PC and easily restore it later if you somehow mess up the eeprom contents).

Robman,

What did you find out?

Jim

What's broken? The Sony preprogrammed code is lacking the DVD/LD command, on your's as on others. The majority of Setup codes beginning with 1***,don't support advanced codes. What temporary fix, with the two FACTS above, the way you did it, is one of two ways you could of accomplished it. The other way, the one I originally suggested, works also. There is nothing to fix. The reason it didn't work in the first place, is probably do to user error.

Well a fine welcome to you too.

Since RS/UEI support indicates the inability to map directly to the key when selecting the rcvr code first is a bug, and hence broken, I'll cast my vote with them.

It is ass backwards to have to set the device to tape or use the AUX key and then "trick" the remote. And that is where it is broken. It is suppose to take the code and use it in a direct fashion. Again, something cust. support has indicated.

The fact that all 1*** codes exhibit the same behavior is simply verification of it being a bug.

Is there another question I can answer for you or is this still a matter of user error for you?

Jim

Everyone here including Edmund, whom has given you very reasonable suggestions, has been trying to help you.


Some setup codes use two byte keymoves and they just don't work. That could be a bug, but it is at least a known issue. Hence the work-a-rounds suggested here that will do what you want. If you want this fixed you should be on with Radio Shack, not here.

Again talk to Radio Shack. As you have seen there are work-a-rounds that solve your problem.

|It is

But that's not the reality of the situation


It might be but it is well known and there are work-a-rounds that allow you to do what you want.


It might not be user error; however, unless you get an updated remote you have to work within the known "bug constraints" which is easy if you follow some of the advice that you asked for.

None of the people that have tried to help are able to fix this "bug" but they have given you the ability not to let it annoy you so much if you choose.

ext

Sure are a lot of hall monitors on this forum.

There was a previous thread which got inudated by hall monitors about this very issue. When I buy a remote and it doesn't work correctly, having work arounds while appreciated, is not acceptable.

Cust. Serv. indicated this is a bug. And to their credit also indicated any expectation that it would be fixed were probably misplaced due to focus on new models.

I for the likes of me don't understand what you hall monitors can't seem to figure out. I expect a thing to work. It doesn't. I can, with your help, make it work. But "making" something work is one thing, having it work as its suppose to is something else. And I expect a thing to work as its suppose to.

As for whether or not you hall monitors think that means I don't appreciate the help or that I don't appreciate having a remote that works is irrelevant.

So long. Could be a nice forum if a little less critical and a few less hall monitors.

Bye.

Jim

Jim, that's not exactly the way to encourage more people to help you. The fact that you don't understand how these remotes work is not our fault.

Rob

Rob,

Did you get a "Hall Monitor" pass from your home room teacher, and approved by the principal's office?

Jim

If I were made "Hall Monitor", I'd probably come down with a Napoleon complex.:) When I was growing up girls were hall monitors, boys were crossing guards.

What is a "hall monitor"? Are those the TV's that schools get donated to them by Channel One?

"Hall Monitors" are CCTV's distributed in upbeat and rich school districts which have concealed "porn cams" strategically located in the girls restrooms and locker rooms.

In less fortunate school districts they are simply "Monitor Lizards" strategically located in hallways to catch and consume; and thereby reduce the local rat population.

Jim