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

JD> MH> From what I understand of most of the people porting to *nix is
JD> MH> that they're not even doing comm port routines.  I'd get up with
JD> MH> Stephen Hurd on this for more details, but last I heard they
JD> MH> were just writing/reading to/from standard input/output and
JD> MH> letting the OS/BBS take care of the comm routines so to speak.
JD> MH> Not sure if that makes life easier for you or not....

JD>I hadn't even thought of that.  It's a lot like the old WWIV days
JD>when you'd write just a stdio app and it'd reroute the output for
JD>you.

Exactly......:)  At least from what I've heard.....:)


JD>The only dilemma then becomes what to do with all the sysops not
JD>running a BBS package that provides that.  Do I just move on and
JD>forget supporting FOSSIL and serial communications altogether (man,
JD>would that be nice)?

Well, the above only works from a Unix-like BBS from what I understand.  
As for the serial communications, you could drop the direct serial and 
just go fossil.  Just about anybody still running a DOS based BBS these 
days has a fossil driver installed due to either the BBS or their other 
games requiring it.


JD>I guess it's something I have to experiment with and ask you all your
JD>opinions on.

I would help you out on the fossil thing, but I never did the pascal 
thing......:(  However, I'm sure the loss of fossil support would leave 
a lot of people in the cold.  Is there nothing that can be gleamed off 
the original source?

þ CMPQwk 1.42 1960 þOriginality is the art of concealing your source.

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

--- MirageNet HQ!