Re: [foxboro] Installing Ver.8.0b/8.1 on Dell 340 PC that was Ver .7.x

Thanks for the feedback, Ed.  You have been very helpful.
Cheers,
Tom VandeWater

Larsen, Ed wrote:
> Tom,
> 
> Almost had to be the Nic drivers. My particular case 340 7.x to 8..x the
> sysdef was v2.7 and had foxapi checked. I also did a V8 box last week that
> had Aim* historian checked. Neither foxapi or Aim* has been loaded yet. Too
> many other things to do.  :(
> 
> Glad you got er done. :)
> 
> Regards,
> 
> 
> 
> -----Original Message-----
> From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] On
> Behalf Of tom.vandewater@xxxxxxxxxxxxxx
> Sent: Tuesday, January 31, 2006 4:27 PM
> To: foxboro@xxxxxxxxxxxxx
> Subject: [foxboro] Installing Ver.8.0b/8.1 on Dell 340 PC that was Ver.7.x
> 
> List,
>       I issued a call for help last Friday regarding installing
> Ver.8.0b/8.1 software on a Dell 340 PC that was originally purchased for
> use at Ver.7.x.  We experienced a continual reboot cycle on our first
> attempt.  I received helpful information from three sources:
> 
> Ali Ahmed Zahidi:  Load FoxAPI from separate CD after DAY0, before
> reboot.
> 
> Russ Boulay: Install Allied Telesyn Fiber NIC cards and driver
> Ver.4.45.0.0 before Day0 install.
> 
> Ed Larsen:  Step-by-Step procedure to upgrade PW340 from V7.1. to V8.0b
> 
> All of these were excellent, and very helpful, feedback to my question
> and I'm including the highlights of each below.
> 
>       BTW, we finally achieved a successful installation Monday
> afternoon.  However, there is still some question as to what really
> fixed our problem because there appears to be several ways to get into
> the reboot cycle.     Unfortunately we changed two things at once, the
> correct driver for the Fiber NIC's, and removed FOXAPI and AIM*Historian
> from our SysDef Commit Disk.
> 
> Thanks to all, and I hope the following info can help others faced with
> the same task.
> Cheers,
> Tom VandeWater
> 
> Ali Ahmed Zahidi sent the following:
> "We had faced the same problem with Win XP based version 8.0 software.
> This problem normally occurs if do not install FoxAPI from a separate
> CD, (came with your system), at the end of the normal installation. To
> fix this problem we restored Windows XP to a pre I/A install checkpoint
> and then re-installed I/A ver 8.0 software. After completion of normal
> Day0 installation we installed FoxAPI and then rebooted. This solved our
> problem."
> 
> Russ Boulay sent the following:
> "Tom....the symptoms you describe are based on the dual NICs not being
> detected.  If during the day0 install you are not prompted the option to
> select dual cards...then the machine does not have the drivers loaded to
> support those NICS.
> V8.x will not run without the existence of dual NICS in the machine.
> The machine will go into a constant reboot about 3-4 minutes into the
> bootup.  Duc mentioned that you never get the dual prompt. That tells me
> there are no drivers for the cards that are installed.  The restore CD
> from your "older" 7.x machine, does not have these drivers depending on
> the machine type and vintage.
> All Dell 360's 370's and 380's have the drivers.
> Dell 340's did not.
> V8.x software has:
> a day0 cdrom (V8.0b)
> a Trailer CD
> a ethernet NIC driver CD
> You must use the driver CD and make sure the allied telesyns are
> detected
> and functioning before beginning your day0 commit."
> 
> Russ, we never received the K0173XA CD-ROM media with our Ver.8.0b/8.1
> software.  Maybe because we didn't buy the Allied Telesyn Fiber NIC's
> from Foxboro.  The driver CD that came from Allied Telesyn with the
> NIC's is, surprisingly, the same date but a slightly different Rev than
> what you said:
> 
> 7/02/2004 4.47.0.0
> Instead of
> 7/02/2004 4.45.0.0
> 
>       We went to:
> http://www.alliedtelesyn.com/support/software/details.aspx?pid=3D167
> 
> and downloaded Ver.4.45.0.0 to insure that we matched what you
> prescribed.  Based on Ed Larsen's experience, it appears that the
> 4.47.0.0 driver for the Allied Telesyn NIC's will also work, and that is
> what we had installed before our initial DAY 0, so I'm not sure if our
> NIC driver was the issue.  However, on our first DAY 0 we did reboot, as
> requested, right after the day 0 CD finished loading and before we
> loaded the Trailer Disk.  The release notes say to load the trailer CD
> before rebooting.
> 
> Ed Larsen sent the following:
> 
> Steps to change PW340 from V7.1. to V8.0b
> 
> 1.  Backup box
> 
> 2. Insert two Allied Telesyn AT2701Fx cards in pci slot 2 and 3
> 
> 3. Restore to factory using restore cd
> 
> 4. My Allied telesyn cards came up as AMD something or other. Used
> Device Manager to uninstall both of them
> 
> 5. Used the Allied Telesyn cd and ran ATSETUP. Reboot and they were now
> recognized as Allied Telesyn. Need to update driver to 4.47 using the
> attached zip file
> 
> 6. Rename computer and setup virtual memory paging file, then reboot
> reboot when prompted
> 
> 7. Run setup from 8.0b cd rev b
> 
> 8. Will prompt for network cards. pick both allied telesyn pick continue
> anyway twice
> 
> 9. Network installation successful pick ok
> 
> 10. Finish commit as expected
> 
> 11. I did get a component select item error popup. Picked ok and it
> continued.
> 
> 12. Release level diskette 11001 when prompted.
> 
> 13. When prompted pick NO to restart and review the logs looking for
> errors
> 
> 14. remove setup=20
> 
> 15. insert Trailer cd. run install.bat
> 
> 16. Reboot or install Foxview
> Presto Worked like a champ.
> 
> Russ Boulay sent the following:
> Installing/Updating the Network Interface Card
> Drivers for I/A Series V8.x Workstations
> B0700BL-D
> Before starting to install I/A Series V8.0 software, the network
> interface
> card drivers must be installed using the procedures below and the
> K0173XA CD-ROM media.
> 
> Installing the Allied Telesyn NIC Driver (Fiber)
> To install the correct driver for your Allied Telesyn NIC(s), perform
> the
> following steps:
> 1. Right-click My Computer and select Manage.
> 2. Click Device Manager.
> 3. Double-click Network Adapters.
> 4. Right-click Allied Telesyn AT-2701FX PCI 100Mb Fiber Ethernet adapter
> or
> AMD PCNet Family PCI Ethernet adapter (or #2 for second adapter) and
> select
> Update Driver.
> 5. The "Hardware Update Wizard" opens. Select Install from list or
> SpecificLocation (Advanced). Click Next.
> 6. The wizard asks you to choose search and installation options. Click
> Don't Search.
> I will choose the driver to install. Click Next.
> 7. The wizard asks you to select the network adapter you want to install
> for
> this hardware.
> Click Have Disk.
> 8. The "Install from Disk" window opens. Type in E:\Allied Telesyn and
> click
> OK.
> 9. The wizard returns to the "Select the network adapter you want to
> install
> for this
> hardware" window. Click Next.
> 10. The "Complete the Hardware Update" window opens. Click Finish.
> 11. The Device Manager should indicate an Allied Telesyn AT-2701FX PCI
> 100Mb
> Fiber Ethernet adapter.
> 12. Right-click on Allied Telesyn AT-2701FX PCI 100Mb Fiber Ethernet
> adapter,
> select Properties, then click on the Driver tab. The driver's version
> should
> be:
> 7/02/2004 4.45.0.0
> Click OK to close window.
> 13. Repeat steps 4 through 12 for a second (#2) or third (#3) Allied
> Telesyn
> (AMD
> PCNet) NIC.
> 14. Shutdown and Restart the workstation for the driver to take full
> effect.
>  
>  
> _______________________________________________________________________
> 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
>  
> 
>  
>  
> _______________________________________________________________________
> 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
>  
> 
 
 
_______________________________________________________________________
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: