| |
G0SYR > JNOS 01.11.04 14:01l 48 Lines 1488 Bytes #999 (0) @ EU
BID : 17762G0SYR
Read: GUEST
Subj: Re: jnos 2.0 Missing parts
Path: DB0FHN<DB0RGB<OK0PPL<DB0RES<ON0AR<EB2BJX<GB7YKS<GB7PZT<GB7YFS<GB7CIP<
GB7CIP<GB7CIP
Sent: 041101/1148Z @:GB7CIP.#32.GBR.EU $:17762G0SYR
T:From: g0syr <g0syr@gb7cip.ampr.org>
T:Newsgroups: ampr.ip.jnos
T:Message-Id: <kiowv8ac5g8$.1vjiksz5y7ptn$.dlg@40tude.net>
Hi Andy and all,
On Sun, 31 Oct 2004 19:13:00 +0000, g0ftd%gb7sxe.#38.gbr.eu@gb7cip.ampr.org
wrote:
> From: G0FTD@GB7SXE.#38.GBR.EU
> To : JNOS@EU
>
>
> Missing parts (in DECIMAL!):
>
> 4/7/13/16
>
> Missing parts (in HEX!):
>
> 4/7/0D/10
>
> - Andy -
Yes same here when I checked with winpack to try and decode it.
In fact the parts are not completely missing they have been
distributed but those 'missing' parts have been truncated by a
few bytes and the 'stop_7+.' to terminate the part is missing
and so are not valid.
I did a bit more investigating and although I can connect to the
senders BBS ON4HU-1 via his node MOU:ON4HU-4 his BBS does not
have a copy of the parts to check. I suspect the corruption may have
been at the senders end as there are a couple of obvious anomalies
in the titles of the parts which suggests the generation of the
parts may not have been clean.
The parts came into GB7CIP via ON4HU>F1HPZ>ON4BEL>GB7CIP
but on checking another copy of part 4 on GB7MAX which
recieved the bulletin along a different path
namely ON4HU>F1CDD>GB7WIS>GB7MAX exactly the same corruption
is seen so I guess we'll have to wait till ON4HU can look into
the problem and send it again.
--
73 de Bryan g0syr.ampr.org [ 44.131.244.60 ]
Amprnet mail g0syr@gb7cip.ampr.org
AX25 mail G0SYR@GB7CIP.#32.GBR.EU
Internet Mail g0syr@beeb.net
Read previous mail | Read next mail
| |
