8017 signature error with extinstall 31
Moderator: Moderators
8017 signature error with extinstall 31
I'm trying to install extender into URC-8017. I saved my eeprom in IR's text format, then applied 6012-2K-3.hex which included in 801x_ex3_1 download file, then opened new eeprom text file into IR. Every step looks good without problem, and IR shows lots new functions. But when I try to upload to RC, signature error warning message popup. How do I solve this problem?
I have 6_80_2x3 (URC-881x_801x_601x x3 2K).rdf & 6_80_8x3 (URC-881x_801x_601x x3 8K$1815).rdf in extender_31.exe directory. What else I need it?
I have 6_80_2x3 (URC-881x_801x_601x x3 2K).rdf & 6_80_8x3 (URC-881x_801x_601x x3 8K$1815).rdf in extender_31.exe directory. What else I need it?
-
usblipitor
- Posts: 516
- Joined: Fri Oct 10, 2003 10:06 pm
- Location: Greenbelt, MD
-
Mark Pierson
- Expert
- Posts: 3018
- Joined: Sun Aug 03, 2003 12:13 am
- Location: Connecticut, USA
- Contact:
Re: 8017 signature error with extinstall 31
The first time you upload an extender configuration to the remote, IR will warn about the signature being different because the extender changes it. In this situation, it is ok to ignore the error and let IR upload to the remote.xgamer123 wrote:But when I try to upload to RC, signature error warning message popup. How do I solve this problem?
Mark
-
usblipitor
- Posts: 516
- Joined: Fri Oct 10, 2003 10:06 pm
- Location: Greenbelt, MD
the README.TXT file wrote:11) Save the file (with modified macros) and upload it to the remote. If this
is the first install of the extender (ever, or after a 981 reset) it should
complain about the signature being different. That is normal and not an
error.
12) To activate the extender on the remote, you must press the Power key (which
is defined to activate the extender only in the default device, which is TV).
Don't worry if you have a Macro or KeyMove on the Power key, nor that you
can't see (in IR) the KeyMove activating the extender. That one key move is in
the old KeyMove memory area that is used only before the extender is active.
ExtInstall copied all your KeyMoves and Macros (from old.txt) into the new
larger KeyMove area (within new.txt) and only that area is visible in IR
(with the extender's RDF file).
13) The activation should blink the LED four times, after which the extender
should continue to run until the next battery or IR reset.
-
Mark Pierson
- Expert
- Posts: 3018
- Joined: Sun Aug 03, 2003 12:13 am
- Location: Connecticut, USA
- Contact:
If you're talking about the C_, M_, T_, etc, keys, they're explained in the readme. Bascially, you have:xgamer123 wrote:But for "new kid in town", so many abbreviation for keys/devices definition start to confuse me. Where I can get fully name list for those abb.name?
Code: Select all
C_ = Channel keys: digits, Ch+, CH-, Info, Enter, Prev, TV/VCR, Sleep, Fav
M_ = Menu keys: Down, Exit, Guide, Left, Menu, Right, Select, Up
O_ = Other keys: Power, M1-4, L1-4, Setup, Light, Home-Th, device keys, phantoms
P_ = PIP keys: Pip, Move, Swap
T_ = Transport keys: Fwd, Pause, Play, Record, Rew, Stop, F_Fwd, F_Rew
V_ = Volume keys: Vol+, Vol-, Mute
X_ = Temporary device selection keysMark
Thanks Mark.
I'd remembered that at the first time I tried to apply extender to my eeprom file. All key moves and Macros are still in there. But when I do some practices for Extinstall, all Key Moves and Macros are gone, only Devices data still in new eeprom file. I want to edit these define key move and macros. I saw Move/Macro space tell me there are some bytes it takes. But where it is?
I'd remembered that at the first time I tried to apply extender to my eeprom file. All key moves and Macros are still in there. But when I do some practices for Extinstall, all Key Moves and Macros are gone, only Devices data still in new eeprom file. I want to edit these define key move and macros. I saw Move/Macro space tell me there are some bytes it takes. But where it is?
The extender install moves all the keymoves and macros to a different section of eeprom. If it looks like they are missing then IR.EXE must not be using the right RDF file to see them where they moved.
I don't understand your description well enough to be sure what you did or why IR is getting the wrong RDF file.
I don't understand your description well enough to be sure what you did or why IR is getting the wrong RDF file.