I was trying to update the firmware to 3.62/4.85 and having a terrible time. Some versions have gone easy and some not. This one was being very stuburn. I tried COM1, COM2, Win98se and Win2k. They would all Fail.

Then while searching this forum someone mentioned the battery meter in an unrelated note. And it struck me, maybe the battery is low. So popped it into the charging stand and left it in their for the upgrade. BINGO it worked !!!

Then I wondered, could this be the same problem causing Win2k to crash while learning IR codes. Bingo again, it learned perfectly whil in the charger.

The battery was not that bad but it was not at peak either.

I think this could explain a LOT of the "It Works for Me/It doesn't for Me" threads.

If your having problems with communication put it in the charger or try fresh batteries.

Interesting thought -- while I doubt it would fix everyone's problems, it's CERTAINLY something to check and try for anyone having communications problems.

I did not mean to imply that it would fix everyone's problems. But for those that are doing everything "right" I believe a low battery (that is, non peak) will cause them havoc. It was the difference between night and day.

And I believe you! First, the remote hates low power levels. Second, communications takes a lot of power (I learned that with my digicam... leave it connected to the PC with the program open and the batteries will go dead in an hour).