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

BPQ32_6.0.2.1_20130608 including BPQMail, BPQChat and BPQAPRS is now available

Expand Messages
  • n5in_ron
    A new release, BPQ32_6.0.2.1_20130608, for Windows, is available for download at: http://groups.yahoo.com/group/BPQ32/.
    Message 1 of 6 , Jun 7, 2013
    • 0 Attachment
      A new release, BPQ32_6.0.2.1_20130608, for Windows, is available for download at: http://groups.yahoo.com/group/BPQ32/.

      A special notice for CMS users is appended at the end of this release announcement.

      John Wiseman, G8BPQ, has created a common code base for BPQ32 allowing both Windows (BPQ32) and Linux (LinBPQ) versions to be produced.

      This release updates BPQ32.dll, BPQMailChat, and AGWtoBPQ.

      BPQMail (a BBS system) and BPQChat (a Chat system) replaces BPQMailChat.

      BPQMailChat is still provided, and can be used for mail, but it will likely be dropped from the next release. The provided shortcuts for BPQMailChat actually point to BPQMail with the goal of easing the transition.

      BPQ32 now has a basic Web Interface option. This provides Browser access to some node status displays, and a simple Web Terminal for access to the Network. It can also act as Web Server for other BPQ32 Applications, such as BPQAPRS

      BPQAPRS is an APRS mapping and messaging application first introduced in BPQ32_5.2.4.1_20120130. BPQAPRS at its current state of development is a viable replacement for UIView32 for many users and in addition is under active development to add additional capability. The BPQ32 digipeater is "New n-N Paradigm " compliant and provides enough objects to fully support the Local Info Initiative. A configuration example is provided to quickly get you 'on the air'. The BPQAPRS program provides mapping using the on-line OpenStreetMap and reliable messaging, to the degree this is possible, with the existing infrastructure.

      As a reminder, you must have all of your node configuration in BPQ32.cfg.

      BPQ32_5.2.1.3_20111018,was the last to support both the new method, all the node configuration statements combined into BPQ32.cfg, as well as the old method of separate configuration files. If you currently have separate config files, a smooth transition to the new system would be to first install BPQ32_5.2.1.3_20111018, which you can find in the links section of the BPQ32 Yahoo Group, and make the changes to your configuration using that version. Once successful, the subsequent upgrade to BPQ32_5.2.9.1_20120925 followed by BPQ32_6.0.2.1_20130608 should proceed with ease.

      My installer is also capable of converting an existing non-compliant installation to a Microsoft compliant installation. In brief, Microsoft has been, since the introduction of Windows XP, recommending that an installation be split in to a "program files" part and an "application data" part. This was not enforced in Windows XP but it is being enforced in Vista and Windows 7. Many programs have been installed in the root, such as C:\Ham Programs to get around this recommendation, but the result is annoying UAC popups...'do you really trust this program' etc. If you have used this workaround, you can, after installing this most recent release, do an uninstall, which will preserve your configuration, and then do a reinstall taking all the defaults. The result will be to divide your installation properly into %programfiles%\bpq32 and %appdata%\bpq32.

      Help will be available in the users group should you have questions.

      The changelog is here:
      http://www.cantab.net/users/john.wiseman/Documents/BPQ32%20Installation.htm#Changelog

      Special notice to CMS users:

      If you use BPQ32 or LinBPQ to access the CMS Servers via the "CMS Telnet" feature, this will not work after
      30th June 2013 unless you enable the Secure Login Mechanism. This version of BPQ32 supports Secure Login

      To enable Secure Login you need to add two lines to your Telnet Server Config.

      CMSCALL=CALLSIGN ; CMS Access Callsign (with SSID if used)
      CMSPASS=XXXXXXX ; Secure CMS Password

      CMSCALL should be set to the callsign+ssid used to access the RMS Gateway
      CMSPASS is your Secure Signon Password. This is the same as your winlink.org webmail password - if you don't
      already have one or have forgotten it, see http://www.winlink.org/WMInstructions for details of how to retrieve
      your password, or set one if you don't have one,

      All gateway stations also need to be authorised by the WL2K team. Gateways that were active when the new system
      was first introduced should have been enabled automatically, but if not you may need to request access.

      If you can't access the CMS after enabling Secure Access check the CMSAccess_yyyymmdd.log file in your BPQ32
      folder for any error messages.

      John G8BPQ
      June 2013


      Thanks to John Wiseman G8BPQ/GM8BPQ for his tireless work enhancing BPQ32!

      73 de Ron Stordahl, AE5E (ex N5IN)

    • Jerry
      Thanks for all the hard work John and Ron... I also appreciate what Ryan and You did for me this past week or so. 73 Jerry From: BPQ32@yahoogroups.com
      Message 2 of 6 , Jun 7, 2013
      • 0 Attachment

        Thanks for all the hard work  John and Ron….. I also appreciate what Ryan and You did for me this past week or so…

         

         

         

        73 Jerry

         

        From: BPQ32@yahoogroups.com [mailto:BPQ32@yahoogroups.com] On Behalf Of n5in_ron
        Sent: Friday, June 7, 2013 6:00 PM
        To: BPQ32@yahoogroups.com
        Subject: [BPQ32] BPQ32_6.0.2.1_20130608 including BPQMail, BPQChat and BPQAPRS is now available

         

         

        A new release, BPQ32_6.0.2.1_20130608, for Windows, is available for download at: http://groups.yahoo.com/group/BPQ32/.

        A special notice for CMS users is appended at the end of this release announcement.

        John Wiseman, G8BPQ, has created a common code base for BPQ32 allowing both Windows (BPQ32) and Linux (LinBPQ) versions to be produced.

        This release updates BPQ32.dll, BPQMailChat, and AGWtoBPQ.

        BPQMail (a BBS system) and BPQChat (a Chat system) replaces BPQMailChat.

        BPQMailChat is still provided, and can be used for mail, but it will likely be dropped from the next release. The provided shortcuts for BPQMailChat actually point to BPQMail with the goal of easing the transition.

        BPQ32 now has a basic Web Interface option. This provides Browser access to some node status displays, and a simple Web Terminal for access to the Network. It can also act as Web Server for other BPQ32 Applications, such as BPQAPRS

        BPQAPRS is an APRS mapping and messaging application first introduced in BPQ32_5.2.4.1_20120130. BPQAPRS at its current state of development is a viable replacement for UIView32 for many users and in addition is under active development to add additional capability. The BPQ32 digipeater is "New n-N Paradigm " compliant and provides enough objects to fully support the Local Info Initiative. A configuration example is provided to quickly get you 'on the air'. The BPQAPRS program provides mapping using the on-line OpenStreetMap and reliable messaging, to the degree this is possible, with the existing infrastructure.

        As a reminder, you must have all of your node configuration in BPQ32.cfg.

        BPQ32_5.2.1.3_20111018,was the last to support both the new method, all the node configuration statements combined into BPQ32.cfg, as well as the old method of separate configuration files. If you currently have separate config files, a smooth transition to the new system would be to first install BPQ32_5.2.1.3_20111018, which you can find in the links section of the BPQ32 Yahoo Group, and make the changes to your configuration using that version. Once successful, the subsequent upgrade to BPQ32_5.2.9.1_20120925 followed by BPQ32_6.0.2.1_20130608 should proceed with ease.

        My installer is also capable of converting an existing non-compliant installation to a Microsoft compliant installation. In brief, Microsoft has been, since the introduction of Windows XP, recommending that an installation be split in to a "program files" part and an "application data" part. This was not enforced in Windows XP but it is being enforced in Vista and Windows 7. Many programs have been installed in the root, such as C:\Ham Programs to get around this recommendation, but the result is annoying UAC popups...'do you really trust this program' etc. If you have used this workaround, you can, after installing this most recent release, do an uninstall, which will preserve your configuration, and then do a reinstall taking all the defaults. The result will be to divide your installation properly into %programfiles%\bpq32 and %appdata%\bpq32.

        Help will be available in the users group should you have questions.

        The changelog is here:
        http://www.cantab.net/users/john.wiseman/Documents/BPQ32%20Installation.htm#Changelog

        Special notice to CMS users:

        If you use BPQ32 or LinBPQ to access the CMS Servers via the "CMS Telnet" feature, this will not work after
        30th June 2013 unless you enable the Secure Login Mechanism. This version of BPQ32 supports Secure Login

        To enable Secure Login you need to add two lines to your Telnet Server Config.

        CMSCALL=CALLSIGN ; CMS Access Callsign (with SSID if used)
        CMSPASS=XXXXXXX ; Secure CMS Password

        CMSCALL should be set to the callsign+ssid used to access the RMS Gateway
        CMSPASS is your Secure Signon Password. This is the same as your winlink.org webmail password - if you don't
        already have one or have forgotten it, see http://www.winlink.org/WMInstructions for details of how to retrieve
        your password, or set one if you don't have one,

        All gateway stations also need to be authorised by the WL2K team. Gateways that were active when the new system
        was first introduced should have been enabled automatically, but if not you may need to request access.

        If you can't access the CMS after enabling Secure Access check the CMSAccess_yyyymmdd.log file in your BPQ32
        folder for any error messages.

        John G8BPQ
        June 2013


        Thanks to John Wiseman G8BPQ/GM8BPQ for his tireless work enhancing BPQ32!

        73 de Ron Stordahl, AE5E (ex N5IN)

      • David Bird
        Agreed! Thanks, John! 73, Dave WA7RYV ________________________________ From: n5in_ron To: BPQ32@yahoogroups.com Sent: Friday, June 7, 2013
        Message 3 of 6 , Jun 8, 2013
        • 0 Attachment
          Agreed!

          Thanks, John!

          73, Dave
          WA7RYV


          From: n5in_ron <ron_n5in@...>
          To: BPQ32@yahoogroups.com
          Sent: Friday, June 7, 2013 3:59 PM
          Subject: [BPQ32] BPQ32_6.0.2.1_20130608 including BPQMail, BPQChat and BPQAPRS is now available

           
          A new release, BPQ32_6.0.2.1_20130608, for Windows, is available for download at: http://groups.yahoo.com/group/BPQ32/.

          A special notice for CMS users is appended at the end of this release announcement.

          John Wiseman, G8BPQ, has created a common code base for BPQ32 allowing both Windows (BPQ32) and Linux (LinBPQ) versions to be produced.

          This release updates BPQ32.dll, BPQMailChat, and AGWtoBPQ.

          BPQMail (a BBS system) and BPQChat (a Chat system) replaces BPQMailChat.

          BPQMailChat is still provided, and can be used for mail, but it will likely be dropped from the next release. The provided shortcuts for BPQMailChat actually point to BPQMail with the goal of easing the transition.

          BPQ32 now has a basic Web Interface option. This provides Browser access to some node status displays, and a simple Web Terminal for access to the Network. It can also act as Web Server for other BPQ32 Applications, such as BPQAPRS

          BPQAPRS is an APRS mapping and messaging application first introduced in BPQ32_5.2.4.1_20120130. BPQAPRS at its current state of development is a viable replacement for UIView32 for many users and in addition is under active development to add additional capability. The BPQ32 digipeater is "New n-N Paradigm " compliant and provides enough objects to fully support the Local Info Initiative. A configuration example is provided to quickly get you 'on the air'. The BPQAPRS program provides mapping using the on-line OpenStreetMap and reliable messaging, to the degree this is possible, with the existing infrastructure.

          As a reminder, you must have all of your node configuration in BPQ32.cfg.

          BPQ32_5.2.1.3_20111018,was the last to support both the new method, all the node configuration statements combined into BPQ32.cfg, as well as the old method of separate configuration files. If you currently have separate config files, a smooth transition to the new system would be to first install BPQ32_5.2.1.3_20111018, which you can find in the links section of the BPQ32 Yahoo Group, and make the changes to your configuration using that version. Once successful, the subsequent upgrade to BPQ32_5.2.9.1_20120925 followed by BPQ32_6.0.2.1_20130608 should proceed with ease.

          My installer is also capable of converting an existing non-compliant installation to a Microsoft compliant installation. In brief, Microsoft has been, since the introduction of Windows XP, recommending that an installation be split in to a "program files" part and an "application data" part. This was not enforced in Windows XP but it is being enforced in Vista and Windows 7. Many programs have been installed in the root, such as C:\Ham Programs to get around this recommendation, but the result is annoying UAC popups...'do you really trust this program' etc. If you have used this workaround, you can, after installing this most recent release, do an uninstall, which will preserve your configuration, and then do a reinstall taking all the defaults. The result will be to divide your installation properly into %programfiles%\bpq32 and %appdata%\bpq32.

          Help will be available in the users group should you have questions.

          The changelog is here:
          http://www.cantab.net/users/john.wiseman/Documents/BPQ32%20Installation.htm#Changelog

          Special notice to CMS users:

          If you use BPQ32 or LinBPQ to access the CMS Servers via the "CMS Telnet" feature, this will not work after
          30th June 2013 unless you enable the Secure Login Mechanism. This version of BPQ32 supports Secure Login

          To enable Secure Login you need to add two lines to your Telnet Server Config.

          CMSCALL=CALLSIGN ; CMS Access Callsign (with SSID if used)
          CMSPASS=XXXXXXX ; Secure CMS Password

          CMSCALL should be set to the callsign+ssid used to access the RMS Gateway
          CMSPASS is your Secure Signon Password. This is the same as your winlink.org webmail password - if you don't
          already have one or have forgotten it, see http://www.winlink.org/WMInstructions for details of how to retrieve
          your password, or set one if you don't have one,

          All gateway stations also need to be authorised by the WL2K team. Gateways that were active when the new system
          was first introduced should have been enabled automatically, but if not you may need to request access.

          If you can't access the CMS after enabling Secure Access check the CMSAccess_yyyymmdd.log file in your BPQ32
          folder for any error messages.

          John G8BPQ
          June 2013


          Thanks to John Wiseman G8BPQ/GM8BPQ for his tireless work enhancing BPQ32!

          73 de Ron Stordahl, AE5E (ex N5IN)



        • Chris Roberts
          Hiya all. Question: To upgrade my Windows 98SE system to the latest versions as below, do I need to save my existing BPQ32.dll , do the upgrade and then
          Message 4 of 6 , Jun 9, 2013
          • 0 Attachment

            Hiya all.

            Question:

            To upgrade my Windows 98SE system to the latest versions as below, do I need to save my existing BPQ32.dll , do the upgrade and then overwrite the newly installed BPQ32.dll with the old (Win98SE) version after completing the upgrade as below.  I had problems with the previous upgrade overwriting BPQ32.dll with a version not suitable for WIN98SE and hence kept getting an error message when I tried to start BPQ32.

            Thanks

            Chris G0CNG Sysop GB7MAX

             

            From: BPQ32@yahoogroups.com [mailto:BPQ32@yahoogroups.com] On Behalf Of David Bird
            Sent: 08 June 2013 16:26
            To: BPQ32@yahoogroups.com
            Subject: Re: [BPQ32] BPQ32_6.0.2.1_20130608 including BPQMail, BPQChat and BPQAPRS is now available

             

             

            Agreed!

            Thanks, John!

            73, Dave
            WA7RYV


            From: n5in_ron <ron_n5in@...>
            To: BPQ32@yahoogroups.com
            Sent: Friday, June 7, 2013 3:59 PM
            Subject: [BPQ32] BPQ32_6.0.2.1_20130608 including BPQMail, BPQChat and BPQAPRS is now available

             

             

            A new release, BPQ32_6.0.2.1_20130608, for Windows, is available for download at: http://groups.yahoo.com/group/BPQ32/.

            A special notice for CMS users is appended at the end of this release announcement.

            John Wiseman, G8BPQ, has created a common code base for BPQ32 allowing both Windows (BPQ32) and Linux (LinBPQ) versions to be produced.

            This release updates BPQ32.dll, BPQMailChat, and AGWtoBPQ.

            BPQMail (a BBS system) and BPQChat (a Chat system) replaces BPQMailChat.

            BPQMailChat is still provided, and can be used for mail, but it will likely be dropped from the next release. The provided shortcuts for BPQMailChat actually point to BPQMail with the goal of easing the transition.

            BPQ32 now has a basic Web Interface option. This provides Browser access to some node status displays, and a simple Web Terminal for access to the Network. It can also act as Web Server for other BPQ32 Applications, such as BPQAPRS

            BPQAPRS is an APRS mapping and messaging application first introduced in BPQ32_5.2.4.1_20120130. BPQAPRS at its current state of development is a viable replacement for UIView32 for many users and in addition is under active development to add additional capability. The BPQ32 digipeater is "New n-N Paradigm " compliant and provides enough objects to fully support the Local Info Initiative. A configuration example is provided to quickly get you 'on the air'. The BPQAPRS program provides mapping using the on-line OpenStreetMap and reliable messaging, to the degree this is possible, with the existing infrastructure.

            As a reminder, you must have all of your node configuration in BPQ32.cfg.

            BPQ32_5.2.1.3_20111018,was the last to support both the new method, all the node configuration statements combined into BPQ32.cfg, as well as the old method of separate configuration files. If you currently have separate config files, a smooth transition to the new system would be to first install BPQ32_5.2.1.3_20111018, which you can find in the links section of the BPQ32 Yahoo Group, and make the changes to your configuration using that version. Once successful, the subsequent upgrade to BPQ32_5.2.9.1_20120925 followed by BPQ32_6.0.2.1_20130608 should proceed with ease.

            My installer is also capable of converting an existing non-compliant installation to a Microsoft compliant installation. In brief, Microsoft has been, since the introduction of Windows XP, recommending that an installation be split in to a "program files" part and an "application data" part. This was not enforced in Windows XP but it is being enforced in Vista and Windows 7. Many programs have been installed in the root, such as C:\Ham Programs to get around this recommendation, but the result is annoying UAC popups...'do you really trust this program' etc. If you have used this workaround, you can, after installing this most recent release, do an uninstall, which will preserve your configuration, and then do a reinstall taking all the defaults. The result will be to divide your installation properly into %programfiles%\bpq32 and %appdata%\bpq32.

            Help will be available in the users group should you have questions.

            The changelog is here:
            http://www.cantab.net/users/john.wiseman/Documents/BPQ32%20Installation.htm#Changelog

            Special notice to CMS users:

            If you use BPQ32 or LinBPQ to access the CMS Servers via the "CMS Telnet" feature, this will not work after
            30th June 2013 unless you enable the Secure Login Mechanism. This version of BPQ32 supports Secure Login

            To enable Secure Login you need to add two lines to your Telnet Server Config.

            CMSCALL=CALLSIGN ; CMS Access Callsign (with SSID if used)
            CMSPASS=XXXXXXX ; Secure CMS Password

            CMSCALL should be set to the callsign+ssid used to access the RMS Gateway
            CMSPASS is your Secure Signon Password. This is the same as your winlink.org webmail password - if you don't
            already have one or have forgotten it, see http://www.winlink.org/WMInstructions for details of how to retrieve
            your password, or set one if you don't have one,

            All gateway stations also need to be authorised by the WL2K team. Gateways that were active when the new system
            was first introduced should have been enabled automatically, but if not you may need to request access.

            If you can't access the CMS after enabling Secure Access check the CMSAccess_yyyymmdd.log file in your BPQ32
            folder for any error messages.

            John G8BPQ
            June 2013


            Thanks to John Wiseman G8BPQ/GM8BPQ for his tireless work enhancing BPQ32!

            73 de Ron Stordahl, AE5E (ex N5IN)

             

          • John Wiseman
            I ve tested the new version on Win98, so it should be ok. 73, John _____ From: BPQ32@yahoogroups.com [mailto:BPQ32@yahoogroups.com] On Behalf Of Chris Roberts
            Message 5 of 6 , Jun 9, 2013
            • 0 Attachment
              I've tested the new version on Win98, so it should be ok.
               
              73, John


              From: BPQ32@yahoogroups.com [mailto:BPQ32@yahoogroups.com] On Behalf Of Chris Roberts
              Sent: 09 June 2013 12:18
              To: BPQ32@yahoogroups.com
              Subject: RE: [BPQ32] BPQ32_6.0.2.1_20130608 including BPQMail, BPQChat and BPQAPRS is now available

               

              Hiya all.

              Question:

              To upgrade my Windows 98SE system to the latest versions as below, do I need to save my existing BPQ32.dll , do the upgrade and then overwrite the newly installed BPQ32.dll with the old (Win98SE) version after completing the upgrade as below.  I had problems with the previous upgrade overwriting BPQ32.dll with a version not suitable for WIN98SE and hence kept getting an error message when I tried to start BPQ32.

              Thanks

              Chris G0CNG Sysop GB7MAX

              From: BPQ32@yahoogroups.com [mailto:BPQ32@yahoogroups.com] On Behalf Of David Bird
              Sent: 08 June 2013 16:26
              To: BPQ32@yahoogroups.com
              Subject: Re: [BPQ32] BPQ32_6.0.2.1_20130608 including BPQMail, BPQChat and BPQAPRS is now available

               

              Agreed!

              Thanks, John!

              73, Dave
              WA7RYV


              From: n5in_ron <ron_n5in@...>
              To: BPQ32@yahoogroups.com
              Sent: Friday, June 7, 2013 3:59 PM
              Subject: [BPQ32] BPQ32_6.0.2.1_20130608 including BPQMail, BPQChat and BPQAPRS is now available

               

              A new release, BPQ32_6.0.2.1_20130608, for Windows, is available for download at: http://groups.yahoo.com/group/BPQ32/.

              A special notice for CMS users is appended at the end of this release announcement.

              John Wiseman, G8BPQ, has created a common code base for BPQ32 allowing both Windows (BPQ32) and Linux (LinBPQ) versions to be produced.

              This release updates BPQ32.dll, BPQMailChat, and AGWtoBPQ.

              BPQMail (a BBS system) and BPQChat (a Chat system) replaces BPQMailChat.

              BPQMailChat is still provided, and can be used for mail, but it will likely be dropped from the next release. The provided shortcuts for BPQMailChat actually point to BPQMail with the goal of easing the transition.

              BPQ32 now has a basic Web Interface option. This provides Browser access to some node status displays, and a simple Web Terminal for access to the Network. It can also act as Web Server for other BPQ32 Applications, such as BPQAPRS

              BPQAPRS is an APRS mapping and messaging application first introduced in BPQ32_5.2.4.1_20120130. BPQAPRS at its current state of development is a viable replacement for UIView32 for many users and in addition is under active development to add additional capability. The BPQ32 digipeater is "New n-N Paradigm " compliant and provides enough objects to fully support the Local Info Initiative. A configuration example is provided to quickly get you 'on the air'. The BPQAPRS program provides mapping using the on-line OpenStreetMap and reliable messaging, to the degree this is possible, with the existing infrastructure.

              As a reminder, you must have all of your node configuration in BPQ32.cfg.

              BPQ32_5.2.1.3_20111018,was the last to support both the new method, all the node configuration statements combined into BPQ32.cfg, as well as the old method of separate configuration files. If you currently have separate config files, a smooth transition to the new system would be to first install BPQ32_5.2.1.3_20111018, which you can find in the links section of the BPQ32 Yahoo Group, and make the changes to your configuration using that version. Once successful, the subsequent upgrade to BPQ32_5.2.9.1_20120925 followed by BPQ32_6.0.2.1_20130608 should proceed with ease.

              My installer is also capable of converting an existing non-compliant installation to a Microsoft compliant installation. In brief, Microsoft has been, since the introduction of Windows XP, recommending that an installation be split in to a "program files" part and an "application data" part. This was not enforced in Windows XP but it is being enforced in Vista and Windows 7. Many programs have been installed in the root, such as C:\Ham Programs to get around this recommendation, but the result is annoying UAC popups...'do you really trust this program' etc. If you have used this workaround, you can, after installing this most recent release, do an uninstall, which will preserve your configuration, and then do a reinstall taking all the defaults. The result will be to divide your installation properly into %programfiles%\bpq32 and %appdata%\bpq32.

              Help will be available in the users group should you have questions.

              The changelog is here:
              http://www.cantab.net/users/john.wiseman/Documents/BPQ32%20Installation.htm#Changelog

              Special notice to CMS users:

              If you use BPQ32 or LinBPQ to access the CMS Servers via the "CMS Telnet" feature, this will not work after
              30th June 2013 unless you enable the Secure Login Mechanism. This version of BPQ32 supports Secure Login

              To enable Secure Login you need to add two lines to your Telnet Server Config.

              CMSCALL=CALLSIGN ; CMS Access Callsign (with SSID if used)
              CMSPASS=XXXXXXX ; Secure CMS Password

              CMSCALL should be set to the callsign+ssid used to access the RMS Gateway
              CMSPASS is your Secure Signon Password. This is the same as your winlink.org webmail password - if you don't
              already have one or have forgotten it, see http://www.winlink.org/WMInstructions for details of how to retrieve
              your password, or set one if you don't have one,

              All gateway stations also need to be authorised by the WL2K team. Gateways that were active when the new system
              was first introduced should have been enabled automatically, but if not you may need to request access.

              If you can't access the CMS after enabling Secure Access check the CMSAccess_yyyymmdd.log file in your BPQ32
              folder for any error messages.

              John G8BPQ
              June 2013


              Thanks to John Wiseman G8BPQ/GM8BPQ for his tireless work enhancing BPQ32!

              73 de Ron Stordahl, AE5E (ex N5IN)

            • Chris Roberts
              That s great news John. Many thanks for the reply. I m in the midst of writing end of year school reports:-( so I ll upgrade when I need a break from these!
              Message 6 of 6 , Jun 9, 2013
              • 0 Attachment
                That's great news John. Many thanks for the reply. I'm in the midst of writing end of year school reports:-( so I'll upgrade when I need a break from these!  Many thanks again. 
                Best wishes from Chris Roberts
                Sent from my Iphone4

                On 9 Jun 2013, at 12:39, "John Wiseman" <john.wiseman@...> wrote:

                 

                I've tested the new version on Win98, so it should be ok.
                 
                73, John


                From: BPQ32@yahoogroups.com [mailto:BPQ32@yahoogroups.com] On Behalf Of Chris Roberts
                Sent: 09 June 2013 12:18
                To: BPQ32@yahoogroups.com
                Subject: RE: [BPQ32] BPQ32_6.0.2.1_20130608 including BPQMail, BPQChat and BPQAPRS is now available

                 

                Hiya all.

                Question:

                To upgrade my Windows 98SE system to the latest versions as below, do I need to save my existing BPQ32.dll , do the upgrade and then overwrite the newly installed BPQ32.dll with the old (Win98SE) version after completing the upgrade as below.  I had problems with the previous upgrade overwriting BPQ32.dll with a version not suitable for WIN98SE and hence kept getting an error message when I tried to start BPQ32.

                Thanks

                Chris G0CNG Sysop GB7MAX

                From: BPQ32@yahoogroups.com [mailto:BPQ32@yahoogroups.com] On Behalf Of David Bird
                Sent: 08 June 2013 16:26
                To: BPQ32@yahoogroups.com
                Subject: Re: [BPQ32] BPQ32_6.0.2.1_20130608 including BPQMail, BPQChat and BPQAPRS is now available

                 

                Agreed!

                Thanks, John!

                73, Dave
                WA7RYV


                From: n5in_ron <ron_n5in@...>
                To: BPQ32@yahoogroups.com
                Sent: Friday, June 7, 2013 3:59 PM
                Subject: [BPQ32] BPQ32_6.0.2.1_20130608 including BPQMail, BPQChat and BPQAPRS is now available

                 

                A new release, BPQ32_6.0.2.1_20130608, for Windows, is available for download at: http://groups.yahoo.com/group/BPQ32/.

                A special notice for CMS users is appended at the end of this release announcement.

                John Wiseman, G8BPQ, has created a common code base for BPQ32 allowing both Windows (BPQ32) and Linux (LinBPQ) versions to be produced.

                This release updates BPQ32.dll, BPQMailChat, and AGWtoBPQ.

                BPQMail (a BBS system) and BPQChat (a Chat system) replaces BPQMailChat.

                BPQMailChat is still provided, and can be used for mail, but it will likely be dropped from the next release. The provided shortcuts for BPQMailChat actually point to BPQMail with the goal of easing the transition.

                BPQ32 now has a basic Web Interface option. This provides Browser access to some node status displays, and a simple Web Terminal for access to the Network. It can also act as Web Server for other BPQ32 Applications, such as BPQAPRS

                BPQAPRS is an APRS mapping and messaging application first introduced in BPQ32_5.2.4.1_20120130. BPQAPRS at its current state of development is a viable replacement for UIView32 for many users and in addition is under active development to add additional capability. The BPQ32 digipeater is "New n-N Paradigm " compliant and provides enough objects to fully support the Local Info Initiative. A configuration example is provided to quickly get you 'on the air'. The BPQAPRS program provides mapping using the on-line OpenStreetMap and reliable messaging, to the degree this is possible, with the existing infrastructure.

                As a reminder, you must have all of your node configuration in BPQ32.cfg.

                BPQ32_5.2.1.3_20111018,was the last to support both the new method, all the node configuration statements combined into BPQ32.cfg, as well as the old method of separate configuration files. If you currently have separate config files, a smooth transition to the new system would be to first install BPQ32_5.2.1.3_20111018, which you can find in the links section of the BPQ32 Yahoo Group, and make the changes to your configuration using that version. Once successful, the subsequent upgrade to BPQ32_5.2.9.1_20120925 followed by BPQ32_6.0.2.1_20130608 should proceed with ease.

                My installer is also capable of converting an existing non-compliant installation to a Microsoft compliant installation. In brief, Microsoft has been, since the introduction of Windows XP, recommending that an installation be split in to a "program files" part and an "application data" part. This was not enforced in Windows XP but it is being enforced in Vista and Windows 7. Many programs have been installed in the root, such as C:\Ham Programs to get around this recommendation, but the result is annoying UAC popups...'do you really trust this program' etc. If you have used this workaround, you can, after installing this most recent release, do an uninstall, which will preserve your configuration, and then do a reinstall taking all the defaults. The result will be to divide your installation properly into %programfiles%\bpq32 and %appdata%\bpq32.

                Help will be available in the users group should you have questions.

                The changelog is here:
                http://www.cantab.net/users/john.wiseman/Documents/BPQ32%20Installation.htm#Changelog

                Special notice to CMS users:

                If you use BPQ32 or LinBPQ to access the CMS Servers via the "CMS Telnet" feature, this will not work after
                30th June 2013 unless you enable the Secure Login Mechanism. This version of BPQ32 supports Secure Login

                To enable Secure Login you need to add two lines to your Telnet Server Config.

                CMSCALL=CALLSIGN ; CMS Access Callsign (with SSID if used)
                CMSPASS=XXXXXXX ; Secure CMS Password

                CMSCALL should be set to the callsign+ssid used to access the RMS Gateway
                CMSPASS is your Secure Signon Password. This is the same as your winlink.org webmail password - if you don't
                already have one or have forgotten it, see http://www.winlink.org/WMInstructions for details of how to retrieve
                your password, or set one if you don't have one,

                All gateway stations also need to be authorised by the WL2K team. Gateways that were active when the new system
                was first introduced should have been enabled automatically, but if not you may need to request access.

                If you can't access the CMS after enabling Secure Access check the CMSAccess_yyyymmdd.log file in your BPQ32
                folder for any error messages.

                John G8BPQ
                June 2013


                Thanks to John Wiseman G8BPQ/GM8BPQ for his tireless work enhancing BPQ32!

                73 de Ron Stordahl, AE5E (ex N5IN)

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