JD>* In a message originally to John Dailey, Mark Hoover said:

JD> MH> This is probably why I never wrote a door.  Couldn't find any
JD> MH> instructions on doing the fossil/comm stuff.

JD>:) I know exactly what you mean.  The hard part is getting a solid
JD>communications base that WORKS first.  The rest (managing
JD>input/output) is a piece of cake.  Like I said earlier, in the past,
JD>I've had commercial products that took care of the dirty work.

There's got to be something out there somewhere.  Just don't know since 
I'm not a Pascal person....:(




JD> MH> JD> I'm ready to say "too hell with FOSSIL and
DOS/16bit" at
JD> MH> this point. As much as I can't help with the programming, I for
JD> MH> one would like to beg you not to do this.  My landline system
JD> MH> still runs DOS and a dialup modem and this is where I run all my
JD> MH> leagues from.....:(

JD>I know there are a lot of systems out there still running this way,
JD>which makes it all the more challenging.  I want to find a solution
JD>that allows me to maintain a single code-base that can be compiled
JD>for multiple targets like DOS/Win/etc.

JD>If I could get the FOSSIL portion of EleCom to work, my problem would
JD>be solved.

I'm assuming you're using some sort of abstration functions to seperate 
the BBS code from the i/o code right?  If you code to those functions 
and then just have the underlying code call out to the appropriate 
communications routines.  Doing something like this should make it easy 
to call the original fossil/serial routines for DOS.  stdio for Unix-
like OSs, EleCom for whatever.....

þ CMPQwk 1.42 1960 þVegetarians eat vegetables-Beware of humanitarians

~~~ Telegard/QWK v3.09.g2-sp4/mL

--- MirageNet HQ!