Update: 8/3/07
I've uploaded a new version of Extinstall-2 that implements the following:
1: supports $FF section terminators. Will allso fill empty memory with the opposite of the section terminator to allow easy location of unused memory.
2: supports LONG format Advance codes used in some of the newer remotes. Will translate between Advance code formats when the extender is different than the base remote (ie: URC-6131)
3: preliminary support for JP1.x extenders by supporting the BaseAddress specified in the RDF. To use this you will have to use the
Code: Select all
-signature=$xxxx command to specifiy where in the IR or HEX file the signature is located. This MUST be the last item on the command line, ie:
Code: Select all
extinstall-2 hexfile inputfile outputfile -signature=EC00 4: copies and merges comments from the HEX and IR file into the output file.
The download is in the diagnosis area here until I get a sense that people are not having issues with the software.
https://www.hifi-remote.com/forums/dload ... le_id=4859
Original Post:
I'm going to try to tackle updating Extinstall. John sent me the source code, I finally got my Visual Studio up and running again and a version of the source that will compile and deliver the same results as the old version did.
My hit parade right now is:
1: deal with the $FF section terminator in the newer remotes
2: deal with the LONG advance code format
3: possibly deal with keeping the comments in the input IR file if I can keep them in sync with the merged IR file.
4: make extinstall work for a JP1.x remote (since there are people working on extenders for those)
Any other suggesitons while I'm in there under the hood?
BTW, I *THINK that dealing with the LONG advance code format will allow Extinstall to insert the extender into a remote that has the LONG format even though the extender does not use that format (ie: URC-6131) Should that be a design goal? I don't think it'll be too hard.