Re: overcoming the XP lag [II]

[Leslie Bialler lb136@xxxxxxxx]

Michael,

Slaps forehead!

Oh Sorry! Yes. I read the wrong line there. Numblock is indeed key 69.
Let me check again . . .


Ah, that reads: ni,tn (no interrupt/toggle numblock/)

And that was my own creation because I see I commented out the original
69=0 which said simply no (no operation--do nothing).


Which is clearly how I got it to work the way I wanted. So, try that.

And you have totally jogged my memory now. I believe I did that (but
when? when Win 3.1 came out?) because the OP Sys was overriding XyWrite
and was toggling the number lock so that whenever I entered XyWrite it
would automatically reverse whatever setting was there and/or turn off
the light when num lock is in fact on, and vice versa. (And that is
crucial for me because with numblock off, my far right kbd does
different things from the keys in the middle keyboard.)


Michael Norman wrote:

> At 11/4/2004 01:00 PM -0500, Leslie Bialler wrote:
>
> > I look at my settings for keyboard scancode 58 and I find there that
> > space which is not a space but the (I think) null character or
> > something, there. What do you have?
>
>
> I have *NO* [no operation], but 58 for me is CAPS LOCK. Num Lock is
> key 69. There I have AS, Alternate Screen, which was the OEM setting.
>
>
> Question is: does toggling NUMLCK give you the same effect as *default
> ks=o,o*, to wit, removing the last the lag?
>
>
> Michael Norman


--
Leslie Bialler, Columbia University Press
lb136@xxxxxxxx
61 W. 62 St, NYC 10023
212-459-0600 X7109 (phone) 212-459-3677 (fax)
> http://www.columbia.edu/cu/cup