Xy 3+ and Windows 95

[Peter Brown pbrown@xxxxxxxx]

Miriam Klieger' replied to Greg Reeves:

 At work, Windows95 "intercepts" F1-F10 until the next keystroke.

 If, for example, I edit my keyboard file to
delete the "Q1," "Q2," etc. speller function calls that occur first on
some
function keys, the "keystroke trapping" that affects (most of) those
keys,
requiring a key to be hit twice, goes away.

I wrote about a similar problem several weeks ago, and thank all who
tried to help. I'm still stuck, though. As I wrote to Marc O'Connor,

I've more or less given up on it for now--just too tangled. What I did
find was that XyWrite is processing the first function call in its
keyboard file, then stopping until I press another key. If there is
only one function (e.g., 63=BC), things work fine. For such keyboard
entries as 63=BC,t,y,xc you only get a blank command line; you then get
the onscreen file to print when you press another key. That suggests a
(long) workaround, involving assigning programs &A-&Z and &0-&9 to the
keyboard files, but it's too painful to write hundreds of these just
now. It also means overlaying several keyboards, since the & and @
calls only give you 72 macros--not enough.

Obviously, this behavior could explain (though not in a very deep way)
why eliminating Q1, etc., seems to work--the function call that would
follows the (deleted) Q1, Q2, etc., could then be processed. I would
ask, does Miriam Klieger's fix work for keys that have more than one
comma in the keyboard file after the Qx?

Leslie Bialler also was helpful, in replying to my first message. To
help with the diagnosis, I'm answering her (three-week-old) queries
below:

Here's the original message:

I'm running Xywrite 3.55+ with Windows 95, recently installed. Xywrite
> works fine on a stand alone machine but when the drivers for our
Novell
> Network are loaded, commands in Xywrite are not executed until another
> keystroke is made at random. I've "rem'd" out virtually everything in
> config.sys and autoexec.bat and stepped through the Windows 95 loading
> sequence from the Windows 95 menu accessible in startup by pressing
F8.
> Restoring things one at a time has narrowed the problem to the
"drivers"
> automatically loaded in the Windows startup sequence. Xywrite also
> works from Windows 95 in safe mode but not in safe mode with Network
> access.
>
> Does anyone have a clue about how to fix this problem or find a
> workaround?
>

Leslie answered:

Does this happen when you issue function calls as well as commands?

Answer: It doesn't happen with commands, only with keys that have more
than one argument assigned to them in the keyboard file.

Is there anything in the Novell system that requires use of the F5 key?
It is
possible that when you type F5 to blank the command line, in order to
issue your
command, you are running into a conflict with something in the Novell
system.

Answer: Don't think so--not sure.

If you know how to modify your keyboard file, search for your table= and
then
search for 63=. You will probably find this:

63=Q5,bc.

Edit this so it says 63=ni,Q5,bc.

That might work.

Answer: It doesn't. But as noted above, 63=bc works just fine.

I assume that if you start with F8 and then load everything BUT the
Novell drivers
things work as usual?

Yes, but I haven't figured out yet how to block the load of the Novell
drivers specifically. The last query brought up by F8 is something like
"load windows drivers". When I say no to that, things work, but Windows
is opened up in its crippled "safe" mode.

Sorry to be so longwinded, but this problem is quite a nuisance.
          Peter G. Brown          
     Editor-in-Chief, The Sciences       
    655 Madison Avenue, 16th floor      
     New York, New York 10024       
voice telephone: (212) 838-6727, ext. 622      
         fax: (212) 355-3795           
      E-mail: pbrown@xxxxxxxx