RE: Report Writer
We have the same problem of not printing data when run from scheduler. We referred this to Foxboro long back. We stopped using report writers and now all reports are being prepared through IP.21 which is our site wide Management Information System. Regards Harshad "Nic Glenister" <[EMAIL PROTECTED]> on 12/29/2000 04:47:33 AM Please respond to "Foxboro DCS Mail List" <[EMAIL PROTECTED]> To: "Foxboro DCS Mail List" <[EMAIL PROTECTED]> cc:(bcc: Harshad Viradia/JAMNAGAR/RIL) Subject: RE: Report Writer G'day Noman, I have a similar situation occurring at one of my sites (although it occurred on "demand" reports as well) and raised a CAR (see #165). Apparently, if you are using a Style B control processor (I guess this would include a CP60) and an AW that is NOT a Style E there is some kind of speed mismatch that will not allow the Report Writer to extract more than 29 consecutive parameters from a CP. Has anyone else had an experience that can confirm/deny the above? I'm told that the target version for a fix for this is V6.3, but I think I'll test it first before informing the customer. Does anyone know what the official release date of V6.3 is? I hope everyone runs suitably amok on New Years Eve. Nic Glenister Foxboro Melbourne > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]]On Behalf Of Noman > Abu-Farha > Sent: Friday, December 29, 2000 9:21 AM > To: [EMAIL PROTECTED] > Subject: Report Writer > > > Hapy New Year to all . > > In our company we have report which is used to collect data from > the object > manager and scheduled daily. In each day we get dashes "---" > in some of > the data field. Every day this happens in different data fields > (not in the > same one). But if we demand the report . The report will be complete and > without any missing. > Pleas help me in solving this problem > > Noman > Jubail Chemical Industries Co. > KSA. > _ > Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com. > > > --- > 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]
Re: Displays Viewer
Best way is to get FV/DM on PC as a x-win and use "alt+printScreen". Paste this to word document, Power Point etc. The advantages are, very fast, good clarity which you may not get by using "snapshot" and one single document containing all the graphics. Best regards Harshad Viradia Stefano Persico <[EMAIL PROTECTED]> on 03/01/2001 10:59:11 PM Please respond to "Foxboro DCS Mail List" <[EMAIL PROTECTED]> To: Foxboro DCS Mail List <[EMAIL PROTECTED]> cc:(bcc: Harshad Viradia/JAMNAGAR/RIL) Subject: Displays Viewer Hi all Does anybody know if exist a kind of viewer for FoxDraw/FoxView and Display Manager displays ? I' m trying to build a backdocumentation cd and my intention is to attach also FV-FD and/or DM display . It will be useful to have the possibility to preview these displays. Thanks in advance --- 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]
Alarms when input changes.
Hi list. I have more than 100 MAIN blocks configured for LIMS. CIMIO & FOXAPI is used for writing value to these MAIN blocks and displaying on graphics. The frequency of writing data is very low may be once or twice a day. I want to generate an alarms when value of any one of the MAIN block input has changed and in turn operator will know about new updates in data. I have configured MAIN block in LIMS graphics. I tried using ACHNGE parameter but than I have to configure AIN block for each MAIN input so that point wise alarm can generated. Is anybody having any better idea? Thanks in advance. Harshad --- 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]
Re: Upgrading Foxboro Boxes
Hi list, We are using six numbers of C boxes out of which two are used for advanced applications and we had a problem of crashing these boxes with "panic:thread broken" error. Foxboro replaced the dual processors (75MHz each) with single processor (150MHz) and we never faced this problem again. This may be helpful for those who are using C boxes. Thanks Harshad Darryl Bond <[EMAIL PROTECTED]> on 04/19/2001 05:15:03 AM Please respond to "Foxboro DCS Mail List" <[EMAIL PROTECTED]> To: Foxboro DCS Mail List <[EMAIL PROTECTED]> cc:(bcc: Harshad Viradia/JAMNAGAR/RIL) Subject: Re: Upgrading Foxboro Boxes "Ball, Patrick G." wrote: > > Steve, > I was originally told that the problem was with the twin processors > on the C box (A SUN problem???). I don't think it was a Sun problem. Here is the output of 2 dual processor Sparc20 & Sparc10 sun boxes (non Foxboro) [dbond@dino dbond]$ psrinfo -v Status of processor 0 as of: 04/19/01 08:35:42 Processor has been on-line since 12/10/99 13:44:13. The sparc processor operates at 75 MHz, and has a sparc floating point processor. Status of processor 2 as of: 04/19/01 08:35:42 Processor has been on-line since 12/10/99 13:44:17. The sparc processor operates at 75 MHz, and has a sparc floating point processor. [dbond@dino dbond]$ uptime 8:35am up 495 day(s), 18:52, 5 users, load average: 0.01, 0.02, 0.03 [dbond@goofy dbond]$ psrinfo -v Status of processor 0 as of: 04/19/01 08:34:04 Processor has been on-line since 11/19/99 06:15:10. The sparc processor operates at 60 MHz, and has a sparc floating point processor. Status of processor 2 as of: 04/19/01 08:34:04 Processor has been on-line since 11/19/99 06:15:14. The sparc processor operates at 60 MHz, and has a sparc floating point processor. [dbond@goofy dbond]$ uptime 8:34am up 517 day(s), 2:19, 8 users, load average: 0.06, 0.05, 0.06 [dbond@goofy dbond]$ > The fix was to disable one of the > processor, but we were upgrading for a faster machine. I think that is why > they changed to D and E boxes. ??? We used the Foxboro upgrade to 150Mhz single processor which fixed the lockups which we saw with the AW51C. This is the report from an upgraded AW51C [dbond@6GA111 dbond]$ psrinfo -v Status of processor 0 as of: 04/19/01 08:42:03 Processor has been on-line since 05/23/00 09:22:16. The sparc processor operates at 150 MHz, and has a sparc floating point processor. [dbond@6GA111 dbond]$ uptime 8:42am up 330 day(s), 23:20, 2 users, load average: 0.30, 0.18, 0.15 Darryl Bond > > Patrick > PSDF > > > -Original Message- > > From: Murray, Steve [SMTP:[EMAIL PROTECTED]] > > Sent: Wednesday, April 18, 2001 2:25 PM > > To: 'Foxboro DCS Mail List' > > Subject: RE: Upgrading Foxboro Boxes > > > > Hi Patrick, > > > > We bought a AW51C a few years ago as part of a new system. It would > > crash > > for no apparent reason and the Foxboro installation team replaced it with > > a > > AW51B before turning the system over to us. We were later told that > > Foxboro > > quit using the Cs altogether. > > > > Stephen Murray > > Asarco > > > > -Original Message- > > From: Ball, Patrick G. [mailto:[EMAIL PROTECTED]] > > Sent: Wednesday, April 18, 2001 10:59 AM > > To: 'Foxboro DCS Mail List' > > Subject: RE: Upgrading Foxboro Boxes > > > > > > Robert, > > I am located at the PSDF (Power System Development Facility) her in > > Wilsonville, AL. back a couple of years ago, we upgraded to an AW51C from > > AW51A box (Ver. 4.1). We also have OSI PI system. I thought the A box was > > slow, but when we got our C box, it would run fine without PI running, but > > when PI was started the C box would crash in about 45 minutes. We had to > > get > > an AW51E box to fix the problem. We did work it out since we had just > > upgraded to a C box. I know this probably does not answer your question, > > but > > I thought I would throw this in. > > > > Patrick G. Ball > > Internet Address -- mailto:[EMAIL PROTECTED] > > Intercompany -- 8-824-5877 > > Bell Phone -- 1-205-670-5877 > > Beeper -- 1-877-986-6814 > > <http://psdf.southernco.com/> > > > > This transmission is for the intended addressee only and is confidential > > information. If you have received this transmission in error, please > > delete > > it and notify the sender. The contents of this E-mail are the opinion of > > the > > writer only and are not endorsed by ASARCO Inc. unless expressly stated > > otherwise. > > > > -
Re: Display overwrite crashes OM database?
Hello, I have experience a problem of corrupting display file (fdf) while distributing on AW51s and WP51s if same display is being closed at the same time. This corruption was leading towards broadcasts (instead of opening OM list) of all the connected C:B.Ps on the graphics when displayed on Foxview, in other word crashing of internal OM database of display. This is because of the displays are changing on the workstation while the same displays are being distributed to the workstation. Display changing on workstation can be verified by looking at the date and time of display files in VT100. ( Display changing means that displays are updated on the disk if the display is being optimised, which happens when a display is being closed). I am using Foxview version 99.2.1 and following work around is mention in release note for above problem. "The safest way to distribute display over workstation is to call in a static display on the workstation and not allow the display to be changed until the distribution is completed. it is not necessary to optimise the display before distribution". Please give feedback Regards Harshad Viradia System Engineer Reliance Petroleum Ltd. Jamnagar "Sascha Wildner" <[EMAIL PROTECTED]> on 07/31/2000 02:25:01 PM Please respond to "Foxboro DCS Mail List" <[EMAIL PROTECTED]> To: "Foxboro Mailing List" <[EMAIL PROTECTED]> cc:(bcc: Harshad Viradia/JAMNAGAR/RIL) Subject: Display overwrite crashes OM database? Hello, has anybody experienced problems on AW70 when overwriting a display on the hard disk (while distributing displays for example) which is being displayed in FoxView? Rumor has it that the display's internal OM database could be damaged then. Can anyone confirm this? I also heard that when a display is closed data from it is written back to the hard disk and could overwrite the newly distributed display. What's the recommended workaround? Someone suggested displaying the initial display while distributing displays. But how do I explain this the the operators? Regards, Sascha Wildner erpicon Software Development GmbH (UUEncoded file named: att1.htm follows) (Its format is: Internet HTML ) Attachment Converted: "C:\PROGRAM FILES\EUDORA\Attach\att1.htm" --- 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]
Sysdef
Hi list I have five systems with plenty of nodes. The sysdef of one of the system having 24 nodes showing incorrect IP address in hardware definition. I am using sysdef, revision 2.0. The first two filed of most of the IP address in hardware definition shows 127.000 and 158.128 instead of 151.128 (Class assigned to Foxboro). After day 0 and commit, /etc/hosts shows correct IP addresses of all the hosts i.e. 151.128. ... . I have checked the uniqueness of MAC address, NSAP and IP, and are ok. The sysdef for other systems shows correct IP address in hardware definition. Can anyone advise, whether its a problem of sysdef software for large configuration or I am committing some errors. Thanks in advance. Harshad Viradia Reliance Petroleum Ltd. Jamnagar. --- 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]
RE: Sysdef
This is also given in version 6.1 release notes.
Regards
Harshad
"Yousif, Mohammed R" <[EMAIL PROTECTED]> on 08/30/2000 10:36:49 AM
Please respond to "Foxboro DCS Mail List"
<[EMAIL PROTECTED]>
To: "'Bruley,Peter'" <[EMAIL PROTECTED]>, "'Foxboro DCS MailList'"
<[EMAIL PROTECTED]>
cc:(bcc: Harshad Viradia/JAMNAGAR/RIL)
Subject: RE: Sysdef
I am referring to " I/A Series V4.3 Installation Considerations" BO193UG
-Original Message-
From: Bruley,Peter [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, August 29, 2000 7:08 PM
To: 'Foxboro DCS Mail List'; Yousif, Mohammed R
Subject: RE: Sysdef
What manual are you referring to ? Can you give us a P0193 number ?
--
From: Yousif, Mohammed R
Sent: Monday, August 28, 2000 9:47 PM
To: 'Foxboro DCS Mail List'
Subject: RE: Sysdef
Hi All
Your problem accrued because you were using different PC to
configure your
System. The first two filed of the IP address need to be set in the
PC that
runs the SysDef by using "regedit.exe" and access HKY_LOCAL_MACHINE
- SYSTEM
- TCP/IP ( Refer to SysDef Manual )
For your Information, only the last two digit are used and stored in
the
commit configuration.
If you want to clean the SysDef you need to set TCPIP then delete
all your
station and add them again. I suggest to leave them since this will
not
effect your operations and could lead to more problem.
Regards,
Mohammed Al-Yousif
Saudi Aramco
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]] On Behalf Of Harshad
Viradia
Sent: Tuesday, August 29, 2000 6:14 AM
To: Foxboro DCS Mail List
Subject: Sysdef
Hi list
I have five systems with plenty of nodes.
The sysdef of one of the system having 24 nodes showing incorrect IP
address
in
hardware definition. I am using sysdef, revision 2.0.
The first two filed of most of the IP address in hardware definition
shows
127.000 and 158.128 instead of 151.128 (Class assigned to Foxboro).
After day 0 and commit, /etc/hosts shows correct IP addresses of
all the
hosts
i.e. 151.128. ... .
I have checked the uniqueness of MAC address, NSAP and IP, and are
ok.
The sysdef for other systems shows correct IP address in hardware
definition.
Can anyone advise, whether its a problem of sysdef software for
large
configuration or I am committing some errors.
Thanks in advance.
Harshad Viradia
Reliance Petroleum Ltd.
Jamnagar.
---
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]
---
This list is neither sponsored nor endorsed by the Foxboro Company. All
postings f
Re: Changing the I/A Series Timezone
Alex, We changed the timezone of our off-line set-up to IST while testing IP.21 interface with I/A using following procedure. #cd /usr/share/lib/zoneinfo #zic asia (this will create directory called /Asia/Culcutta..) #cd /etc #vi TIMEZONE Modify TZ=GMT to TZ=Asia/Calcutta Reboot AW. AW also got rebooted and it worked fine. We checked system monitor time and was showing ok. We did not check historian data time stamp and CP time at that time. This was done way back in early 1999. This is not implemented in any of our on-line systems at site as Local Foxboro office said that in I/A we can not change time zone from GMT to any other time zone. Regards Harshad Viradia Reliance Petroleum Ltd. Jamnagar "Johnson,Alex" <[EMAIL PROTECTED]> on 09/20/2000 06:12:46 AM Please respond to "Foxboro DCS Mail List" <[EMAIL PROTECTED]> To: Foxboro DCS Mail List <[EMAIL PROTECTED]> cc:(bcc: Harshad Viradia/JAMNAGAR/RIL) Subject: Changing the I/A Series Timezone Have any of you changed the time zone setting from GMT to something else? If so, did you use /etc/default/init? If so, what did you see as behavior, good and bad. I've can contribute three items: 1) The corporate documentation says don't change it from GMT and do not enable automatic timezone changes. 2) Some folks that I know say that they did change the time zone at a site and that the following happened: The time indication with following I/A application was correct: *System Monitor, *Display Manager display *Historian sample data display *Historian reduction data *Historian trend display *Operator Action Journal report *CP STATION block's HOUR and MINUTE parameters *Historian Schedule and Archive window But GMT time was shown in : *Historian Configuration, Data Display and MDE Data Entry 3) On one occasion many years ago, a project team changed the timezone and the machine would not reboot. However, that was a long time ago. Any one else have any experience? Regards, Alex Johnson The Foxboro Company 10707 Haddington Houston, TX 77043 713.722.2859 (v) 713.722.2700 (sb) 713.932.0222 (f) [EMAIL PROTECTED] <mailto:[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]
Re: Changing the I/A Series Timezone
-- Forwarded by Harshad Viradia/JAMNAGAR/RIL on 09/21/2000 09:20 AM --- Harshad Viradia 09/20/2000 09:42 AM To: "Foxboro DCS Mail List" <[EMAIL PROTECTED]> cc: Subject: Re: Changing the I/A Series Timezone (Document link: Harshad Viradia) Alex, We changed the timezone of our off-line set-up to IST while testing IP.21 interface with I/A using following procedure. #cd /usr/share/lib/zoneinfo #zic asia (this will create directory called /Asia/Culcutta..) #cd /etc #vi TIMEZONE Modify TZ=GMT to TZ=Asia/Calcutta Reboot AW. AW also got rebooted and it worked fine. We checked system monitor time and was showing ok. We did not check historian data time stamp and CP time at that time. This was done way back in early 1999. This is not implemented in any of our on-line systems at site as Local Foxboro office said that in I/A we can not change time zone from GMT to any other time zone. Regards Harshad Viradia Reliance Petroleum Ltd. Jamnagar "Johnson,Alex" <[EMAIL PROTECTED]> on 09/20/2000 06:12:46 AM Please respond to "Foxboro DCS Mail List" <[EMAIL PROTECTED]> To: Foxboro DCS Mail List <[EMAIL PROTECTED]> cc:(bcc: Harshad Viradia/JAMNAGAR/RIL) Subject: Changing the I/A Series Timezone Have any of you changed the time zone setting from GMT to something else? If so, did you use /etc/default/init? If so, what did you see as behavior, good and bad. I've can contribute three items: 1) The corporate documentation says don't change it from GMT and do not enable automatic timezone changes. 2) Some folks that I know say that they did change the time zone at a site and that the following happened: The time indication with following I/A application was correct: *System Monitor, *Display Manager display *Historian sample data display *Historian reduction data *Historian trend display *Operator Action Journal report *CP STATION block's HOUR and MINUTE parameters *Historian Schedule and Archive window But GMT time was shown in : *Historian Configuration, Data Display and MDE Data Entry 3) On one occasion many years ago, a project team changed the timezone and the machine would not reboot. However, that was a long time ago. Any one else have any experience? Regards, Alex Johnson The Foxboro Company 10707 Haddington Houston, TX 77043 713.722.2859 (v) 713.722.2700 (sb) 713.932.0222 (f) [EMAIL PROTECTED] <mailto:[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]
RE: find command ussage?
I am using following script to delete core files. I have put this on cron to delete cores daily at 12.00PM. #find / -fstype urfs -prune -o -name core -print > core_data #cat core_data | while read corefile #do #rm $corefile This is working fine on AW51Bs, WP51Bs and AW51Es version 6.1. Regards Harshad Viradia Reliance Petroleum Ltd Jamnagar "Lowell, Tim:" <[EMAIL PROTECTED]> on 09/27/2000 05:50:25 PM Please respond to "Foxboro DCS Mail List" <[EMAIL PROTECTED]> To: "'Foxboro DCS Mail List'" <[EMAIL PROTECTED]> cc:(bcc: Harshad Viradia/JAMNAGAR/RIL) Subject: RE: find command ussage? When I said I remove it every Monday, that just means that Monday is when I happen to look for it. I use one of Angel Corbera's scripts on a crontab schedule to find the core files (Thanks, Angel!), and I delete them each Monday morning. We use GoGlobal instead of eXceed here, and I think that has a lot to do with FoxSelect creating these core files. By the way, here is Angel's command for finding core files, which works well: find / -fstype urfs -prune -o -name core -ls I don't know what urfs is either, but I know this works on an AW51E at v6.1 every week. Tim -Original Message- From: Murray, Steve [SMTP:[EMAIL PROTECTED]] Sent: Tuesday, September 26, 2000 2:54 PM To: 'Foxboro DCS Mail List' Subject: RE: find command ussage? Hi Tim, My particular core file was generated last Thursday when a PC running Exceed had a Fox Select window freeze up. I had to shutdown Foxview (on the PC) to get the Fox Select window to go away, and I found the core file on Friday morning. "file core" indicated the culprit was Fox Select, and the timestamp was from Thursday, so I am "assuming" the PC exceed problem caused the core dump. Is Fox Select causing your core dumps? If you get one every Monday and it has the same timestamp, you might look for something in cron that runs about the same time. A few years ago on my first Foxboro system I had a core file generated every five minutes by the historian reduction group program. It wasn't very big, but it was dumped every five minutes for at least five months. My predecessor had deleted some collection points but had not removed them from the reduction groups. Didn't seem to cause any harm, but it was odd when I found the core files . . . --- 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]
RE: Problem in Foxapi/CIMIO
We faced this problem initially with CIMIO V4.9 and then we upgraded to V4.91. After installing CIMIO 4.91, we never faced any problem and is quite stable. Any clue for Foxapi problem? Latest finding is when we delete 5 of the AW out of 37 total from "sldb" and "hldb" files (not from sysdef) and restart FoxAPI, it works fine. Is there any limit on number of AW in a single system? Thanks & regards Harshad "Airhart, Chad M." <[EMAIL PROTECTED]> on 12/13/2000 09:10:21 PM Please respond to "Foxboro DCS Mail List" <[EMAIL PROTECTED]> To: "'Foxboro DCS Mail List'" <[EMAIL PROTECTED]> cc:(bcc: Harshad Viradia/JAMNAGAR/RIL) Subject: RE: Problem in Foxapi/CIMIO Just a note of a problem we have encountered with IP/21/CIMIO/FoxAPI that may or may not apply here. There is a bug in how IP/21 handles get records. We thought initially if we turned the record processing off when we added points and turned it back on it would rebuild the sets properly. This is not the case. It begins rebuilding (close and reopen) the set in API as soon as a change is made and . This causes a problem when multiple points are being changed or added. CIMIO is trying to open and close the same set multiple times at the same time. What happens is one of the CIMIO processes dies and dumps a huge core file which really drags down the system. This really gave us fits for a while because IP/21 just would not communicate. We had to get an Aspen tech out to resolve this issue. He did state this is not happening on all installations for some reason. It is just random. What we are now doing on Aspen's recommendation in the interim (a fix is supposedly in work) is to stop CIMIO make all changes and restart it. This works but is annoying. Chad Airhart Instrument, Electrical & Control Systems Engineer Equistar Chemicals, LP. Victoria, TX Wk. (361) 572-2568 Pgr. (361) 270-2214 alpha messaging at [EMAIL PROTECTED] Fx. (361) 572-2541 > -Original Message- > From: John Miller [SMTP:[EMAIL PROTECTED]] > Sent: Monday, December 11, 2000 1:48 PM > To: 'Foxboro DCS Mail List' > Subject: RE: Problem in Foxapi/CIMIO > > I don't remember the specifics, but I've done roughly the same thing. > However, based upon my observations, it seems that it takes about fifteen > minutes before all of the CIMIO GET tables are functioning properly. > > -Original Message- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] > Sent: Monday, December 11, 2000 8:34 AM > To: [EMAIL PROTECTED] > Subject: RE: Problem in Foxapi/CIMIO > > > > > > We are using a 5 minute delay in the CIMIO startup script > (/etc/fox/go_CIMIOFOXIA). The script is kicked off by placing > it in /etc/fox/user_apps.dat. We collect about 4000 tags per > AW, and are using QF990084. Our workstations are all 250MHz > AW51Es (Ultra30). > > Foxapi is started with a sleep 40 in /usr/fox/bin/go_FOXAPI. I > don't believe we altered that script. > > Jim Murphy > > O-O > | James D. MurphyPhone: 317-276-6859 | > | Sr. Process Control Engineer FAX: 317-277-9270 | > | Eli Lilly and Company Pager: 317-256-5500 | > | Lilly Corporate Center Email: [EMAIL PROTECTED] | > | Mail Drop Code: 3418| > | Indianapolis, Indiana 46285 | > O-O > |++--- > -| > || John Miller | > | > ||| > || .com>| 'Foxboro DCS Mail > | > || Sent by: | List' > | > || [EMAIL PROTECTED]| > <[EMAIL PROTECTED]| > || andraProject.org | sandraProject.org> > | > ||| cc: > | > || 12/11/00 09:02 AM| Subject: > | > || Please respond to| RE: Problem in > | > || Foxboro DCS Mail List| Foxapi/CIMIO > | > ||| > | > |++--- > -| > > > > > > > > > We've been told by some very knowledgeable folks at Foxboro that it takes > roughly fifteen minutes after re-booting before an AW is really itself. > I've just
Re: Alarm Formats
Hi list, We have just comissioned IMAC software and removed all our 72 printers. Its really nice and you can have alarms on your desk PC. Regards Harshad --- 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]
Dot Matrix Printer
Hi all, I am facing strange problem in one of the three dot matrix printers connected to one COMM10. Two printers are working normally meaning printing file, alarms etc. One printer which is connected to first port is meant for system alarm messages is not printing system alarms as well as text file. The printing of text file from any of the workstations in the system is not working and while trying giving error message "failed to open the printer port (transport endpoint not connected)" I have tried all possible ways like delete and adding again, reinstallation of OS1CS, changing all the possible h/w and cables, but result is same. This printer stopped working after recommittal of new sysdef. We restored the recent dump tapes to our off-line set-up for further analysis and found printer is working in off-line set-up (printing all system alarms, files). Same disks we took to on-line system and found that same printer is still not working. We have more than 30 dot matrix printers (all are replaced with Imac PCs) and are working fine. Are there anything more to try other than helpful hint #694 ? Best regards Harshad Viradia --- 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]
Re: Re[2]: Dot Matrix Printer
Thanks. We have used sysdef 2.1 for the expansion of our existing sysdef which was developed earlier in 1.1, than revised in 2.0 as our sysdef being a very large contains more than 600 letterbugs it was not possible to start from scratch. This was also analysed by Foxboro, experts from USA, and local office. We have also tested this in our off-line set-up before committal. Further to add in a problem, this printer (LP03) is configured as a back up printer to process alarm printer (LP04) and by failing LP04 process alarms are getting directed to LP03. So the problem due to device monitor also is ruled out, We have also installed QF for Device Monitor in all workstations. What I believe is problem has to do some thing with the print service and network port (tcp). Meaning some how print request from any of the workstation is not getting accepted on network. I have checked the "tcp" port activity for "lp" services on host AW & WPs and is showing ENABLED. Best regards Harshad "Daren Bishop" <[EMAIL PROTECTED]> on 08/28/2001 09:30:43 PM Please respond to "Foxboro DCS Mail List" <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] cc:(bcc: Harshad Viradia/JAMNAGAR/RIL) Subject: Re[2]: Dot Matrix Printer Harshad, Question: Did you use a newer or different version of SysDef to create the new commit?? Answer: If so, it is always a good idea to rebuild the SysDef from scratch when using a new version of Sysdef. I know this is a major hassle, but I have had major "unexplainable" problems updating a SysDef configuration with a newer version of SysDef. Daren Bishop ASC. Inc. __ Reply Separator _ Subject: Re: Dot Matrix Printer Author: "Foxboro DCS Mail List" <[EMAIL PROTECTED]> at INTERNET-MAIL Date:8/28/01 8:46 AM Hi, You might get some help from HH832 and HH843 on the Device Monitor. This has ca used us problems before. Also there is good printer help on Angel Corbera's web site: http://www.geocities.com/SiliconValley/Peaks/5825/contents.htm Hope this helps. Jim Kahlden [EMAIL PROTECTED] >>> [EMAIL PROTECTED] 08/28/01 05:20AM >>> Hi all, I am facing strange problem in one of the three dot matrix printers connected to one COMM10. Two printers are working normally meaning printing file, alarms etc. One printer which is connected to first port is meant for system alarm messages is not printing system alarms as well as text file. The printing of text file from any of the workstations in the system is not working and while trying giving error message "failed to open the printer port (transport endpoint not connected)" I have tried all possible ways like delete and adding again, reinstallation of OS1CS, changing all the possible h/w and cables, but result is same. This printer stopped working after recommittal of new sysdef. We restored the recent dump tapes to our off-line set-up for further analysis and found printer is working in off-line set-up (printing all system alarms, files). Same disks we took to on-line system and found that same printer is still not working. We have more than 30 dot matrix printers (all are replaced with Imac PCs) and are working fine. Are there anything more to try other than helpful hint #694 ? Best regards Harshad Viradia --- 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 postingsfrom 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 su bscribing to this list you agree to hold the list sponsor(s) blameless for any a nd all mishaps which might occur due to your application of information receivedfrom this mailing list. To be removed from this list, send mail to [EMAIL PROTECTED] g 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 wa
RE: Re[2]: Dot Matrix Printer
Dear Ron, As you said and as I mentioned earlier, I checked device monitor before and is not a problem as process (block) alarms are getting printed (on LP03) and the status of LP03 in DEV_MONITOR is showing OK. The problem: System monitor alarm messages, which are configured for this printer (LP03) are not printed. Text file from host AW or from any of the workstations in the same system (WPs) is not getting printed on the same printer (LP03). Other two printers (LP04, LP05) are working fine connectd to same COMM10. Same LP03 is working in my off-line set-up (restored from the recent dump tapes of host AW). Best regards Harshad "Deen, Ron" <[EMAIL PROTECTED]> on 08/29/2001 02:10:36 PM Please respond to "Foxboro DCS Mail List" <[EMAIL PROTECTED]> To: Foxboro DCS Mail List <[EMAIL PROTECTED]> cc:(bcc: Harshad Viradia/JAMNAGAR/RIL) Subject: RE: Re[2]: Dot Matrix Printer I think this was mentioned before but anyway... If you can't print a file direct like: "myfile > /dev/LP03", you have another problem. If you can print "lp myfile -dLP03" but alarms do not go to that same printer read on. On one of your hosts go to the directory "/usr/fox/cs": 1 remove (if it exsists) the "cs_dm.current" file. (If it does NOT exsist, don't remove it ;-)) 2 run the command "dm_recon t". This will Take Device Monitor mastership to this station. 3 run the command "dm_recon d" which will dump the current status of all devices as found by devmon in a file "cs_dm.current" This can take a little while. Be patient! In this file look for the printer that does not work. You will find it after the word "STATUS" in that file. The file could look something like this: . . . STATION: "1CM1B1": STATE: OPERATIVE TYPE: COMM10 Device: 1 " LP01" TYPE: PRINTER STATUS: FAIL PR REMOTE ' LP04' Device: 2 " LP02" TYPE: PRINTER STATUS: OK PR REMOTE ' LP04' Device: 3 " LP03" TYPE: PRINTER STATUS: FAIL PR REMOTE ' LP04' Device: 4 " TT01" TYPE: TERMINAL STATUS: OK PR NONE STATION: "1FW1E1": STATE: OPERATIVE TYPE: COMM10 Device: 1- NOT CONFIGURED Device: 2- NOT CONFIGURED . . . If it reads FAIL but you are sure it should work, try to do a "dm_recon" (without any parameters). This will force the Master Devmon (which is the station you are working on because of the step 2 above) to analyse all devices again. After some time (minutes) try to do a "dm_recon d" again and have a look at the "cs_dm.current" file again if your problem is solved. I hope it is... Regards, Ron Deen (Foxboro) -Original Message- From: Harshad Viradia [mailto:[EMAIL PROTECTED]] Sent: Wednesday, August 29, 2001 5:14 AM To: Foxboro DCS Mail List Subject: Re: Re[2]: Dot Matrix Printer Thanks. We have used sysdef 2.1 for the expansion of our existing sysdef which was developed earlier in 1.1, than revised in 2.0 as our sysdef being a very large contains more than 600 letterbugs it was not possible to start from scratch. This was also analysed by Foxboro, experts from USA, and local office. We have also tested this in our off-line set-up before committal. Further to add in a problem, this printer (LP03) is configured as a back up printer to process alarm printer (LP04) and by failing LP04 process alarms are getting directed to LP03. So the problem due to device monitor also is ruled out, We have also installed QF for Device Monitor in all workstations. What I believe is problem has to do some thing with the print service and network port (tcp). Meaning some how print request from any of the workstation is not getting accepted on network. I have checked the "tcp" port activity for "lp" services on host AW & WPs and is showing ENABLED. Best regards Harshad "Daren Bishop" <[EMAIL PROTECTED]> on 08/28/2001 09:30:43 PM Please respond to "Foxboro DCS Mail List" <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] cc:(bcc: Harshad Viradia/JAMNAGAR/RIL) Subject: Re[2]: Dot Matrix Printer Harshad, Question: Did you use a newer or different version of SysDef to create the new commit?? Answer: If so, it is always a good idea to rebuild the SysDef from scratch when using a new version of Sysdef. I know this is a major hassle, but I have had major "unexplainable" problems updating a SysDef configuration with a newer version of SysDef. Daren Bishop ASC. Inc. __ Reply Separator _ Subject: Re: Dot Matrix Printer Author: "Foxboro DCS Mail List" <[EMAIL PROTECTED]> at INTERNET-MAIL Date:8/28/01 8:46 AM Hi, You might ge
RE: Re[2]: Dot Matrix Printer
Hi all, The problem got resolved by rebooting the DZLI for this node. I have a questions, is system alarm messages using Device Monitor for routing messages to printer? As when I rebooted DZLI (LAN module), one of the WP on this node has become the device monitor master and started printing alarms on LP03. Thanks for all help Best regards Harshad -- Forwarded by Harshad Viradia/JAMNAGAR/RIL on 08/29/2001 03:42 PM --- "Harshad Viradia" <[EMAIL PROTECTED]> on 08/29/2001 02:19:07 PM Please respond to "Foxboro DCS Mail List" <[EMAIL PROTECTED]> To: "Foxboro DCS Mail List" <[EMAIL PROTECTED]> cc:(bcc: Harshad Viradia/JAMNAGAR/RIL) Subject: RE: Re[2]: Dot Matrix Printer Dear Ron, As you said and as I mentioned earlier, I checked device monitor before and is not a problem as process (block) alarms are getting printed (on LP03) and the status of LP03 in DEV_MONITOR is showing OK. The problem: System monitor alarm messages, which are configured for this printer (LP03) are not printed. Text file from host AW or from any of the workstations in the same system (WPs) is not getting printed on the same printer (LP03). Other two printers (LP04, LP05) are working fine connectd to same COMM10. Same LP03 is working in my off-line set-up (restored from the recent dump tapes of host AW). Best regards Harshad "Deen, Ron" <[EMAIL PROTECTED]> on 08/29/2001 02:10:36 PM Please respond to "Foxboro DCS Mail List" <[EMAIL PROTECTED]> To: Foxboro DCS Mail List <[EMAIL PROTECTED]> cc:(bcc: Harshad Viradia/JAMNAGAR/RIL) Subject: RE: Re[2]: Dot Matrix Printer I think this was mentioned before but anyway... If you can't print a file direct like: "myfile > /dev/LP03", you have another problem. If you can print "lp myfile -dLP03" but alarms do not go to that same printer read on. On one of your hosts go to the directory "/usr/fox/cs": 1 remove (if it exsists) the "cs_dm.current" file. (If it does NOT exsist, don't remove it ;-)) 2 run the command "dm_recon t". This will Take Device Monitor mastership to this station. 3 run the command "dm_recon d" which will dump the current status of all devices as found by devmon in a file "cs_dm.current" This can take a little while. Be patient! In this file look for the printer that does not work. You will find it after the word "STATUS" in that file. The file could look something like this: . . . STATION: "1CM1B1": STATE: OPERATIVE TYPE: COMM10 Device: 1 " LP01" TYPE: PRINTER STATUS: FAIL PR REMOTE ' LP04' Device: 2 " LP02" TYPE: PRINTER STATUS: OK PR REMOTE ' LP04' Device: 3 " LP03" TYPE: PRINTER STATUS: FAIL PR REMOTE ' LP04' Device: 4 " TT01" TYPE: TERMINAL STATUS: OK PR NONE STATION: "1FW1E1": STATE: OPERATIVE TYPE: COMM10 Device: 1- NOT CONFIGURED Device: 2- NOT CONFIGURED . . . If it reads FAIL but you are sure it should work, try to do a "dm_recon" (without any parameters). This will force the Master Devmon (which is the station you are working on because of the step 2 above) to analyse all devices again. After some time (minutes) try to do a "dm_recon d" again and have a look at the "cs_dm.current" file again if your problem is solved. I hope it is... Regards, Ron Deen (Foxboro) -Original Message- From: Harshad Viradia [mailto:[EMAIL PROTECTED]] Sent: Wednesday, August 29, 2001 5:14 AM To: Foxboro DCS Mail List Subject: Re: Re[2]: Dot Matrix Printer Thanks. We have used sysdef 2.1 for the expansion of our existing sysdef which was developed earlier in 1.1, than revised in 2.0 as our sysdef being a very large contains more than 600 letterbugs it was not possible to start from scratch. This was also analysed by Foxboro, experts from USA, and local office. We have also tested this in our off-line set-up before committal. Further to add in a problem, this printer (LP03) is configured as a back up printer to process alarm printer (LP04) and by failing LP04 process alarms are getting directed to LP03. So the problem due to device monitor also is ruled out, We have also installed QF for Device Monitor in all workstations. What I believe is problem has to do some thing with the print service and network port (tcp). Meaning some how print request from any of the workstation is not getting accepted on network. I have checked the "tcp" port activity for "lp" services on host AW & WPs and is showing ENABLED. Best regards Harshad "Daren Bishop" <[EMAIL PROTECTED]> on 08/28/2001 09:30:43 PM Please respond to "Foxboro DCS Mail List" <[EMAIL PRO
RE: AW BOXES
Re 1: If host AW51B (Sun box) is replaced with new one, you can use helpful hint #845 to change PSAP address of all CPs hosted by this AW. No need to reboot any CPs. Re 2: As far as I know AW51B may not be directly replaced by AW51C. You may require to change in sysdef, day0, committal, reboot of all stations and loadall. Hope above helps. Best regards Harshad "dhawly hawpyt" <[EMAIL PROTECTED]> on 09/01/2001 07:52:37 AM Please respond to "Foxboro DCS Mail List" <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] cc:(bcc: Harshad Viradia/JAMNAGAR/RIL) Subject: RE: AW BOXES Thanx a Lot. Our AW51B has crashed and we have to replace by new one. And We are not having AW51B But in our other plant AW51C is spare . 1.If some how we get same AW51B then also what is the procedure to replace sun box? As MAC Address will be changed of AW Box ,is it required to reboot the each CP? Can we just replace it or something is to be done? 2And we have to replace AW51B by AW51C which we can get immediatelly ,then also what is to be done? Is sysdef is to be changed? And same questions as above also? Thanx a lot in advance Shawly Hawl >From: [EMAIL PROTECTED] >Reply-To: "Foxboro DCS Mail List" <[EMAIL PROTECTED]> >To: [EMAIL PROTECTED] >Subject: RE: AW BOXES >Date: Fri, 31 Aug 2001 09:27:16 -0400 > >In addition to the information offered by Alex, check out the Cassandra FAQ >page: > > http://www.thecassandraproject.org/hardware_faq.html#B2 > >Duc > >-- >The Cassandra Project >http://www.thecassandraproject.org/ > > >-Original Message- >From: Johnson, Alex (Foxboro) [mailto:[EMAIL PROTECTED]] >Sent: Thursday, August 30, 2001 10:15 PM >To: Foxboro DCS Mail List >Subject: RE: AW BOXES > > >AW51B - SPARCstation 5 - Clock rates range are 85 MHz, 110 MHz, 175 MHz >AW51C - SPARCstation 20 with dual 65 MHz microprocessors >AW51E - UltraSPARC 30 with a 248 MHz processor > >Hope this helps. > >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: dhawly hawpyt [SMTP:[EMAIL PROTECTED]] >Sent: Thursday, August 30, 2001 5:53 PM >To: [EMAIL PROTECTED] >Subject: AW BOXES > >Hi Friends, > >can you help to know > >..The differences between AW51B ,AW51C & AW51E? > > >Thanx in Advance > >Sawly hawl > > >_ >This message has been checked for all known viruses by the >MessageLabs Virus Scanning Service. For further information visit >http://www.messagelabs.com/stats.asp > > >--- >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] > _ Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp --- 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]
Contact Information
My Info. Harshad Viradia Manager Reliance Petroleum Ltd. Moti Khavadi Jamnagar Gujarat India Contact : +91 288 295337 Fax : +91 288 295296 Best regards Harshad Viradia Phone - 515337 --- 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]
