That peculiar stage again: all tools are ready, all options explored, the basic design defined... what am I waiting for? It really feels like the phase in old-time strategy games like Command & Conquer where you had amassed a huge army, but were waiting for just the right moment to get into action. The interesting thing is that this never happens at work, seems like having a well developed software process (with milestones and all) pays off...
Oh well, let the fun begin - tune in to Philosomatika, turn the test code into a standalone task, add the event handler, and the rest will just follow :)!
The engineering documentation on UNNA for the Newton mentions that the internal modem port can only handle 19200kbps. That's true, unless you use DMA. I'm now more or less done with figuring out how to enable DMA, and can now proceed with Blunt 2 - the always-on Bluetooth stack. Gotta love Hammer ;)
Don't put a TEndpoint into a TUTaskWorld task on its own. It will crash because it wants to run in a TAppWorld task, with all the associated port and event handler glory. Which is unfortunate, because now I have to replicate all that nice endpoint functionality for my standalone Bluetooth server (Blunt 2 if you want to call it like that).