FB> Actually, {COMMO} sends "~~~+++~~~ATH|" when the driver interface is
Yea it does, my modem is programmed to ignore escape codes due to the fact 
that I user could lock up the board for a while by just typing +++... trust 
e
it does really funny things....
Its also not reliable, everyone adjusts their modems... some modems don't use 
DTR, and so require the +++ATH...  another option for configuration...
FB> You have to use XU to fully activate the FOSSIL.  I'll include a
FB> note in the new beta to that effect.
I was usingg my ONEFOSsil, which contains no BIOS emulator, the fossil must 
e
activated before its used, X00 does not require this, it has BIOS emulation 
n
all the time.  
What I was getting at, is that I think you could also use to support the 
FOSSIL specification a little more completely ALONG WITH the BIOS 
specification.
One reason I would do this a little better is that right now, it is 
mpossible
to pass the baudrate from a BBS to COMMO using the INT14 interface.  One 
reason is that COMMO wants a *? to use INT 14, where the BBS didn't care, it 
always used a FOSSIL, and so passes a baud rate directly... this means that 
the macro author then has to know whether or not he running in direct or int 
14 mode, and then convert accordingly...  Also as I think you noted in the 
text, fossils and the bios have different baudrate settings, and BNU has an 
extension beyond that yet, and X00 and compatibles have a whole set of 
extensions.
anyway, I can't complain, I am just offering suggestions...  I write my own 
FOSSIL driver, and I write libraries for using a FOSSIL in C/C++ code...
--- Renegade v5-11 Exp
---------------