Help with EXTINSTALL on URC7800

[aclinml]

I am trying to go from the old Extender 2 for a Cinema 7 (URC-7800) to the new version 5 extender. When I give IR the supplied HEX file and output file name on the Merge, I get the following error message;

SYSTEM ERROR. CODE 14001

THIS APPLICATION HAS FAILED TO START BECAUSE THE APPLICATION CONFIGURATION IS INCORRECT. REINSTALLING THE APPLICATION MAY FIX THIS PROBLEM.

I should also note, if I tried to execute the EXTINSTALL from a "C" command prompt, I got the following error;

THE SYSTEM CANNOT EXECUTE THE SPECIFIED PROGRAM

What do you think my problem is???

[unclemiltie]

which version of Extinstall?


V2 requires the Microsoft C run time that you can download from their web site for free. The requirement is mentioned in the release notes for ExtinstallV2.


I have seen that error in the past, there are a lot of posts on the web about what causes it, but in general no-one seems to really know. My recommendation would be to make sure that you get V2 of extinstall, make sure that the C runtime is properly installed and then try again.

[unclemiltie]

Oh, one other suggestion: when you're trying to fix this, make it work from the C command prompt first, then it'll work from IR. There is no need layering on complexity as you're trying to make things work.

[aclinml]

I'm really not familiar with 'C'. There are several references to "c", "c++", visual c and others at microsoft.

Could you be kind enough to point me in the right direction for the download that I need?

Thanks for the help.

[aclinml]

Sorry, should also have mentioned I'm running Windows XP Home SP3

[unclemiltie]

I am not home right now but if you download v2 the readme has a description of what u need. I think that there is also a topic on extinstall v2 in here with links to ms but that's too hard to find on my phone!

[binky123]

The Beginner's Extender FAQ here references this EXTINSTALL.EXE here which in turn mentions the MS download here.

[aclinml]

OK, I got the version 2 of Extinstall to run successfully, and the output and comments look good from a cursory examination. I do have a couple of new questions.

1. The following is in the Readme file on the Extender 5;

"After Extinstall runs, in macros, you'll see odd-looking translations
due to the new and remapped pseudo-devices, so, for instance, the old
M_AUX comes out as XShift-Phantom2. It's no problem. ExtenderCode
Calculator (ECC) does a fine job and preserves notes for both keymoves
and macros"

I don't really understand what this means. I did look at my macros and there were a bunch of changes to keys with a lot of 'XSHIFT' keys being specified. I assume I need to edit all of these back to the way they were spedcifed pre Ext5?

I noticed a new menu tab in IR that says 'Special Protocols' although nothing is in there. The special protocols included with the Ext5 are all loaded in the regular Protocols tab. What is this for?

Thanks again for the help

[unclemiltie]

I'll let someone who is familiar with the extender for the 7800 answer your first question

The second question is that when the special protocols are included in the extender (as defined by the RDF and included in the device & protocol upgrade tables) you will get a tab in IR that helps you define what you want to do with the protocols. if you don't use them, no big deal.

But if you want to define a ToadTog or a LKP you would use this tab to define them.

In the past the special protocols would be done in IR via keymoves and you had to understand how to construct the specials. But with the later versions of IR, they are built for you with pull-down menus and a much nicer interface.

[Capn Trips]

I noticed a new menu tab in IR that says 'Special Protocols' although nothing is in there. The special protocols included with the Ext5 are all loaded in the regular Protocols tab. What is this for?

The actual PROTOCOLS are loaded in the Protocols Tab, but the Special Protocols Tab is used to construct any functions (Device-specific Macros, ToadTogs, Short-Long Key Press sequences) you want to USE the Special Protocols. As unclemiltie states above, it USED to be that you had to create Special Protocol hex sequences direclty in the Keymoves Tab, and it was rather involved and tedious. The Special Protocols Tab simply provides a location and the means to construct these functions in an easier, more intuitive manner.

[ElizabethD]

If this still not resolved - few notes from me for starters since I hardly remember what the problem was and how to change -

Bill has a cmd or bat file to run from the DOS window (start > Run > cmd)

extinstall 7800ext5.HEX newIRfile.IR
pause

If you'd rather use IR to make the conversion, put the HEX file, extinstall2 in the same directory as IR, then File>SetDirectory>ExtInstall path, and run the merge.

When Vicky started working on ext5, Extender 2 had these lines in the RDF

M_CBL=$F8:AllBind, M_TV, M_DVD, M_VCR, M_RCV, M_AUX, M_CD,
V_CBL=$E0:AllBind, V_TV, V_DVD, V_VCR, V_RCV, V_AUX, V_CD,
T_CBL=$E8:AllBind, T_TV, T_DVD, T_VCR, T_RCV, T_AUX, T_CD,
P_CBL=$F0:AllBind, P_TV, P_DVD, P_VCR, P_RCV, P_AUX, P_CD

So I think key codes $E0 and up now show up as various new X-shifts which require remapping

Current Extender 5 lines are

X_CBL=$47:AllBind,T_CBL,V_CBL,C_CBLT,M_CBL,P_CBL,O_CBL,
X_TV,T_TV,V_TV,C_TV,M_TV,P_TV,O_TV,
X_DVD=$55:AllBind,T_DVD,V_DVD,C_DVD,M_DVD,P_DVD,O_DVD,
X_VCR=$5C:AllBind,T_VCR,V_VCR,C_VCR,M_VCR,P_VCR,O_VCR,
X_RCV=$63:AllBind,T_RCV,V_RCV,C_RCV,M_RCV,P_RCV,O_RCV,
X_AUX,T_AUX,V_AUX,C_AUX,M_AUX,P_AUX,O_AUX,
X_CD,T_CD,V_CD,C_CD,M_CD,P_CD,O_CD
X_Cancel=$7F:AllBind

If your ext2 file isn't too big, you can open 2 sessions of IR.
Open your ext2 IR file in one, and ext5 IR file in another and just fix macro buttons.

I had many long macros, so I used ECC (extender code calculator) I think using the new ext5 RDF and doing global replacements. But it would take me some time to dust off the steps I went through and I'd rather not bother if you have no more problems.

[vickyg2003]

1. The following is in the Readme file on the Extender 5;

"After Extinstall runs, in macros, you'll see odd-looking translations
due to the new and remapped pseudo-devices, so, for instance, the old
M_AUX comes out as XShift-Phantom2. It's no problem. ExtenderCode
Calculator (ECC) does a fine job and preserves notes for both keymoves
and macros"

In order to add the x-shift capability to the extender, the device psuedo keys had to be moved. So the psuedo keys will need to be fixed after you merge into the new extender.

[ElizabethD]

To simplify things, here's a tiny, quick&dirty, helper list.
When ext2 file is converted to ext5, these are the only conflict values as far as I recall.
Three examples:
1. when you see xshift-Light it means in Ext2 it was V_RCR
2. when you now see xshift-Exit, it was T_DVD in Ext2
3. When you now see xshift-DiscreteOff it was M_VCR in Ext2.

Code: Select all

XSHIFT-Key  :	KeyCode	in Ext2 it was
TV/VCR      :	E0	V_CBL
CD          :	E1	V_TV
DVD         :	E2	V_DVD
MENU        :	E3	V_VCR
LIGHT       :	E4	V_RCV
(notUsed)   :	E5	V_AUX
M1          :	E6	V_CD
SELECT      :	E8	T_CBL
INFO        :	E9	T_TV
EXIT        :	EA	T_DVD
PIP         :	EB	T_VCR
SWAP        :	EC	T_RCV
MOVE        :	ED	T_AUX
GUIDE       :	EE	T_CD
L2          :	F0	P_CBL
UP          :	F1	P_TV
DOWN        :	F2	P_DVD
LEFT        :	F3	P_VCR
RIGHT       :	F4	P_RCV
L3          :	F5	P_AUX
L4          :	F6	P_CD
(notUsed)   :	F8	M_CBL
(notUsed)   :	F9	M_TV
Discrete On :	FA	M_DVD
Discrete Off:	FB	M_VCR
Phantom1    :	FC	M_RCV
Phantom2    :	FD	M_AUX
Phantom3    :	FE	M_CD