<?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"
	>
<channel>
	<title>Comments on: File Name Warning</title>
	<atom:link href="http://www.intelliot.com/blog/archives/2004/05/09/file-name-warning/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.intelliot.com/blog/archives/2004/05/09/file-name-warning/</link>
	<description>Thoughts, opinions and fascinating discoveries by Elliot, a student at USC</description>
	<pubDate>Sun, 06 Jul 2008 15:36:46 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>By: Scott</title>
		<link>http://www.intelliot.com/blog/archives/2004/05/09/file-name-warning/#comment-382112</link>
		<dc:creator>Scott</dc:creator>
		<pubDate>Fri, 11 Jan 2008 02:56:53 +0000</pubDate>
		<guid isPermaLink="false">http://www.intelliot.com/blog/archives/2004/05/09/file-name-warning/#comment-382112</guid>
		<description>Jah, it's a Windows bug when a call "%systemroot%\program files\anything" is made without the quotes.  There's tons of posts on the net about it.  It'll screw up all kinds of things and it's the devil to find it if the dialog box doesn't pop up.  For one thing it broke my file search function in explorer as long as the file was present on the system root.  I wrote a batch file that just deletes it and set Win.ini to activate the batch on boot.  You could do the same with a login script or whatever.  Problem solved.

Funny thing, there are a lot of posts about this but MICROSHAFT doesn't have a thing in the MS KB about it.  Not even the error dialog.</description>
		<content:encoded><![CDATA[<p>Jah, it&#8217;s a Windows bug when a call &#8220;%systemroot%\program files\anything&#8221; is made without the quotes.  There&#8217;s tons of posts on the net about it.  It&#8217;ll screw up all kinds of things and it&#8217;s the devil to find it if the dialog box doesn&#8217;t pop up.  For one thing it broke my file search function in explorer as long as the file was present on the system root.  I wrote a batch file that just deletes it and set Win.ini to activate the batch on boot.  You could do the same with a login script or whatever.  Problem solved.</p>
<p>Funny thing, there are a lot of posts about this but MICROSHAFT doesn&#8217;t have a thing in the MS KB about it.  Not even the error dialog.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Voidwalker68</title>
		<link>http://www.intelliot.com/blog/archives/2004/05/09/file-name-warning/#comment-318320</link>
		<dc:creator>Voidwalker68</dc:creator>
		<pubDate>Wed, 26 Sep 2007 08:17:01 +0000</pubDate>
		<guid isPermaLink="false">http://www.intelliot.com/blog/archives/2004/05/09/file-name-warning/#comment-318320</guid>
		<description>Got the same problem, file was created by an error dump from a demo I downloaded which terminally crashed so I assume itÂ´s only a Microsoft cleanup routine although as many has mentioned with a rather dodgy and non user friendly explaination. I checked the file content in Notepad and deleted the file. If youÂ´re unsure whatÂ´s in the file open it in Notepad and have a peek before deleting or renaming it.</description>
		<content:encoded><![CDATA[<p>Got the same problem, file was created by an error dump from a demo I downloaded which terminally crashed so I assume itÂ´s only a Microsoft cleanup routine although as many has mentioned with a rather dodgy and non user friendly explaination. I checked the file content in Notepad and deleted the file. If youÂ´re unsure whatÂ´s in the file open it in Notepad and have a peek before deleting or renaming it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Atraxen</title>
		<link>http://www.intelliot.com/blog/archives/2004/05/09/file-name-warning/#comment-314292</link>
		<dc:creator>Atraxen</dc:creator>
		<pubDate>Tue, 18 Sep 2007 19:54:42 +0000</pubDate>
		<guid isPermaLink="false">http://www.intelliot.com/blog/archives/2004/05/09/file-name-warning/#comment-314292</guid>
		<description>I had the same error.  Once I opened the file, I saw ASCII text that I recognized as being from a molecular modeling experiment I ran the day before.  I agree with the last few posts - the appearance of the "c:\program" file is due to sloppy command line use sticking something there.  This might explain why some people are reporting seeing it after installing a program, but also when they haven't (the program probably had a sloppy bit of scripting, or if you were working in a command prompt window, maybe you did.)  When I check the processID for the message box it's the same process as Explorer.exe - so yeah, it's some kind of Windows internal check...</description>
		<content:encoded><![CDATA[<p>I had the same error.  Once I opened the file, I saw ASCII text that I recognized as being from a molecular modeling experiment I ran the day before.  I agree with the last few posts - the appearance of the &#8220;c:\program&#8221; file is due to sloppy command line use sticking something there.  This might explain why some people are reporting seeing it after installing a program, but also when they haven&#8217;t (the program probably had a sloppy bit of scripting, or if you were working in a command prompt window, maybe you did.)  When I check the processID for the message box it&#8217;s the same process as Explorer.exe - so yeah, it&#8217;s some kind of Windows internal check&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dale</title>
		<link>http://www.intelliot.com/blog/archives/2004/05/09/file-name-warning/#comment-302481</link>
		<dc:creator>Dale</dc:creator>
		<pubDate>Thu, 23 Aug 2007 22:06:32 +0000</pubDate>
		<guid isPermaLink="false">http://www.intelliot.com/blog/archives/2004/05/09/file-name-warning/#comment-302481</guid>
		<description>Yep, the goof up is on Windows' part.  I'd run different softwares that are known to be safe over an extensive period of time with this message popping up occasionally.  One could view the "Program" file with any text editor and see that there is nothing important.  Just choose ignore (or rename, doesn't matter) and delete the file.</description>
		<content:encoded><![CDATA[<p>Yep, the goof up is on Windows&#8217; part.  I&#8217;d run different softwares that are known to be safe over an extensive period of time with this message popping up occasionally.  One could view the &#8220;Program&#8221; file with any text editor and see that there is nothing important.  Just choose ignore (or rename, doesn&#8217;t matter) and delete the file.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Windows Master</title>
		<link>http://www.intelliot.com/blog/archives/2004/05/09/file-name-warning/#comment-299022</link>
		<dc:creator>Windows Master</dc:creator>
		<pubDate>Thu, 09 Aug 2007 06:51:05 +0000</pubDate>
		<guid isPermaLink="false">http://www.intelliot.com/blog/archives/2004/05/09/file-name-warning/#comment-299022</guid>
		<description>This is nothing to be worried about. It is just accidental in more than one application installer and uninstaller out there. I am a programmer and I have had this happen during some of my tests. It is an issue when Windows does not  read a full path for creation correctly. Instead of making c:\program files\my application it can only see c:\program and so makes a file named just that. This happens when the services that control that function fail. Then on a reboot it comes up with that message. Any time this happens just delete the file and you will be fine. This can also happen when Windows itself needs to update a file or folder on boot up from c:\program files\whatever. If it tries to update something before the services for the function start then it will just create the file c:\program. YAY Microsoft for this little confusing mix up. :D

Have a nice day and switch to Linux.</description>
		<content:encoded><![CDATA[<p>This is nothing to be worried about. It is just accidental in more than one application installer and uninstaller out there. I am a programmer and I have had this happen during some of my tests. It is an issue when Windows does not  read a full path for creation correctly. Instead of making c:\program files\my application it can only see c:\program and so makes a file named just that. This happens when the services that control that function fail. Then on a reboot it comes up with that message. Any time this happens just delete the file and you will be fine. This can also happen when Windows itself needs to update a file or folder on boot up from c:\program files\whatever. If it tries to update something before the services for the function start then it will just create the file c:\program. YAY Microsoft for this little confusing mix up. <img src='http://www.intelliot.com/blog/wp-includes/images/smilies/icon_biggrin.gif' alt=':D' class='wp-smiley' /><br />
Have a nice day and switch to Linux.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bruce Meyer</title>
		<link>http://www.intelliot.com/blog/archives/2004/05/09/file-name-warning/#comment-292957</link>
		<dc:creator>Bruce Meyer</dc:creator>
		<pubDate>Sun, 15 Jul 2007 00:06:52 +0000</pubDate>
		<guid isPermaLink="false">http://www.intelliot.com/blog/archives/2004/05/09/file-name-warning/#comment-292957</guid>
		<description>I am running Vista Ultimate, all updates. I go to command prompt, and delte the file.
If I open a command prompt as normal user, it is not present. Every time I open command prompt as administrator the C:\Program is recreated.

I think it is from a install program for an app that isn't fully Vista complaint in my case,. I isntalled several older utils yesterday and had the warning of 'You may need to reinstall again, if you have problems with this odler application.'

Bruce</description>
		<content:encoded><![CDATA[<p>I am running Vista Ultimate, all updates. I go to command prompt, and delte the file.<br />
If I open a command prompt as normal user, it is not present. Every time I open command prompt as administrator the C:\Program is recreated.</p>
<p>I think it is from a install program for an app that isn&#8217;t fully Vista complaint in my case,. I isntalled several older utils yesterday and had the warning of &#8216;You may need to reinstall again, if you have problems with this odler application.&#8217;</p>
<p>Bruce</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nick</title>
		<link>http://www.intelliot.com/blog/archives/2004/05/09/file-name-warning/#comment-292953</link>
		<dc:creator>Nick</dc:creator>
		<pubDate>Sat, 14 Jul 2007 23:34:45 +0000</pubDate>
		<guid isPermaLink="false">http://www.intelliot.com/blog/archives/2004/05/09/file-name-warning/#comment-292953</guid>
		<description>Same as the others, I found this site when googling for this error msg.  I suspect it is the result of running applications through a CMD window, perhaps as part of the Scheduler.  The space in Program Files confuses the CMD window.

JKDefrag caused it for me by leaving a log file called c:\program.  I wonder if it was actually trying to leave a log in c:\program files\jkdefrag\log or similar.</description>
		<content:encoded><![CDATA[<p>Same as the others, I found this site when googling for this error msg.  I suspect it is the result of running applications through a CMD window, perhaps as part of the Scheduler.  The space in Program Files confuses the CMD window.</p>
<p>JKDefrag caused it for me by leaving a log file called c:\program.  I wonder if it was actually trying to leave a log in c:\program files\jkdefrag\log or similar.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Craig</title>
		<link>http://www.intelliot.com/blog/archives/2004/05/09/file-name-warning/#comment-286235</link>
		<dc:creator>Craig</dc:creator>
		<pubDate>Tue, 26 Jun 2007 14:23:37 +0000</pubDate>
		<guid isPermaLink="false">http://www.intelliot.com/blog/archives/2004/05/09/file-name-warning/#comment-286235</guid>
		<description>I've just been having the same problem since I started up this morning. I think it may have been to do with trying out several IRC scripts to find one that worked with my itunes. When my comp started, I got that error, and was asked to rename to program1. I did so. Second time I started up, it was the same but said program2. I ignored it and told it not to check again. The only other thing I noticed wrong was that my AIM wouldn't open, but I never use that anyway and uninstalled it. 

Deleted the "program" file and some of the IRC scripts I installed last night.</description>
		<content:encoded><![CDATA[<p>I&#8217;ve just been having the same problem since I started up this morning. I think it may have been to do with trying out several IRC scripts to find one that worked with my itunes. When my comp started, I got that error, and was asked to rename to program1. I did so. Second time I started up, it was the same but said program2. I ignored it and told it not to check again. The only other thing I noticed wrong was that my AIM wouldn&#8217;t open, but I never use that anyway and uninstalled it. </p>
<p>Deleted the &#8220;program&#8221; file and some of the IRC scripts I installed last night.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Peter</title>
		<link>http://www.intelliot.com/blog/archives/2004/05/09/file-name-warning/#comment-258235</link>
		<dc:creator>Peter</dc:creator>
		<pubDate>Tue, 05 Jun 2007 21:11:18 +0000</pubDate>
		<guid isPermaLink="false">http://www.intelliot.com/blog/archives/2004/05/09/file-name-warning/#comment-258235</guid>
		<description>Hi!
This same shit happened to me.. I didn't find any folder with that name either. And I startted to get error in Internet Explorer every time I changed the page. A day later I Serched for "program" on my system drive and found one file "Program" on the root with no file-ext and hidden. I removed it and all problems are gone.</description>
		<content:encoded><![CDATA[<p>Hi!<br />
This same shit happened to me.. I didn&#8217;t find any folder with that name either. And I startted to get error in Internet Explorer every time I changed the page. A day later I Serched for &#8220;program&#8221; on my system drive and found one file &#8220;Program&#8221; on the root with no file-ext and hidden. I removed it and all problems are gone.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Robin</title>
		<link>http://www.intelliot.com/blog/archives/2004/05/09/file-name-warning/#comment-254205</link>
		<dc:creator>Robin</dc:creator>
		<pubDate>Wed, 23 May 2007 20:14:53 +0000</pubDate>
		<guid isPermaLink="false">http://www.intelliot.com/blog/archives/2004/05/09/file-name-warning/#comment-254205</guid>
		<description>For those who can't see the file, check your folder options settings under - windows explorer\tools\folder options\view\hidden file and folders.  Might be a hidden file.</description>
		<content:encoded><![CDATA[<p>For those who can&#8217;t see the file, check your folder options settings under - windows explorer\tools\folder options\view\hidden file and folders.  Might be a hidden file.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
