<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>. ..::Hyn172.info::..  .  Nguyễn Hồng Hải &#187; hp firebird</title>
	<atom:link href="http://nguyenhonghai.com/tag/hp-firebird/feed/" rel="self" type="application/rss+xml" />
	<link>http://nguyenhonghai.com</link>
	<description></description>
	<lastBuildDate>Sat, 11 Jun 2011 19:49:11 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1.1</generator>
		<item>
		<title>About HP Firebird 803 with VoodooDNA in Cnet !</title>
		<link>http://nguyenhonghai.com/2009/02/22/about-hp-firebird-803-with-voodoodna-in-cnet/</link>
		<comments>http://nguyenhonghai.com/2009/02/22/about-hp-firebird-803-with-voodoodna-in-cnet/#comments</comments>
		<pubDate>Sun, 22 Feb 2009 02:01:22 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Computer]]></category>
		<category><![CDATA[Experience]]></category>
		<category><![CDATA[cnet]]></category>
		<category><![CDATA[hp firebird]]></category>

		<guid isPermaLink="false">http://nguyenhonghai.com/?p=132</guid>
		<description><![CDATA[Hôm nay tự hứng lên coi giới thiệu sản phẩm HP firebird 803 trên Cnet tự dưng thấy Hard drives của cấu hình chung mỗi nơi một kiểu . Sock hơn khi đĩa cứng chỉ có 4GB bên specifications trong khi bên review là 320GB khi so sánh HP firebird 803 với Dell XPS 625 [...]]]></description>
		<wfw:commentRss>http://nguyenhonghai.com/2009/02/22/about-hp-firebird-803-with-voodoodna-in-cnet/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
<!-- WP Super Cache is installed but broken. The path to wp-cache-phase1.php in wp-content/advanced-cache.php must be fixed! -->
