On Thursday 20 November 2003 08:39 am, Shawn Tayler wrote: > On Wed, 19 Nov 2003 22:36:20 -0800 (PST) Keith Morse <[EMAIL PROTECTED]> > > professed: > > Because the F'ing vendors of those devices only make their > > config/management tools able to run under windows and the bulk of your > > staff are thoroughly perplexed as to the nature and reason for a > > command line. > > I know what you mean. Our new comm system need you to run a DOS based > serial app to configure parts of the system while using a custom > Telnet/FTP/something IP Winblows app for other configs at the same time. > Win2K is fairly inept at DOS stuff.... Makes it interesting..
This may be of help in **some** cases: Particularly in cases where a CLI communications program or terminal emulation is involved, I would be tempted to give kermit a try. I have to dial into various vendor's servers for telnetting and/or transferring files. Many of them only offer tech support for their own apps or hyperterminal. I was motivated to try new methods because the transfers were "exceeding the error limit" fairly frequently. I wasn't sure whether the problem was the software, the phone lines (rural area) or a combination of both. The vendors and phone company, however, were sure it was someone else's problem. I've found that kermit is at the base of many communication applications. After learning how to dial a modem in kermit, I was able to connect and conduct my business successfully in more than half the cases. In all the cases where I am able to use kermit by itself, my transmissions have had few or no (none, zip, zero) errors. On a side note, the online documentation states that you can run kermit over ssh using command line options. Kermit appears to be quite extensive in abilities. Once again, I find myself with much to learn. Andrew Gould _______________________________________________ Linux-users mailing list [EMAIL PROTECTED] Unsubscribe/Suspend/Etc -> http://smtp.linux-sxs.org/mailman/listinfo/linux-users
