Re: Re Keystrokes: Possible BIOS compatibility

["M.W. Poirier" poirmw@xxxxxxxx]

 I'm not absolutely certain that I understand what is meant
 by "add two character function...." However, I do not get
 much of a chance to do anything of this sort, since immediately
 when I issue the command "run ," the following appears
 in the message area: "too many program call" , and
 this is repeated until I hit CTRL Break. That is all I see
 and hear from the message area.

 M.W. Poirier

----
On Tue, 26 Jul 2005, Robert Holmgren wrote:

> ** Reply to message from "M.W. Poirier"  on Mon, 25
> Jul 2005 19:36:35 -0400 (EDT)
>
>
> > I tried making Robert's changes to KEYSTROKES, but
> > this too made no difference.
>
> I need, first, to see a keyboard file from a machine that doesn't like
> KEYSTROKES. If that doesn't trigger the problem on my machines, then I either
> need to visit a machine that fails, or -- better -- find someone who is capable
> of debugging the routine. Or... maybe I could publish a debugging version!
> Try this -- instructions at the bottom (save to a filename, DECODE it,
> and then RUN as a freestanding routine):
>
> XPLeNCODE v2.0
> b-gin [UNTITLED]
> {<}GLC{>}{{;5keystrokes}} List current .KBD assignments for f
> unctions RJH LastRev.7/26/05 -- *Debugging Version* -- RUN a
> s freestanding PM![cr|lf]{002}{<}LBC{>}{<}SX01,{<}VA$WA{>}{>}
> {<}IF{<}PV01{>}<1{>}{<}PRNo window available{>}{<}EX{>}{<}EI{
> >}[BX_]func #{<}PV01{>}[Q2_][BX_]ne[Q2_][BX_]wait[Q2_][XP_]{<
> }SV01,#$&@ABCDEFGHIJKLMNOPQRSTUVWXYZ{>}{<}SV02,0123456789@ABC
> DEFGHIJKLMNOPQRSTUVWXYZ{>}{<}SV03,{027}X{>}{<}SU04,{<}GT05{>}
> {<}GT06{>}: {<}GT07{>}[255+048+068]{>}{<}LBA{>}{<}SX08,{<}IS0
> 1{>}{>}{<}SX09,{<}IS02{>}{>}{<}XS08,03,,05,01{>}{<}LBB{>}{<}X
> S09,03,,06,10{>};*;[cr|lf];*;[cr|lf]{<}IF("|"+{<}IS05{>}+{<}I
> S06{>}+"|"){238}"|MS|"<0{>};*; <==Add 2-char funcs to EXCLUDE
> [cr|lf];*; here, in format "|MS|AA|BB|CC|"etc.[cr|lf];*;[cr|l
> f];*; Starting with "N{second_character}", display 2 chars on
> the CMline,[cr|lf];*; then wait one second before testing fo
> r validity of the two[cr|lf];*; characters with VA_ :[cr|lf]{
> <}IF{<}IS05{>}>"M"{>}[BC_]{<}PV05{>}{<}PV06{>}[GT_][BX_]p 1[Q
> 2_]{<}EI{>};*;[cr|lf];*; To revert to FAST processing, commen
> t out (with leading ";*;")[cr|lf];*; the line above[cr|lf];*;
> [cr|lf]{<}SX11,"{<}SX07,{<}VA_"+{<}IS05{>}+{<}IS06{>}+"{>}{>}
> "{>}{<}PV11{>}{<}IF{<}VA|07{>}>0{>}{<}GT04{>}{<}EI{>}{<}EI{>}
> {<}IF{<}VA|10{>}>0{>}{<}SX09,{<}IS10{>}{>}{<}GLB{>}{<}EI{>}{<
> }IF{<}VA|01{>}>0{>}{<}GLA{>}{<}EI{>}[TF_]{<}PRDone{>}{<}EX{>}
> {002}[cr|lf][cr|lf]The concept here is to trap the misbehavin
> g function(s). The function name will appear on the CMline f
> or one second BEFORE it is tested. The act of testing it wit
> h  is what causes the crash (almost certainly). Misbeh
> aving function(s) should appear on the CMline first, and then
> crash the session before they have a chance to write a KBD a
> ssignment in the text window. Once you spot a misbehaving fu
> nction, add it to the exclusion list (in CAPS), and
> try again... If it runs too fast for you, change "[BX_]p 1[
> Q2_]" to "[BX_]p 2[Q2_]" (pause 2 secs). If the crash occurs
> after the Ns, change the letter to start displaying 2-char c
> ombos to a lower letter, e.g. {greater_than}"N" or "
> P" or whatever...>[cr|lf]
> -nd
> XPLeNCODE
>
>