> Believe it or not, there are all expected -- at least, I get most of them > :-). Piper is still under heavy development, so some of this is > debugging output and some of this is errors that haven't been fixed Aha. Good. Sort of suspected that. However, wasn't quite sure and thought it might be better to report that in case I bumped into something. > I think you're doing really well. Happy to hear you are trying it out! Piper is getting more punishment in the future for sure as I intend to use it in my own project. And here already the big question: FreeSpeech / Overflow has a GUI and Piper has one. I guess that the FreeSpeech / Overflow GUI is gonna be scrapped sometime in the future, right ? So it would be a bad idea to look into the interfaces to the components, I guess - I'd better stick to piper. Is there already something like an interface description to hook my stuff in ? My intention is to use the application interface ( or whatever it is called ) in order to be piper compatible. Is that already sort of fixed or - due to development - sort of a moving target ? ======================================================================= "It was hell. They knew it. Karl-Max Wagner But they called it karlmax at oberland.net W-I-N-D-O-Z-E" ham radio: DB8CO *********Member of No Code International********* ***********Visit http://www.nocode.org*********** ********Membership Number NCI-2563-DB8CO********* _ / / (_)__ __ ____ __ / /__/ / _ \/ // /\ \/ / . . . t h e c h o i c e o f a /____/_/_//_/\_,_/ /_/\_\ G N U g e n e r a t i o n . . "Et ceterum censeo ut Microsoftem delendum esse" (Cato, adapted) "Quo usque tandem abutere nostra patientia ?" (Cicero, original) =======================================================================