[foxboro] Windows AW user app startup (was: FV DMNAME objects smurfing)

Out of curiosity, why did this change?  I mean, really -- this is one of 
those thousand cuts that cause death when going to Windows.

I know I got some gray hair with my first AW70, between the keyboard not 
working the same in ICC (and it's different again on Solaris 8!), the old 
standby Unix commands not working,local ICC only, etc.  I got explanations 
for all of it, some of which make sense, some not.  As usual, I worked 
around it enough to get my pain down to a tolerable level.  One thing 
Foxboro has done is create a small army of highly resourceful individuals, 
most of whom inhabit this list.  If I were some company looking for a 
controls person, I'd come here first :)


OK, back to the topic -- my decidedly unofficial solution is a batch file 
in the Fox user's "Startup" folder.  I have a virtual CP in it (R.I.P. to 
that, apparently, if I go to v8),  and in it I spin on an omget of the 
STATION.MINUTE variable in the virtual CP (I'm sure a real CP would work 
here, too).  Once I'm able to get it, I assume all of I/A is up and start 
my user programs (OPC I/O Gate and OPC servers, mostly).


Corey Clingo
BASF Corporation






"Landry, Scott" <scott.landry@xxxxxxxxxxxxxxxx> 
Sent by: foxboro-bounce@xxxxxxxxxxxxx
11/19/2008 10:06 PM
Please respond to
foxboro@xxxxxxxxxxxxx


To
<foxboro@xxxxxxxxxxxxx>
cc

Subject
Re: [foxboro] FV DMNAME objects smurfing








  Mr. Ricker,


   /usr/fox/bin/fox_apps.dat on NT/V7.x/V8.x has become the default
   place to start user apps from. Not the official place though.

   A good rule to follow is to make sure the user app start lines
   always come after the IPS ones. 

   I ran into a situation yesterday where a IPS package was added.
   The package was AIMSTAR. The AIMSTAR installer adds to the
fox_apps.dat
   file. The installer added the line on the same line as a user app
which
   was on the last line.

   C_VARAIMSTAR  , so neither started.  Moral to the story, be careful.



   Best Regards,


    Scott L. Landry

    IPS  Region6 Field Service USA



 
 

 

-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx]
On
Behalf Of Doucet, Terrence
Sent: Tuesday, November 18, 2008 6:06 PM
To: foxboro@xxxxxxxxxxxxx
Subject: Re: [foxboro] FV DMNAME objects smurfing

William,
 
a)  The AW70 does not support the \etc\fox\user_apps.dat function. There
are
some files located in the directory but you cannot execute anything from
these files on boot up of the AW70.   I have not tested the Server 70
but I
suspect - no, it does not support the user_apps.dat function.
 
b) the \usr\fox\bin\fox_apps.dat is the method for starting custom
applications. Since this also starts the Foxboro apps, care is required
to
ensure OM and FoxAPI and other apps are (100%) started before you
application gets started otherwise some of your calls might fail.  The
other
thing to consider is to save this custom file in event that a Foxboro
release upgrade over-writes the file.
 
Regards,
 
Terry
 




 
 
_______________________________________________________________________
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:             http://www.freelists.org/list/foxboro
to subscribe:         mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
to unsubscribe:      mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave

Other related posts: