Menu
▾
▴
#45 win32: LINES value must be >= 2 and <= 0: got 1
When logging into a Windows host remotely via
Microsoft’s bundled telnet service (tlntsvr.exe),
programs compiled with PDCurses will display the
folowing error (for example the fireworks.exe demo):
LINES value must be >= 2 and <= 0: got 1
initscr(): LINES=1 COLS=1: too small.
Tested on Windows 2003 R2 with PDCurses v2.8, compiled
with ‘nmake –f vcwin32.mak’
Seems that this is an issue when run from other telnet
or ssh servers as well.
Regards,
Ron
Discussion
Logged In: YES
user_id=27933
PDCurses is not designed to work in any environment except a
local console. See some of my other comments on the subject:
http://sourceforge.net/forum/forum.php?thread_id=733874&forum_id=95731
http://sourceforge.net/tracker/index.php?func=detail&aid=676826&group_id=30480&atid=399168
http://lists.gnu.org/archive/html/bug-ncurses/2005-11/msg00027.html
NCurses may work for you. Or you can use Remote Desktop
instead of telnet; or rewrite the app to use stdio. I'm
afraid that's all I can offer you right now. But I will look
into replacing that error message with a more informative one.
Logged In: YES
user_id=27933
Originator: NO
I've taken another look at this. I telnetted in from localhost, and it actually mostly worked. Apparently Windows has some ability to translate the console calls to ANSI. However, so far I can't make it work except with Windows' command-line telnet. (Things that don't help: manually settings LINES, COLS and TERM.) I'll look into it further.
Logged In: YES
user_id=27933
Originator: NO
Confirmed that it also works remotely (from the Windows command-line telnet client only). There are some serious problems (whether local or remote), like frequent failure to recognize the Enter key. Possibly better than nothing, but I wouldn't want to rely on it... I'll keep on it though.
Logged In: YES
user_id=27933
Originator: NO
Hmm, found this:
http://groups.google.com/group/comp.terminals/msg/919b154fc2770f47
The Microsoft Telnet client and server when used together negotiate
a special terminal type, NTVT, which turns the telnet client into
a relay for the Windows console. The data structures used in both
directions are binary blobs representing Windows events. There is
no stream as you would think of it for a terminal. -- Jeffrey Altman
So, that explains it. Funny it doesn't work better, given that. Anyway, I'm afraid that brings this bug back to the status of "Won't Fix". Maybe you can find a suitable client that supports NTVT?
Logged In: YES
user_id=27933
Originator: NO
...or as most other references seem to have it, VTNT.