Well, the corrupt stack is really a file with a lot of stacks in it, and because it's corrupt, RR 2.0r2 (the only version that will open it at all) tends to go off into some kind of loop at the drop of a hat, so the suggested technique is likely to lead to a lot of tedious force-quit situations etc. I see the merit of your technique, but I would really like to make as few changes to the corrupt stack as is humanly possible, and just copy bits out of it hopefully leaving corruption behind.
That's easy to get around, if the looping is due to the scripts (if it isn't, then you are out of luck, as you say.) You can do this in the message box:
lock messages;answer file empty;go stack it
This will open the corrupt stack without running any scripts. Then change its name. Then open the "good" stack. You can copy from the bad one to the good one.
I do think this inability to have two stacks in RAM each called 'myStack' or whatever is a weakness of RR.
It's been marginally inconvenient once in a while, but I haven't found it to be a problem. I hardly ever need to have two same-named stacks open at once, but since it isn't necessary to save the renamed stack, it's easy to make a temporary name change and then just close the stack when I'm done with it. When it closes, the name reverts back to what it was.
-- Jacqueline Landman Gay | [EMAIL PROTECTED] HyperActive Software | http://www.hyperactivesw.com
_______________________________________________ use-revolution mailing list [EMAIL PROTECTED] http://lists.runrev.com/mailman/listinfo/use-revolution
