Why is it I seem to come up with the issues that no one can answer? Hmm.
Anyway, this issue was successfully resolved by:
1) eliminating software flow control (which uses chars 0x11 ^Q and 0x13 ^S).
2) setting up the 90M to allow telnet client binary duplex transfers and no
software flow control.
Xmodem/CRC sends a packet count through the datastream and surprisingly enough,
packet 17 is 0x11, which would be consumed by the modem and/or 90M.
Bob
>Has anyone successfully combined the following components for a binary file
>transfer system using XMODEM/CRC:
>
>Alpha 2100 running Digital Unix 3.2c DECServer 90M
>USRobotics Sportster 28.8 modem
>
>I've managed to get most of the other problems with my modems out of the way
>except for sending large files using XMODEM/CRC, which is the only protocol I
>can use. I can successfully send a file that is 1,986 bytes long, but it will
>fail on a file that is 2,068 bytes long (17 XMODEM packets). This is through a
>telnet session, which is the default service setup on the 90M.
>
>Bob Capps
>bob.capps_at_ps.net
Received on Wed Sep 04 1996 - 22:30:14 NZST