🚀 go-pugleaf

I'm sure that I'll be corrected on a few points, but here are my
observations.

1) If you power off the gateway and bring it back up it should come up on its
own. As I am paranoid, I tend to reload it by hand anyhow.

2) No informed answer.

3) I've had no stability problems and I've pounded on it pretty hard at
times. From my experience, you should be able to count on it for weeks. 

4) We do not have MacServe. We have had problems with Hayes InterBridges,
though.

5) The timeout in MacTelenet (CMU/Columbia) is quite long. You can pick up
the code from Columbia and change it, I believe. You can also talk to
Stanford and pick up their version of Telenet which will soon have multiple
connections and FTP. University of Illinois also has a multiple connection
version with FTP. Stanford requires a license and $50 for the binary. I'm not
sure about U.I. (You out there, Gaige?)

6) MacTelenet will probably not be getting many improvements. Mark Sherman
worked on it to work with the new gateways and Charlie Kim has improved the
TFTP handling and fixed a few bugs, but noone, as far as I know, is doing
serious development on it. I take that back. We have a group of students who
are working on designing and building a new interface for it but I have no
time estimate on it. Stanford's version has two pages of scroll back and
seems to be a good vt100 emulation.

7) Prompt frequently loses the Kinetics box. When I use Reset, the Kinetics
box will reset, but Prompt will not find it. Power cycling always works. The
Prompt screen is also totally useless and the configuration file drives me
nuts. Having to encode the name and load file in hex is insane. If Kinetics
would release the source, I'd be happy to upgrade it. If I had the time, I'd
just write it from scratch, but I'm not that nuts, yet. Once I start handing
boxes out to local administrators on campus I'm certain that I'm going to
wish that I had rewritten it.

-David Kovar