A quick test indicates that this seems to work. Is there any thing else that might be using the same registers in another protocol, and if so how do I check for it?
Richard
I could not get ToadTog to fail after this change no matter where I ran it from. It was actually what I thought was an available register but it looks like the remote itself used it as a temp register. It is the only protocol that is using this register so there should no longer be a conflict.
I actually did that search already. Checked a few others while I was in there also and see no other conflicts.
Nils_Ekberg wrote:
Edit the $0181 protocol in your extender image and replace the data in the box with the following data and let me know if it helps with the ToadTog problem. Just trying a different register. Make sure you don't have any spaces on the end of each line.
