My RU950 has stopped sending and learning IR. I've concluded that it this is probably a hardware fault, but would be pleased to hear any suggestions or similar problems that others may have.

This has happened three days after installing the new version of firmware and PENG. Whether this is significant, I don't know.

The unit had frozen completely. Pressing the reset button brought it back to life. All menus work as before except that no IR signal seems to be sent. The transmitting symbol appears on screen when it should. RF signals to X10 still work fine.

I downloaded the PCF file again, then re-installed the firmware. The problem remains the same with my old PCF file or using the default one. The unit will neither send nor learn IR. I tried to go back to the previous version of firmware, but find that you can't install older versions.

I'm seeing similar problems: but the unit IS transmitting, just at much shorter ranges: about 30 cm (12") for both TV and audio. Interestingly, the firmware and editor updates appeared to be fine, but -- about three days later -- the whole thing failed. Mike: are you seeing ANY signal sent over any distance?

Remove the batteries for about 20 minutes, then put em back in and reflash the firmware. See if this fixes the problem. If it repeats again, then I'd say it's a potential bug.

I've just tried that, and I find that the range is still hopelessly short: under two feet. This looks like some incompatibility between hardware (RU950) and the new firmware andor ProntoEdit.  Or is the real problem just indicated by the 'Philips' name on the front of the unit? — the company has a solid reputation for half-baked solutions, after all.
 
I'm going to submit a new thread which will be found under 'reduced range', the obvious search phrase, and see if others have the same problem.  Thanks, all.

Thanks for the suggestions guys.

I can't test to see whether the Pronto is actually transmitting on reduced power because I've now got a replacement unit from my supplier.

I contacted Philips who did not (at least at that stage) know of a problem, and suggested that the unit be returned under warranty.

I had tried removing the batteries for extended periods with no sucess.

It does now begin to sound as if there is a firmware/software related problem, so I think that I'm going to stick to the earlier version for a couple of weeks and keep an eye on this forum to see if the issue develops.

Although we now have some instructions on how to go back to an older version of firmware, it looks a bit tricky to me, and I would sooner not risk killing another pronto.