For a long time all I had was an old Windows 98 computer and version 3.85 of A.T. Recently I was able to acquire a new machine runninig Windows XP Pro SP2. I downloaded the current (6.28) version, tried it out, and bought it this afternoon. However, I am running into something puzzling. I use A.T. to login to a remote netBSD server with SSH2. My ISP has multiple servers, so with the old version I had multiple *.tnt files, one for each server, although I most commonly use just one of them. I ported them over to the new computer and version of A.T. Every time I logout from the server, A.T. prompts me that the connection / configuration (whatever it's called) file has been modified. No matter how many times I say to save the modified file, the next time I get the same prompt that the file has been modified: do I want to save it or not. Is there something in the current version of A.T. that chokes on these old *.tnt files? Apart from the save prompt, everything seems to be working perfectly well.

[size=1][ September 19, 2008, 07:51 AM: Message edited by: Brian T. Pence ][/size]

Paul,

There are so many options in the config file that it is sometimes hard to know which one changed, prompting the (modified) indicator. Most commonly, though, it would be either the size or position of the window. With 'remember position' enabled, just changing the position of the window can cause this prompt.

Are you running with the tabbed interface?

I would suggest the following:

1. Disable the 'remember position' flag and see if the prompt goes away.

2. Select a default for the prompt on the 'Global' property tab. Choose either 'yes' or 'no' for the 'save on exit' option.

If neither of these options is satisfactory, let me know and I'll look at it some more.

Not using tabbed interface (not even sure how to turn it on and at present have no need for it, as I only telnet/SSH to one client at a time).

Remember position flag was already off.

Changed the save on exit prompt to no. Prompt went away, at least as of the first time I used it. Thanks, will let you know if anything else needs attention.

There is one thing. When I start A.T. from a .tnt file, I have to resize the window after I am logged on to my shell account in order to get the full screen size in use. I reduce the window, jiggle the lower right hand corner to "sqeeze" the text I get on login to the shell, and then maximize the window. I don't know why, but if I don't, I do not get use of the full screen. The output from the shell does not fill up the screen. If I do, then I get the full screen. It's certainly not a show stopper, just requiring a little mouse jiggling. It was the same way with earlier versions as well.

I just did a little bit of experimenting. It seems to be the resizing of the window which I mentioned in my last post that is triggering the "modified" indicator.

Screen size is one of those things that is stored in the configuration file and used the next time you start up. Changing the screen size WILL cause the (modified) parameter to display.

As for the 'jiggling' chaning the behavior on the host side, this is entirely possible. When the window is resized, the window dimensions are sent to the host so the host can draw the screen size properly. It is possible that the *initial* size is not getting set and resizing the window causes the proper dimensions to be set on the host. The unix command 'stty -a' will show you (among other things) the values that the host has for the terminal rows and columns. Please try your procedure below, but make note of the stty -a output at each step. This may give me a clue as to where to look next.

Regards,

Brian

As long as I jiggle things, I am satisfied. When I first login to the shell host, stty -a shows 24x80, and if I do not change anything, this is what it stays. However, if I reduce the window, shrink it, and then maximize the window, stty -a shows 30x97, which fills up the window. There is no real *problem* here, it just takes some jacking around to be able to use the full screen area. (Incidentally, this board now requires accepting 47 2/3 cookies to use it, which I definitely do not like. I consider cookies to be little better than viruses. Many of them are of the __utmX variety which show up on a lot of boards. Why are cookies necessary to use this board at all?)

Which SSH server are you running (and what version)? This info should be available on the Options->SSH Info dialog.

Unfortunately I cannot copy and paste from that dropdown (why not?), so I have to put it in by hand, which is prone to error. Is this what you are looking for?

My ID: SSH-2.0-1.81 sshlib: Absolute Telnet
Server ID: SSH-1.99-Open SSH_4.4 NetBSD_Secure_Shell-20061114
Key Exchange: diffie-hellman-group14-sha1
(There is more, but since I cannot copy and paste, it is tedious to try to type in by hand.)

That's enough. When a shell is started, Absolute passes the initial dimensions of the screen to the server. After that, each time the dimensions change, the new dimensions are sent to the server and (if the host app supports it), the screen can be redrawn with the new size. It seems in your case that the proper initial dimensions are not being sent to the server. I'm curious if it is a bug on the server side. I have never seen this before. Unfortunately, I don't have an OpenSSH version 4.4 compiled or I'd give it a try myself.

Still thinking........

This is an ISP out of New York City which seems to have many, many subscribers. When I do a 'who' I get a lot of responses on just one of their five shell hosts. Until recently I had to use dialup, and they have dialup PoPs thoughout much of the USA, so they are not a trivial mom and pop in the garage operation. The login give me "NetBSD 4.0 (PANIX-12) #0: Thu Jul 10 19:38:33 EDT 2008" for a shell login. Recently I moved to a DSL broadband connection from a major TELCOM service provider, and AT works just find (I am happy enough that I have been willing to pay the license fee a couple of times) except for the minor nuisance of having to resize the screen twice at login to get the maximum use of the window. It is not a show stopper, just a minor annoyance.