wtm@neoucom.UUCP (Bill Mayhew) (12/28/87)
Hi, I'd like to get my HP2645 off the desk and have room for my 3b1 and couple of manuals and some room to work. I won't get rid of my 2645 until I can get the 3b1 to act as a reasonable dial-up terminal. I have to work at my account on a vax quite a bit, and I'd just like to log in instead of uucp'ing stuff, editing, and then uucp'ing back to the vax. Just by looking, it looks like the effective scroll rate of the 3b1 is about 4800 baud when working on something directly on the 3b1. Like native vi, for instance. That's OK by me, since my brain is slower than 4800 baud anyway. Now the gripe: the ATE software is incredibly slow. It can only keep up with 300 baud!! I asked not to log my session to a file, but every character received still goes into a file in /u/name/Filecabinet/somelogfilename. I've read the dang ATE manual a couple of times and I can't see anything I'm doing worng. Is this a known problem, or am I being a dummy as usual? I gave up on the ATE and decided to use cu instead. cu still only manages to make about 1000 baud throughput. I know cu does do some internal buffering and checking for tilde sequences, but that doesn't explain the lethargy. I know quasi-reasonable serial throughts are possible, as my uucp calls to the vax average around 550 characters/sec via a 9600 baud Trialblazer modem. While this is less than I'd hope for, I think the load on the vax is bogging down the uucp xfer. I think the 3b1 is keeping up on its end. Thanks for letting me bend your ear. Happy holidays, Bill
alex@umbc3.UMD.EDU (Alex S. Crain) (12/30/87)
In article <890@neoucom.UUCP> wtm@neoucom.UUCP (Bill Mayhew) writes:
[misc complaints about the term emulator package deleted]
I didn't really notice the spped problems after using a C-128 for a year :-)
What I never got used to was the packet sizes that the emulator talks in,
the 30 character bursts. My eventual solution was so simple that I kiked myself
for waiting so long. I snagged the kermit program, and then uploaded the s4
termcap to my VAX. The 3b1 makes a great terminal, and since we're running a
very new version of emacs (18.4x) on the vax, my arrow keys even work!
--
:alex.
alex@umbc3.umd.eduwtm@neoucom.UUCP (Bill Mayhew) (12/31/87)
In article <660@umbc3.UMD.EDU>, alex@umbc3.UMD.EDU (Alex S. Crain) writes: > and then uploaded the s4 > termcap to my VAX. The 3b1 makes a great terminal, and since we're running a > very new version of emacs (18.4x) on the vax, my arrow keys even work! As you might guess, I immediately put the s4 termcap and terminfo up on the vax and went with cu, scapping ATE. I did everything I could to make sure performance of the 3b1 was maximized-- no user agent, full window, nothing going on in the background. Even at 1200 baud, try doing a tail -100 /etc/termcap on the vax via cu. If you are using an external modem, you'll notice that the SD light starts blinking after about 1/2 screen of text scrolls. What is happening is ^S/^Q flow control becuase teh 3b1 can't keep up. You'll certainly notice the slowness on a 2400+ baud modem or a direct wire. cu manages to get about 100 char/sec to the screen on receiving. My point was that the serial port is capable of getting 550+ char/sec though at 9600 baud-- and that is including all the handshaking that is done in the uucp g protocol. 3b native applications seem to be able to write around 500 char/sec to the screen. This would imply that if serail receive using full CPU bandwidth is 550 char/sec and text render is 500 char/sec. That with additional overhead added, cu should be able to get at least 200 char/sec to the screen. It's only making half of that. My real question is why the heck is ATE so s-l-o-w? It would be handy to use the vt100 emulation on a vms machine I call. Moral of the story: the 3b isn't meant to be a terminal emulator. You should download/edit/upload. Fortunately uucp makes this relatively painless when talking to other Unix oriented machines. Sorry if it sounds like I complain too much; I like the 3b none the less. Peace and happiness in the New Year, Bill