Re: Sumpin's broke
- From: "Rock" <rock@xxxxxxxxxx>
- Date: Thu, 8 Feb 2007 14:38:13 -0800
"Noncompliant" <spamyourself@xxxxxxxxx> wrote
XP HE w/sp2 here. Awhile back, tried to install NAV 2007. I had to uninstall NAV 2004. Did that with add/remove programs. Then used the Symantec removal tool from their website. It didn't like Zone Alarm Pro at install time, so uninstalled it. After completing the uneventful installation of NAV, ran into some things not occurring before. See next to last paragraph for less detail.
MSXML not installed correctly per AOE III game.
DI 7.0 stated saved image file was internally corrupted or not supported when checking the image file after saving. I save my image files to the H: partition (see below).
Tracked down the culprit. It was the Symantec removal tool that wrecked the MSXML 4.0 sp2 update install (KB927978). I save my image files on another partition which is on another physical hard drive formatted NTFS, H: partition. On this partition at the root were 2 folders named for numerical IDs. In each folder was an installation outcome of MSXML 4.0 for SP2. Why is this here instead of on the C: partition?
I uninstalled the MSXML 4.0 sp2 update via add/remove programs. Experimenting with the H: partition, its allowed me to delete the folders with the file containing the MSXML 4.0 sp2 update outcome. Upon selecting "turn off computer", said something about an update. The update would only be installed if I selected "turn off". I rebooted instead of turning the PC off. Checked if the folders reappeared or if MSXML 4.0 sp2 update had reappeared. All good. This time, I elected to turn off the PC. XP showed installing 1 update during shutdown. Upon turning the PC back on, found MSXML 4.0 sp2 update was back in add/remove programs. Another 2 folders showed up on the H: drive.
System restore folder was on the H: drive, and it was being monitored by system restore per device manager. I could not delete the folder. I removed the read only attribute to this folder, and it just reappeared after I checked its properties again.
I was unable to copy or move any of my image files with Windows explorer on the H: drive/partition. I could copy image files to another partition with DI explorer, but that was taking forever. Copying the partition to another was a 5 hour affair. So, I copied the most critical image files with DI explorer. Then, wiped the H: partition with a 3rd party partition application booted from CD. Disk management would not let me remove the H: drive/partition.
I had to restore a previous image file of an XP installation prior to the MSXML 4.0 sp2 update as those after that were confused when they couldn't find the folders and installation outcome on the H: partition. That is, AOE III said MSXML wasn't installed correctly again.
Oh, one other thing. Installing NAV 2007 over ZA or ZA Pro doesn't really break anything in ZA. The installation results in the inoperability of some of NAV 2007's intrustion blocks and alerts.
In a nutshell, Symantec/Norton removal tool wrecked MSXML 4.0 sp2 update.
The update was putting the installation outcome in file format on the H: partition.
System restore folder on H: was unremovable.
Disk management wouldn't let me remove the H: partition.
A new H: partition resulted in MSXML 4.0 sp2 update not installed correctly per AOE III (the game wouldn't start as result)
Questions-
Why did the MSXML 4.0 sp2 update put the folder and installation result file on the H: partition?
Windows update looks for the partition with the most space for to park it's temp files. For some reason the folder with the log file for the installation of that MSXML 4.0 SP2 update is not being deleted. I have just deleted the folder after the update was successful. Deleting the folder does not cause any issues with the update.
Why did there result a loss of installation when I deleted these folder/file combos?
You cannot delete the System Volume Information folder. What you can do is turn off SR for that partition, and it should be turned off on only data only partitions. The folder will still be there but with minimal content.
Why you were having all the other problems I don't know, but to begin with I would not have any of the Norton home products running on a system. They are resource hogs and cause problems sooner or later.
--
Rock [MVP - User/Shell]
.
- Follow-Ups:
- Re: Sumpin's broke
- From: Noncompliant
- Re: Sumpin's broke
- References:
- Sumpin's broke
- From: Noncompliant
- Sumpin's broke
- Prev by Date: Re: MEMORY UPGRADE
- Next by Date: Re: pc wont work
- Previous by thread: Sumpin's broke
- Next by thread: Re: Sumpin's broke
- Index(es):
Relevant Pages
|
Loading