-=> Quoting Sean Dennis to Nancy Backus on 09-13-09  09:20 <=-

 SD> Saturday September 12 2009 at 21:34, you wrote to me:
 NB>> Sean, this (without the quoting bit) is how I've seen this message,
 NB>> every packet I've read it in...  It's not as mangled as your reply
 NB>> seemed to indicate, although the message itself does seem to cut off
 NB>> in mid-stream... and the origin line got munged at the end...
 
 MM>> (1:218/*FF2700D9.QQQ 218/1 109

 SD> There's the problem line.  That singular high ASCII character causes
 SD> Telegard to spazz out for some reason, so that's why I'm doing this
 SD> reply in another editor. :)

AhA!  I changed it to a *, this time.  Interestingly enough, this time
around, I noticed that my editor changed it to a control-L which is what
tells my printer that it should go to the next sheet of paper... Maybe
that's why TG spazzes?   And when I tried to read your reply to me, most
bbses (particularly WC boards) just spat it so fast that all I got of
the message was the part starting with the FF2 to the end of what would
have been the first screen.  You must have finally seen the original
message from Matt, at least from my repost, then? 

In BW, the character didn't cause any problems, and it displayed as the
same symbol I see on a few boards at the bottom of a welcome screen just
before it goes to the next screen...  

ttyl        neb

... I don't have a solution but I admire the problem.

___ Blue Wave/QWK v2.20
--- Platinum Xpress/Win/WINServer v3.0pr5