[Date Prev][Date Next][Subject Prev][Subject Next][Date Index][Subject Index]

Re: vdosplus keyboard anomaly



John,
Ok. CapsLock can be problematic between host and virtual machines/apps (state is lost or not captured by one or the other). If you can figure out what keypress causes a problem, you could bypass normal input with the help of Autohotkey. E.g., I have these in my Autohotkey file:

; vDosPlus keyboad
; ----------------
#IfWinActive, vDosPlus ahk_class vDos

; Alt-Ctrl-NumpadIns
!^NumpadIns::
{
Send, #^v
Exit
}

; vDosXy keyboard
; ---------------
#IfWinActive, ahk_class SDL_app

; Alt-Ctrl-NumpadIns
!^NumpadIns::
{
Send, #^v
Exit
}
To suppress external influences in the XyWrite keyboard file, there are NI (= no Xy-external interrupt), NO (= no operation) and bk (= stop current process). These used judiciously may also alleviate the situation.

Best regards,

Kari Eveli
LEXITEC Book Publishing (Finland)
lexitec@xxxxxxxxxx

*** Lexitec Online ***
Lexitec in English: https://www.lexitec.fi/english.html
Lexitec English and Finnish dictionaries: https://sk.lexitec.fi/en/
Home page in Finnish: https://www.lexitec.fi/
Kari,
I think it must be vdosplus; I'm on the machine several hours a day, 7-days a week, and it's never happened outside xy3/vdosplus.  For the same reason I'm dubious about static electricity.
Per Carl's point, I do recall now caplocks freezes from time to time, 
over the years.  But this one is more extreme and so far resistant to 
fixes, including keyboard disconnects/reconnects. But we'll see if it 
continues...