kim@amdahl.uts.amdahl.com (Kim DeVaughn) (03/21/88)
[ "Nicaragua" is Spanish for "Vietnam." --Bob Page ] Sorry for crossposting this. It really belongs in .tech, but many people who might know the answer don't/can't get .tech yet. Anyhow ... Tony Sumrall is trying to solve a problem that vt100 has when trying to talk to some braindamaged MVS application with a 500/2000, and asked me to do a MonIDCMP dump of the keypad events on the 2000. Simple enough, no? No. I haven't used MonIDCMP before, but sort of got it to respond after awhile (which included a few trips to the Guru). Unfortunately, I couldn't get it to "see" any key press events, no matter what I did. My note to Tony below gives more details. Anyone know what I'm doing wrong, or if there is some problem with MonIDCMP on a 2000 (expansion ram, and a 68010 are the only h/w addons, thus far)? Thanks! /kim > Date: Sun, 20 Mar 88 01:31 PST > From: kim (Kim DeVaughn) > To: acs > Subject: monidcmp ... > > > Well, I really don't know what the problem is with MonIDCMP (C00000 memory > that's on the 2000's, expansion ram, 68010, phase of the moon, or what. > > I did get *some* action from the "VT100 Info & Xfer Status" window finally, > but nothing I did would get it to record key presses/releases. Nothing. > > I even went so far as to go back to a vanilla WB floppy, that is about as > stock as you can get, thinking that some of the little goodies I use was > somehow causing the problem (AutoPoint, ClickToFront, GRABBiT, PopCli, ARP, > MemWatch, etc.) > > Didn't help. Is it possible you're using a newer version of MonIDCMP, or > something (I'm using the copy from Fish #108 --- v1.0)? I'd try it on the > 1000, but the 1080 is down, and the 1000's all disconnected. This really > has me stumped, because (as you can see below), MonIDCMP *is* seeing some > events. > > Also, the Xfer/Status window was the only window that would even give me > this much of a response. A "PopCLI" window generated *nothing*, as did > (didn't) the normal "AmigaDOS" window. And, I got the same results from > vt100 when running it on the WB screen, as with running it on a custom > screen. > > Any other words of wisdom? > > BTW, did you say this is to support some stupid MVS application? I say > anybody who uses MVS gets what they deserve. [ Just kidding! ] > > /kim > > > MonIDCMP v1.0 (May 1987) - IDCMP Monitor Program > Monitor Installed - press CTRL-C to cancel > Activate Window (388,038) C000 Button(L) > Activate Window (389,025) C000 Button(L) > New Size (381,078) 8000 > Requester Set (271,020) > Activate Window (271,021) 8000 > Requester Clear (273,026) 8000 > Activate Window (285,058) C000 Button(L) > <--------------+ > New Size (476,091) 8100 NumPad | > Activate Window (404,067) C100 Button(L),NumPad | > Activate Window (301,073) C000 Button(L) | > Cancelling...Monitor Removed | > | > | > >---| > At this point I went thru the keypad, shift/alt/cntl keys, | > some regular keys, mouse buttons, etc. I followed this | > with a window resizing, which I knew MonIDCMP had been | > seeing. As you can see (or rather can't see), NO keys | > were seen. When I tried the "mask" option (with masks of | > FF, 00, and FFFF), I MonIDCMP didn't even see the above | > events. | > >---+ -- UUCP: kim@amdahl.amdahl.com or: {sun,decwrl,hplabs,pyramid,ihnp4,uunet,oliveb,cbosgd,ames}!amdahl!kim DDD: 408-746-8462 USPS: Amdahl Corp. M/S 249, 1250 E. Arques Av, Sunnyvale, CA 94086 CIS: 76535,25