Loading ...
Sorry, an error occurred while loading the content.

telnet.dll

Expand Messages
  • Danny PD0SNK
    Hi, i see something about externel telnet.dll port in bpq32.cfg where do i find/get the telnet.dll file ? 73 s Danny PD0SNK
    Message 1 of 10 , Oct 31, 2010
    • 0 Attachment
      Hi,
       
      i see something about externel telnet.dll port in bpq32.cfg
      where do i find/get the telnet.dll file ?
       
      73's Danny PD0SNK
    • John Wiseman
      Danny, You don t!. Athough it is configured as if it was an external .dll, it is build into the latest released bpq32.dll 73 John ... From:
      Message 2 of 10 , Oct 31, 2010
      • 0 Attachment
        Message
        Danny,
         
        You don't!. Athough it is configured as if it was an external .dll, it is build into the latest released bpq32.dll
         
        73
        John
         
        -----Original Message-----
        From: BPQ32@yahoogroups.com [mailto:BPQ32@yahoogroups.com] On Behalf Of Danny PD0SNK
        Sent: 31 October 2010 21:06
        To: bpq32@yahoogroups.com
        Subject: [BPQ32] telnet.dll

         

        Hi,
         
        i see something about externel telnet.dll port in bpq32.cfg
        where do i find/get the telnet.dll file ?
         
        73's Danny PD0SNK

      • Dave Webb AFA2HV
        Where is the $MID getting lost? The two logs are from 2 BPQ systems. First contact was a Forward from MSYS to BPQ, the second was BPQ to BPQ. Dave wb2hvf
        Message 3 of 10 , Oct 31, 2010
        • 0 Attachment
          Where is the $MID getting lost?
          The two logs are from 2 BPQ systems. First contact was a Forward from MSYS to BPQ, the second was BPQ to BPQ.

          Dave wb2hvf


          101031 20:41:20 >AFC2MC-4  [BPQ-1.0.4.24-BFH$]
          101031 20:41:20 >AFC2MC-4 
          101031 20:41:20 >AFC2MC-4  de AFC2MC>
          101031 20:41:26 <AFC2MC-4  [MSYS-1.20beta4-HI$]
          101031 20:41:26 >AFC2MC-4  >
          101031 20:41:30 <AFC2MC-4  SB PROP @ SOLAR < AFB2MC
          101031 20:41:30 >AFC2MC-4  OK
          101031 20:41:39 <AFC2MC-4  PROPAGATION BULLETIN NR-43
          101031 20:41:42 <AFC2MC-4  R:101031/2054z 21925@... $:ARLP_10043
          --------------------------------------------------------------------------------------------------------------------------------------
          101031 23:29:40 <AFC2MC    WRI:AFC2MC-2} Connected to BBS
          101031 23:29:40 <AFC2MC    [BPQ-1.0.4.24-B2FH$]
          101031 23:29:40 <AFC2MC    de AFC2MC>
          101031 23:29:40 >AFC2MC    [BPQ-1.0.4.24-B2FH$]
          101031 23:29:40 >AFC2MC    FF
          101031 23:29:41 <AFC2MC    FC EM 163_AFC2MC 2688 1424 0
          101031 23:29:41 <AFC2MC    F> E0
          101031 23:29:41 >AFC2MC    FS Y
          101031 23:29:43 |AFC2MC    Uncompressing Message Comp Len 1424 Msg Len 2688 CRC e43f
          101031 23:29:43 ?AFC2MC    B2 Msg To: PROP@SOLAR
          1
        • Peter - ZL2BAU
          ... Hi, If the Bulletin below is the correct one as above, then there appears to be a big big problem. My systems here are, xFBB Linux BBS and BPQMailChat.
          Message 4 of 10 , Oct 31, 2010
          • 0 Attachment
            On 01/11/10 12:58, Dave Webb AFA2HV wrote:
             

            Where is the $MID getting lost?
            The two logs are from 2 BPQ systems. First contact was a Forward from MSYS to BPQ, the second was BPQ to BPQ.

            Dave wb2hvf


            101031 20:41:20 >AFC2MC-4  [BPQ-1.0.4.24-BFH$]
            101031 20:41:20 >AFC2MC-4 
            101031 20:41:20 >AFC2MC-4  de AFC2MC>
            101031 20:41:26 <AFC2MC-4  [MSYS-1.20beta4-HI$]
            101031 20:41:26 >AFC2MC-4  >
            101031 20:41:30 <AFC2MC-4  SB PROP @ SOLAR < AFB2MC
            101031 20:41:30 >AFC2MC-4  OK
            101031 20:41:39 <AFC2MC-4  PROPAGATION BULLETIN NR-43
            101031 20:41:42 <AFC2MC-4  R:101031/2054z 21925@... $:ARLP_10043
            --------------------------------------------------------------------------------------------------------------------------------------
            101031 23:29:40 <AFC2MC    WRI:AFC2MC-2} Connected to BBS
            101031 23:29:40 <AFC2MC    [BPQ-1.0.4.24-B2FH$]
            101031 23:29:40 <AFC2MC    de AFC2MC>
            101031 23:29:40 >AFC2MC    [BPQ-1.0.4.24-B2FH$]
            101031 23:29:40 >AFC2MC    FF
            101031 23:29:41 <AFC2MC    FC EM 163_AFC2MC 2688 1424 0
            101031 23:29:41 <AFC2MC    F> E0
            101031 23:29:41 >AFC2MC    FS Y
            101031 23:29:43 |AFC2MC    Uncompressing Message Comp Len 1424 Msg Len 2688 CRC e43f
            101031 23:29:43 ?AFC2MC    B2 Msg To: PROP@SOLAR

            ,_.___


            Hi,

                If the Bulletin below is the correct one as above, then there appears to be a big big problem.

            My systems here are, xFBB Linux BBS and BPQMailChat.

            Regards ..... Peter


             
            * BPQMailChat *
            ---------------
             
            [BPQ-1.0.4.23-BFH$]
            Hello Peter. Latest Message Is 25904, Last Listed Is 25283
            de ZL2BAU>
            l> prop
            25801  29-Oct BN    5334 PROP   @ARL    CX2SA  ARLP043 Propagation de K7RA
            de ZL2BAU>
             
            From: CX2SA
            To: PROP
            Type/Status: BN
            Date/Time: 29-Oct 21:45Z
            Bid: ARLP043
            Title: ARLP043 Propagation de K7RA
             
            R:101029/2234Z 25783@N4JOA.#WPBFL.FL.USA.NOAM BPQ1.0.4
            R:101029/2207Z @:N4JOA.#WPBFL.FL.USA.NOAM #:18498 $:ARLP043
            R:101029/2204Z @:N9ZZK.#CIL.IL.USA.NOAM #:48658 [DIAMOND, IL.] FBB7.00e
            R:101029/2228Z @:CT1EJC.CTST.PRT.EU #:63999 XFBB7.04j Bid:ARLP043
            R:101029/2145Z @:CX2SA.LAV.URY.SA #:28807 [Minas] FBB7.00e $:ARLP043
             
            From: CX2SA@...
            To  : PROP@ARL
             
            ZCZC AP43
            QST de W1AW
            Propagation Forecast Bulletin 43  ARLP043
             
             
            * From XFBB Linux System *
            --------------------------
             
            From        : CX2SA
            To          : PROP@ARL
            Type/Status : BF
            Date/Time   : 30-Oct 10:56
            BID (MID)   : ARLP043
            Message #   : 406589
            Title       : ARLP043 Propagation de K7RA
             
            R:101029/2255Z @:ON0BEL.#LG.BEL.EU #:250 [BBS-Belgium WFBB] $:ARLP043
            R:101029/2145Z @:CX2SA.LAV.URY.SA #:28807 [Minas] FBB7.00e $:ARLP043
             
            From: CX2SA@...
            To  : PROP@ARL
             
             
            ZCZC AP43
            QST de W1AW
            Propagation Forecast Bulletin 43  ARLP043
            From Tad Cook, K7RA
            Seattle, WA  October 29, 2010
            To all radio amateurs
             
            SB PROP ARL ARLP043
            ARLP043 Propagation de K7RA
             









          • Dave Webb AFA2HV
            $:ARLP_10043 Would be the correct $MID for the AFMARS system and is not refiled to the ham network. That is not the problem. The change of bid from ARLP_10043
            Message 5 of 10 , Oct 31, 2010
            • 0 Attachment
              $:ARLP_10043 Would be the correct $MID for the AFMARS system and is not refiled to the ham network. That is not the problem. The change of bid from ARLP_10043 to 163_AFC2MC is what I am concerned with. That still is a BIG problem. The 10xxx is for the year.
              73 Dave


              On 10/31/2010 8:54 PM, Peter - ZL2BAU wrote:
               

              On 01/11/10 12:58, Dave Webb AFA2HV wrote:

               

              Where is the $MID getting lost?
              The two logs are from 2 BPQ systems. First contact was a Forward from MSYS to BPQ, the second was BPQ to BPQ.

              Dave wb2hvf


              101031 20:41:20 >AFC2MC-4  [BPQ-1.0.4.24-BFH$]
              101031 20:41:20 >AFC2MC-4 
              101031 20:41:20 >AFC2MC-4  de AFC2MC>
              101031 20:41:26 <AFC2MC-4  [MSYS-1.20beta4-HI$]
              101031 20:41:26 >AFC2MC-4  >
              101031 20:41:30 <AFC2MC-4  SB PROP @ SOLAR < AFB2MC
              101031 20:41:30 >AFC2MC-4  OK
              101031 20:41:39 <AFC2MC-4  PROPAGATION BULLETIN NR-43
              101031 20:41:42 <AFC2MC-4  R:101031/2054z 21925@... $:ARLP_10043
              --------------------------------------------------------------------------------------------------------------------------------------
              101031 23:29:40 <AFC2MC    WRI:AFC2MC-2} Connected to BBS
              101031 23:29:40 <AFC2MC    [BPQ-1.0.4.24-B2FH$]
              101031 23:29:40 <AFC2MC    de AFC2MC>
              101031 23:29:40 >AFC2MC    [BPQ-1.0.4.24-B2FH$]
              101031 23:29:40 >AFC2MC    FF
              101031 23:29:41 <AFC2MC    FC EM 163_AFC2MC 2688 1424 0
              101031 23:29:41 <AFC2MC    F> E0
              101031 23:29:41 >AFC2MC    FS Y
              101031 23:29:43 |AFC2MC    Uncompressing Message Comp Len 1424 Msg Len 2688 CRC e43f
              101031 23:29:43 ?AFC2MC    B2 Msg To: PROP@SOLAR

              ,_.___


              Hi,

                  If the Bulletin below is the correct one as above, then there appears to be a big big problem.

              My systems here are, xFBB Linux BBS and BPQMailChat.

              Regards ..... Peter


               
              * BPQMailChat *
              ---------------
               
              [BPQ-1.0.4.23-BFH$]
              Hello Peter. Latest Message Is 25904, Last Listed Is 25283
              de ZL2BAU>
              l> prop
              25801  29-Oct BN    5334 PROP   @ARL    CX2SA  ARLP043 Propagation de K7RA
              de ZL2BAU>
               
              From: CX2SA
              To: PROP
              Type/Status: BN
              Date/Time: 29-Oct 21:45Z
              Bid: ARLP043
              Title: ARLP043 Propagation de K7RA
               
              R:101029/2234Z 25783@N4JOA.#WPBFL.FL.USA.NOAM BPQ1.0.4
              R:101029/2207Z @:N4JOA.#WPBFL.FL.USA.NOAM #:18498 $:ARLP043
              R:101029/2204Z @:N9ZZK.#CIL.IL.USA.NOAM #:48658 [DIAMOND, IL.] FBB7.00e
              R:101029/2228Z @:CT1EJC.CTST.PRT.EU #:63999 XFBB7.04j Bid:ARLP043
              R:101029/2145Z @:CX2SA.LAV.URY.SA #:28807 [Minas] FBB7.00e $:ARLP043
               
              From: CX2SA@...
              To  : PROP@ARL
               
              ZCZC AP43
              QST de W1AW
              Propagation Forecast Bulletin 43  ARLP043
               
               
              * From XFBB Linux System *
              --------------------------
               
              From        : CX2SA
              To          : PROP@ARL
              Type/Status : BF
              Date/Time   : 30-Oct 10:56
              BID (MID)   : ARLP043
              Message #   : 406589
              Title       : ARLP043 Propagation de K7RA
               
              R:101029/2255Z @:ON0BEL.#LG.BEL.EU #:250 [BBS-Belgium WFBB] $:ARLP043
              R:101029/2145Z @:CX2SA.LAV.URY.SA #:28807 [Minas] FBB7.00e $:ARLP043
               
              From: CX2SA@...
              To  : PROP@ARL
               
               
              ZCZC AP43
              QST de W1AW
              Propagation Forecast Bulletin 43  ARLP043
              >From Tad Cook, K7RA
              Seattle, WA  October 29, 2010
              To all radio amateurs
               
              SB PROP ARL ARLP043
              ARLP043 Propagation de K7RA
               









            • Peter - ZL2BAU
              ... Hi Dave, Well I guess you have to work out where it`s being changed, is it your MSYS BBS making the change on the forward of the message or is it
              Message 6 of 10 , Oct 31, 2010
              • 0 Attachment
                On 01/11/10 15:23, Dave Webb AFA2HV wrote:
                 

                $:ARLP_10043 Would be the correct $MID for the AFMARS system and is not refiled to the ham network. That is not the problem. The change of bid from ARLP_10043 to 163_AFC2MC is what I am concerned with. That still is a BIG problem. The 10xxx is for the year.
                73 Dave


                .



                Hi Dave,

                             Well I guess you have to work out where it`s being changed, is it your MSYS BBS making the change on the forward of the message or is it BPQMailChat making the change on decompression ?

                Does this happen to *all* mail, MSYS <> BPQMailChat or just certain ones ?

                Have you tried going back one version of BPQMailChat, I note you are running 1.0.4.24 ?

                Did this happen with 1.0.4.23 ?

                Maybe something to do with *B2* ?

                Regards ..... Peter



              • Dave Webb AFA2HV
                Thanks for the ideas Peter. I ll look into those. 73 Dave
                Message 7 of 10 , Oct 31, 2010
                • 0 Attachment
                  Thanks for the ideas Peter. I'll look into those.
                  73
                  Dave


                  On 10/31/2010 11:55 PM, Peter - ZL2BAU wrote:
                   

                  On 01/11/10 15:23, Dave Webb AFA2HV wrote:

                   

                  $:ARLP_10043 Would be the correct $MID for the AFMARS system and is not refiled to the ham network. That is not the problem. The change of bid from ARLP_10043 to 163_AFC2MC is what I am concerned with. That still is a BIG problem. The 10xxx is for the year.
                  73 Dave


                  .



                  Hi Dave,

                               Well I guess you have to work out where it`s being changed, is it your MSYS BBS making the change on the forward of the message or is it BPQMailChat making the change on decompression ?

                  Does this happen to *all* mail, MSYS <> BPQMailChat or just certain ones ?

                  Have you tried going back one version of BPQMailChat, I note you are running 1.0.4.24 ?

                  Did this happen with 1.0.4.23 ?

                  Maybe something to do with *B2* ?

                  Regards ..... Peter



                • John Wiseman
                  Dave, MSYS isn t providing a MID/BID. It should come after the from call - SB PROP @ SOLAR
                  Message 8 of 10 , Nov 1, 2010
                  • 0 Attachment
                    Message
                    Dave,
                     
                    MSYS isn't providing a MID/BID. It should come after the from call   -
                     
                    SB PROP @ SOLAR < AFB2MC $MID
                     
                    73  John
                     

                    -----Original Message-----
                    From: BPQ32@yahoogroups.com [mailto:BPQ32@yahoogroups.com] On Behalf Of Dave Webb AFA2HV
                    Sent: 31 October 2010 23:59
                    To: BPQ32@yahoogroups.com
                    Subject: [BPQ32] $MID changes.

                     

                    Where is the $MID getting lost?
                    The two logs are from 2 BPQ systems. First contact was a Forward from MSYS to BPQ, the second was BPQ to BPQ.

                    Dave wb2hvf


                    101031 20:41:20 >AFC2MC-4  [BPQ-1.0.4.24-BFH$]
                    101031 20:41:20 >AFC2MC-4 
                    101031 20:41:20 >AFC2MC-4  de AFC2MC>
                    101031 20:41:26 <AFC2MC-4  [MSYS-1.20beta4-HI$]
                    101031 20:41:26 >AFC2MC-4  >
                    101031 20:41:30 <AFC2MC-4  SB PROP @ SOLAR < AFB2MC
                    101031 20:41:30 >AFC2MC-4  OK
                    101031 20:41:39 <AFC2MC-4  PROPAGATION BULLETIN NR-43
                    101031 20:41:42 <AFC2MC-4  R:101031/2054z 21925@... $:ARLP_10043
                    --------------------------------------------------------------------------------------------------------------------------------------
                    101031 23:29:40 <AFC2MC    WRI:AFC2MC-2} Connected to BBS
                    101031 23:29:40 <AFC2MC    [BPQ-1.0.4.24-B2FH$]
                    101031 23:29:40 <AFC2MC    de AFC2MC>
                    101031 23:29:40 >AFC2MC    [BPQ-1.0.4.24-B2FH$]
                    101031 23:29:40 >AFC2MC    FF
                    101031 23:29:41 <AFC2MC    FC EM 163_AFC2MC 2688 1424 0
                    101031 23:29:41 <AFC2MC    F> E0
                    101031 23:29:41 >AFC2MC    FS Y
                    101031 23:29:43 |AFC2MC    Uncompressing Message Comp Len 1424 Msg Len 2688 CRC e43f
                    101031 23:29:43 ?AFC2MC    B2 Msg To: PROP@SOLAR
                    1

                  • Mike Melnik
                    If I recall right the option MID has to be set in the .DO file Mike Melnik-N9PMO Web WWW.N9PMO.com Group Moderator http://groups.yahoo.com/group/BPQ32/ ...
                    Message 9 of 10 , Nov 1, 2010
                    • 0 Attachment
                      If I recall right the option MID has to be set in the .DO file

                      Mike Melnik-N9PMO
                      Web WWW.N9PMO.com
                      Group Moderator http://groups.yahoo.com/group/BPQ32/
                      -----Original Message-----
                      From: BPQ32@yahoogroups.com [mailto:BPQ32@yahoogroups.com] On Behalf Of John
                      Wiseman
                      Sent: Monday, November 01, 2010 4:22 AM
                      To: BPQ32@yahoogroups.com
                      Subject: RE: [BPQ32] $MID changes.




                      Dave,
                       
                      MSYS isn't providing a MID/BID. It should come after the from call   -
                       
                      SB PROP @ SOLAR < AFB2MC $MID
                       
                      73  John
                       

                      -----Original Message-----
                      From: BPQ32@yahoogroups.com [mailto:BPQ32@yahoogroups.com] On Behalf Of Dave
                      Webb AFA2HV
                      Sent: 31 October 2010 23:59
                      To: BPQ32@yahoogroups.com
                      Subject: [BPQ32] $MID changes.
                       
                      Where is the $MID getting lost?
                      The two logs are from 2 BPQ systems. First contact was a Forward from MSYS
                      to BPQ, the second was BPQ to BPQ.

                      Dave wb2hvf


                      101031 20:41:20 >AFC2MC-4  [BPQ-1.0.4.24-BFH$]
                      101031 20:41:20 >AFC2MC-4 
                      101031 20:41:20 >AFC2MC-4  de AFC2MC>
                      101031 20:41:26 <AFC2MC-4  [MSYS-1.20beta4-HI$]
                      101031 20:41:26 >AFC2MC-4  >
                      101031 20:41:30 <AFC2MC-4  SB PROP @ SOLAR < AFB2MC
                      101031 20:41:30 >AFC2MC-4  OK
                      101031 20:41:39 <AFC2MC-4  PROPAGATION BULLETIN NR-43
                      101031 20:41:42 <AFC2MC-4  R:101031/2054z 21925@...
                      $:ARLP_10043
                      ----------------------------------------------------------------------------
                      ----------------------------------------------------------
                      101031 23:29:40 <AFC2MC    WRI:AFC2MC-2} Connected to BBS
                      101031 23:29:40 <AFC2MC    [BPQ-1.0.4.24-B2FH$]
                      101031 23:29:40 <AFC2MC    de AFC2MC>
                      101031 23:29:40 >AFC2MC    [BPQ-1.0.4.24-B2FH$]
                      101031 23:29:40 >AFC2MC    FF
                      101031 23:29:41 <AFC2MC    FC EM 163_AFC2MC 2688 1424 0
                      101031 23:29:41 <AFC2MC    F> E0
                      101031 23:29:41 >AFC2MC    FS Y
                      101031 23:29:43 |AFC2MC    Uncompressing Message Comp Len 1424 Msg Len 2688
                      CRC e43f
                      101031 23:29:43 ?AFC2MC    B2 Msg To: PROP@SOLAR
                      1
                    • Dave Webb AFA2HV
                      Turns out the problem was in the protocol used in forwarding. Once I checked the allow binary switch in the BPQ forwarding configuration (not B1 or B2) the
                      Message 10 of 10 , Nov 1, 2010
                      • 0 Attachment
                        Turns out the problem was in the protocol used in forwarding. Once I checked the allow binary switch in the BPQ forwarding configuration (not B1 or B2)  the problem went away.
                        Thank you for all your suggestions.
                        73
                        Dave


                        On 11/1/2010 8:21 PM, Mike Melnik wrote:
                         

                        If I recall right the option MID has to be set in the .DO file

                        MIDchar is set to "M"


                        Mike Melnik-N9PMO
                        Web WWW.N9PMO.com
                        Group Moderator http://groups.yahoo.com/group/BPQ32/
                        -----Original Message-----
                        From: BPQ32@yahoogroups.com [mailto:BPQ32@yahoogroups.com] On Behalf Of John
                        Wiseman
                        Sent: Monday, November 01, 2010 4:22 AM
                        To: BPQ32@yahoogroups.com
                        Subject: RE: [BPQ32] $MID changes.

                        Dave,
                         
                        MSYS isn't providing a MID/BID. It should come after the from call   -
                         
                        SB PROP @ SOLAR < AFB2MC $MID
                         
                        73  John
                         

                        -----Original Message-----
                        From: BPQ32@yahoogroups.com [mailto:BPQ32@yahoogroups.com] On Behalf Of Dave
                        Webb AFA2HV
                        Sent: 31 October 2010 23:59
                        To: BPQ32@yahoogroups.com
                        Subject: [BPQ32] $MID changes.
                         
                        Where is the $MID getting lost?
                        The two logs are from 2 BPQ systems. First contact was a Forward from MSYS
                        to BPQ, the second was BPQ to BPQ.

                        Dave wb2hvf

                        101031 20:41:20 >AFC2MC-4  [BPQ-1.0.4.24-BFH$]
                        101031 20:41:20 >AFC2MC-4 
                        101031 20:41:20 >AFC2MC-4  de AFC2MC>
                        101031 20:41:26 <AFC2MC-4  [MSYS-1.20beta4-HI$]
                        101031 20:41:26 >AFC2MC-4  >
                        101031 20:41:30 <AFC2MC-4  SB PROP @ SOLAR < AFB2MC
                        101031 20:41:30 >AFC2MC-4  OK
                        101031 20:41:39 <AFC2MC-4  PROPAGATION BULLETIN NR-43
                        101031 20:41:42 <AFC2MC-4  R:101031/2054z 21925@...
                        $:ARLP_10043
                        ----------------------------------------------------------
                        ----------------------------------------------------------
                        101031 23:29:40 <AFC2MC    WRI:AFC2MC-2} Connected to BBS
                        101031 23:29:40 <AFC2MC    [BPQ-1.0.4.24-B2FH$]
                        101031 23:29:40 <AFC2MC    de AFC2MC>
                        101031 23:29:40 >AFC2MC    [BPQ-1.0.4.24-B2FH$]
                        101031 23:29:40 >AFC2MC    FF
                        101031 23:29:41 <AFC2MC    FC EM 163_AFC2MC 2688 1424 0
                        101031 23:29:41 <AFC2MC    F> E0
                        101031 23:29:41 >AFC2MC    FS Y
                        101031 23:29:43 |AFC2MC    Uncompressing Message Comp Len 1424 Msg Len 2688
                        CRC e43f
                        101031 23:29:43 ?AFC2MC    B2 Msg To: PROP@SOLAR
                        1

                      Your message has been successfully submitted and would be delivered to recipients shortly.