<?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/"
		>
<channel>
	<title>Comments on: PowerShell Functions and Filters &#8211; The basics</title>
	<atom:link href="http://www.powershellpro.com/powershell-tutorial-introduction/powershell-functions-filters/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.powershellpro.com</link>
	<description>Sharing the Experience</description>
	<lastBuildDate>Fri, 03 Feb 2012 08:09:32 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: garryman</title>
		<link>http://www.powershellpro.com/powershell-tutorial-introduction/powershell-functions-filters/comment-page-1/#comment-683</link>
		<dc:creator>garryman</dc:creator>
		<pubDate>Sun, 04 Sep 2011 05:05:51 +0000</pubDate>
		<guid isPermaLink="false">http://www.powershellpro.com/powershell-tutorial-introduction/powershell-functions-filters/#comment-683</guid>
		<description>OK..For anybody else having the prob that I was having...I was initially using a single quote(&#039;) instead of a tick(`). But, after inserting the correct tick, I had to erase and re-insert the previous double-quotes(&quot;) before it would work..Now....moving on!!!</description>
		<content:encoded><![CDATA[<p>OK..For anybody else having the prob that I was having&#8230;I was initially using a single quote(&#8216;) instead of a tick(`). But, after inserting the correct tick, I had to erase and re-insert the previous double-quotes(&#8220;) before it would work..Now&#8230;.moving on!!!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: garryman</title>
		<link>http://www.powershellpro.com/powershell-tutorial-introduction/powershell-functions-filters/comment-page-1/#comment-682</link>
		<dc:creator>garryman</dc:creator>
		<pubDate>Sun, 04 Sep 2011 02:41:55 +0000</pubDate>
		<guid isPermaLink="false">http://www.powershellpro.com/powershell-tutorial-introduction/powershell-functions-filters/#comment-682</guid>
		<description>Notice how, when I copy and paste the $colItems line, that a (?)  is shown instead of the closing (&quot;). Odd.</description>
		<content:encoded><![CDATA[<p>Notice how, when I copy and paste the $colItems line, that a (?)  is shown instead of the closing (&#8220;). Odd.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: garryman</title>
		<link>http://www.powershellpro.com/powershell-tutorial-introduction/powershell-functions-filters/comment-page-1/#comment-681</link>
		<dc:creator>garryman</dc:creator>
		<pubDate>Sun, 04 Sep 2011 02:33:09 +0000</pubDate>
		<guid isPermaLink="false">http://www.powershellpro.com/powershell-tutorial-introduction/powershell-functions-filters/#comment-681</guid>
		<description>I am getting the same error as Wally S., however, I am running listDisk and listProcessor when the error appears. I tried moving
$colItems = get-wmiobject -class “Win32_DiskDrive” -namespace “root\CIMV2? `
-computername $strComputer
into a single line and removing the &quot; &#039; &quot;, cause that seemed to be causing a prob...but still, no dice....</description>
		<content:encoded><![CDATA[<p>I am getting the same error as Wally S., however, I am running listDisk and listProcessor when the error appears. I tried moving<br />
$colItems = get-wmiobject -class “Win32_DiskDrive” -namespace “root\CIMV2? `<br />
-computername $strComputer<br />
into a single line and removing the &#8221; &#8216; &#8220;, cause that seemed to be causing a prob&#8230;but still, no dice&#8230;.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Wally S.</title>
		<link>http://www.powershellpro.com/powershell-tutorial-introduction/powershell-functions-filters/comment-page-1/#comment-640</link>
		<dc:creator>Wally S.</dc:creator>
		<pubDate>Tue, 14 Jun 2011 18:57:43 +0000</pubDate>
		<guid isPermaLink="false">http://www.powershellpro.com/powershell-tutorial-introduction/powershell-functions-filters/#comment-640</guid>
		<description>I am working with the ListCPU script, and when I run it I get 

The string starting:
At C:\mytest\CPU.ps1:13 char:19
+ write-host &quot;Name:  &lt;&lt;&lt;&lt; &quot; $objItem.Name
is missing the terminator: &quot;.
At C:\mytest\CPU.ps1:19 char:1
+  &lt;&lt;&lt;&lt; 
    + CategoryInfo          : ParserError: ( $objItem.Name
write-host
}



:String) [], ParseException
    + FullyQualifiedErrorId : TerminatorExpectedAtEndOfString

as you can see It is coming back with what to me seems an ambiguous error.  If somebody got the script working, please help me.

Thanks in advance.</description>
		<content:encoded><![CDATA[<p>I am working with the ListCPU script, and when I run it I get </p>
<p>The string starting:<br />
At C:\mytest\CPU.ps1:13 char:19<br />
+ write-host &#8220;Name:  &lt;&lt;&lt;&lt; &quot; $objItem.Name<br />
is missing the terminator: &quot;.<br />
At C:\mytest\CPU.ps1:19 char:1<br />
+  &lt;&lt;&lt;&lt;<br />
    + CategoryInfo          : ParserError: ( $objItem.Name<br />
write-host<br />
}</p>
<p>:String) [], ParseException<br />
    + FullyQualifiedErrorId : TerminatorExpectedAtEndOfString</p>
<p>as you can see It is coming back with what to me seems an ambiguous error.  If somebody got the script working, please help me.</p>
<p>Thanks in advance.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bailey</title>
		<link>http://www.powershellpro.com/powershell-tutorial-introduction/powershell-functions-filters/comment-page-1/#comment-639</link>
		<dc:creator>Bailey</dc:creator>
		<pubDate>Tue, 14 Jun 2011 11:14:37 +0000</pubDate>
		<guid isPermaLink="false">http://www.powershellpro.com/powershell-tutorial-introduction/powershell-functions-filters/#comment-639</guid>
		<description>@Russ - Thanks, your solution did help me as I was having the same issue.</description>
		<content:encoded><![CDATA[<p>@Russ &#8211; Thanks, your solution did help me as I was having the same issue.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: huvanile</title>
		<link>http://www.powershellpro.com/powershell-tutorial-introduction/powershell-functions-filters/comment-page-1/#comment-638</link>
		<dc:creator>huvanile</dc:creator>
		<pubDate>Sat, 11 Jun 2011 17:37:31 +0000</pubDate>
		<guid isPermaLink="false">http://www.powershellpro.com/powershell-tutorial-introduction/powershell-functions-filters/#comment-638</guid>
		<description>@chris:  Yep.  At least, I was able to using the Powershell ISE.</description>
		<content:encoded><![CDATA[<p>@chris:  Yep.  At least, I was able to using the Powershell ISE.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: chris</title>
		<link>http://www.powershellpro.com/powershell-tutorial-introduction/powershell-functions-filters/comment-page-1/#comment-637</link>
		<dc:creator>chris</dc:creator>
		<pubDate>Fri, 10 Jun 2011 12:38:41 +0000</pubDate>
		<guid isPermaLink="false">http://www.powershellpro.com/powershell-tutorial-introduction/powershell-functions-filters/#comment-637</guid>
		<description>Can&#039;t I put functions at the end of the file instead of stating it up front?</description>
		<content:encoded><![CDATA[<p>Can&#8217;t I put functions at the end of the file instead of stating it up front?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Russ</title>
		<link>http://www.powershellpro.com/powershell-tutorial-introduction/powershell-functions-filters/comment-page-1/#comment-620</link>
		<dc:creator>Russ</dc:creator>
		<pubDate>Sun, 15 May 2011 13:01:44 +0000</pubDate>
		<guid isPermaLink="false">http://www.powershellpro.com/powershell-tutorial-introduction/powershell-functions-filters/#comment-620</guid>
		<description>Whoops!
I kept getting a error page when I tried to submit a comment. I didn&#039;t realize the comments where actually accepted despite the errors mentioned on the error page I was seeing, so I kept submitting variations of my comment.</description>
		<content:encoded><![CDATA[<p>Whoops!<br />
I kept getting a error page when I tried to submit a comment. I didn&#8217;t realize the comments where actually accepted despite the errors mentioned on the error page I was seeing, so I kept submitting variations of my comment.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Russ</title>
		<link>http://www.powershellpro.com/powershell-tutorial-introduction/powershell-functions-filters/comment-page-1/#comment-619</link>
		<dc:creator>Russ</dc:creator>
		<pubDate>Sun, 15 May 2011 12:54:13 +0000</pubDate>
		<guid isPermaLink="false">http://www.powershellpro.com/powershell-tutorial-introduction/powershell-functions-filters/#comment-619</guid>
		<description>I&#039;m reading this site with Safari on a Mac.

When I tried to copy and paste the ListDisk function or the ListProcessor function into a Powershell window on Parallels running Windows 7, I kept getting a double right angle bracket continuation prompt that wouldn&#039;t go away until I pressed Control C and the functions wouldn&#039;t be created.
I tracked it down to a double quote character following the quoted:&quot;root\CIMV2&quot;
That double quote character, which was different from the others, would not paste into the Powershell window and Powershell would keep expecting a ending-double-quote, and therefore repeatedly gave the double right angle bracket continuation prompt.
I post this, in case anyone else runs into similar problem and something like this may be the answer.</description>
		<content:encoded><![CDATA[<p>I&#8217;m reading this site with Safari on a Mac.</p>
<p>When I tried to copy and paste the ListDisk function or the ListProcessor function into a Powershell window on Parallels running Windows 7, I kept getting a double right angle bracket continuation prompt that wouldn&#8217;t go away until I pressed Control C and the functions wouldn&#8217;t be created.<br />
I tracked it down to a double quote character following the quoted:&#8221;root\CIMV2&#8243;<br />
That double quote character, which was different from the others, would not paste into the Powershell window and Powershell would keep expecting a ending-double-quote, and therefore repeatedly gave the double right angle bracket continuation prompt.<br />
I post this, in case anyone else runs into similar problem and something like this may be the answer.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Russ</title>
		<link>http://www.powershellpro.com/powershell-tutorial-introduction/powershell-functions-filters/comment-page-1/#comment-618</link>
		<dc:creator>Russ</dc:creator>
		<pubDate>Sun, 15 May 2011 12:53:25 +0000</pubDate>
		<guid isPermaLink="false">http://www.powershellpro.com/powershell-tutorial-introduction/powershell-functions-filters/#comment-618</guid>
		<description>I&#039;m reading this site with Safari on a Mac.

When I tried to copy and paste the ListDisk function or the ListProcessor function into a Powershell window on Parallels running Windows 7, I kept getting a double right angle bracket continuation prompt that wouldn&#039;t go away until I pressed Control C and the functions wouldn&#039;t be created.
I tracked it down to a double quote character following the quoted:&quot;root\CIMV2&quot; &lt;--&lt;&lt;
That double quote character, which was different from the others, would not paste into the Powershell window and Powershell would keep expecting a ending-double-quote, and therefore repeatedly gave the double right angle bracket continuation prompt.
I post this, in case anyone else runs into similar problem and something like this may be the answer.</description>
		<content:encoded><![CDATA[<p>I&#8217;m reading this site with Safari on a Mac.</p>
<p>When I tried to copy and paste the ListDisk function or the ListProcessor function into a Powershell window on Parallels running Windows 7, I kept getting a double right angle bracket continuation prompt that wouldn&#8217;t go away until I pressed Control C and the functions wouldn&#8217;t be created.<br />
I tracked it down to a double quote character following the quoted:&#8221;root\CIMV2&#8243; &lt;&#8211;&lt;&lt;<br />
That double quote character, which was different from the others, would not paste into the Powershell window and Powershell would keep expecting a ending-double-quote, and therefore repeatedly gave the double right angle bracket continuation prompt.<br />
I post this, in case anyone else runs into similar problem and something like this may be the answer.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

