Celestial Software

(If I am in the wrong forum, please direct me accordingly.)

I run Absolute Telnet 3.85 on Windows 98. (I cannot afford to upgrade either.) I establish a dialup PPP connection to my ISP, which runs netBSD servers, and "A.T." into my shell account using SSH-2 and XTERM emulation.

From time to time I want to transfer files between my shell account and my Win98 box. Just this evening I had no problem transferring straight text files in both directions with Ascii Zmodem transfer. However, I am not able to download a binary file from the shell host to the Win box.

On the shell host, I cd to the directory where the file resides. Then I enter (no quotes) 'sz -b sample.jpg' for a 252830-byte JPEG file. The A.T. Zmodem receive message box opens, and the "progress meter" shows file transfer. But as soon as it appears that the transfer is complete, I get the error message "Transfer failed!" and there is no file on the local machine.

This happens every time I try it. I know that the JPEG file is good, because I can open it with a web browser (Opera, in my case). See http://www.panix.com/~bartlett/sample.jpg . (No viruses, but obviously appropriate precautions should always be taken.)

Any ideas on why Ascii transfers succeed and binary transfers fail? Thanks.

[ November 02, 2006, 12:32 AM: Message edited by: Brian T. Pence ]

Paul,

Can you test with 5.06 to see if it makes a difference? A number of changes have been made to the file transfer since 3.85.

http://www.celestialsoftware.net/telnet/AbsoluteTelnet5.06.exe

Brian

I downloaded it but have not installed it. Will I be charged if I install it? My year of free upgrades has come and gone. You are entitled to the fruits of your labor, but I genuinely am in a money pinch just now. (I think A.T. is a great product, and your support shines. I have been using it for several years now and have pitched it on my ISP's in-house newsgroup.)

If I install the later version, will my *.TNT files still be valid? They are what I use to access my ISP's servers so that all my settings are rolled in. Do I just install the later version right over the top of what I have?

I forgot to mention that the problem with binary file transfers only arose after I switched to using SSH-2, if that is significant. Most of the transfers I do are Ascii.

You can install 5 on top of what you have or in a separate directory.

You can always install the older version after you're done testing. TNT files will not be affectedd, but make a copy of them if you're worried about that.

Just a short time ago I finally had a chance to install version 5.06. The installation went fine, but it turns out not to be usable, at least as things are now set up.

I started v. 5.06 and went to open one of my .tnt files. Very quickly I got an error message: "Connect to panix2.panix.com failed. Winsock Error: the namelen argument is incorrect." (My ISP has five shell servers. I commonly login to one of them specifically for SSH-2. However, I have SSH-2 .tnt files set up for all five.)

So v. 5.06 is not working. I reinstalled v. 3.85 back over the top, and I am able to login again just as before. When I did the installation, I forgot to install 5.06 in a separate directory, so it and the reinstallation of 3.85 went into the same directory.

I do have a problem with this machine, something having to do with name resolution, that affects three different web browsers as well as A.T. Sometimes things will hang for almost a minute and then break loose on their own. However, I got this winsock error message almot immediately, and I tried it a couple of times.

[ November 03, 2006, 06:08 PM: Message edited by: Paul O. Bartlett ]

Winsock Error: the namelen argument is incorrect You're the second person to report this. May have something to do with the new IPV6 code in version 5 not working properly under Win98. In Win98, it is supposed to gracefully degrade to IPV4-only because Win98 does not support IPV6. I'll have a look.

I do have a problem with this machine, something having to do with name resolutionI've heard of this happening on Win9x with dialup accounts. I'm not sure why it happens, but it is not A.T. specific, so I'm not going to be much help resolving that. In any case, it is not related to the problem above.

I'll have to work out the "namelen argument is incorrect" issue and get back to you to test the real original problem of zmodem transfer.

Brian