Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!usc!jarthur!bgribble From: bgribble@jarthur.Claremont.EDU (Bill Gribble) Newsgroups: comp.sys.handhelds Subject: Re: HP48 buffer read problems (still). Message-ID: <11522@jarthur.Claremont.EDU> Date: 3 Apr 91 19:27:01 GMT References: <91092.195502LEIF@SLACVM.SLAC.STANFORD.EDU> <21685@shlump.nac.dec.com> Organization: Harvey Mudd College, Claremont, CA 91711 Lines: 27 A few notes from a person who's seen most of your problems: first, like a previous poster said, there's no way to receive only after a carriage return from user language, and if you can do it from machine language you're a better man than I am. Dealing with the serial buffer in machine language is very difficult, and there's really nothing you can't do with user language that you can in machine language. Second: as odd as it sounds, the 48 does drop characters when connected to a modem, flow control or no. While I was testing NRTS, I thought it was a bug in my code, so (being the clever guy I am) I did the following, which you can do as well to verify that the 48 doesn't handle buffer overflows well: log in to your favorite computer with your favorite hp term program. I suggest NRTS :-). Quit the program. Execute "ls -laR" XMIT. (or equivalent if you're not on a UNIX machine). Check the buffer. You would think it would be 255, the buffer having overflowed, right? I get an average of 45 to 70 characters in the buffer, usually the first line or so of the output, and nothing else. Even with flow control on, I get the same thing with no XOFF sent. A large number of characters just evaporate. This doesn't happen when connected directly to any sort of terminal line, so it doesn't bother me that much, but it is an anomaly, I think. ***************************************************************************** ** Bill Gribble Harvey Mudd College, Claremont, CA ** ** bgribble@jarthur.claremont.edu Never heard of it? You're stupid. ** *****************************************************************************