[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: lynx-dev Telnet Problem with Win32 Lynx
From: |
Wayne Buttles |
Subject: |
Re: lynx-dev Telnet Problem with Win32 Lynx |
Date: |
Sat, 11 Jul 1998 08:40:05 -0400 (EDT) |
Is there any way I can get a test telnet server to play with? If it ran
on Win95 that would be awesome, but if not I do have access to an NT box.
On Fri, 10 Jul 1998, Keith Russell wrote:
> On Fri, 10 Jul 1998 11:59:44 -0400 (EDT), you wrote:
>
> >The problem is with pdcurses, not lynx. I don't know if another library
> >would have the same problem. pdcurses is asking for the term width and
> >height from Windows and it is telling it an invalid amount. I sent Keith
> >a workaround test compile, but I can't really dive into the problem right
> >now. I don't even have a way to test it myself if I had time.
>
> Wayne, here are the results with your test compile:
>
> 1. With the UniVerse telnet server, same results (unfortunately). From
> what Dean said, it sounds like the problem is not with Lynx OR pdcurses,
> but with uvtelnet not accepting the parameters. Am I wrong?
>
> 2. With a third-party server, Lynx does run (the process shows up with a
> ps); it didn't before. However, it still doesn't display 8-(.
>
> Keith
>
> >On Fri, 10 Jul 1998, Dean Walker wrote:
> >
> >>
> >> Keith,
> >>
> >> Yes, I misunderstood your problem. I have now connected
> >> to a UV telnet server (on NT) and shelled out to DOS to
> >> run Lynx, and get the same error. Setting LINES & COLUMNS
> >> in this shell also has no effect.
> >>
> >> Thoughts:
> >> When a telnet client connects to a server, I believe it
> >> can tell the server the width and height of it's window
> >> (TELOPT_NAOL, TELOPT_NAOP), along with other stuff like
> >> the terminal type and whether to echo or not.
> >>
> >> The uvtelnet server does not look for the width/height
> >> and does not put them in the environment where they would
> >> be useful. It does put the termtype in.
> >>
> >> It would be useful for the uvtelnet server to do this
> >> as it would help Lynx and other programs using curses to
> >> work within the shell, and it would also mean that the
> >> TERM values for page width and depth could be set up also.
> >>
> >> Does anyone know why either initscr() or Lynx cannot get
> >> the values of LINES & COLUMNS, as above ?
> >>
> >> Cheers, Dean
> >>
> >> ---
> >> Dean Walker
> >> mailto:address@hidden
> >>
> >>
> >> > -----Original Message-----
> >> > From: address@hidden [mailto:address@hidden
> >> > Sent: Thursday, July 09, 1998 5:49 PM
> >> > To: address@hidden
> >> > Subject: Re: lynx-dev Telnet Problem with Win32 Lynx
> >> >
> >> >
> >> > Dean, I am trying to telnet TO Lynx on an NT, not telnet out.
> >> >
> >> > The info-ardent list is a good suggestion. Thanks.
> >> >
> >> > Keith
> >> >
> >> > On Wed, 8 Jul 1998 09:34:49 +0100 , you wrote:
> >> >
> >> > >
> >> > >Keith,
> >> > >
> >> > >I have tried this on my PC and found no problem
> >> > >connecting lynx to telnet://mymachine. I got the usual
> >> > >UniVerse prompts for user/passwd/account. What Telnet
> >> > >client is your Lynx launching ? What version of UV ?
> >> > >Are you redirecting output to a file, which would
> >> > >generate the same message ? Have you tried the info-ardent
> >> > >list as well ?
> >> > >
> >> > >Cheers, Dean
> >> > >---
> >> > >Dean Walker
> >> > >mailto:address@hidden
> >> > >
> >> > >
> >> > >> -----Original Message-----
> >> > >> From: Wayne Buttles [mailto:address@hidden
> >> > >> Sent: Tuesday, July 07, 1998 7:13 PM
> >> > >> To: Keith Russell
> >> > >> Cc: address@hidden
> >> > >> Subject: Re: lynx-dev Telnet Problem with Win32 Lynx
> >> > >>
> >> > >>
> >> > >> Can you change their shells environment? Lynx is asking the
> >> > >> window what
> >> > >> its size is and it is being told 0x0. If you can SET
> >> > LINES=24 and SET
> >> > >> COLS=80 I think it would run correctly.
> >> > >>
> >> > >> On Tue, 7 Jul 1998, Keith Russell wrote:
> >> > >>
> >> > >> > I downloaded lynx_32.zip and installed it at a customer NT
> >> > >> site (version
> >> > >> > 2.8.1dev.16). It runs fine locally, and also if we connect
> >> > >> through PC
> >> > >> > Anywhere or through a third-party telnet client.
> >> > >> >
> >> > >> > However, the customer is running Ardent's UniVerse DBMS
> >> > >> with Ardent's
> >> > >> > telnet server software. When we try to run Lynx through
> >> > >> Ardent's telnet
> >> > >> > server, we get the following error message, and Lynx
> >> > will not run:
> >> > >> >
> >> > >> > initscr():LINES=0 COLS=0:too small
> >> > >> >
> >> > >> > Ardent says the problem is in Lynx and not in their
> >> > >> software. I searched
> >> > >> > the Lynx-Dev archives back to January '97 and could not
> >> > >> find a mention
> >> > >> > of this problem. Has anyone else come across it?
> >> > >> >
> >> > >> > I'm quite frustrated at this point, because we are
> >> > trying to solve a
> >> > >> > unique problem for this high-profile customer, and we
> >> > thought we had
> >> > >> > finally found a solution in Lynx. And now it won't run....
> >> > >> >
> >> > >> > Thanks in advance for any help you can give me.
> >> > >> >
> >> > >> > Keith Russell
> >> > >> >
> >> > >>
> >> > >
> >> >
> >>
> >
>