Re: [foxboro] OSISoft PI Startup on P90 Windows 2003 Server

What exactly is the Windows equivalent of "kill <process>"?  Does Windows 
have signals?  Does the Foxboro Winix have signals?  And what does Windows 
do to a program when it shuts down, since there are no kill scripts 
(/etc/rc0.d/Knnxxxx) scripts like Solaris has?

Corey





<duc.do@xxxxxxxxxxxxxx> 
Sent by: foxboro-bounce@xxxxxxxxxxxxx
04/21/2009 04:51 PM
Please respond to
foxboro@xxxxxxxxxxxxx


To
<foxboro@xxxxxxxxxxxxx>
cc

Subject
Re: [foxboro] OSISoft PI Startup on P90 Windows 2003 Server






> FoxAPI doesn't do a very
> good job closing the lists and giving up resources when you stop fxbais
> no matter which way you start it, so you end up having to reboot the box
> anyway 

Well, there goes another case of reduced functionalities as one "upgrades" 
to Windows. On one of my Solaris boxes used for PI interface, I haven't 
had to reboot it in nearly two years (I had stopped and restarted the 
interface many times).

03AW01-dmdo> uptime
  5:51pm  up 651 day(s),  4:06,  2 users,  load average: 0.06, 0.04, 0.04

But ... progress marches on.

Duc


-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] 
On Behalf Of Lowell, Timothy
Sent: Tuesday, April 21, 2009 5:42 PM
To: foxboro@xxxxxxxxxxxxx
Subject: Re: [foxboro] OSISoft PI Startup on P90 Windows 2003 Server

So, fxbais.exe doesn't run as a service, then?  The QF supposedly fixed
that problem on Win2K3 Server.  The go_FXBAIS file is the tried and true
method. 

We have the PI interface running on Windows XP here in Hawaii, and the
QF doesn't address running fxbais.exe as service on that operating
system.  We also use go_FXBAIS and it works great.  We even have two
interfaces running on the same P92 with no problems.  There really isn't
much advantage to running it as a service.  FoxAPI doesn't do a very
good job closing the lists and giving up resources when you stop fxbais
no matter which way you start it, so you end up having to reboot the box
anyway if you make any changes to the interface itself (adding and
deleting points works OK, just not adding new scan classes, for
example).

Tim Lowell
Control Systems Engineer
Tesoro Petroleum Company
210-626-4929 (w)
210-253-0225 (c)
Timothy.Lowell@xxxxxxxxxxx

 



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