debugger anomaly updated

[J. Landman Gay]

On 7/13/05 9:02 PM, Timothy Miller wrote:

> There's a HC stack that rebuilds a new 
> stack from scratch, an identical copy of an existing stack. It was used 
> to "rescue" corrupted HC stacks. Typically, it was able to rebuild a 
> stack by bypassing a bad card. It's been widely used for years. as you 
> probably know.

If you are thinking of the "Recover" stack, that didn't do what Alex is 
describing. It just did a straight card copy from the old stack to the 
new. When it hit a bad card and crashed, it picked up on restart at the 
next card and kept on copying. It didn't recreate objects.

In the case of badly formed HC stacks, copying cards might just copy the 
bad parts along with the rest of the card and you'd be back where you 
started. Also, copying cards can create duplicate backgrounds (as it 
often did in HC) which isn't what you'd want.

Recreating objects individually from scratch by using a saved 
description probably would work fine, as long as the model placed 
background groups correctly.

-- 
Jacqueline Landman Gay         |     jacque at hyperactivesw.com
HyperActive Software           |     http://www.hyperactivesw.com