OpenBCM V1.08-5-g2f4a (Linux)

Packet Radio Mailbox

IZ3LSV

[San Dona' di P. JN]

 Login: GUEST





  
PY2BIL > TEST     05.12.19 14:22l 48 Lines 1547 Bytes #999 (0) @ WW
BID : 10536PY2BIL
Read: GUEST
Subj: Re: PY2BIL > F>
Path: IZ3LSV<IQ2LB<IQ5KG<I0OJJ<GB7CIP<N7HPX<N3DWB<LU9HGS<LU1HVK<PY2BIL
Sent: 191204/2207Z 18024@PY2BIL.SP.BRA.SOAM LinBPQ6.0.19

+------------------------------------------------------------------------------+

Brian,


Quoting from a previous message...

> As you see, your follow up to your own bulletin was fine because it avoided
> 6.0.16 version:

Yes, I figured that out with the message exchange from yesterdaay and the fact 
that it reached two divfferent nodes through different paths with different 
results.

> Regardless of the reasons why it occurs, the fact of the matter is that
> it does occur. This is one of the issues that gives just cause to updating
> the BBS specs.

I took some action on it and reached out to the BPQ support forum where John 
Wieseman (G8BPQ) himself mentioned that that issue was fixed already some time 
ago. With that in hand I emailed VE1MPF to let him know about the issue and 
suggested he considers upgrading his BPQ BBS to the latest version.

I haven't heard back from him yet, but I hope he will follow that advise.


73 to all and thanks for the support in troubleshooting this.

Guillermo/Bill (PY2BIL)


What follows is just a Tagline....
ASCII stupid question, get a stupid ANSI.


+--------------------------  SAO PAULO PACKET NODE  ---------------------------+
| Grid GG66                Sao Paulo - SP - Brazil                144.390MHz |
| Sysop: PY2BIL              PY2BIL.SP.BRA.SOAM             py2bil@gmail.com |
+------------------------------------------------------------------------------+
(Message sent with Sally 7.2.032)
Timed 04-dez-2019 19:00 E. South America Standard Time
BBS: PY2BIL.SP.BRA.SOAM







Read previous mail | Read next mail


 24.12.2024 00:35:29lGo back Go up