182 lines
6.4 KiB
Plaintext
182 lines
6.4 KiB
Plaintext
Tested my system in various compatibility modes against two D'bridge
|
|
installations:
|
|
|
|
1:2601/506 d'bridge 1.21
|
|
1:138/120 d'bridge 1.30
|
|
|
|
|
|
Tested both with Wazoo, all worked fine. Not logged here.
|
|
|
|
wazoo yes/no yes == YOOHOO/2U2 etc
|
|
fsc001 no yes == by-the-book; no 'C' as NAK!
|
|
fsc011 no yes == allows skipfilename
|
|
|
|
----------------------------------------------------------------
|
|
wazoo no
|
|
fsc001 no
|
|
fsc011 no
|
|
|
|
File attaches
|
|
|
|
* FS0/FS1: Calling 1:2601/506, "Beacon Hill CBIS" 1-412-962-9514 19:22:32
|
|
* Connected at 9600/ARQ/HST
|
|
* FS2: Initial synchronization
|
|
* FS3: Waiting for clear line
|
|
* FS3: Sending TSYNC
|
|
* FS4: Sending Packet
|
|
* XMODEM/CRC: OUTBOUND\3384.OUT 272
|
|
* XMODEM/CRC: Sending as "11105495.PKT" 272
|
|
* XMODEM/CRC: Recv'd 0x01 128 SEAlink ACK packet
|
|
* XMODEM/CRC: Recv'd 0x02 256 SEAlink ACK packet
|
|
* XMODEM/CRC: XS4: Recv'd 0x03 at EOF 0 SEAlink ACK packet
|
|
* XMODEM/CRC: Protocol Complete 0
|
|
* FS5: Packet sent (272 bytes)
|
|
* FS6: Sending (possible) attached files and requests
|
|
* TELINK/CRC: FOO 21
|
|
* TELINK/CRC: SendFN got 0x04 1 unknown
|
|
* TELINK/CRC: Skip filename, ignored 1 D'bridge tried to skipfilename
|
|
* TELINK/CRC: Skip filename, ignored 2
|
|
* TELINK/CRC: Recv'd 0x00 0 ... eventually accepted MODEM7
|
|
* TELINK/CRC: XS4: Recv'd 0x01 at EOF 0
|
|
* TELINK/CRC: XS4-3: 'C' as EOT NAK? 0 out-of-spec NAK character
|
|
* TELINK/CRC: (OK...) 0 tolerated
|
|
* TELINK/CRC: XS4: Recv'd 0x02 at EOF 0 SEAlink ACK packet I guess
|
|
* TELINK/CRC: Protocol Complete 0
|
|
* FS7: File attach complete (1 files, 21 bytes)
|
|
* FS8: Attempting Mail Pickup d'bridge didn't hang up when
|
|
* FR2/WVx: Waiting for sync there was no mail waiting
|
|
* Total connect time was 1:31 for me, hence the 1:31
|
|
* Packet to 1:2601/506 sent
|
|
Msg #22 --> 1:2601/506 (SENT)
|
|
|
|
Except for 'C' as NAK, worked fine. SEAlink ACK packet data ignored
|
|
cuz Fido doesn't do SEAlink.
|
|
|
|
|
|
* FS0/FS1: Calling 1:138/120, "Group Medical BBS II" 1-206-581-9088 19:24:06
|
|
* Connected at 2400
|
|
* FS2: Initial synchronization
|
|
* FS3: Waiting for clear line
|
|
* FS3: Sending TSYNC
|
|
* FS3: Sending TSYNC
|
|
* FS4: Sending Packet
|
|
* XMODEM/CRC: OUTBOUND\4931.OUT 271
|
|
* XMODEM/CRC: Sending as "16759406.PKT" 271
|
|
* XMODEM/CRC: Protocol Complete 0 note no SEAlink ACK packets...
|
|
* FS5: Packet sent (271 bytes)
|
|
* FS6: Sending (possible) attached files and requests
|
|
* TELINK/CRC: FOO 21 accepted MODEM7 filename
|
|
* TELINK/CRC: XS4-3: NAK 0 immediately, no SEAlink stuff
|
|
* TELINK/CRC: Protocol Complete 0
|
|
* FS7: File attach complete (1 files, 21 bytes)
|
|
* FS8: Attempting Mail Pickup
|
|
* FR2/WVx: Waiting for sync
|
|
* Total connect time was 0:52 as before
|
|
* Packet to 1:138/120 sent
|
|
Msg #23 --> 1:138/120 (SENT)
|
|
|
|
|
|
'C' as NAK on EOT went away? Probably it simpyl ACKed eveything (no errors
|
|
or timeouts).
|
|
|
|
----------------------------------------------------------------
|
|
wazoo no
|
|
fsc001 yes
|
|
fsc011 no
|
|
|
|
File attaches
|
|
|
|
Almost no program passes this (SEAdog, Bink I think)
|
|
|
|
|
|
* FS0/FS1: Calling 1:2601/506, "Beacon Hill CBIS" 1-412-962-9514 19:29:35
|
|
* Connected at 9600/ARQ/HST
|
|
* FS2: Initial synchronization
|
|
* FS3: Waiting for clear line
|
|
* FS3: Sending TSYNC
|
|
* FS4: Sending Packet
|
|
* FSC-0001 XMODEM: OUTBOUND\3384.OUT 272
|
|
* FSC-0001 XMODEM: Sending as "06900482.PKT" 272
|
|
* FSC-0001 XMODEM: Recv'd 0x01 128 more SEAlink ACK stuff
|
|
* FSC-0001 XMODEM: Recv'd 0x02 256
|
|
* FSC-0001 XMODEM: XS4: Recv'd 0x03 at EOF 0
|
|
* FSC-0001 XMODEM: Protocol Complete 0
|
|
* FS5: Packet sent (272 bytes)
|
|
* FS6: Sending (possible) attached files and requests
|
|
* FSC-0001 TELINK: FOO 21
|
|
* FSC-0001 TELINK: SendFN got 0x04 1
|
|
* FSC-0001 TELINK: Skip filename, ignored 1
|
|
* FSC-0001 TELINK: Skip filename, ignored 2 as before
|
|
* FSC-0001 TELINK: Recv'd 0x00 0
|
|
* FSC-0001 TELINK: XS4: Recv'd 0x01 at EOF 0
|
|
* FSC-0001 TELINK: XS4-3: 'C' as EOT NAK? 0 Fido won't accept 'C' as NAK
|
|
* FSC-0001 TELINK: XS4: Recv'd 0x02 at EOF 0
|
|
* FSC-0001 TELINK: XS4-3: 'C' as EOT NAK? 0 and simply ignores it
|
|
* FSC-0001 TELINK: XS4: Recv'd 0x02 at EOF 0
|
|
* FSC-0001 TELINK: XS4-3: 'C' as EOT NAK? 0
|
|
* FSC-0001 TELINK: XS4: Recv'd 0x02 at EOF 0
|
|
* FSC-0001 TELINK: XS4-3: 'C' as EOT NAK? 0
|
|
* FSC-0001 TELINK: XS4: Recv'd 0x02 at EOF 0
|
|
* FSC-0001 TELINK: Protocol Complete 0 ... so fileattach fails
|
|
* FS7: File attach failed
|
|
(Error sending packet or file(s))
|
|
* Total connect time was 0:52
|
|
|
|
... Failed because of 'C' as NAK. Fido ignored it, and therefore the block
|
|
or EOT didn't get re-sent. (only NAK causes that).
|
|
|
|
|
|
* FS0/FS1: Calling 1:138/120, "Group Medical BBS II" 1-206-581-9088 20:12:58
|
|
* Connected at 2400
|
|
* FS2: Initial synchronization
|
|
* FS3: Waiting for clear line
|
|
* FS3: Sending TSYNC
|
|
* FS4: Sending Packet
|
|
* FSC-0001 XMODEM: OUTBOUND\4931.OUT 271
|
|
* FSC-0001 XMODEM: Sending as "09458779.PKT" 271
|
|
* FSC-0001 XMODEM: XS0: Waiting to Start 0
|
|
* FSC-0001 XMODEM: Protocol Complete 0
|
|
(Error sending packet)
|
|
(Error sending packet or file(s))
|
|
* Total connect time was 0:35
|
|
|
|
What's happening here is that Fido is a bit over-eager on FSC-0001. It only
|
|
sends one TSYNC instead of TSYNC...wait for response, before dropping into
|
|
XMODEM to send the packet. D'bridge missed or ignored the first TSYNC, and
|
|
Fido was in XMODEM and it's all too late ....
|
|
|
|
This is a screwup on my part, because I have a control:
|
|
|
|
multi-tsync yes/no
|
|
|
|
That is supposed to control that. I am in the middle of moving Fido from
|
|
Lattice 2.15 to M'soft C 5.1, so I can't tweak the code right now. But I think
|
|
the story is somewhat plain?
|
|
|
|
Looks to me like D'bridge's XMODEM is AFU, in it's use of 'C' as anything
|
|
more than the initial NAK. (Seems to me I remember this from a loooong time
|
|
ago...)
|
|
|
|
The TSYNC thing may screw up other mailers. It "shouldn't" miss the first
|
|
TSYNC, but there's that note at the bottom of page 9 in FSC-0001-9 that sez:
|
|
|
|
"Although the above shows the sender emitting only one
|
|
TSYNCH, it is reccommended that a timeout of 5-20 seconds
|
|
should initiate another TSYNCH. The receiver should tolerate
|
|
multiple TSYNCHs."
|
|
|
|
I'll tell Mike Bryeans about this, maybe his problem is the TSYNC thing.
|
|
He said he had erratic problems. Mine were not erratic, anyways.
|
|
|
|
It oughta be tested with Bink, Seadog, FrontDoor, etc ...
|
|
|
|
MY CONCLUSIONS:
|
|
|
|
-*- 1.30 seems to require more than one TSYNC to get started.
|
|
|
|
-*- Both versions don't do a correct XMODEM.
|
|
|
|
-*- 1.21 seems to do a tolerant SEAlink instead of XMODEM. 1.30 seems to
|
|
separate them out, and not do SEAlink when Fido doesn't respond. (Either
|
|
works.)
|