dz@pumpkin.ucsb.edu (Daniel James Zerkle) (09/12/89)
Our little NeXT is connected to a terminal server network through ttya. We use tip & kermit to get to assorted other machines around campus. Every once in awhile, the thing drops characters. It seems to happen in chunks, about three lines at a time. This is far worse when there is a heavy load on the system. Kermit can not perform a download with a heavy load, because too many characters are missed. Sending data is never a problem. Why should this happen? The NeXT does have a powerful enough processor to handle a measly 9600 bps without any problem. Has anybody else met this problem? Will it be fixed in 1.0? | Dan Zerkle home:(805) 968-4683 morning:961-2434 afternoon:687-0110 | | dz@cornu.ucsb.edu dz%cornu@ucsbuxa.bitnet ...ucbvax!hub!cornu!dz | | Snailmail: 6681 Berkshire Terrace #5, Isla Vista, CA 93117 | | Disclaimer: If it's wrong or stupid, pretend I didn't do it. |
avie@wb1.cs.cmu.edu (Avadis Tevanian) (09/13/89)
In article <2336@hub.UUCP> dz@cornu.ucsb.edu (Daniel James Zerkle) writes: >Every once in awhile, the thing drops characters. It seems >to happen in chunks, about three lines at a time. >Will it be fixed in 1.0? In 1.0 the serial lines can easily handle 19.2KB input and can take 38.4KB for fairly long bursts. -- Avadis Tevanian, Jr. (Avie) Manager, System Software Group / Chief Operating System Scientist NeXT, Inc. avie@cs.cmu.edu or avie@NeXT.com
hughes@silver.bacs.indiana.edu (larry hughes) (09/13/89)
In article <2336@hub.UUCP> dz@cornu.ucsb.edu (Daniel James Zerkle) writes: >Our little NeXT is connected to a terminal server network through >ttya. We use tip & kermit to get to assorted other machines around >campus. Every once in awhile, the thing drops characters. It seems >to happen in chunks, about three lines at a time. This is far worse >when there is a heavy load on the system. Kermit can not perform a >download with a heavy load, because too many characters are missed. >Sending data is never a problem. Why should this happen? The NeXT >does have a powerful enough processor to handle a measly 9600 bps >without any problem. Has anybody else met this problem? Will it >be fixed in 1.0? I frequently dialout and perform file transfers at 2400 baud through ttyda (via Kermit)...I haven't experienced any problems thus far. //=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=\\ || Larry J. Hughes, Senior Programmer || hughes@silver.bacs.indiana.edu || || Indiana University || || || University Computing Services || "The person who knows everything || || 750 N. State Road 46 Bypass || has a lot to learn." || || Bloomington, IN 47405 || || || (812) 855-9255 || Disclaimer: See quote above. || \\=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=//
epsilon@wet.UUCP (Eric P. Scott) (09/15/89)
In article <6133@pt.cs.cmu.edu> avie@wb1.cs.cmu.edu (Avadis Tevanian) writes: >In 1.0 the serial lines can easily handle 19.2KB input and can take 38.4KB >for fairly long bursts. Are SLIP and uucp supported?
avie@wb1.cs.cmu.edu (Avadis Tevanian) (09/15/89)
In article <546@wet.UUCP> epsilon@wet.UUCP (Eric P. Scott) writes: >In article <6133@pt.cs.cmu.edu> avie@wb1.cs.cmu.edu (Avadis Tevanian) writes: >>In 1.0 the serial lines can easily handle 19.2KB input and can take 38.4KB >>for fairly long bursts. > >Are SLIP and uucp supported? SLIP and uucp are not supported in 1.0. However, uucp is "on the disk" so you can use it at your own risk. I have also put together a loadable version of SLIP (which was used to determine the capabilities of serial line input) which is not on the disk. We will probably soon figure out the best way to make this available to those that want it. -- Avadis Tevanian, Jr. (Avie) Manager, Systems Software NeXT, Inc. avie@cs.cmu.edu or avie@NeXT.com