On Mar 20, 1996 at 21:50, Paul Edwards of 3:711/934.9 wrote:

 db>> The next line begins with "error" (for
error-correction), so Bink sees
 db>> that and hangs-up;  unless you're using an unmodified version of Bink
 db>> (likely) that stops reading the "connect string"
after 50 characters or
 db>> so...
 PE>
 PE> What's this 50-characters business?  I didn't notice it in
 PE> Binkley 2.50.  BFN.  Paul.

Date:   1992-12-21 20:16:32
From:   Graham Broadbridge of 3:711/907
To:     David Begley of 3:711/934.4
Subj:   Re: bink and xtended modem codes
Attr:   priv recvd
Area:   NETMAIL

G'day David,

 > Graham, I'm trying to experiment with AT\V9 (ie., return
 > detailed connection status), but during the connection,
 > Bink just hangs up.  As so:

Yep, that's been reported before.

 > # 20 Dec 22:42:52 BINK Terminal      : 19200  No Parity
 > # 20 Dec 22:42:52 BINK Line          :  9600  V.32
 > # 20 Dec 22:42:52 BINK Error Correct : Mnp 4

Seems to me that there are more than 50 characters there, and if I'm reading
the code right (just dug it out :-) Bink only waits 50 characters for a
CONNECT string.

Check out lines 261 - 409 of MDM_PROC.C from the Bink 2.50 sources (tried to
cut'n'paste but the long lines screw everything up :-( )


char *get_response (long end_time)
{
   char *p = response_string;              /* points to character cell
   char c;                                 /* current modem character
   int count = 0;                          /* count of characters

   while ((count < 50)                     /* until we have 50 chars,
          && (!timeup (end_time))          /* or out of time,
          && (!KEYPRESS ()))               /* or user gets impatient
      {
>[...]

Regards,
Graham.

---