TIP: Click on subject to list as thread! ANSI
echo: muffin
to: All
from: Wes Garland
date: 2003-06-08 13:27:14
subject: Maximus/Squish Kludge Line Mystery: Solved

Right from the Horse's Mouth -- "it's not a bug". Can somebody
verify the delinquent behaviour under Max/HPT for non-UNIX and get back to
the Husky team?
 
Here is a snippet from a private e-mail between Scott and myself:
 
wwg> max/me_misc.c -- Always writes \0x01 at the end of the kludge
wwg> lines -- Bo Simonsen is reporting that this appears to be the
wwg> source of the extra empty kludge lines showing up in echomail
wwg> posts originating from Maximus (NT versions, too), but tossed
wwg> with something other than Squish. Comments?
 
sjd> The MsgAPI "control string" is not the same thing as a Fido
sjd> kludge line.  The MsgAPI spec in the Squish developer's kit
sjd> states (at least implicitly in the examples) that the control
sjd> info can end in SOH. (Okay, perhaps this could have been better
sjd> documented in the  original description of the control info.)
 
sjd> If other people are converting control info directly to kludge
sjd> lines, they're not doing it right.  See CvtCtrlToKludge() in
sjd> msgapi\msgapi.c.
 
Cheers,
Wes

--- Maximus/2 3.01
* Origin: COMM Port OS/2 juge.com 204.89.247.1 (281) 980-9671 (1:106/2000)
SEEN-BY: 633/267 270
@PATH: 106/2000 633/267

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™.