Article View: comp.os.os2.networking
Article #1379Re: Yet another IBM TCP/IP bug.
From: Rick Beebe
Date: Fri, 22 Jan 1993 22:00
Date: Fri, 22 Jan 1993 22:00
45 lines
3026 bytes
3026 bytes
In article <GHENNIGA.93Jan22115449@ampere.NMSU.Edu> ghenniga@NMSU.Edu writes: >I think I found another bug in IBMs TCP/IP CSD Level UN32131, or at least a >"feature" that no longer works. Before I applied the CSD I would commonly >increase the size of my OS/2 command window and then "vt100 hostname". If the >remote was a Sun I could then make use of the extra rows in the window. Now >it appears that the vt100.exe binary doesn't allow this, it's stuck at 25 >lines/rows. Here's what I did before the CSD: > 1) Open an OS/2 command window. > 2) [C:\] mode co80,30 > 3) [C:\] vt100 hostname > 4) (login to remote Sun host) > 5) hostname[1]% stty rows 30 >Normally, if I brought up the editor it would then recognize the additional >lines in my window, which made editing large code that much easier. This, at >least for me, no longer functions. Can anyone confirm this? > Also I thought I'd try the above with vt220.exe and the same thing >happened, although I can't be sure if it ever worked before. Also, I >noticed that vt220.exe now does not pass Ctrl+C through to the remote host. >When in emacs if I type a Ctrl+C emacs doesn't receive it but instead I get >the familiar: > "External process cancelled by a Ctrl+Break or another process" >even though it doesn't actually kill the vt220 session. > What's the deal with this CSD by the way? Did they totally rewrite >a large chunk of it? Perhaps converting to 32-bit C or something? I noticed this problem in the previous CSD with TELNET. I switched back to the last version that did work and everything was fine. It's a shame, too, because the newer ones seem to display faster. Anyway, I got this latest CSD and noticed that TELNET and VT220 are still broken. Sigh. I hadn't noticed the Ctrl-C problem--I don't use Emacs--but you might take a look that the "local character" setting (hit Ctrl-] and then type "help.") there may be a solution somewhere in there. ...................................................................... Rick Beebe (203) 785-4566 Data Network Operations Biomedical Computing Unit beebe@biomed.med.yale.edu Yale University School of Medicine beebe@yalemed.bitnet ......................................................................
Technical Details
Message-ID:
<rbeebe.26.0@surgery.med.yale.edu>Path:
arc1-ca.pugleaf.net!sparky!uunet!cs.utexas.edu!qt.cs.utexas.edu!yale.edu!news.yale.edu!SURGERY-2ND-NODE.MED.YALE.EDU!rbeebeReferences:
<GHENNIGA.93Jan22115449@ampere.NMSU.Edu>Show Full Headers
Complete Article Headers
Newsgroups: comp.os.os2.networking Path: arc1-ca.pugleaf.net!sparky!uunet!cs.utexas.edu!qt.cs.utexas.edu!yale.edu!news.yale.edu!SURGERY-2ND-NODE.MED.YALE.EDU!rbeebe From: rbeebe@surgery.med.yale.edu (Rick Beebe) Subject: Re: Yet another IBM TCP/IP bug. Message-ID: <rbeebe.26.0@surgery.med.yale.edu> Sender: news@news.yale.edu (USENET News System) Nntp-Posting-Host: surgery-2nd-node.med.yale.edu Organization: Department of Surgery, Yale University School of Medicine References: <GHENNIGA.93Jan22115449@ampere.NMSU.Edu> Date: Fri, 22 Jan 1993 22:00:07 GMT Lines: 45