ML>> just to clarify... EMSI is mailer to mailer... IEMSI is
ML>> Interactive and terminal to bbs... there's a very
ML>> important distinction there... hummm... i think i
ML>> understand, now, where this thread started but i don't
ML>> know if anything can be done about it... part of the
ML>> "problem" is likely from the bbs side and the order in
ML>> which it detects ANSI and sends the IEMSI trigger...

 TJM> FD 2.12 (which one of my nodes just setup), does not
 TJM> display the IEMSI crap to the screen.

ok, like i stated earlier, this is likely because FD v2.12's terminal
specifically hides it... no other terminal does or did... only FD 2.12's,
apparently...

 TJM> Anyone with 2.3x it does.

possibly an oversight in the complete rewrite... then again, joho and mats
were streamlining a lot of stuff... this might just have been one of those
"its not really needed" things that was not put back in... kinda
like many of the "fixing other people's foulups" stuff that
wasn't put back in... that lead to a lot of stuff being fixed all over the
network since it was "suddenly" visible to everyone and not just
the developers and beta members ;)

 TJM> I just wish there was a way to black it out.

no, there's not... not unless you can set something in the terminal to do
it... that is apparently something that FD v2.12's terminal does but no
other... i know that telix, qmodem, procomm, hyperterm, ZOC, and {COMMO}
don't...

 TJM> That's all I said.  I have no idea how THIS thread
 TJM> got started. ;)

hehehe, trying to figure out exactly what was being discussed (EMSI or
IEMSI) and where the effect you have seen and desire would be being
implemented... other than that, its been great talking about FD again after
all these years of no traffic in here... i'd love to see more! ;)

)\/(ark