FB> About the only change in that area was that {COMMO} now
  > hooks INT 61h to use for the "other copy running" test.
  > Do you know if any of your programs use INT 61h?
 Checked the 4DOS24H2 docs, and it says
 If 4DOS24H2 seems to load a new copy of itself into memory every
 time you make a shell (and thereby wasting useful memory) you
 may have loaded a resident program (TSR) which interferes with
 4DOS24H2.  [...]  The trouble might be that for some purpose your
 TSR uses interrupt 61h.  4DOS24H2 itself uses interrupt vector
 61h to see if it is already installed and can not identify
 itself in memory if this interrupt is hooked by some TSR after
 installation of 4DOS24H2.
FB> The only time the strings should display is when the
  > emulation is set to TTY (when you're offline the strings
  > are being echoed by the modem).  Your macro sets the
  > emulation to "A".  Does that mean you're in TTY initially?
 Yes, because it defeats those annoying tests where a BBS assumes
 that simply because you *can* handle color, you want color,
 which I rarely waste time with.  The new modem defaults to echo
 on, and I hadn't gotten around to changing it.  Hadn't noticed
 that TTY echoes and ANSI doesn't before.
... Reality is merely an illusion, albeit a very persistent one. * Einstein
-+- OLMS 2.53 UNREG
---
---------------