| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | Re: DosDevIOCtl for COM ports |
ML>> what FTS file is that? there is not one that lays out the *.MSG ML>> file format specifically as the FTSC is not concerned with local ML>> storage issues. once again, the only time a "*.MSG" needs an ML>> ending null is when that *.MSG mess is packed inside a PKT file ML>> CG> FTS-0001. see above paragraph > CG> All messages that GEcho tosses end with a NULL. As CG> far as I know, all .MSGs that Squish tosses end with a NULL too. CG> And most of the messages FastEcho tosses end with a NULL as well. these are all written in C... C uses the null, itself, as a terminator. it makes sense > CG> Regardless.. CDRMAIL now adds the NULL there itself, just to be CG> safe. :) good deal... i wrote a program in pascal to add the null for use with programs like wwivgate that are also written in C and expect to find a null as the buffer terminator. > )\/(ark* Origin: (1:3634/12) SEEN-BY: 50/99 270/101 620/243 625/160 711/401 409 410 413 430 808 809 934 SEEN-BY: 711/955 712/407 515 624 628 713/317 800/1 @PATH: 3634/12 170/400 396/1 270/101 712/515 711/808 934 |
|
| SOURCE: echomail via fidonet.ozzmosis.com | |
Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.