Folks,
I don't care what anyone else tells you. What follows is true:
* No official support for local FoxAPI on a WP.
* The FoxAPI QFs are always (actually, have always been) complete
loads and can be installed by a clever person on a WP. This is not
forbidden, but don't call us to complain if it doesn't work or if it is
hard.
* The AIM* version of Data for Windows does not install FoxAPI (local
or net) and the libraries it does load are of no use to the end user since
they are not the netFoxAPI libraries that are documented.
* PIMS 2.0 Data for Windows installed FoxAPI V5.0, but has been
superceded by the AIM* version of Data for Windows and FoxAPI V5.0 has been
withdrawn and replaced by AIM*API.
* Data for Windows older than PIMS 2.0 installed an old version of
FoxAPI 4.x
This means that if you want FoxAPI on a WP, you must load a QF that contains
the complete FoxAPI by hand. No other mechanism works and absolutely no
mechanism is official.
I will mention to our Marketing folks that many people would like to buy
FoxAPI for use on WPs. Who knows maybe they will part number it.
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: Julie Monsour [SMTP:[EMAIL PROTECTED]]
Sent: Monday, January 29, 2001 10:34 PM
To: Foxboro DCS Mail List
Subject: Re: FoxAPI on WP70s / FoxView crashes
We have quite a few WP70s that require FoxAPI to run on them so that
we may
select a "server" for the FoxDraw application. The way that we
install the
FoxAPI is to select "Data for Windows" as part of the WP70s software
packages to install in System Definition before creating the commit.
Upon
completion of this committal process, FoxAPI is installed on the
WP70 and is
auto started on reboot.
Julie M. Monsour
Foxboro Field Service
----- Original Message -----
From: "Johnson, Alex" <[EMAIL PROTECTED]>
To: "Foxboro DCS Mail List" <[EMAIL PROTECTED]>
Sent: Friday, January 26, 2001 9:07 AM
Subject: RE: FoxAPI on WP70s / FoxView crashes
> Re: What's the canonical way of installing FoxAPI on a virgin
WP70?
>
> The answer is "There is no canonical way of installing FoxAPI on a
virgin
> WP70." FoxAPI is not supported as an "end product" on the WP70.
>
> It will run on a WP70, but there is no standard installation.
>
>
> Re: I have here an application which needs to run on a WP70 but
also needs
> FoxAPI (for reading object values)
>
> One of the true joys of NT - no remote displays.
>
> The recent Server 70 product would allow your application to run
on the AW
> and put its display on the WP, but I'm sure you don't have one and
they
cost
> more.
>
>
>
> 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: Friday, January 26, 2001 4:48 AM
> 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]
-----------------------------------------------------------------------
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]
