ML>> would alter the speed setting of the port and the fossil would
ML>> not know about it. when the system then returned to using the
ML>> fossil, the port and the fossil would be out of sync and you'd
ML>> get nothing but garbage on the screen.

 CG>     Okay.. so if I use DosDevIOCtl, is through the fossil?

honestly, i don't know... i haven't gotten that far... i was simply
imparting information on locking the port with a fossil.

ML>> BTW: you do understand that ending null is not part of the
ML>> *.MSG format, ri
ML>> only part of the packed messages in the PKT file. -=B-)

 CG> Where do you get that information?  The FTS file I have says
 CG> the .MSG format should be NULL terminated.  I'd say 90% of
 CG> the .MSG files I've seen are that way.

what FTS file is that? there is not one that lays out the *.MSG file format
specifically as the FTSC is not concerned with local storage issues. once
again, the only time a "*.MSG" needs an ending null is when that
*.MSG message is packed inside a PKT file 

 CG> Coincidence? :)

yes... very... -=B-)

)\/(ark