Re: [foxboro] CAR# 1003752 Keyboard Lockup on Fox Diisplay Manage r on 51 Series !
- From: tom.vandewater@xxxxxxxxxxxxxx
- To: foxboro@xxxxxxxxxxxxx
- Date: Thu, 10 Oct 2002 18:45:33 -0400
Patricia,
Thanks for this suggestion. We will try it on our next lockup
instead of dismissing the Alarm Manager. It is a more simple work-around. I
still think the best solution is to fix the cause of the problem. If that
had happened in the first place, we wouldn't be discussing all of the
possible work-arounds today. Imagine all of the CAR's, Helpful Hints, Quick
Fixes, and disgruntled users that would have been eliminated if it had been
fixed before the new Motif applications were released on Sun boxes!!
Tom VandeWater
-----Original Message-----
From: Calabria, Patricia [mailto:Patricia.Calabria@xxxxxxxxxxxx]
Sent: Thursday, October 10, 2002 2:24 PM
To: 'foxboro@xxxxxxxxxxxxx'
Subject: Re: [foxboro] CAR# 1003752 Keyboard Lockup on Fox Diisplay
Manage r on 51 Series !
For all of you experiencing lock ups. In case you're still able to move the
pointer. Could you try minimizing ALL windows and then open them back again.
It would be interesting to know if this is a pattern because we found that
this fixed many lock ups.
Thanks and regards,
Patricia Calabria
> -----Original Message-----
> From: foxboro-bounce@xxxxxxxxxxxxx@CORP On Behalf Of Corey R
> Clingo <clingoc@xxxxxxxxxxxxx>
> Sent: Thursday, October 10, 2002 1:07 PM
> To: foxboro@xxxxxxxxxxxxx
> Subject: Re: [foxboro] CAR# 1003752 Keyboard Lockup on Fox Diisplay
> Manager on 51 Series !
>
>
>
> Tom,
>
> I submitted one for Foxview along these same lines. In my case, it
> appeared when I called up Foxdraw and exited several times. I was
> actually
> attempting to set up a machine to facilitate our conversion to Foxview and
> abandoned the effort because of these problems. The machine still has
> legacy Alarm Manager on it, so I don't think that was the cause of our
> problem.
>
> I did get a call back from FoxMass, and have talked to them a couple
> times,
> but no resolution yet. Unfortunately, I'm reluctant to try again because
> I'm doing this on an AW and having it lock up isn't a good thing.
>
> Corey Clingo
> BASF Corp.
>
>
>
> |---------+----------------------------->
> | | tom.vandewater@dow|
> | | corning.com |
> | | Sent by: |
> | | foxboro-bounce@fre|
> | | elists.org |
> | | |
> | | |
> | | 10/09/2002 06:08 |
> | | PM |
> | | Please respond to |
> | | foxboro |
> | | |
> |---------+----------------------------->
>
> >-------------------------------------------------------------------------
> ------------------------------------------------------|
> |
> |
> | To: foxboro
> |
> | cc:
> |
> | Subject: [foxboro] CAR# 1003752 Keyboard Lockup on Fox Diisplay
> Manager on 51 Series ! |
>
> >-------------------------------------------------------------------------
> ------------------------------------------------------|
>
>
>
>
>
> List,
> I have just submitted a CAR regarding Keyboard Lockup on Fox Display
> Managers on 51 Series Sun workstations! A description of the problem,
> symptoms, and work-around follows. I urge all of you that are
> experiencing
> this problem to submit a CAR also. You are welcome to cut and paste my
> text
> directly into the CAR. This list is a great forum to communicate both the
> good and the bad about Fox IA and represents a good cross section of
> users.
> The CAR system is the only "formal" way we have to define problems to
> Foxboro. Let's use it to our advantage!
>
> Tom VandeWater
> Control Systems Developer/Analyst
> Dow Corning Corp.
> Carrollton, KY USA
>
> Problem description: At Ver. 6.2.1 keyboard entry into Fox Display
> Manager windows running on AW/WP-51B, C, or D style boxes occasionally
> ceases to function giving the appearance of a faulty keyboard.
>
> Replacing the keyboard does not resolve the problem. Rebooting the
> Sun workstation, (AW/WP), does resolve the problem and was our only known
> way to make the keyboard work again. After repeatedly experiencing
> keyboard
> lockup problems on the local DM's of the Sun Workstations, we started
> using
> remote DM's called up on PC's running Windows 2000 and Hummingbird Exceed.
> The PC's experienced the same keyboard lockups as the AW/WP's but only on
> the Fox DM window. The PC keyboard continued to work in other Windows
> applications. We have now discovered that if we close out, or dismiss,
> the
> Alarm Manager window associated with the Fox DM, the keyboard will begin
> to
> function properly again.
>
> This led us to the conclusion that the Alarm Manager window somehow
> captures or locks up the keyboard function as far as the Fox DM is
> concerned. Dismissing the Alarm Manager releases the keyboard to be used
> by
> the DM. Calling up the Alarm Manager window doesn't always cause the
> keyboard to quit functioning in the Fox DM window. There must be some
> scenario or sequence of events that causes the keyboard lockup to begin!
> Although we haven't pinned down the exact sequence of events that cause
> the
> lockup, we are convinced that there is a problem with the Alarm Manager
> application, which, by the way, is displayed in a Motif window!! I don't
> know the difference between a Motif and a standard X-window used by the
> Fox
> DM, but I have heard that it makes a difference to Solaris. Foxboro has
> blamed the Sun OS for the cursor lockup problem, which I believe, is part
> of
> the same problem.
>
> We have 10 dual head WP-51's in our Central Control Room that use
> the Alarm Manager for monitoring process alarms. Each one is adjacent to
> a
> dual head PC that calls up remote DM's from its WP partner. The PC's also
> use the Alarm Manager. We have seen the keyboard on the local SUN WP
> continue to function in its DM window while the keyboard on the PC calling
> a
> remote DM from that same WP ceased to function in the PC DM window.
> Likewise we have seen the Sun keyboard fail to function while the PC
> keyboard still worked.
>
> We have 13 AW's where the DM's are used extensively both local and
> remote but don't use the Alarm Manager application. They do not
> experience
> keyboard lockups anymore, but we had a few that were used as process
> alarming stations in the past and they locked up when the Alarm Manager
> application was used on them! There is no doubt in our mind what is the
> root cause of the keyboard lock ups. It is the Alarm Manager!!
>
> We don't know if this same problem exists when using instances of
> Foxview instead of Display Managers because we don't use Foxview, which
> I'm
> told is a Motif application. We do know that we can work around the
> problem
> by closing or dismissing the Alarm Manager application on the affected
> workstation whether it is a PC or a Sun box.
>
> For your information, the default Alarm Managers on the local Sun
> workstation are configured in the /usr/fox/customer/hi/dmcfg file as:
> <type> Operator which is un-quittable. As such, they cannot be dismissed.
> To make them quittable go to the AMNAME section of the dmcfg file, as
> shown
> below and set them to RemoteOperator. The WP/AW must be rebooted for the
> changes to take effect.
> #---------------------------------------------------------
> # AMNAME <lbug> <amname> <dedicated monitor(s)>
> <type>
> #---------------------------------------------------------
> AMNAME 01AW01 01AW01 -
> RemoteOperator
> AMNAME " 01A011 -
> "
> AMNAME " 01A012 -
> "
> AMNAME " 01A013 -
> "
> AMNAME " 01A014 -
> "
>
> Work Around: If you cannot type in values or passwords in a Foxboro
> Display Manager Window and it looks as if you have a faulty keyboard, call
> up the Alarm Manager window associated with that DM and pick "FILE" and
> then
> "DISMISS". If you get a Message "Alarm Manager Application Un-Quittable"
> you either haven't editted the dmcfg file mentioned above or haven't
> rebooted the AW/WP since modifying the dmcfg file.When the Alarm Manager
> exits return to the DM and try again to type in values.
>
> This problem has been around since the inception of the Motif "Alarm
> Manager" and needs to be fixed!!
>
> ________________________________________________________________________
> This email has been scanned for all viruses by the MessageLabs SkyScan
> service. For more information on a proactive anti-virus service working
> around the clock, around the globe, visit http://www.messagelabs.com
> ________________________________________________________________________
>
>
> _______________________________________________________________________
> This mailing list is neither sponsored nor endorsed by Invensys Process
> Systems (formerly The Foxboro Company). Use the info you obtain here at
> your own risks. Read http://www.thecassandraproject.org/disclaimer.html
>
> foxboro mailing list: //www.freelists.org/list/foxboro
> to subscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
> to unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave
>
>
>
>
>
>
>
>
> _______________________________________________________________________
> This mailing list is neither sponsored nor endorsed by Invensys Process
> Systems (formerly The Foxboro Company). Use the info you obtain here at
> your own risks. Read http://www.thecassandraproject.org/disclaimer.html
>
> foxboro mailing list: //www.freelists.org/list/foxboro
> to subscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
> to unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave
>
-- No attachments (even text) are allowed --
-- Type: application/ms-tnef
_______________________________________________________________________
This mailing list is neither sponsored nor endorsed by Invensys Process
Systems (formerly The Foxboro Company). Use the info you obtain here at
your own risks. Read http://www.thecassandraproject.org/disclaimer.html
foxboro mailing list: //www.freelists.org/list/foxboro
to subscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
to unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave
________________________________________________________________________
This email has been scanned for all viruses by the MessageLabs SkyScan
service. For more information on a proactive anti-virus service working
around the clock, around the globe, visit http://www.messagelabs.com
________________________________________________________________________
________________________________________________________________________
This email has been scanned for all viruses by the MessageLabs SkyScan
service. For more information on a proactive anti-virus service working
around the clock, around the globe, visit http://www.messagelabs.com
________________________________________________________________________
_______________________________________________________________________
This mailing list is neither sponsored nor endorsed by Invensys Process
Systems (formerly The Foxboro Company). Use the info you obtain here at
your own risks. Read http://www.thecassandraproject.org/disclaimer.html
foxboro mailing list: //www.freelists.org/list/foxboro
to subscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
to unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave
Other related posts:
