Re: UNDO

["Robert Holmgren" holmgren@xxxxxxxx]

** Reply to message from Harry Binswanger  on
Sun, 13 Jul 2008 11:37:48 -0400


> I'll put the frames (which adds a prompt "okay"
> to undo.int) at the end.

Put them at the BEGINNING of U2. Right at the top. Anything
you're experimenting with should always go at the top, where it
will supersede any other frame with the same or a similar name
(or an asterisk, which makes them grab everything -- for
example, a frame named UN* will supersede UNDO unless UNDO is
located _before_ UN* in U2). And do NOT change my frames!
Don't add anything that you've cooked up -- just add what I say
to add.

> No DUMMY.* in the current director (c:xy) nor the
> c:\xy\undo directory.

C:\XY\UD, I hope. OK! That at least indicates that the
problem, whatever is it, is purely a matter between XyWrite and
Windows, and UnDo.exe plays no part in it. (I can stop trying
to determine whether UnDo.exe is stepping on XyWrite's toes...
it isn't.)

In frame {{5undo.int,rud}} you have an extra space character
between "...UnDo.exe ..." -- there should be ONE space
there only! How did that creep in? That would cause failure,
if you got past "Access denied.". But it is not your problem.

What IS your problem? Carl got it working in 1 minute, out of
the box, 10 days ago!

Try this, manually -- this is an obvious first step. CAll
DUMMY.TMP into a window -- make that your current window.
Command, on the CMline:
 sa/nv C:\XY\UD\DUMMY.BAK
Execute that command EXACTLY. Do you get "Access denied."?

-----------------------------
Robert Holmgren
holmgren@xxxxxxxx
-----------------------------