Re: help needed

[Harry Binswanger hb@xxxxxxxx]

In principle, you apply Mill's Methods (John Stuart Mill,
that is): isolate each factor, until you find the one that creates the
problem.

Of course, it can be difficult to know all the factors to test. But try,
as Carl suggests, a different XyWrite installation on the same computer.

Maybe the easiest thing to try is launching editor.exe without any .kbd
file:
1. find your startup.int file
2. add at the very top of the file, ≪ex≫, where the double
brackets indicate the guillements (ASCII 174 and 175). If you don't know
how to add the guillemets, you can just position your cursor at the top
of the startup.int file, go to the command line (F5), type in
"ex" (w/o quotes) and hit enter.
3. Save startup.int
4. Launch XyWrite as you normally do (you don't have to quit the present
instance).

That loads Editor.exe without any external keyboard file, but there's a
rudimentary built-in one. So if running it that way still shows typing
problems, then the culprit is likely your .kbd file.

If the problem is gone, trying moving that ≪ex≫ (which
means: exit) to be after lines that are lower and lower down in
startup.int.

Let us know.

> thanks much, I will try that and
> let you know.