TIP: Click on subject to list as thread! ANSI
echo: locsysop
to: Rod Speed
from: Paul Edwards
date: 1993-04-28 00:17:50
subject: sealink

Hello Rod!

Now let the fun begin.  I wrote a communications package, and in it I used
Sealink.  To do this I downloaded the Sealink C source code written by Thom
Henderson of SEA.  It took me a long time to debug it to make it work. 
Hence I am very familiar with the workings of Sealink. The sender of
Sealink waits until he gets either a 'C' (0x43) or a NAK. It then sends
block 0.  The 'C' means CRC checking is to be done.  If the 'C' or NAK is
followed by a block 0 and 0xff, the sender knows it is speaking to another
Sealink, otherwise it assumes Xmodem.  If the receiver is Sealink, the
sender will send a block 0, instead of block 1.  The receiver will make use
of this to get the filename automatically.

Dial on to any BBS you care to name, do a Sealink download, and you will
find that NOTHING happens.  It is up to YOU to send out a NAK or 'C'.  THAT
is what triggers the BBS off.  I did do an upload from Telix, and I waited
and waited for you to begin the download, but you didn't.  Telix just said
'waiting'.

In other words, you are wrong and a hoon.  :-)  BFN.


Paul

--- GoldED 2.40
* Origin: Ten Minute Limit (3:711/934)

SOURCE: echomail via fidonet.ozzmosis.com

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™.