<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd"
		>
<channel>
	<title>Comments on: Resolve Program And Application Installation Problems On Windows With Installer Cleanup Utility</title>
	<atom:link href="http://www.watchingthenet.com/resolve-program-and-application-installation-problems-on-windows-with-installer-cleanup-utility.html/feed" rel="self" type="application/rss+xml" />
	<link>http://www.watchingthenet.com/resolve-program-and-application-installation-problems-on-windows-with-installer-cleanup-utility.html</link>
	<description>Computer - Internet - Technology Tips And Tutorials</description>
	<lastBuildDate>Thu, 29 Jul 2010 13:38:51 +0000</lastBuildDate>
	
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Michael</title>
		<link>http://www.watchingthenet.com/resolve-program-and-application-installation-problems-on-windows-with-installer-cleanup-utility.html#comment-21605</link>
		<dc:creator>Michael</dc:creator>
		<pubDate>Mon, 14 Dec 2009 16:07:27 +0000</pubDate>
		<guid isPermaLink="false">http://www.watchingthenet.com/how-to-resolve-program-application-install-problems-on-windows-xp-vista-95-98.html#comment-21605</guid>
		<description>A little over a year ago, an MSI script executed on several PCs with the option to monitor certain file(s).  If Windows detected a file changed, it assume that corruption occurred.  The installer would respond by putting the old file back on the PC.  The problem is, whenever an upgrade is made, the installer thinks the file has been corrupted.  Its response is to put the old file back.  This means that an upgrade cannot be done.  By using your utility, I can do a cleanup and resolve the problem; However, since well over 100 PCs are involved, to do it manually would be quite an effort.  Can your utility be called from the command prompt to do the cleanup?  If it can, I could create a bat file and have it executed on each PC.</description>
		<content:encoded><![CDATA[<p>A little over a year ago, an MSI script executed on several PCs with the option to monitor certain file(s).  If Windows detected a file changed, it assume that corruption occurred.  The installer would respond by putting the old file back on the PC.  The problem is, whenever an upgrade is made, the installer thinks the file has been corrupted.  Its response is to put the old file back.  This means that an upgrade cannot be done.  By using your utility, I can do a cleanup and resolve the problem; However, since well over 100 PCs are involved, to do it manually would be quite an effort.  Can your utility be called from the command prompt to do the cleanup?  If it can, I could create a bat file and have it executed on each PC.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
