Text 82, 116 rader
Skriven 2006-01-17 23:27:18 av Peter Knapper (3:772/1.10)
     Kommentar till text 80 av Sean Dennis (1:18/200)
Ärende: Re: Problems getting Binkley/2 to answer
================================================
Hi Sean,

PK> Do you have a suitable EVENT covering the phone answering period?

 SD> The only event I have is this one:

 SD> [%Task%==1]
 SD> Event "Loop"     All             00:00 00:00           B

What does Bink show in its "Current Settings" window, Events: field when
running? The Events field is the key to what Bink is able to DO should
something happen...

I also suspect your event data is wrong, as I dont know what your "Loop" value
is trying to do, and the other entries appear to be out of order. Lastly your
times wont work, the END time MUST either not exist at all or be AFTER your
START time (they can't be the same values, thats a 0 time event!!!), and the
highest value for START or END is 23:59, as 24:00 is invalid. If you leave the
END time off altogether, then you get an effective END of 23:59:59

So an all day event line should probably read something like this -

  Event All 00:00 B
    1    2    3   4
Indicating -
        1       An event entry
        2       Execute on all days of the week
        3       Start at midnight and run ALL day
        4       Allow BBS callers during this event


The docs indicate (watch wrapping) -
========================================================================
             The syntax for the entries is:

             Event <day> <start> [<stop>] [<string>] <flags/options>

             Details of these parameters are as follows:

          <day>

             This tells BinkleyTerm which days this event line applies to. This
             is a REQUIRED parameter.  Options are:

                   All      Every day of the week
                   Week.    Weekdays, Monday through Friday only
                   WkEnd    Weekends, Saturday and Sunday only
                   Sun      Sunday only
                   Mon      Monday only
                   Tue      Tuesday only
                   Wed      Wednesday only
                   Thu      Thursday only
                   Fri      Friday only
                   Sat      Saturday only

             Several <day> parameters can be linked with the pipe character (|)
             to indicate more than one option.  For example, "Mon|Wed|Fri"
would
             indicate that the event applies to Monday, Wednesday and Friday
             only.  No spaces may be used between the parameters.

          <start>

             This tells BinkleyTerm what time to start the event, in 24 hour
             "military" time, in the format hh:mm, where hh is the hour and mm
             is the minute.  Note that <start> must NOT be greater than <stop>,
             i.e., events may NOT stretch through the midnight hour.  The
             <start> parameter is REQUIRED.

==================================================================


PK> Assuming your BT/2 below is the OS/2 version, then speeds/errorlevels 
PK> are irrelevant as once its set with Bink, MAXP just inherits the File 
PK> Handle from Bink forthe modem, so it doesn't need to know any speed 
PK> setting at all.

 SD> I'm using Telegard/2, so it picks up the handle too.  
 SD> Here's the problem: when my friend was calling, he 
 SD> didn't see anything-not BT/2 sending out an EMSI 
 SD> string, no banner string (which I have set up).  When 
 SD> he pressed ESC, I actually saw it in BT's modem window 
 SD> as two backarrows.  

Ok, that sounds like no event was active at that time as Bink was not reacting
to anything, so if the events are sorted you should be good for action.


 SD> However, he was using Hyperterminal (yeech).  He did 
 SD> switch to GT Term to try it out also and the same 
 SD> problem occured.

No, forget all this, it sounds fine except for the events.


 SD> PreInit |v``^``ATZ|~
 SD> Init |ATS0=0|~
 SD> Prefix ATDT
 SD> Answer ATA|

Thats fairly standard, so it should be fine, as long as there is an event
telling it to answer the call....

 SD> The weird thing is that I've never had this problem 
 SD> before, but then again, I was using my old BT setup.  
 SD> This is a new one and I haven't had a dialup line in 
 SD> years...

I run BT/2 v2.60 myself, but the Bink 2.60 docs apply to BT-XE for the control
files as they are compatible.

Cheers...........pk.


--- Maximus/2 3.01
 * Origin: Another Good Point About OS/2 (3:772/1.10)