On Tue, 20 Feb 2001, Tim Seifert wrote:
> By: Fred Wright <[EMAIL PROTECTED]>
> On: Tuesday, February 20, 2001, 10:31:45 AM
>
> > I have it in one of my DEVS: directories, and it works fine there (with
> > VLT). That's certainly where you're supposed to put drivers. If Term
> > expects otherwise it's a bug. It also shouldn't be necessary to include
> > "DEVS:" in the name, since that's where OpenDevice() is going to look.
>
> I never did work out why it needed me to do that. But it wouldn't work,
> unless I did.
SnoopDOS is your friend. :-)
> > I've certainly used file transfers with VLT+Telser on the client side,
> > though perhaps only with Kermit. IIRC I had trouble with ZModem, which I
> > suspected was due to a transparency bug in Telser. I *have* used
> > MiamiTelnet for ZModem transfers, though.
>
> I've got them to work, where I've logged into a service as a client. But
> not when I was running my BBS through telser.device as a server.
With what transfer protocol? There are a couple of transparency issues:
1) Telser (as client at least) fails to convert transmitted CR to CR-LF or
CR-NUL. When the server correctly converts received CR-LF to CR, this
means that a real LF that follows a CR gets swallowed.
2) Given #1, I wouldn't be surprised if it failed to convert an apparent
IAC (0xFF) to IAC-IAC to get it through Telnet command parsing.
Fred Wright
--
To unsubscribe send "unsubscribe miami-talk-ml" to
"[EMAIL PROTECTED]". For help on list commands send "help" to
"[EMAIL PROTECTED]".
