Setting up Telser with MiamiDX - SOLVED!

[broken]

Anyone have a guide to setting up Telser to work with MiamiDX instead of AmiTCP?

I have had Telser work just fine with AmiTCP, but my current install I am using just MiamiDX and during the Telser install it expects to find AmiTCP installed.

[broken]

OK, worked this out.

I created an empty drawer and called it AmiTCP.

Made an assign for AmiTCP and pointed it at that drawer.

Installed Telser picking AmiTCP at the install prompt (it was looking for the AmiTCP assign before).

It breezed through installing all the necessary files and configs.


Thats it!


Rebooted and launched MiamiDX.

Loaded up NComm and was able to telnet out to my favorite bbs's.


Unsure about incoming telnet connections, but outgoing certainly works.

[Kernel]

OK, worked this out.

I created an empty drawer and called it AmiTCP.

Made an assign for AmiTCP and pointed it at that drawer.

Installed Telser picking AmiTCP at the install prompt (it was looking for the AmiTCP assign before).

It breezed through installing all the necessary files and configs.


Thats it!


Rebooted and launched MiamiDX.

Loaded up NComm and was able to telnet out to my favorite bbs's.


Unsure about incoming telnet connections, but outgoing certainly works.

Did you need to do anything special setup wise?  I can't get this working and it sounds like all you need to do is make the AmiTCP assign, install it, reboot, run MiamiDx, run NComm, change to telser.device and you're off?

I might have to start disabling programs to see f there is a conflict...

[broken]

I wrote a brief guide on setting it up a couple years ago over @ Amibay:

http://www.amibay.com/showthread.php?7665-Quick-Guide-to-installing-setting-up-Telser-(modem-simulator)-with-MiamiDX

[pVC]

And of course if you just need the client to connect the telnet bbs'es you could use real telnet clients without needing this telser step.

AmTelnet should work quite well and especially DCTelnet is made for telnetting bbs: http://aminet.net/package/comm/tcp/DCTelnet_16

But if you want to run your own bbs, then telser or telnetd is needed.

[Kernel]

I wrote a brief guide on setting it up a couple years ago over @ Amibay:

http://www.amibay.com/showthread.php?7665-Quick-Guide-to-installing-setting-up-Telser-(modem-simulator)-with-MiamiDX

Yes I actually had already found this... but it just doesn't want to work for some reason.  I'm looking at a "System device error: telser.device" message in Terminus right now.

Also, the TelserMon commodity shows nothing in the list; clicking on the buttons does nothing.

 suppose I'll need to disable everything in my startup scripts to see if something is interfering with it...

As to the other recommendation of using a Telnet program, yes I will try that of course but I like the idea of being able to use a terminal program for it as well.

[Kernel]

I just tried term and the error message is

'term' has a problem.
Device "telser.device" is currently busy!

This makes no sense to me...

[Kernel]

Ok so in another troubleshooting effort, I installed EasyNet and then reinstalled Telser.  Still getting the same problem.  NComm and Terminus throw a general error trying to access the telser.device, and Term pops up a "device is busy" message.

I can ping internet addresses fine; I have no idea what would be stopping telser.device from working.  I installed it onto an AmiKit OS 3.9 installation with Terminus and it works fine?!

Could there be some incompatibility with using a USB dongle via DENEB on the pegasus.device?

[Kernel]

SOLVED!

The AmiTCP:bin/telser program was corrupted.  Reinstalling using the supplied installer (multiple times even!) didn't fix it even with a complete wipe of the AmiTCP: directory first or a wipe and re-extract of the aminet 1.40 archive... but copying the file manually from the install folder to AmiTCP:bin/ worked.  I used a combination of SnoopDOS and an AmiKit install of OS 3.9 to track it to this program.

I copied the program manually from the install directory to AmiTCP:bin/ directory and it immediately started working.

So I guess the question that lingers now is do I have a flakey Installer program, a flakey Installer script for telser 1.40, an even flakier A3K that I thought, or could a running patch/utility be wreaking minor bits of havoc on installations I'm running?

BTW, I was able to duplicate the issue on the AmiKit side as well so I'm leaning away from the A3K being an issue.

Insight would be welcomed.