Moreover... More Broken XyWin

[Robert Holmgren]

Dear SysOp: Would you _please_ take a look at my msg #9349, and explain what
is going on here? I can't get an enormous number of mainstay facilities to
work with reliability in XyWin. *Many* programs that I try to R,U,N, from the
KBD file crash -- whereas if I run them from the CMline, they're OK. In other
words, it's not the XPL, it's the KBD. The most you can do with KBD file seems
to be to run a couple of functions or call a single frame in a Help file. But
call multiple frames on a single key, or RUN one program and then execute a
couple of commands on a single key, and it bombs. Other times the keyboard
just starts acting funny, almost as if it were a straight DOS keyboard with
nothing at all mapped on the keys except the BIOS keystrokes. If I hit Ctrl
key a few times, the KBD mapping usually comes back to life again -- but
occasionally I have to close the Windows session (OS/2). Still other times,
it's like one or more shifting keys were depressed to access a TABLE other than
unshifted -- but no keys are in fact depressed. None of this behavior appears
in Xy4. What's up?

 Lemme see if I can tabulate the first problem:

 OK: nn=XHJM,(,2,.,f,r,a,m,e,)
 OK: {2}JM 2.frame®SV50,argument¯Q2 {2}
 (Here & elsewhere, S/G 50 takes the arbitrary place of S/G 00, because with
XyWin you can no longer pass an argument between frames via 00)
 OK: nn=NOJM,(,2,.,f,r,a,m,e,+,w,a,i,t,+,q,u,i,t,)
 OK: {2}JM 2.frame®SV50,argument¯Q2 BN (wait)BN (quit/nv){2}
 OK: {2}BN run c:\xw\program.pm argumentQ2 BN (wait)BN (quit/nv){2}

 OK: nn=NOBN,(,a,b,),BN,(,w,a,i,t,),BN,(,q,u,i,t,/,n,v,)
 OK: nn=NOBX,r,u,n, ,p,r,o,g,r,a,m,.,p,m, ,a,r,g,u,m,e,n,t,Q2
 Bad: nn=NOBX,r,u,n, ,p,r,o,g,r,a,m,.,p,m,
,a,r,g,u,m,e,n,t,Q2BX,(,w,a,i,t,),BX,(,q,u,i,t,/,n,v,)
 Bad: nn=XHNIJM,(,2,.,f,r,a,m,e,),BX,(,w,a,i,t,),BX,(,q,u,i,t,/,n,v,)
 OK: nn=NOJM,(,2,.,P,r,s,K,b,d,A,r,g,),f,r,a,m,e, ,a,r,g,u,m,e,n,t,NO
 Bad: nn=NOJM,(,2,.,P,r,s,K,b,d,A,r,g,),f,r,a,m,e,
,a,r,g,u,m,e,n,t,NO,BN,(,q,u,i,t,/,n,v,)

 And so forth... The _general_ procedure above was to do something ("program"
or "frame"), wait for it to conclude, then quit.