Re: UnDo2

[Harry Binswanger hb@xxxxxxxx]

> So it seems to be okay on this score. And, this time UD shows:
>  1.001
> It's contents, when REad, are three test lines left
> over from before I quit Xy the time before.
> What does it all mean?

It means that frame UNDO.INT, which is run in STARTUP.INT (or
manually), either isn't actually running or, for some reason,
isn't deleting all the files in C:\XY\UD.

Manually SAve a file in C:\XY\UD, then issue these two commands:
 undo.int
 dir C:\XY\UD
Is that file still in C:\XY\UD? The dir should be completely
empty.
Yes it is empty. UnDo.int, when issued "manually" is working. And the same
test is passed when saving the file, exiting Xy, then re-launching; so
undo.int runs from startup.int.
It's looking to me like it isn't getting activated by the $K. I tried
$K and UD is still empty. But, again, if I do UnDo, I get
the .001, the .DAT, and the .CTL files suddenly appearing. I'm guessing
that something that is supposed to be activated when $K is poked is failing
to be activated. And all this worked with version 1.

Thanks, Robert.


Harry Binswanger
hb@xxxxxxxx