Hm, I've never seen this lockup thing myself, so I'm just wondering about your config options. There's a config option for Status line 25 in "Window setup" that seems to change the behavior of terminal status messages. I wonder if something like that could explain why some get this and other don't. Eric DeLong Sally Beauty Company MIS-Project Manager (BSG) 940-898-7863 or ext. 1863 -----Original Message----- From: John Taylor [mailto:lists@xxxxxxxxxxxxxxxxxxxx] Sent: Tuesday, March 16, 2004 12:39 PM To: 'Midrange Systems Technical Discussion' Subject: RE: break messages locking session up - a survey > -----Original Message----- > From: midrange-l-bounces@xxxxxxxxxxxx > On Behalf Of jt > > I abhor break messages, however have had occasional keyboard > lockups. VERY occasional since W2K. Rare biggie, but > compared with experience I had in past with real terminals, > an order of magnitude or two more problems. It doesn't have to be a *BREAK message. I've seen it happen just as often without them. Maybe it has something to do with workstation message notification in a more general sense. Interestingly, the problem doesn't actually result in a locked keyboard. What seems to happen is that the emulator starts ignoring all command keys (CF, Enter, etc.). It also ignores alternative means of issuing those command keys, such as Hotspots and Popups. Regards, John Taylor _______________________________________________ This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/midrange-l or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.
As an Amazon Associate we earn from qualifying purchases.
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.