dups

Hi Tim!

It’s _very_ important for me to know who the duplication is from.
Either someone was experimenting with the software, or because of double gating in St. Petersburg,
which I warned about.

When they pulled the echo, Kharkov asked to cut off the ZXNet link a day before
the start of the fidosh work. In St. Petersburg, judging by the latest route, the echo began to go further along Fido. Maybe we are to blame, although I personally haven’t seen a single
duplicated one :(

Report on this topic right here, we won’t have time to respond quickly without soap
(at the moment ZXNen channels are faster, since few cities are connected).

Sincerely, Alexey Ivanov

I greet you from the bottom of my heart, Alexey!

Thu Jun 25 1998, Alexey Ivanov squeezed the keyboard, hoping that the following words would reach Tim Kelly:

AI> It’s _very_ important for me to know who the duplication is from.
AI> Either someone experimented with the software, or because of double gating
AI> in St. Petersburg, what I’m talking about warned.

AI> When they pulled the echo, Kharkov asked to cut off the ZXNet link a day before
AI> the start of the fidosh work. In St. Petersburg, judging by the latest route,
AI> the echo began to move further along the fido. Maybe we are to blame, although I personally haven’t seen a single
AI> duplicated :(

AI> Report this topic right here, we won’t have time to react quickly
AI> (at the moment ZXNen channels are faster, since few
AI> cities are connected).

Here is an excerpt from the letter sent to me:

=== Cut ===

So I came across two identical letters that came on
different paths.

Here is the ^aPATH from both:

a) ^aPATH: 5052/7 17 5020/1381 238 400 4616/3

b) ^aPATH: 5052/7 17 5020/1381 238 204 5030/251 100 465/70

As you can see, the ring looks like this:

5020/238 5020/400 4616/3 4616/2 465/70 5030/100 5030/251
5020/204 5020/238

=== Cut ===

I'm trying break the ring on 5020/238 before the sysop answers me.
Maybe you can help?

Hasta la vista.
TimKelly