TIP: Click on subject to list as thread! ANSI
echo: asian_link
to: LITTLE MIKEY
from: ALAN IANSON
date: 2018-04-22 21:31:00
subject: jumpin` jack flash

  Re: jumpin' jack flash
  By: Little Mikey to Alan Ianson on Mon Apr 23 2018 02:49 am

 LM> Now this is REALLY confusing as the first two tests just got resent, and
 LM> if you are replying to the original test, then if the uplink cannot handle
 LM> a regular fts-0001.016 compliant pktheader it should show up later without
 LM> the first test (the one you just replied to) as it will be a dupe in that
 LM> pkt. Hopefully that will tell the tale and eleviate the confusion.

I only see the one message here so if there were more than one transmissions I
can only tell you that I replied to the one I received!

The one I replied to has a path of 153/7001 7715, and the message I am replying
to now has a path of 153/7001 154/10 (and a few others).

 LM> Also I sent out a third test that if it doesn't show up here should
 LM> confirm that the uplink in question indeed cnnot process fts-0001.016
 LM> compliant pktHeaders ... or whatever the kids are calling them these days.

 LM> For the record this reply is being sent to an uplink that CAN handle 
 LM> fts-0001.016 compliant pktHeaders as this reply should confirm.

Confirmed. sbbsecho logs pkt files received from 153/7715 as being type 2+. Is
that different than fts-0001.016?

 Ttyl :-),
         Al


... It's not the money I want, it's the stuff.
--- SBBSecho 3.04-Linux
* Origin: The Rusty MailBox - Penticton, BC trmb.synchro.net (1:153/757)

SOURCE: echomail via QWK@docsplace.org

Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.