I have upgraded the TSU9600 to firmware 4.0.17. Now when I download a new configuration to the unit I get the following messages in the Pronto PRO Debugger (shown in the "newest on top" order that the debugger displays):

[Device started]
-->SendSpecificScan @68072
ERROR: CFH_Mount: cannot mount /dev/loop/5 to /opt/store: Device or resource busy
ERROR: CFH_Mount: cannot setup loopback device /dev/loop/5 for /opt/user/msd: Illegal seek
ERROR: CFH_LoSetup: LOOP_SET_FD failed: Device or resource busy
##### Time 10:59
EV_PCCOM_SETTIME received!
EV_PCCOM_SETDATE received!
HWAC - Associated @52071
<--SendSpecificScan @51939

The ERROR lines did not occure with the previous firmware. Any ideas?

There are lots of debug and diagnostic messages that are shown on this link that are not necessarily for consumption outside of the Pronto Team. If you reboot the Pronto, you can also see alot of data with Barry's tool. It is likely this reason that Philips was likely hesitant to allow Barry to publish.

If you are new to the debugging with Barry's tool, pretty much ignore this message.

I've seen it as well with the beta firmware. If the unit connects, I would not be concerned.

You could not see it before, not because it wasn't there, I and Lyndel have always seen them. The issue is most probably that the Pronto is not far enough in its initialization process and startup processes. I have no idea what they signify, but I am sure they mean something to the Pronto Team. probably related to hardware initialization. It would be nice to know what is going on, but I am happy with what I have now.

I want to express my appreciation to Barry & others for all of their work getting this to the point others can use it. Anyone using Prontoscript would be crazy not to take advantage of this technique.

Barry mentions in the documentation a donation which I hope others took the opportunity to do. While I'm sure thank yous are nice, showing your thanks with a contribution is a nice gesture.

I personally would have given up on trying to debug a complex prontoscript activity staring at the 9600 screen.

While I am not sure if the 9400 has the same capability, I have an interesting workaround. I have both a 9600 and a 9400. I load a 9400 xcf into the 9600 editor and download it at which time it tries to find a 9600 and not a 9400. It loads fine and the prontoscript engines are the same on both. The Pronto script editing tool even knows about the two extra buttons on the 9400. While you are in the 9600 editor you can add two buttons below the "9400 screen" called Info and Back and give them the same actions as the buttons in the 9400 program. They will appear on the 9600 screen but not the 9400 screen due to screen geometry differences.

The 9600 doesn't know it is running a 9400 program and the serial debug stream is available, It is still 99 characters wide but on the PC and much better than that 240x320 9400 screen.

I actually do all my 9400 work on the 9600. I love the extra real estate that is "off" the 9400 screen dimensions. You can actually slide in static images dynamically iPOD like if you want. The 9400 slim server does a lot of that. If the Pronto allowed for manipulating a bunch of widgets as a group (at the harware level, treating the multiple widgets as a single graphic) that would really be nice.

The only other point (an upcoming pun) when dealing with the 9400/9600 is that fonts are supposed to be in points, and points (worth the wait?) have nothing to do with screen resolution or with screen geometry (size). 72 points = 1 inch. Always. If it doesn't then the unit is not points.