After I left my previous message I had a chance to re-review the one you 
wrote to all of here in Meadow. I realized that there was a few points that 
were unclear.
There is an OEC that says IF this person has ansi or avatar do the rest of 
this line.
well, in my expirements with those conditionals. it did not seem to work 
right.
        It was of importance to those of us who wanted to use animated 
bbs screens.
        The Easiest way is to create TWO files. the normal BBS and 
a standard ASCII file perhaps using either *.txt or *.ASC that would be shown 
if the user is not either ansi or avatar graphics.
        We all are aware of the baudrate difficulties with Opus 1.73a 
and new high tech fancy modems. I hope that will be corrected as well 
considering that modems certainly are NOT getting slower. With ISDN around 
the corner for most of the U.S handling whatever rates we get will be of 
importance in the future. I know that standard V5 Fossils are limited to 
38400, thats not our problem, thats X00 and BNU's problem.
        Also reading along I see many want opus to be internetabble. 
Me included. But to be REALLY internetabble we need Freebsd or Linux 2.0.0 or 
later. Some have suggested things like web server type ideas and PPP ideas. 
Let me just give you my side. If opus was available for Linux or freebsd, 
those two things would be easier dealt with as then you just hook into the 
standard OS hooks to allow those features.
        The New boonebase idea for messages is also out of the question. 
no one wants to support it. I use *.MSG and some want Squish or (GASP) 
hudson. Sticking with squish,JAMbase or Hudson or just plain *.MSG might be a 
wise idea. But some have no desire to switch from *.MSG, Opus should allow a 
choice, for those who want to stick with the standard 
*.MSG they should be allows to.
        The File areas should be similar. some like the filesbbs.dat 
system (I kinda do) some what files.bbs. let the users descide which they 
want when they install opus x.xx.
        Now we all know Opus follows the small memory model. and its 
has its advantages. but even my XT has 640K so why not use more than the 128K 
that the small memory model uses? Then we can expand opus with those desired 
and needed improvements while maintainling backwards compatibility.
        Last on my list is door drop files. Opus and its specialized 
lastusxx.dat file is ok but no one really used it. most doors use 
dorinfox.def. or long door.sys how about supporting those as well as the 
standard lastusxx.dat.
        Please pass these along to your development team. I want the 
team to consider Linux and/or freebsd as there is nothing that comes close to 
Opus on those platforms
                                Michele Marie Dalene
--- Opus-CBCS 1.73a
---------------