Re: (ASCEND) 6.1.7 Microcode for Max

To: "Mark E. Dunlap" <mdunlap@s1.ds.net>
Subject: Re: (ASCEND) 6.1.7 Microcode for Max
From: Neale Banks <neale@idesign.com.au>
Date: Wed, 02 Sep 1998 12:12:38 +1100
Cc: ascend-users@bungi.com
Sender: owner-ascend-users@max.bungi.com

At 16:21 1/09/98 -0400, Mark E. Dunlap wrote:
[...]
>From what I have read and my brief experience, if you are planning on 6.1.7
>on a 4000, give yourself a root cannel with a Dremel tool instead.  Thanks
>again Ascend for another wonderful TAOS.

Speaking as one of the complainants, I think that's somewhat unfair.  Our
experience has been good to fair and we are watching to see how long/well it
holds up in the "fair" case (the "good" case is 13 days and counting,
purring nicely).  Overall, I'm happy so far.

As with any upgrade, it's obviously prudent to have a back-out contingency
plan.  We all know that there may be something odd lurking that will only
pop out in a specific configuration.

Regards,
Neale.

++ Ascend Users Mailing List ++
To unsubscribe:	send unsubscribe to ascend-users-request@bungi.com
To get FAQ'd:	<http://www.nealis.net/ascend/faq>

Prev by Date: Re: (ASCEND) high density access server
Next by Date: Re: (ASCEND) high density access server
Prev by thread: Re: (ASCEND) 6.1.7 Microcode for Max
Next by thread: (ASCEND) Ascend SNMP Browser and MIB
Index(es):
- Main
- Thread