Ascend Archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: (ASCEND) fatal error 29
Not that it makes *much* difference, but I made a calc error below
(thought the day was different). The MAX was up for about 60 hours
before rebooting due to fatal error 29.
> -----Original Message-----
> From: Steven Guerin
> Sent: Thursday, December 11, 1997 7:59 PM
> To: 'Leon McCalla'; ascend-users
> Subject: RE: (ASCEND) fatal error 29
>
> yes, one of our MAXen (1 of about 20) has had a fatal error 29 on
> tik.m40 5.0Ap36. It was up for approximately 36 hours when it
> rebooted.
>
> Other than that, all of the others have been up for several days with
> no
> fatal errors and no warnings.
>
> ===
> Steven Guerin <mailto:sguerin@staff.communique.net>
> Communiqué Technical Operations
>
>
> > -----Original Message-----
> > From: Leon McCalla [SMTP:ascend@caribbeanlink.com]
> > Sent: Thursday, December 11, 1997 6:04 PM
> > To: ascend-users
> > Subject: (ASCEND) fatal error 29
> >
> > had anyone had a fatal error 29?
> >
> > ti.m40 5.0Ap36 on a max 4004
> > Leon
> >
> >
> > ++ Ascend Users Mailing List ++
> > To unsubscribe: send unsubscribe to
> > ascend-users-request@bungi.com
> > To get FAQ'd: <http://www.nealis.net/ascend/faq>
> ++ Ascend Users Mailing List ++
> To unsubscribe: send unsubscribe to
> ascend-users-request@bungi.com
> To get FAQ'd: <http://www.nealis.net/ascend/faq>
++ Ascend Users Mailing List ++
To unsubscribe: send unsubscribe to ascend-users-request@bungi.com
To get FAQ'd: <http://www.nealis.net/ascend/faq>