On Sat, Nov 29, 2014 at 10:46 PM, Peter Bennett (cats22) <cats22 at comcast.net> wrote: .... > If that is the case, the problem is not fixed by that firmware. That is good information (although bad news). We now know the 1201 firmware did not address the issue. Thanks!