<?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 for ping</title>
	<atom:link href="http://ping.graabek.com/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://ping.graabek.com</link>
	<description>digital home life</description>
	<lastBuildDate>Thu, 22 Oct 2009 14:38:58 +0100</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.6</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>Comment on Netgear lies! 802.11n will (probably) not give you higher speed and better coverage by Eric Duncan</title>
		<link>http://ping.graabek.com/2009/10/09/netgear-lies-802-11n-will-probably-not-give-you-higher-speed-and-better-coverage/comment-page-1/#comment-176</link>
		<dc:creator>Eric Duncan</dc:creator>
		<pubDate>Thu, 22 Oct 2009 14:38:58 +0000</pubDate>
		<guid isPermaLink="false">http://ping.graabek.com/?p=31#comment-176</guid>
		<description>Yes, I completely agree with the fustration 802.11n has caused me and my friends.  I was a big fan of 802.11a waay back in the day for it&#039;s 5.8Ghz range, but it was too costly for home consumers.  And when the 2.4Ghz spectrum was expanded to include all other consumer devices that wanted to go wireless, it killed any chance of us having a solid connection wirelessly.

I also believe that the 802.11n standard is a big cheat as well.  When it was first drafted, it was only suppose to be 5.8Ghz and I praised that decision!  But, the commitee bent to the pressure of the industry that it would be too costly for consumers to upgrade their 802.11g networks - the same issue why 802.11a did not take off.  So, the commitee decided to write in the backwards compatibility for 2.4Ghz devices over the existing specs - and call it Draft 1.1, and now hardened in Draft 2.0 of 802.11n.

What gets me is, the Draft 2.0 specs calls for the entire &quot;default&quot; setup to default to 2.4Ghz.  This is the worse mistake they could have written into the specifications.

Only when all of the planets align, the stars pulsate in unison, and peace on Earth is accepted is when your two matching wireless devices and firmware &quot;may&quot; decide to switch up to 5.8Ghz - only to fall back to 2.4Ghz when there is any blocking.</description>
		<content:encoded><![CDATA[<p>Yes, I completely agree with the fustration 802.11n has caused me and my friends.  I was a big fan of 802.11a waay back in the day for it&#8217;s 5.8Ghz range, but it was too costly for home consumers.  And when the 2.4Ghz spectrum was expanded to include all other consumer devices that wanted to go wireless, it killed any chance of us having a solid connection wirelessly.</p>
<p>I also believe that the 802.11n standard is a big cheat as well.  When it was first drafted, it was only suppose to be 5.8Ghz and I praised that decision!  But, the commitee bent to the pressure of the industry that it would be too costly for consumers to upgrade their 802.11g networks &#8211; the same issue why 802.11a did not take off.  So, the commitee decided to write in the backwards compatibility for 2.4Ghz devices over the existing specs &#8211; and call it Draft 1.1, and now hardened in Draft 2.0 of 802.11n.</p>
<p>What gets me is, the Draft 2.0 specs calls for the entire &#8220;default&#8221; setup to default to 2.4Ghz.  This is the worse mistake they could have written into the specifications.</p>
<p>Only when all of the planets align, the stars pulsate in unison, and peace on Earth is accepted is when your two matching wireless devices and firmware &#8220;may&#8221; decide to switch up to 5.8Ghz &#8211; only to fall back to 2.4Ghz when there is any blocking.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on The Sagem PVR 6280T has left the building by Sagem</title>
		<link>http://ping.graabek.com/2008/03/03/the-sagem-pvr-6280t-has-left-the-building/comment-page-1/#comment-27</link>
		<dc:creator>Sagem</dc:creator>
		<pubDate>Mon, 07 Apr 2008 15:15:58 +0000</pubDate>
		<guid isPermaLink="false">http://ping.graabek.com/2008/03/03/the-sagem-pvr-6280t-has-left-the-building/#comment-27</guid>
		<description>I disliked this HD, too expensive for my tastes</description>
		<content:encoded><![CDATA[<p>I disliked this HD, too expensive for my tastes</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on D-Link DSM-320 Media Player by Jaak Ennuste</title>
		<link>http://ping.graabek.com/2007/01/20/d-link-dsm-320-media-player/comment-page-1/#comment-7</link>
		<dc:creator>Jaak Ennuste</dc:creator>
		<pubDate>Mon, 05 Feb 2007 06:39:16 +0000</pubDate>
		<guid isPermaLink="false">http://ping.graabek.com/1969/12/31/d-link-dsm-320-media-player/#comment-7</guid>
		<description>Very good and easy to understand piece! I have also used DSM-329 about a year, tried severan media servers and also ended up with TwonkyMedia. I&#039;m missing few things from 320, to be implemented in upcoming models:
- HD component output for GUI, photos and videos 
- better performance with MPEG4 files
- stability, playing VOB (mpeg 2) files
- fast forward/backward in videos
- album art

more about my home media server and projects: http://jacksgadgets.blogspot.com/</description>
		<content:encoded><![CDATA[<p>Very good and easy to understand piece! I have also used DSM-329 about a year, tried severan media servers and also ended up with TwonkyMedia. I&#8217;m missing few things from 320, to be implemented in upcoming models:<br />
- HD component output for GUI, photos and videos<br />
- better performance with MPEG4 files<br />
- stability, playing VOB (mpeg 2) files<br />
- fast forward/backward in videos<br />
- album art</p>
<p>more about my home media server and projects: <a href="http://jacksgadgets.blogspot.com/" rel="nofollow">http://jacksgadgets.blogspot.com/</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>
