Re: [foxboro] RE : Barriers to migration to Windows
- From: "Johnson, Alex P \(IPS\)" <alex.johnson@xxxxxxxxxxxxxxxx>
- To: <foxboro@xxxxxxxxxxxxx>
- Date: Wed, 29 Aug 2007 15:10:58 -0400
I understand that xcopy will copy files between machines using the standard=
MS notation
xcopy <file> \\<serverName>\<path>
It can copy sub-directories as well.
Regards,
Alex Johnson
Invensys Systems, Inc.
10900 Equity Drive
Houston, TX 77041
713.329.8472 (voice)
713.329.1700 (fax)
713.329.1600 (switchboard)
alex.johnson@xxxxxxxxxxxxxxxx
-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] On=
Behalf Of Hillier, Bill
Sent: Wednesday, August 29, 2007 11:35 AM
To: foxboro@xxxxxxxxxxxxx
Subject: Re: [foxboro] RE=A0: Barriers to migration to Windows
I use a utility from Microsoft called Robocopy. It makes the target =3D
folders the same as the source. It only copies/deletes the files it =3D
needs to in order make the source and target the same. It comes in the =3D
Windows Server 2003 Resource Kit Tools package. It works great and is =3D
fast.
Here is the syntax I use in a batch file to make the folder on the =3D
source the same as the folder on the target station. I put a line in the =
=3D
batch file for each AW.
robocopy d:\opt\lup\ \\1aw1we\IA\opt\lup\ /e
Bill Hillier
Process Control Superintendent
=3D20
600 ROUTE 785
UTOPIA, N.B.
E5C 2K4
(: (506)755-4468
Fax: (506)755-6303
@*: hillier.bill@xxxxxxxxxxxxxxxxxxx
-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] =
=3D
On Behalf Of Wiggins, Bryan
Sent: Wednesday, August 29, 2007 2:45 PM
To: foxboro@xxxxxxxxxxxxx
Subject: Re: [foxboro] RE=3DA0: Barriers to migration to Windows
We Use the scrip "Blow" also. =3D3D20
Bryan Wiggins=3D3D20
Xcel Energy=3D3D20
Hayden Co
-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx
[mailto:foxboro-bounce@xxxxxxxxxxxxx]On Behalf Of Pulas, Philip
Sent: Wednesday, August 29, 2007 11:38 AM
To: foxboro@xxxxxxxxxxxxx
Subject: Re: [foxboro] RE : Barriers to migration to Windows
We currently have 101 MS AW's on our Mesh (as well as 12 more on 3 =3D3D3D
offline nodes for training and development) and there is no file sharing =
=3D
=3D3D
=3D3D3D
possible. All "common" files (displays, library objects, etc.) must be =3D=
=3D3D
=3D3D3D
copied around to every workstation, though FTP and TELNET are not needed =
=3D
=3D3D
=3D3D3D
for this.
There are two ways to do this (one makes it very easy and one is very =3D
=3D3D
=3D3D3D
time consuming):
Method 1: We were provided a scripting tool called Blow (I don't know if =
=3D
=3D3D
=3D3D3D
Foxboro provided it or not) that copies files around to any/all AW's =3D
=3D3D3D
that you choose. On I/A v8.2 AW's you have to make sure the log to a =3D
=3D3D
=3D3D3D
file option is not checked. Here is a description from its readme file:
Blow Readme
General
The blow script resembles the traditional blow script that was written
=
=3D
=3D3D
=3D3D3D
for Solaris. The blow script will copy files from the local machine to =
=3D
=3D3D
=3D3D3D
all remote machines defined in the rhosts.txt, located in the same =3D
=3D3D3D
directory as the script.
Description
The blow script does not require any typing to copy files over to
=3D
=3D3D3D
remote stations. Instead, a shortcut to the blow script may be added =3D
=3D3D
=3D3D3D
to the Send To items under the contextual menu (right mouse menu) or to =
=3D
=3D3D
=3D3D3D
the desktop. Then, any number of files and folders may be selected to =3D=
=3D3D
=3D3D3D
be remote copied. The user may then right mouse click on the selected =3D=
=3D3D
=3D3D3D
items and under the Send To menu, send them to the remote stations. =3D
=3D3D
=3D3D3D
Alternatively, the user may then drag and drop the items to the Blow =3D
=3D3D
=3D3D3D
Shortcut on the desktop.
Method 2: In Windows Explorer, you can add each workstation as a network =
=3D
=3D3D
=3D3D3D
place as follows: Open Windows Explorer, click on My Network Places, =3D
=3D3D3D
double-click Add Network Place, click Next when the prompt appears, wait =
=3D
=3D3D
=3D3D3D
for an option to appear for "Choose another network location" and select =
=3D
=3D3D
=3D3D3D
it (this can be immediate or within a couple of minutes), click Next, =3D
=3D3D
=3D3D3D
for the address enter \\$GCLBUG\ia (for d drive) or \\$GCLBUG\c$ (for c =3D=
=3D3D
=3D3D3D
drive), click Next, click Next (or change the name it will display), =3D
=3D3D3D
click Finish. It will now always appear under My Network Places.
Thanks,
Philip Pulas
Tesoro
Golden Eagle Refinery
Martinez, CA
-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] =
=3D
=3D3D
=3D3D3D
On Behalf Of tom.vandewater@xxxxxxxxxxxxxx
Sent: Wednesday, August 29, 2007 10:09 AM
To: foxboro@xxxxxxxxxxxxx
Subject: Re: [foxboro] RE=3D3D3DA0: Barriers to migration to Windows
This is an interesting thread indeed. USB drives on MS AW's. When we
=3D=
=3D3D
=3D3D3D
=3D3D3D3D
moved to the MESH and AWXP's we immediately realized that the Windows =3D
=3D3D
=3D3D3D
=3D3D3D3D
boxes appeared to be intentionally isolated from access to other boxes, =3D=
=3D3D
=3D3D3D
=3D3D3D3D
(even other Windows boxes on the MESH. Unless I'm missing something, =3D
=3D3D
=3D3D3D
=3D3D3D3D
there is no way to do even a basic file transfer or remote login to the =3D=
=3D3D
=3D3D3D
=3D3D3D3D
MS AW's unless you take matters into your own hands. Given a fast new =3D
=3D3D
=3D3D3D
=3D3D3D3D
network, you might have expected that Foxboro would have provided some =3D
=3D3D
=3D3D3D
=3D3D3D3D
way to keep common system files and shared graphics updated between =3D3D
=3D3D3D3D
boxes. It wasn't obvious to me. We immediately started using USB =3D
=3D3D3D3D
drives to handle all of these administrative transfers. FTP and Telnet =3D=
=3D3D
=3D3D3D
=3D3D3D3D
services are by default disabled and Foxboro doesn't create a common =3D3D
=3D3D3D3D
workgroup that would allow sharing via the standard MS capability.
All this makes me ask, are there any large scale MS/MESH users out =3D3D
=3D3D3D3D
there? Please chime in. What have you done to share files between the =3D=
=3D3D
=3D3D3D
=3D3D3D3D
MS AW's/WP's? Have you enabled FTP and/or TELNET services? Have you =3D
=3D3D
=3D3D3D
=3D3D3D3D
established an MS workgroup to share files between AW's? If so, is it a =
=3D
=3D3D
=3D3D3D
=3D3D3D3D
Foxboro approved method? Did you go-it-alone and break any of the =3D
=3D3D3D3D
Foxboro apps? Given my perceived lack of connectivity between MS AW's =3D
=3D3D
=3D3D3D
=3D3D3D3D
it is even harder for me to understand what the drivers are to migrate. =
=3D
=3D3D
=3D3D3D
=3D3D3D3D
I am far from being Foxboro MS savvy so don't hesitate to enlighten me =3D
=3D3D
=3D3D3D
=3D3D3D3D
on how I can better use/administer the boxes running on this platform. =3D=
=3D3D
=3D3D3D
=3D3D3D3D
My reply might sound cynical but my intent is really bent at learning =3D
=3D3D
=3D3D3D
=3D3D3D3D
how to optimize/utilize the two MS AW's that we MUST have on site to =3D3D
=3D3D3D3D
support the MESH stations.
Tom VandeWater
Control Systems Developer/Analyst
Dow Corning Corporation
Carrollton, KY USA=3D3D3D20
=3D3D20
=3D3D20
_______________________________________________________________________
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
=3D3D20
foxboro mailing list: //www.freelists.org/list/foxboro
to subscribe: =3D3D
mailto:foxboro-request@xxxxxxxxxxxxx?subject=3D3D3Djoin
to unsubscribe: =3D3D
mailto:foxboro-request@xxxxxxxxxxxxx?subject=3D3D3Dleave
=3D3D20
=3D20
=3D20
_______________________________________________________________________
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
=3D20
foxboro mailing list: //www.freelists.org/list/foxboro
to subscribe: =3D
mailto:foxboro-request@xxxxxxxxxxxxx?subject=3D3Djoin
to unsubscribe: =3D
mailto:foxboro-request@xxxxxxxxxxxxx?subject=3D3Dleave
=3D20
=
=
_______________________________________________________________________
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: //www.freelists.org/list/foxboro
to subscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=3Djoin
to unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=3Dleave
=
Confidentiality Notice:
The information contained in this electronic message and any attachment(s) =
to this message are intended for the exclusive use of the recipient(s) and =
may contain confidential, privileged or proprietary information. If you are=
not the intended recipient, please notify the sender immediately, delete a=
ll copies of this message and any attachment(s). Any other use of the E-Mai=
l by you is prohibited.
_______________________________________________________________________
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: //www.freelists.org/list/foxboro
to subscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
to unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave
Other related posts: