Path: utzoo!attcan!uunet!zephyr.ens.tek.com!uw-beaver!milton!dali.cs.montana.edu!uakari.primate.wisc.edu!zaphod.mps.ohio-state.edu!wuarchive!decwrl!nsc!voder!apple!jdevoto
From: jdevoto@Apple.COM (Jeanne A. E. DeVoto)
Newsgroups: comp.sys.mac.hypercard
Subject: Re: Unexpected error 5455 occured, Sorry?!?!?
Message-ID: <45960@apple.Apple.COM>
Date: 24 Oct 90 23:29:52 GMT
References: <1990Oct24.204918.24815@ecn.purdue.edu>
Organization: Apple Computer Inc., Cupertino, CA
Lines: 33

In article <1990Oct24.204918.24815@ecn.purdue.edu> mckay@ecn.purdue.edu
(Dwight D. McKay) writes:
> [ that he has a damaged stack ]
>Questions:
>     1) Can this problem be fixed? 

"Unexpected error xxx" generally means that one or more cards or backgrounds
are damaged. You can recover undamaged cards by copying them to a new stack.
Unfortunately, I don't know of any way to delete the damaged objects in
place.

If you cannot open the stack without seeing the error, try typing in
     go card 2 of stack "Broken"
into the message box from another stack. You can keep doing this until
you find an undamaged card.

If you cannot get into the stack at all, using ResEdit (or some other file
utility) to change the file type of a copy of your stack to TEXT will let
you open the stack from within a word processor or text editor. This will
let you salvage scripts and field contents.

>     2) How I can check to find out that a stack is damaged before I
>overwrite a backup of the stack?

Compact the stack. During compaction, the stack's structure is checked.
Compacting your stacks often will help prevent stack corruption.
-- 
========= jeanne a. e. devoto ========================================
 jdevoto@apple.com     |  You may not distribute this article under a
 jdevoto@well.sf.ca.us |  compilation copyright without my permission.
______________________________________________________________________
 Apple Computer and I are not authorized      |        CI$: 72411,165
 to speak for each other.                     |