Page 1 of 1

keymap-master v9.19 available!

Posted: Sun Jan 24, 2010 3:45 pm
by mr_d_p_gumby
The latest version of KM (v9.19) is available.
Changes include:
  • Replaced Dreambox (016C) protocol with XMP (016C) and revised S3C8+ & HCS08 pcode.
  • Added hacked 1-byte XMP-1/2 (016C) protocol for S3C8, HCS08, 6805-RC16/18 & P8/740 remotes.
  • Added support for Pioneer MIX 4x4 (007E:4) and Pioneer MIX 4x4x4 protocol variants and updated pcode.
  • Added HCS08 pcode for PID 0162 (DirecTV).
  • Added URC-7781, RCA RCRP06B & URC-6/8/10820N remotes.
  • Modified Setup sheet to allow entry of an alternate PID whenever a protocol upgrade is required.
  • Revised logic to notify when protocol upgrade is too big for remote.

Posted: Tue Apr 20, 2010 5:13 pm
by Capn Trips
Mike, I have been using RM almost exclusively in recent times, but whenever there is a hiccup with RM, I'm very happy that there is the KM option to use until Greg issues a fix. Right now there's a problem with the latest RM that prohibits entering ANY device number, so I fired up KM and it did the job. Created my upgrade, and copied it onver to IR.

However, upon SAVING the upgrade, KM reverts to the RS 15-1994 remote selection and that is the format that it gets saved as. Upon opening the upgrade, it's a 15-1994 upgrade and I have to change the remote again.

It's a simple upgrade - NEC1, Device 130, about a dozen functions with OBCs 2-15.

I'm running Win 7 (64) and MS Office 2010 Beta (free download and activation from MS for anybody interested).

Does anybody else see this behavior or is it just me?

Posted: Tue Apr 20, 2010 7:35 pm
by ElizabethD
Can't prove the negative. Can't prove you're seeing things.
On XP-SP3 and Office2003, every upgrade I loaded for all my remotes plus Comcast and Atlas, the correct remote was displayed in KM.

Posted: Tue Apr 20, 2010 8:02 pm
by mr_d_p_gumby
The most recent version of MS Office that I have used to test KM is 2007. The 15-1994 is KM's default remote, and it is substituted for any remote not recognized. Perhaps something is going on in 2010 while saving the file that wouild cause this...?