Sascha,

Is the DM/FV dying or is the station rebooting?

If the station is rebooting, the next question is, "Are these displays
optimizable or not, i.e., do they have complete path names or are they
generic?"

A good way to crash a WP/AW is to copy a file to a station while an earlier
version is being displayed on the station. DM/FV write to the OM table in
the file to optimize display call-up. If the file is copied while this write
is occurring, the OM table will be corrupted. Since the data in this table
is used directly by the OM, the OM will crash. If the OM crashes, the
station reboots.


Regards,


Alex Johnson
10707 Haddington
Houston, TX 77043
713.722.2859 (office)
713.722.2700 (switchboard)
713.932.0222 (fax)
[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> 


        -----Original Message-----
        From:   Sascha Wildner [SMTP:[EMAIL PROTECTED]]
        Sent:   Tuesday, January 23, 2001 6:56 AM
        To:     Foxboro Mailing List
        Subject:        Help! FoxView crashes

        Hello Folks,
         
        under which circumstances can a display with faceplates crash
FoxView with a segmentation fault?
         
        I have a set of displays here which do exactly that.  The problem
occurs usually after 7 or so callups of different displays (e.g. jumping in
between displays or calling them from the button row).  Testing revealed
that the faceplates seem to be responsible for it (e.g. if I move the
faceplates directory somewhere else, everything works fine).
         
        But I could not find any errors there.  Just normal faceplates with
.ALMSTA links for example.  They were created on an AW70 and then
transferred to AW51 with m1g/gm1.
         
        I have already tried the following:

*       dumped all displays and faceplates, removed the originals and
uploaded again
*       resized my displays in such a way that no graphics is outside of the
rectangle in foxdraw
*       run several incantations of fdf_version on both displays and
faceplates
*       downgraded my foxview from 99.2.1 to 99.2

        All to no avail.  I suspect that it is some object manager hiccup.
Is there anything else I overlooked?
         
         
        Sascha Wildner
        erpicon Software Development GmbH
        

-----------------------------------------------------------------------
This list is neither sponsored nor endorsed by the Foxboro Company. All 
postings from this list are the work of list subscribers and no warranty 
is made or implied as to the accuracy of any information disseminated 
through this medium. By subscribing to this list you agree to hold the 
list sponsor(s) blameless for any and all mishaps which might occur due to 
your application of information received from this mailing list.

To be removed from this list, send mail to 
[EMAIL PROTECTED] 
with "unsubscribe foxboro" in the Subject. Or, send any mail to
[EMAIL PROTECTED]

Reply via email to