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

Re: [BPQ32] Re: TLN and WinFBB32

Expand Messages
  • Joel Yates
    Hello, DE Joel N4JOA, Check the attached file for a screen shot showing the version of TLN that I am running. The actual DLL file says 1.6.0.0 Telnet
    Message 1 of 2 , Nov 1, 2006
    • 0 Attachment
      Hello, DE Joel N4JOA, Check the attached file for a screen shot
      showing the version of TLN that I am running. The actual DLL file says
      1.6.0.0
      Telnet forwarding works fine for me.
      ...73's...Joel N4JOA

      On 11/1/06, Mark Harloff <mharloff@...> wrote:
      > Hi Mike,
      >
      > The problem was with the versions of the bpq and bpq32 dlls I was using.
      > I uprev'd to the latest versions and that eliminated the lockup problem.
      >
      > There is saturation of the CPU from time to time on All the machines
      > here but that does not affect any one or more of the applications I have
      > running on any of the machines to the extent of locking up the
      > application. It slows them down a bit, but that's all.
      >
      > I run multiple UDP ports on the switch. But, as you mentioned, the
      > newest switch release handles that fine.
      >
      > There is another problem with WinFBB32's telnet dll that I am currently
      > working on tracking down. This is unrelated to the earlier 'lockup'
      > problem. I try to keep the group posted on that.
      >
      > IF you (or anyone else) is running a telnet port for forwarding in
      > WinFBB32 it would help me if you could check the version of the tln.dll
      > you are using and let me know what it is.
      > (right click on the file, left click 'properties' and read the 'version'
      > tab info)
      >
      > Thanks for your suggestions. I appreciate them!
      >
      > - Mark K2CAN
      >
      >
      > MIchael Melnik Sr. wrote:
      > >
      > >
      > > Mark, K2CAN
      > > WinFbb 7.01-35 uses 2 to 4% of processor under normal operation,
      > > how ever when forwarding takes place either Telnet or Calls to BPQ
      > > for R.F Forwarding it will peak out at 98% leaving only 2% left
      > > for other programs such as your ARC, The BPQ32.dll solves the
      > > monitoring of all ports problem, all these operations accuring at
      > > one time is more then likely the lock up problem, by using two
      > > computers ARC on one and WinFbb on the other is less processor
      > > intensive, I don't know if this will help, try changing the
      > > compatibilty in WinFbb and Bpq, Right click on the .EXE, Properities
      > > I run mine on my Xp at W2K.
      > >
      > > I am not sure if you are using mutilple AXIP UDP Ports, previous
      > > versions of BPQ32 409UBetaMay2006 wont support Multiple UDP Ports
      > > You will get a Bad Record Record Error in the Dos Box when Bpq.exe
      > > starts up, these are just a couple of thoughts.
      > >
      > > Mike/N9PMO
      > > --- In BPQ32@yahoogroups.com <mailto:BPQ32%40yahoogroups.com>, Mark
      > > Harloff <mharloff@...> wrote:
      > >>
      > >> Hi John,
      > >>
      > >> I just sent you a 'personel' note so this reply may be moot.
      > >>
      > >> 1) I cannot access the switch from BPQTerminal at the point where
      > > it locks.
      > >>
      > >> 2) CTRL/C does not produce any response since the 'DOS BOX' is not
      > >> accessible. ALL the boxes are locked up in the system tray at that
      > > point.
      > >>
      > >> - Mark K2CAN
      > >>
      > >>
      > >>
      > >> John Wiseman wrote:
      > >> >
      > >> >
      > >> > Ok, Mark. I wonder if you could try a few things to help track
      > > doen the
      > >> > problem? When the switch locks up, it is possible to access it
      > > from, for
      > >> > instance, BPQTerminal? Is it possible to get a dump from BPQ32
      > > (by
      > >> > typing CTRL/C in the BPQ32 "DOS BOX")? Also could you run
      > > DebugView
      > >> > (http://www.sysinternals.com/Utilities/DebugView.html
      > > <http://www.sysinternals.com/Utilities/DebugView.html>
      > >> > <http://www.sysinternals.com/Utilities/DebugView.html
      > > <http://www.sysinternals.com/Utilities/DebugView.html>>). This
      > > may
      > >> > display additional debugging information from BPQ.
      > >> >
      > >> >
      > >> > Thanks,
      > >> >
      > >> > John
      > >> >
      > >> >
      > >> > -----Original Message-----
      > >> > *From:* BPQ32@yahoogroups.com <mailto:BPQ32%40yahoogroups.com>
      > > [mailto:BPQ32@yahoogroups.com <mailto:BPQ32%40yahoogroups.com>]
      > > *On
      > >> > Behalf Of *Mark Harloff
      > >> > *Sent:* Tuesday, October 31, 2006 20:21
      > >> > *To:* BPQ32@yahoogroups.com <mailto:BPQ32%40yahoogroups.com>
      > >> > *Subject:* Re: [BPQ32] BPQ32 ARC and WinFBB32
      > >> >
      > >> > Hi John and the group,
      > >> >
      > >> > Last night I uprev'd both dll's on the P4 to the latest
      > > versions
      > >> > (creation dates). That did not solve the 'lockup' problem,
      > > in fact, it
      > >> > made it worse.
      > >> >
      > >> > So, for now, I've gone back to the old configuration where
      > > BPQ32 and ARC
      > >> > are running on the P4 and BPQ32 and WinFBB32 are running on
      > > a separate
      > >> > machine here. Both machines are linked to the internet via a
      > > hub and
      > >> > then into a adsl modem.
      > >> >
      > >> > 73, Mark K2CAN
      > >> >
      > >> > Mark Harloff wrote:
      > >> > >
      > >> > >
      > >> > > Hi John and the group,
      > >> > >
      > >> > > I've tracked down the problem to what I think is
      > > difference in version
      > >> > > of the BPQ.DLL and BPQ32.DLL that I have been running here.
      > >> > >
      > >> > > On the XP Pro machine (that BPQ32 locks up on) I was
      > > running Version
      > >> > > 1.0.0.1 of the BPQ.DLL dated 3/29/06. That DLL running on
      > > the
      > >> > Win2K Pro
      > >> > > machine (which works fine) has the same Version number but
      > > a different
      > >> > > creation date.. 3/30/06.
      > >> > >
      > >> > > I assume I need to run the one created on 3/30/06 ?
      > >> > > (if so, the version number should probably be changed at
      > > some point)
      > >> > >
      > >> > >
      > > *******************************************************************
      > >> > >
      > >> > > On the XP Pro machine (that BPQ32 locks up on) I was
      > > running Version
      > >> > > 4.9.21.2 of the BPQ32.DLL dated 3/13/06. That DLL running
      > > on the Win2K
      > >> > > Pro machine (which works fine) is Version 4.9.21.3 also
      > > created on
      > >> > 3/13/06.
      > >> > >
      > >> > > I assume that 4.9.21.3 is the most current version and the
      > > one I
      > >> > should
      > >> > > be running ?
      > >> > >
      > >> > >
      > > *******************************************************************
      > >> > >
      > >> > > I'm pretty sure these two dll's are the source of the
      > > problem here.
      > >> > >
      > >> > > 73, Mark K2CAN
      > >> > >
      > >> > > Mark Harloff wrote:
      > >> > >>
      > >> > >>
      > >> > >> Hi John,
      > >> > >>
      > >> > >> Thanks for the reply. The problem I was having was that
      > > when I
      > >> > ran BPQ32
      > >> > >> 4.09u Rev 3, ARC 4.4.25 and WinFbb32 7.01.35a on the same
      > > machine
      > >> > (a 1.8
      > >> > >> Gig P4 running Win XP Pro) the switch would lock up after
      > > awhile (not
      > >> > >> sure how long, it varied). The Cluster and the BBS would
      > > continue
      > >> > to run
      > >> > >> even though the switch was locked. There was no fault
      > > indication from
      > >> > >> the switch code (or the OS), it was just unreachable from
      > > a
      > >> > BPQTerminal
      > >> > >> console or either of the ports (serial and telnet) I run.
      > >> > >>
      > >> > >> I have since moved the BBS off to another machine here
      > > and am
      > >> > trying to
      > >> > >> track down the source of the problem by recreating the
      > > setup on
      > >> > the P4.
      > >> > >> I'll keep you and group posted as to how that goes.
      > >> > >>
      > >> > >> Adding the option to have L4 call and alias for each
      > > application
      > >> > will be
      > >> > >> a major benefit for folks that run multiple applications
      > > on the same
      > >> > >> switch (like me).. Your work is very appreciated!
      > >> > >>
      > >> > >> 73, Mark K2CAN
      > >> > >>
      > >> > >> John Wiseman wrote:
      > >> > >>>
      > >> > >>>
      > >> > >>> Hi Mark,
      > >> > >>>
      > >> > >>> I can run ARCluster and WinFBB, although I only do it
      > > for testing,
      > >> > >>> rather than running a production system. I use 7.01.35
      > > Alpha of
      > >> > WinFBB,
      > >> > >>> Version 4.09u of BPQ32 and I have 4.4.18 of AR-Cluster.
      > >> > AR-Cluster can
      > >> > >>> only run as BPQ application 1, so you have to run FBB as
      > > some other
      > >> > >>> application. This requires using the bpq.dll from the
      > > files
      > >> > section of
      > >> > >>> this group, rather than the one provided with winfbb32. I
      > >> > suggest anyone
      > >> > >>> using WinFBB 7.01 uses this replacement, as it fixes
      > > other
      > >> > problems with
      > >> > >>> the original.
      > >> > >>>
      > >> > >>> With the current version, each application can have it's
      > > own L2
      > >> > >>> callsign, but only one can respond to the L4 (Netrom)
      > > call
      > >> > BBSCALL. By
      > >> > >>> default this is application 1, but it is possible to
      > > change this
      > >> > with
      > >> > >>> the L4APPL command in bpqcfg.txt. Users access the other
      > >> > applications by
      > >> > >>> connecting first to the node, then entering the
      > > appropriate
      > >> > command. I
      > >> > >>> am working on a version which will allow each
      > > application have
      > >> > it's own
      > >> > >>> L4 call and alias.
      > >> > >>>
      > >> > >>> Regards,
      > >> > >>>
      > >> > >>> John
      > >> > > <snip>
      > >> >
      > >> >
      > >> >
      > >> >
      > >> > ----------------------------------------------------------
      > > -------
      > >> >
      > >> > No virus found in this incoming message.
      > >> > Checked by AVG Free Edition.
      > >> > Version: 7.1.409 / Virus Database: 268.13.20/508 - Release Date:
      > > 10/31/2006
      > >> >
      > >>
      > >
      > >
      > >
      > >
      > > ------------------------------------------------------------------------
      > >
      > > No virus found in this incoming message.
      > > Checked by AVG Free Edition.
      > > Version: 7.1.409 / Virus Database: 268.13.21/511 - Release Date: 11/1/2006
      >
      >
      >
      > Yahoo! Groups Links
      >
      >
      >
      >
      >


      --
      Joel Yates
      yate4899@...
    • Mark Harloff
      Thanks for the feedback Joel. The 1.6.0.0 dll fixed the problem. 73, Mark K2CAN
      Message 2 of 2 , Nov 2, 2006
      • 0 Attachment
        Thanks for the feedback Joel.

        The 1.6.0.0 dll fixed the problem.

        73, Mark K2CAN


        Joel Yates wrote:
        >
        >
        > Hello, DE Joel N4JOA, Check the attached file for a screen shot
        > showing the version of TLN that I am running. The actual DLL file says
        > 1.6.0.0
        > Telnet forwarding works fine for me.
        > ...73's...Joel N4JOA
        >
        > On 11/1/06, Mark Harloff <mharloff@...
        > <mailto:mharloff%40frontiernet.net>> wrote:
        >> Hi Mike,
        >>
        >> The problem was with the versions of the bpq and bpq32 dlls I was using.
        >> I uprev'd to the latest versions and that eliminated the lockup problem.
        >>
        >> There is saturation of the CPU from time to time on All the machines
        >> here but that does not affect any one or more of the applications I have
        >> running on any of the machines to the extent of locking up the
        >> application. It slows them down a bit, but that's all.
        >>
        >> I run multiple UDP ports on the switch. But, as you mentioned, the
        >> newest switch release handles that fine.
        >>
        >> There is another problem with WinFBB32's telnet dll that I am currently
        >> working on tracking down. This is unrelated to the earlier 'lockup'
        >> problem. I try to keep the group posted on that.
        >>
        >> IF you (or anyone else) is running a telnet port for forwarding in
        >> WinFBB32 it would help me if you could check the version of the tln.dll
        >> you are using and let me know what it is.
        >> (right click on the file, left click 'properties' and read the 'version'
        >> tab info)
        >>
        >> Thanks for your suggestions. I appreciate them!
        >>
        >> - Mark K2CAN
      Your message has been successfully submitted and would be delivered to recipients shortly.