KpyM Telnet/SSH Server - Forum
Display Issues |
Michael Karami |
Display Issues |
Mar 19 2006 19:28 |
|
Thanks for your help on allusers.bet script. Now everything works ok, except when I am running my program, there are some display issues. For example the program is simply a C++ console application and it has a clear screen function to obviously clear screen. When this happens in the program, the next display of screen jumps to the firs line after clear screen; but in KTS, there are reminance of the previous displays in the rest of the screen. Also if there are more than 20 chars on the same line, it does not wrap it and the screen goes blank. I hope I explained things correctly for you. Please advise. Thanks.
Michael Karami
I.T. Director
|
Kroum Grigorov |
|
Mar 20 2006 22:17 |
|
What you describe looks to me like if there is some screen size mismatch between server and client. Most telnet clients negotiate window size upon connection and you should not have problems with them. However some older (or simplier) telnet clients do not initialise screen size. In that case KTS would use it's default screen size ( 80 x 24 ) that is default for most windows telnet clients too. But if your telnet client has some other screen size ( and does not negotiate the size ) you will have the described behaviour.
To fix that, you can try to adjust KTS default screen size so that it best matches your telnet client screen size. You should do the following:
1) in kts.ini file set buff_height = 0 this will switch off scrollback buffer,
set width and height too, these are screen_width and screen_height parameters.
2) you have to fix TERM.exe.lnk too( this is the shortcut in KTS directory ). In the "Layout" tab set "Window size width/height" and "Screen buffer size width/height" so that they match your telnet client screen size ( make sure that there is no scrollback buffer )
Note that you should change screen size in BOTH 1) and 2), I will make these params easier to adjust in the next KTS version.
Tell me if that helps.
Kroum
|
bob |
same problem |
Dec 12 2006 16:08 |
|
Hi,
I'm experiencing the same problem. Should I still follow these instructions, or has the new released been updated to help me configure xpym. BTW, I'm using sshd, not telnetd.
Thanks,
Bob Rossi
|
Kroum Grigorov |
|
Dec 13 2006 21:36 |
|
Yes, try the same workaround, only for step 2) change term-ssh.exe.lnk properties instead TERM.exe.lnk
Kroum
|
Bob |
|
Dec 14 2006 01:55 |
|
How come your ssh server can't negotiate the size properly? I would very much like this to work. I followed the suggestion that you gave, and things work better, however, I'd really like it to work out-of-the-box.
Can I provide you with more information so a newer release can automatically work?
BTW, thanks for the great ssh server. FYI, I'm using the mingw/msys environment. This environment does not work with the Cygwin ssh server, and never will. However, with your server I have most things working nicely. I need the backspace key to work, and I need to get vim working a little better.
Bob Rossi
|
Kroum Grigorov |
|
Dec 14 2006 21:44 |
|
The "size negotiation" problem comes from the ssh client you are using.
What I can suggest you is to use [url=l0c41://www.chiark.greenend.org.uk/~sgtatham/putty/download.html]PuTTY[/url] ssh client, I believe there is a linux port too.
Once you set up PuTTY you can check this [url=l0c41://www.kpym.com/phpbb/viewtopic.php?t=37&highlight=backspace]thread[/url] for configuring backspace key.
Kroum
|
Bob |
|
Dec 15 2006 02:02 |
|
I do use putty on a daily basis. However, right now, I'm using standard 'ssh'. This is probably the most widely used ssh client there is. Don't you think the negotiation should work with it?
Bob Rossi
|
Bob Rossi |
|
Dec 18 2006 22:04 |
|
Well, what do you think? Don't you want your ssh server to work with the most popular ssh client in the world?! :)
Is there something I can do to help you out?
Thanks,
Bob Rossi
|
Kroum Grigorov |
|
Jan 03 2007 20:27 |
|
Huh, finally got little free time:)
The good news is that I was wrong accusing the standard 'ssh' for your problems. I checked it recently and it works fine with KTS.
Now the bad news; I tested KTS with some windows bash port and got the same problems you describe(del key doesn't work, screen problems, ctrl+c not working, etc.)
I believe the problems you have are tied with the mingw/msys environment you are using.
If you can post a link to the envirenment you are using.
I will have a look at it, but frankly I don't see any good reason for all these ports to work that bad.
Kroum
|
© 2007 - 2008 Kroum Grigorov
|
|