<?xml version="1.0" encoding="UTF-8"?>
<!-- generator="FeedCreator 1.7.2" -->
<rss version="2.0">
	<channel>
		<title>Batch File %ProgramFiles(x86)% Parenthesis Anomaly</title>
		<description>Comments for Batch File %ProgramFiles(x86)% Parenthesis Anomaly at http://marsbox.com , comment 1 to 2 out of 2 comments</description>
		<link>http://marsbox.com</link>
		<lastBuildDate>Tue, 07 Sep 2010 13:02:36 +0100</lastBuildDate>
		<generator>FeedCreator 1.7.2</generator>
		<item>
			<title>...</title>
			<link>http://marsbox.com/blog/howtos/batch-file-programfiles-x86-parenthesis-anomaly/#comment-185</link>
			<description>Yeah I forget exactly why, but I couldn't use the brackets either. Maybe something to do with quotes. - Grant Brown</description>
			<pubDate>Wed, 16 Sep 2009 13:37:57 +0100</pubDate>
		</item>
		<item>
			<title>...</title>
			<link>http://marsbox.com/blog/howtos/batch-file-programfiles-x86-parenthesis-anomaly/#comment-181</link>
			<description>This works for me:

set _pf=&amp;#37;ProgramFiles&amp;#37;
if not &quot;[&amp;#37;ProgramFiles(x86)&amp;#37;]&quot;==&quot;[]&quot; set _pf=&amp;#37;ProgramFiles(x86)&amp;#37;
@start &quot;&quot; /b &quot;&amp;#37;_pf&amp;#37;SourceGearDiffMergeDiffMerge.exe&quot;

In general, I've learned to test for the existence of environment variables by bracketing them in both double quotes and square brackets.
 - George V. Reilly</description>
			<pubDate>Fri, 11 Sep 2009 18:55:24 +0100</pubDate>
		</item>
	</channel>
</rss>
