Hi Carl.
> The first problem is int14 is not the same as a fossil....
I understand.  But, in this case the int14 interface for commo will let
{commo} talk to a fossil and to a program called tcpport wich uses
int14.
remember x00 is 
> only providing bios compatbility...
That has some truth but, the x00 as well as bnu etc provide extra
functions / features as well.
> I have foud that when running on int14 commo can't hang up the modem 
ithout
> crashing the window...  thats liky because the int14 interface of an ibm pc 
> does not contain a function to control the dtr line, nor the cts/rts lines 
> (which ever... I think its rts)...  so now if he gave true fossil support 
> without requiring the *x then everything would work  fine...
That is also true.  But, who is saying he is providing true fossil
support?
I think he is making {commo} talk to int14 smart programs.
He He has a basic implementation no question.  But, in time he can and
may add support for many things.
Now how exactly do we define a fossil driver?
The drivers are far different from the way they started... Just like the
ibm pc to the computers today are not nearly the same.
sure some of the core things are but, much different.
> And since I write a FOSSIL driver ... if Fred wants any notes on how to 
ake
> the most use of a fossil driver ... just let him write me...
How do I let him write you?
I mean he's a great programmer and he's more than capable of getting any
info he wants.
All I ment to say in my last post was that Fred has done a great job for
the first beta of int14 support.
If you think you can do a better job I issue the challenge!
Sam
-!- MacroBBS 4.0 using {COMMO} 6.6a BETA TEST RELEASE
 ! Origin: LIBERTY BELL LET FREEDOM RING! (m4A)
--- Blue Wave/DOS v2.30
---------------