Unexpected Changes To Raw Data When '.rmir' File Is Loaded

Discussion forum for JP1 software tools currently in use, or being developed, such as IR, KM, RemoteMaster, and other misc apps/tools.

Moderator: Moderators

Post Reply
WagonMaster
Posts: 366
Joined: Thu Apr 16, 2009 2:25 pm

Unexpected Changes To Raw Data When '.rmir' File Is Loaded

Post by WagonMaster »

Ran into an oddity with RMIR while testing the new version today.

A bit of preliminary info.... I have a "virgin" '.ir' file for my RS 15-135, saved after a download with 'IR.exe' when it was brand-new. It obviously makes a nice baseline when I'm testing. When using RMIR, I can load it just fine but since RMIR doesn't save '.ir' files in the "File" -> "Recent" menu list, I decided to save myself some time by just saving it in '.rmir' format too. So I used RMIR to load the '.ir' file and then merely saved it in '.rmir' format. So far, so good.

The problem comes in whenever I load that '.rmir' file. Even after a fresh startup of RMIR, whenever I load that file, I see that 3 bytes in the early part of the flash RAM (at addresses 0x0608, 0x0609, and 0x061D) are unexpectedly colored red!

I looked in the original '.ir' file and in the '.rmir' file and those bytes have indeed been changed ever so slightly (by 1 bit in each case) from what they're specified as in the original files! Here are the changes:

Code: Select all

   0x0608: 0x43 -> 0x42
   0x0609: 0xBC -> 0xBD
   0x061D: 0xFF -> 0xFE
For those unaware, the flash memory in the RS 15-135 begins at 0x0600.

Just to be thorough, I went so far as to do an automated comparison (after massaging the spacing/format to match, of course) of the '.ir' and '.rmir' files' versions of the flash memory data area. The 2 files match perfectly.

So it seems like something in the '.rmir' file is triggering those bytes to be changed as/after the '.rmir' file is loaded.

If I load the '.ir' version of the file with RMIR, there is (as expected) no change in those bytes as shown on the "Raw Data" page from what they are specified as in the '.ir' file.

I cannot think of any reason for these bytes to be changing. I figure that it either has to be something at the end of the '.rmir' file that's causing this or just a bug. Here's the end of the '.rmir' file:

Code: Select all

[Settings]
My System Transport Device=2
My System Volume Device   =1
My System Channel Device  =0
My System Menu Device     =0
My System PIP Device      =1
VPT Status=1
VPT Device=1
CBL/SAT uses VPT=1
TV  uses VPT    =1
DVR uses VPT    =1
DVD uses VPT    =1
AV1 uses VPT    =1
AV2 uses VPT    =1
VCR uses VPT    =1
dev8 uses VPT   =1
CBL/SAT Setup Code Lock=0
TV  Setup Code Lock    =0
DVR Setup Code Lock    =0
DVD Setup Code Lock    =0
AV1 Setup Code Lock    =0
AV2 Setup Code Lock    =0
VCR Setup Code Lock    =0
dev8 Setup Code Lock   =0
I've uploaded the '.rmir' file ('RS-15-135-virgin.rmir') which causes this phenomenon.

I've also tried this with a URC-10820 remote control and its virgin '.rmir' file and I see a similar alteration of just 3 bytes.

Can anyone enlighten me, please? Is this a bug or merely some sort of normal, expected side-effect?

Regards,
Bill
gfb107
Expert
Posts: 3411
Joined: Sun Aug 03, 2003 7:18 pm
Location: Cary, NC
Contact:

Post by gfb107 »

It's a bug, in the code for storing settings into the remote image.
Post Reply