Path: utzoo!attcan!uunet!munnari.oz.au!uhccux!ames!uakari.primate.wisc.edu!zaphod.mps.ohio-state.edu!math.lsa.umich.edu!emv
From: kre@cs.mu.oz.au (Robert Elz)
Newsgroups: comp.archives
Subject: [comp.sys.sun] Re: problems with KIP0688 and CAP5.0 on Sparkstation1
Message-ID: <10832@stag.math.lsa.umich.edu>
Date: 7 Feb 90 22:52:14 GMT
Sender: news@math.lsa.umich.edu
Reply-To: kre@cs.mu.oz.au (Robert Elz)
Followup-To: comp.sys.sun
Lines: 21
Approved: emv@math.lsa.umich.edu (Edward Vielmetti)

Archive-name: sparc-atalkad/v1.20
Original-posting-by: kre@cs.mu.oz.au (Robert Elz)
Original-subject: Re: problems with KIP0688 and CAP5.0 on Sparkstation1
Archive-site: munnari.oz.au [128.250.1.21]
Archive-directory: multigate
Archive-files: atalkad.1.20.shar.Z
Reposted-by: emv@math.lsa.umich.edu (Edward Vielmetti)

In article <4362@brazos.Rice.edu>, MLMCKEE@AUDUCVAX.BITNET writes:
> and then atalkad core dumps (at inet_ntoa() at 0xf777a860).  Has anyone
> encountered this before?

Yes .. for atalkad on a sparc (or probably other risc processor) fetch
multigate/atalkad.1.20.shar.Z (in binary mode, using anon ftp) from
munnari.oz.au [128.250.1.21]

It has zillions of unrelated changes, but will work for standard kip using
a fairly standard atalkatab (a few minor syntax changes described in a
README), and will work correctly on SPARCS, and other similar processors.

kre