JP1 Remotes

OK, I think I have a problem with Extinstall running on my machine, since I've tried from a batch file and I've checked and double-checked that
(1) it is the latest version of EXTINSTALL (distributed with the extender);
(2) All of the relevant files (.hex, .ir) are in the same directory as Extinstall;

and I get a Command Line note that Here is the batch file I'm running: where Test6ext.ir is my input IR file, and Test7ext.ir is the desired name of my output IR file.

I've tried with the switch "-sig=..." and "-signature=..." and both yield the same result.

Something has gone wrong with your setup. I did, like you did, just copy the new RDF into my RDF folder and replaced the old one (I didn't think ahead with that move).

I didn't try just Extinstalling on an existing hex. I re-asm-ed the source. To do that I had to copy over SC38asm and the batch file to run it to my new extender beta folder. I changed the name of the source file in that batch script and ran it and it seemed to work. I got no errors and new HEX and LST files.

Is this the invocation of extinstall that's causing you problems, the one in the asm script?

jeff

extinstall-2 needs vcredist_x86.exe installed. You can try re-installing the runtime library.

binky123 wrote:extinstall-2 needs vcredist_x86.exe installed. You can try re-installing the runtime library.

OK, found the link in the file section where Extinstall2 is. That wasn't obvious when you just include Extinstall2.exe with the extender package.

RATS! At work, I have insufficient provileges to run vcredist_x86.exe and install the dlls required.

Extinstall looks in the current directory for the RDF by using the signature, so it'll never see the difference in the RDF way down in the title describing that this is V0.2 or V0.4. It'll use the version that you have for both files.

What Extinstall does with the RDF is find out where to find things in the IR file so that it can put macros, keymoves, etc in the right place. Nothing has changed in those areas for the extender so there should be no issue.

That said, the error that you are getting from Windows says that it can't even start Extinstall. Something else has gone wrong in your windows configuration that has screwed up Extinstall's abiltiy to run. Since Extinstall is a DOS program, my bet is that something has messed with the paths for the Visual C runtime that was installed and is necessary for Extinstall to run. Other than that advice, I'm not sure I can be much more help other than suggesting that you reinstall the VC Runtime that you installed when you first started using Extinstall.


-bill

It was indeed the VC Runtime. Although when I tried to install it here at work, I got LOTS of errors (insufficient privileges to write to registry), I just clicked "Ignore" about 31 times and let the program run its course.

Afterwards, Extinstall2.exe seems to run fine, and creates a new IR file. I don't know how corrupted it is and whether other errors have been introduced until I test it at home, but it LOOKS finr in IR. If it doesn't work right, the first thing I'll do is re-extinstall it at home, where the VC runtime has been fully installed and give it a shot that way.

you CAN do a DIFF (a program called ExamDiff is a free download and works fine) on the IR files as they are just text. The area for keymoves and macros should be no different. You'll see a change in the checksum and then a change in the area where the extender resides (and of course, the last byte will be changed as that's the version number)

But that will tell you if your configuration survived the upgrade. (it should as Extinstall reads the entire configuration into its internal buffer and then writes it out based on the new config but there could always be a bug)

Thanks for the update!

I'm still not having any luck with macros that contain X_ device selections though (just on normal keys, didn't even try device buttons). I get a single light on the current device, and at the end of the macro the current device seems to be changed to the last device selected in the macro (X_AUD in this case) even though X_Cancel is the last command in the macro. If I replace all the X_device with normal device buttons then the macro fires correctly, so I guess it's just the X_ part of the selection that doesn't work.

If it's of any value, I can upload the .ir file.

Ad

Sorry I've not gotten back with feedback. I encountered the same issue as adamwh is having with the latest version. temporary device selection does not work, except it it's X_TV, but that might be a feature of my setup.

Adamwh please upload your file(s), if they're simple and make the bug clear. Also include a link back to this thread to the upload.

To aid debugging by an expert, I have an extra 1056 OACP 3033 remote I could loan out. Let me know if anyone's interested.

Thanks,
jeff

Jeff and Adam

can either of you upload your IR file for me to take a look at? I've gone back into the extender and built in my debug macros and then load/watch what is going on with the device table and all appears to be well.

The device table is updated correctly with all of the X_ commands as well as with the X_Cancel.

thanks

-bill

I uploaded a zip file with the original IR file I used to create the extended version as well as the extended version. I included the original file in case I've simply screwed up the extinstall process.

https://www.hifi-remote.com/forums/dload ... le_id=5363

The extact remote is a Brighthouse branded ATLAS OCAP 5-Device with Learning 1056BC1-XLX-001-0001-001-R.

I've noticed another strange behavior. I have all of my device keys set to V_Aud since I have all my audio routed through my receiver. If I hit CBL and the VOL+ (or -), the first press lights the CBL key but subsequent presses light the AUD key like they should. If I hit any other device key, the first press of VOL+ (or -) doesn't light any device buttons, but subsequent presses light the AUD key correctly. It's always the first press of a VOL key that goes wrong, even if I press other buttons for the device before pressing a VOL key. The correct VOL command is not sent when the AUD key isn't lit so I don't know what it thinks it's doing. The volume keys are the only set of keys I have set to a different device than the device selected by the button. I thought the fact that CBL behaves differently maybe provides some clue.

Thanks again

Ad

Here's my IR file: link.

Mainly look at the CBL LKP special macro and the CBL macro. On the long side of the LKP, it should select TV (X_TV) and change the TV input. X_TV within this macro refuses to work.

Bill, if you want I can loan you the 3033 OCAP if it'd make it easier. Let me know.
jeff

Adam, the behaviour you are describing matches what I described several pages ago in this thread.

Lacking a better way of describing it, I see that the "device association" assigned to a particular button does not "kick in" WHEN YOU PRESS the button, but AFTER THE BUTTON EXECUTES the function (associated with the previously-"active" device).

Haven't done much testing with the new extender, but it sounds like the same problem persists.

I am also seeing the same problem you describe several posts above with X_Device settings.

Hoping to test more when I get back home from my current travels/travails.

Jeff

Can you isolate the functions on the LKP to individual keys and make sure that I don't have an issue with LKP and not with the device selection?


I will download and look at your IR later this weekend

Ok, Bill. I'll take the macro off of CBL: longside and see if I can get it to execute on another key, as device selection, then input function.

I'm watching the game now, but will do it after...

Best,
jeff