[nos-bbs] forwarding error -how to fix?

[jerome schatten]

OK thank you Gus!

Setting pilinbpq so that it 'allows binary' solves the error problem. Getting rid of '!' in the jnos forward bbs file made no difference. I presume that setting pilinbpq to allow B1 would do the same.

My original intent was to have poo forward to ass in plain text (uncompressed). I know how to do that with bpq, but I apparently do not know how to make jnos do that. Some really old jnos2 docs indicated that '!' in the commands section of the forward.bbs file would force plain text forward from jnos. 

Right now Poo's ID: [JNOS-2.0p.5-B1FHIM$] and ASS's ID: [BPQ-6.0.24.56-BFIHJM$] and that works with no errors. So, as an academic question (consistent with 'non multa, sed multum') - how do you force jnos forward uncompressed?

Best regards,
jerome 





----- Original Message -----
From: "Gustavo Ponza" <g.ponza at tin.it>
To: "TAPR xNOS Mailing List" <nos-bbs at lists.tapr.org>
Sent: Tuesday, February 11, 2025 6:02:24 AM
Subject: Re: [nos-bbs] forwarding error -how to fix?

Why rape the original SID?

It actually should be in both JNOS2 and LinBPQ as the following:

[JNOS-2.0P.6-B1FHIM$]
[BPQ-6.0.24.59-B1FIHJM$]

Namely: for JNOS2 the FBB style forwarding 2 enabled
         for LinBPQ the compress forwarding with B1 enabled

The LinBPQ, as today, is faulty ONLY when forwarding to
JNOS2 via TELNET mode.
Many times the author G8BPQ has been advised about this,
but never considered :(

The JNOS2 has NO limitations versus any possible existing
programs: DOS, old and new windoze, linux etc. :)


jerome schatten wrote:
> What is this error trying to tell me?  ve7ass is the bpq machine and ve7poo is the jnos machine -- In jnos, 'mbox kick' initiates the forward cycle. A prepared message from a jnos-non bbs user (ve7spy) is in the 'usa' area. Below is the transaction after the 'jnos mbox kick'.

>    VE7ASS-7 to VE7POO-7 ttl 25 cct=0107  <INFO S0 R0>:
> [BPQ-6.0.24.56-FWIHJM$]
> 
> de VE7ASS>


> 03:35:21R VE7POO-7>VE7ASS-7 Port=3 <I C S3 R2> NET/ROM
>    VE7POO-7 to VE7ASS-1 ttl 15 cct=02DE  <INFO S0 R1>:
> [JNOS-2.0p.5-FHIM$]
> FB B VE7SPY USA TEST3 3PN_VE7POO 429
> F>
> 03:35:22T VE7ASS-7>VE7POO-7 Port=3 <I C P S2 R4> NET/ROM
>    VE7ASS-7 to VE7POO-7 ttl 25 cct=0107  <INFO S1 R1>:
>>
> *** DONE

The above reply means that the forwarding is finished
so the reply should be FQ (or DISC ?).


> 03:35:22R VE7POO-7>VE7ASS-7 Port=3 <RR R F R3>
> 03:35:26R VE7POO-7>VE7ASS-7 Port=3 <I C S4 R3> NET/ROM
>    VE7POO-7 to VE7ASS-1 ttl 15 cct=02DE  <INFO S0 R1>:
> [JNOS-2.0p.5-FHIM$]
> FB B VE7SPY USA TEST3 3PN_VE7POO 429
> F>
> 03:35:26R VE7POO-7>VE7ASS-7 Port=3 <I C S5 R3> NET/ROM
>    VE7POO-7 to VE7ASS-1 ttl 15 cct=02DE  <INFO S1 R2>:
> FBB Error: Expected 'FS ' string. Received '>' string.
> 03:35:26T VE7ASS-7>VE7POO-7 Port=3 <I C P S3 R6> NET/ROM
>    VE7ASS-7 to VE7POO-7 ttl 25 cct=0107  <DISC REQ>
> [...]

ditto.


> ######################################
> # This is POO's 'forward.bbs' file' #
> #####################################
> 
> 
> ve7ass
> net assbbs
> !             <<<< It does not exit in the JNOS2 nomenclature:
> usa                remove it, and all should be OK :) 
> ve7ass
> --------

> Thanks for your suggestions.
> jerome


-- 
73 and ciao, gustavo i0ojj/ir0aab/ir0eq
non multa, sed multum

_______________________________________________
nos-bbs mailing list
nos-bbs at lists.tapr.org
http://lists.tapr.org/mailman/listinfo/nos-bbs_lists.tapr.org