Re: configuring U2

[Robert Holmgren holmgren@xxxxxxxx]

** Reply to note from Morris Krok  on Wed, 14
Feb 2001 06:45:45 -0800

> In spite of increasing the pause component of the startup.int file, some
> messages flash to fast for me to read them properly. I can glimpse fo
> something being invalid but do not know what it is... The program [U2??]
> otherwise works as it can launch programs from the command line.

Morris, let's not mix apples and oranges. Problems with your
STARTUP.INT have NOTHING to do with U2! If "va/nv $U2" returns U2's
filename, then it is loaded, and it is not your problem. Do this: If
you think there is only one error message that is flying by, put an
 in the middle of STARTUP.INT. Move that  up or down in the
file, one line at a time, until the error msg either appears or
disappears -- just successively re-launch XyWrite over and over until
you pin down which file has the problem. When  is located
immediately after the bad file, the error msg will stay on screen
(obviously, if  is immediately above the bad file, no error msg
will appear, which in itself tells you that the bad file is below that
point in processing). If you are setting the WAit variable at the top
of STARTUP.INT (BX d wa=90Q2 ;*;), on my machine anyway that generates
a looong pause, certainly long enough to read.

SETTINGS.DFL would be my prime suspect (the changes you made screwed
something up); I'd look next for an improper command in STARTUP.INT
itself; a bad assignment in KBD could cause it; U2 would be the least
likely (there is nothing in U2 that would impede loading or generate
an error in STARTUP.INT).

You can also try to execute each line in STARTUP.INT manually. Then
you can look at the messages to your heart's content.

Recognize that STARTUP.INT is just an XPL program. You write XPL,
don't you? Isn't this how you go about debugging, statement by
statement?

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