_Replying to a message_
By: Mark Edward Reed <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED] <[EMAIL PROTECTED]>
On: Wednesday, January 31, 2001, 12:31:42 PM
Re: [Miami] Re: telser.device
Hi Mark,
..[much ado about wanting to use telser.device missing]...
>> You need to be using a terminal that allows you to specify the device
>> name for the device you're using. Look through your terminal's
>> configuration for an entry saying serial.device (or whatever
>> alternative serial device you're using), and replace it with
>> telser.device.
> I have the setup for the terminal program set up OK. What I'm not sure
> on is how to configure the telser.device to work with Miami. I remember
> a bunch of things I'm supposed to do if I were to set it up for use with
> AmiTCP. I don't know if I'm supposed to set anything up just to connect
> with Termite.
For using it as a client (so your terminal program can telnet into some
server), virtually all you had to do was configure your terminal program.
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).
It's a while since I've used it, so I can't remember all my experimenting.
But I do remember that if I had been using telser.device with Miami (as a
server), that it was already in memory, and I didn't strike the problem of
Term requiring telser.device to be located in the Term directory, before
it could use it.
Here's the gist of things though:
Your TCP/IP stack has to be running before trying to use telser.device
(you don't have to be on-line, though).
Put telser.device (maybe you should try "DEVS:telser.device") into the
terminals serial device configuration gadget. And pick unit 0 (zero), if
you have an option for that.
I didn't have to do anything to Miami, to get telser.device working for
just a client function. I was using the terminal program to determine
what server (or IP) I was connecting to, and for the terminal
configuration.
If you wanted to use telser.device as part of a server (for a BBS, for
instance), then you needed to set up INetD parameters in Miami, similar to
how you set them up in AmiTCP. This is what I have left of telnet server
configurations in Miami:
Service: telnet
Socket: stream
Protocol: tcp
Wait: nowait
User: root
Server: AmiTCP:serv/telserd
Name: telser
Args: -telserd
Which suggests I was using something other than telser.device. Just
firing up my BBS now, with the telnet server, and I'm getting the AmiTCP
telnet daemon shell. Yep, the configuration is definitely set for the
AmiTCP telnet server.
> I'm also interested in possibly setting things up in the future for having
> a telnettable BBS. I know that is another can of worms and would probally
> require MiamiDX.
It can be done with Miami. So long as you don't need multiple hardware
interfaces (LANs and serial ports, etc). Any TCP/IP stack handles
multiple TCP connections.
> I can try just putting the telser.device in DEVS: and seeing if it will run
> without hassle, but I'm worried about all the different thins I'm supposed
> to set up. (Like all the db directory files, ect...)
Until it's registered, and when I tried to contact the author I couldn't
reach them, parts of the database are ignored anyway. On top of that,
it's badly documented.
> Later I do plan on paying for a good telmet client. AmTelnet looks OK
> and was the one I was playing with a bit. I don't really know how good
> the Miami Telnet is since I don't have MiamiDX. (Does it allow 16
> colour ANSI screens?)
Yes it does, though since you're using your CLI console, you're limited to
it's interface (all the problems associated with using different fonts,
and colours, etc., that you get with the CLI).
I found AmTelnet a bit dire, like many MUI programs.
The best terminal program I've used is Term, and using the telser.device
with it, made it the best telnet client I've ever used.
> If I get the BBS setup, I understand that a lot do use the telser.device.
> So I'll need to know what I'd need for that as well.
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.
--
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]".
