Tim, Did you verify the commit disk is OK? We had a somewhat similar situation and it turned out to be a bad commit diskette. System Rebooted, Restarted Install Program and Hung Up - I manually Rebooted system from Task Bar - System would restart and get to the point of loading Foxview and then reboot. - Disabled IA System which allowed System to startup to desktop. Logfile d:\usr\fox\sp\SetupLog.xxxxx indicated there was an error reading the tar file from the commit disk. Install program never fully completed. Tar tvf of Commit Disk indicated a tar read error Made a new commit diskette and we were OK. Just thought I would throw this out. Tom Badura Plastics Engineering Company tbadura@xxxxxxxxxx -----Original Message----- From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] On Behalf Of Lowell, Timothy Sent: Thursday, August 26, 2010 5:20 PM To: 'foxboro@xxxxxxxxxxxxx' Subject: [foxboro] Software Install failure We had a Software Install fail on a P92 running v.8.4.2 recently, and I was hoping somebody out there had seen this particular type of failure and could enlighten us on what they think might have caused it. The purpose of the Software Install was to run a commit disk through with a new CP and some new workstations in a different area of the refinery. We wanted this P92 to know about those changes so the new stations would show up in System Monitor and be accessible with FoxSelect and so on. This particular P92 had no new CP's to host or any other significant changes to its own files, just a few PCHANG's for SysMon. After the Software Install environment is invoked, the box reboots, and the commit disk is requested and loaded, the process always stalls at a dialog box that reads "The system is now modifying registry settings" or something like that. When we checked the installation log, it always stops at the last entry for modifying the registry, as compared to older installation logs from successful commits. The next step that never runs is "Setting of Environment Variables". We have some third-party services running on the box, but we either uninstalled or disabled these services and re-ran the commit with the same results. Has anybody had a failure similar to this? As usual with Software Install failures, the standard answer is a Day Zero of the box. We will do that when time and circumstance permit, but if we had an idea of the cause, we might be able to avoid this in the future. Thanks, Tim Lowell Tesoro Refining Companies 19100 RidgeWood Parkway San Antonio, TX 78259 210-626-4929 (work) 210-253-0225 (cell) Timothy.lowell@xxxxxxxxxxx<mailto: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: //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: //www.freelists.org/list/foxboro to subscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=join to unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave