I've got a 6000 running 9.0.0 that is appearantly resetting itself. I'm not sure why but the following is a snippet of the fatal-history log. I checked esight's fatal log list but it didn't show an entry for 330 or 385. If anybody has any ideas I'd appreaciate the info. <snip> WARNING: Index: 330 Load: tik.m60 Revision: 9.0.0 Date: 11/19/2000. Time: 10:52:18 Location: b0111018 b02d4234 b02d5df0 b0252e8c b0141000 b0204434 FATAL ERROR: Index: 1 Load: tik.m60 Revision: 9.0.0 Date: 11/19/2000. Time: 10:52:18 Location: b02d425c b02d5df0 b0252e8c b0141000 b0204434 b02044f0 SYSTEM IS UP: Index: 100 Load: tik.m60 Revision: 9.0.0 Date: 11/19/2000. Time: 10:55:36 WARNING: Index: 109 Load: tik.m60 Revision: 9.0.0 Date: 11/20/2000. Time: 21:21:22 Location: b02d5888 b0251894 b02a467c b02dd5e8 b02dd4b8 b02dacf4 SYSTEM RESET OCCURRED: Index: 385 Load: tik.m60 Revision: 9.0.0 Date: 11/20/2000. Time: 21:24:40 Location: b0187ee4 b02498f0 b0185a6c 00000000 00000000 00000000 SYSTEM IS UP: Index: 100 Load: tik.m60 Revision: 9.0.0 Date: 11/20/2000. Time: 21:24:40 </snip> Thanks. ---Dave Montgomery ++ Ascend Users Mailing List ++ To unsubscribe: send unsubscribe to ascend-users-request at bungi.com To get FAQ'd: <http://www.nealis.net/ascend/faq>