_Replying to a message_
By: Fred Wright <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED] <[EMAIL PROTECTED]>
On: Tuesday, February 20, 2001, 10:31:45 AM
Re: [Miami] Re: telser.device
Hi Fred,
>> I found I had to put the telser.device file into the same directory as the
>> terminal program, so I suspect I should have put "DEVS:telser.device"
>> rather than just "telser.device" into the serial device gadget
>> (remembering that device names are usually CaSE SeNSItive).
> 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.
>> By the time I've remembered how I did it before, you'll probably work it
>> out too. One thing I never did get to work, that way, was file transfers.
>> They just bombed out terribly. Which was probably just due to general
>> internet comms problems I has having at the time. I never resolved it, as
>> my ISPs didn't allow servers, so there wasn't much motivation.
> 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.
--
Bye,
Tim.
http://www.picknowl.com.au/homepages/Tim_Seifert/
mailto:[EMAIL PROTECTED]
(Modbury, near Adelaide, South Australia)
Video productions, electronics engineering, service and technical
support, and more. For further information, visit the web site.
*** DO NOT SEND JUNK MAIL ***
--
To unsubscribe send "unsubscribe miami-talk-ml" to
"[EMAIL PROTECTED]". For help on list commands send "help" to
"[EMAIL PROTECTED]".
