PC>>  CG> And if a port is "locked", do you have to
"unlock" it
PC>>  CG> before you can  change the rate, then do you have to
PC>>  CG> "relock" it?

PC>> I'm lost here, I use SIO which locks the port.

 CG>     So do I.  My question was from a programs standpoint.  SIO
 CG> locks the port, yes.  When you tell it to change the port rate,
 CG> and it's already locked, does SIO unlock, then change it, then
 CG> lock it, or does it just change it, and it stays locked?  So if
 CG> it was locked, by SIO, and I changed it to a new value, would
 CG> it still be locked?

if the port is locked then it is locked. NOTHING can change it via the
fossil/ comm driver... only by going around to the hardware door and doing
it there. that's why, in the DOS world, there has been so many problems
with external BBS doors that use the fossil and those that do not... many
of those that do not would alter the speed setting of the port and the
fossil would not know about it. when the system then returned to using the
fossil, the port and the fossil would be out of sync and you'd get nothing
but garbage on the screen.

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

)\/(ark