Only for models that have modem upgrade capability.

ABerguerand wrote a program that hasn't been released yet, but has been tested on a URC7562 and an RS 15-2133. It converts data from the IR.EXE program into a .wav file so it can be loaded into a remote without using a JP1 cable.

You can load upgrades similar to the ones available by phone from UEI; But you can also do much more.

When you make your own upgrade: You can decide which function goes on which key. You can include discrete codes and other special functions UIE doesn't. You can use the protocols Jon has built with PB to support devices UEI doesn't support.

You aren't limited to upgrades: You can load macros and key moves into the remote, including those key moves that need 2-byte hex commands and cannot be programmed into the remote manually. You can define the remote's entire configuration with IR.EXE and load the whole thing into the remote via .wav file.

This still isn't as good as using the JP1 cable: It takes a bit longer to load (I think it was 90 seconds for a full eeprom image, instead of just a few seconds via JP1 cable). You can only transfer data TO the remote this way, you can't read anything back from the remote.

Since you can't read back learned signals, you can't use IR.EXE's decoding of learned signals to figure out what your upgrade should do. To get the basic starting point you need one of: A) a UEI setup code that's nearly right; B) a file for your device from the JP1 group device library; C) a ccf file for your device; D) help from someone who has a JP1 cable, a JP1 learning remote, and the same orriginal remote.

You can't read the eeprom and edit the results. You need to construct a new eeprom image with IR.EXE and transfer whole sections: If you want to transfer any key move or macro from IR, you must transfer the entire key move and macro section of the eeprom, replacing all key moves and macros you defined manually on the remote with the set of key moves and macros you defined in IR.EXE.

The major sections are:
1) Basic setup data such as setup codes and VPT settings and HT settings.
2) Key moves and Macros.
3) Upgrades.
4) Learned signals.

Transfering part of any of sections 2, 3 or 4 would be too tricky to seriously consider. Transfering part of section 1 wouldn't ever be worth the bother. Plan on transfering one or more entire sections.

ABerguerand hasn't released any of this yet (I think he's still considering a change request I made to make it easier to select which sections you transfer). Learning to use IR.EXE to create an EEPROM image and the KM spreadsheet to create your own upgrades may take long enough that he'll have released it by the time you're ready for it. I suggest joining the JP1 group now and starting to learn this (if you have a 2133 or other modem upgradeable remote and you've had trouble with unsupported devices and/or setup codes that have 2-byte hex commands and can't use EFCs).

Please read the JP1 faq before asking all the usual questions about how to use IR and KM. If still confused, it's probably best to ask those questions in the JP1 group. General questions about what can or can't be done by .wav file are probably better asked in this thread. Specific questions about using the .wav files also could go here. I'll try to answer most; But I don't actually have a modem upgradeable remote, so when it gets to details of how to hold the remote relative to the PC speakers to make it work etc., I can't help.