On Sat, 20 Apr 2002 17:00:58 -0500, Samuel W. Heywood wrote: > On Sat, 20 Apr 2002 14:44:52 -0500, Sam Ewalt wrote:
>> Ok. I tried this following your example and I get the message of >> "unable to resolve sdf.lonestar.org" >> I just let the APM install itself and didn't change or configure >> anything. >> What do I need to do to get this to work? Sams, if I may interject at this point ? I did NOT let the .APM install itself as it is against my religion. I took it apart and tried the SSHDOS.exe by itself. > Maybe there is something wrong with your WATTCP.CFG Possibly, because if I recall correctly I had to DELETE WATTCP.cfg to get SSHDOS to work. I just checked my HD and I do NOT have that file. I use both TELNET and SSHDOS and I have only a CONFIG.tel. There was a question about how to get the "T" key to call SSHDOS. Simply rename SSHDOS.exe to Telnet.exe. You may encounter a problem in the future if you don't remember what you did, but that is the only drawback in addition to not being able to "hotkey" to Telnet. Your other option is to make your own hotkey for SSHDOS as I did: Arachne.cfg: ShiftF7 file://sshdos.dgi and in MIME.cfg I added: file/sshdos.dgi |@sshdos.exe -tvt100 caverge-arachne arachne.cz The commandline syntax is: Usage: sshdos [options] username remotehost and you can see I'm taking the default cipher which is "3des". I have no "path.cfg" and I use Telnet and SSHDOS with both a dial-up connection (using EITHER EPPPD or LSPPP) and also with a pre-established network connection using BOOTP. I hope this is useful to someone. - Clarence Verge - Back to using Arachne V1.62 ....
