<x-html><!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content="text/html; charset=iso-8859-1" http-equiv=Content-Type>
<META content="MSHTML 5.00.2919.6307" name=GENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#ffffff>
<DIV><FONT face=Arial size=2>Folks,</FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=Arial size=2>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.</FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=Arial size=2>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:</FONT></DIV>
<UL>
<LI><FONT face=Arial size=2>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.</FONT></LI>
<LI><FONT face=Arial size=2>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.</FONT></LI></UL>
<DIV><FONT face=Arial size=2>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).</FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=Arial size=2>Sascha Wildner<BR>erpicon Software Development
GmbH<BR></DIV></FONT></BODY></HTML>
</x-html>
