Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!uwm.edu!rpi!zaphod.mps.ohio-state.edu!uakari.primate.wisc.edu!ames!excelan!minshall
From: minshall@kinetics.com (Greg Minshall)
Newsgroups: comp.protocols.appletalk
Subject: Re: KFatPath: Reliability? (atalk [0007])
Summary: minor correction
Message-ID: <1534@excelan.COM>
Date: 12 Jul 90 16:55:23 GMT
References: <900712072314.754849@SYSTEM-M.PHX.BULL.COM>
Sender: news@excelan.COM
Reply-To: minshall@plasma.kinetics.com (Greg Minshall)
Organization: Novell Corp., Walnut Creek, CA.
Lines: 15

In article <900712072314.754849@SYSTEM-M.PHX.BULL.COM> Beattie@SYSTEM-M.PHX.BULL.COM (Art Beattie) writes:
...
>One big reason for staying with the PROM code and AppleTalk Phase1 is
>that when power failures occur (our monsoon season, about 2 months long,
>involves thunder storms that our power utilities cannot deal with), the
>units have to reloaded with the KStar software.

Actually, the software will stay loaded over a power failure (assuming the
battery is working), as will configuration information.  The one thing
that will not stay loaded is the so-called "atalkatab information", which
is only needed in large, TCP/IPish sites which already have a server
around.

Greg Minshall			Novell, Inc.
minshall@wc.novell.com		1-415-975-4507