Graham,

so, generally speaking: In an AW51/WP70 environment you can't process and
visualize object data at the same time in the WP.  You would have to run an
X application on the AW51 (using FoxAPI to get the data) and have it open
its windows on the WP via Exceed (to visualize it for the operators).

Well...It's not what I hoped for, but so be it...

Regards and thanks,
Sascha


----- Original Message -----
From: "Heath, Graham" <[EMAIL PROTECTED]>
To: "'Foxboro DCS Mail List'" <[EMAIL PROTECTED]>
Sent: Friday, January 26, 2001 12:55 PM
Subject: RE: FoxAPI on WP70s / FoxView crashes


> Foxapi is not supported or designed to run ona WP70 hence the installation
> problems. If you have an application that requires it then it should be
run
> on an application (AW) processor.
>
> egds Graham Heath
>
> -----Original Message-----
> From: Sascha Wildner [mailto:[EMAIL PROTECTED]]
> Sent: 26 January 2001 10:48
> To: Foxboro Mailing List
> Subject: FoxAPI on WP70s / FoxView crashes
>
>
> Folks,
>
> thanks for the answers to my "FoxView crashes" mail.  I suspect that it is
a
> conversion problem from Display Manager to FoxView like David Johnson
> suggested.  I will verify that on Tuesday.
>
> Another question: What's the canonical way of installing FoxAPI on a
virgin
> WP70?  I have here an application which needs to run on a WP70 but also
> needs FoxAPI (for reading object values).  WP70s don't have FoxAPI and
when
> I asked some Foxboro people I got the following answers:
>
> * Add the Data for Windows / FoxAPI package to the WP70's system
> configuration.  Not satisfying since the application needs only FoxAPI and
> the customer is rather reluctant to install a package like DfW just to get
> the API onto the machine.
>
> * Install QF990084 (to install FoxAPI 4.2.2) and then QF990341 (to
> upgrade to 4.2.4) "on top of it".  This doesn't work since QF990084 has
been
> officially superseded by QF990341 and the latter needs an existing FoxAPI
to
> upgrade.  If there is no FoxAPI on the machine, the installation script
will
> fail because it will not find the API directory (/opt/fox/ais/bin).
> QF990084 is no longer available for NT machines on the CSC site.
>
> I could, of course, unpack the QF990341 manually and copy the files where
> they belong.  But this is far from being "official" (whatever that means).
>
> 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]
>


-----------------------------------------------------------------------
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