<?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/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
	>

<channel>
	<title>All has it's own start line...</title>
	<atom:link href="http://cedoxs.wordpress.com/feed/" rel="self" type="application/rss+xml" />
	<link>http://cedoxs.wordpress.com</link>
	<description>Thee Who Starts Shall Yield</description>
	<lastBuildDate>Tue, 19 Apr 2011 12:53:30 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
<cloud domain='cedoxs.wordpress.com' port='80' path='/?rsscloud=notify' registerProcedure='' protocol='http-post' />
<image>
		<url>http://s2.wp.com/i/buttonw-com.png</url>
		<title>All has it's own start line...</title>
		<link>http://cedoxs.wordpress.com</link>
	</image>
	<atom:link rel="search" type="application/opensearchdescription+xml" href="http://cedoxs.wordpress.com/osd.xml" title="All has it&#039;s own start line..." />
	<atom:link rel='hub' href='http://cedoxs.wordpress.com/?pushpress=hub'/>
		<item>
		<title>Multithreading and Multicore Architectures</title>
		<link>http://cedoxs.wordpress.com/2006/12/21/multithreading-and-multicore-architectures/</link>
		<comments>http://cedoxs.wordpress.com/2006/12/21/multithreading-and-multicore-architectures/#comments</comments>
		<pubDate>Thu, 21 Dec 2006 07:52:27 +0000</pubDate>
		<dc:creator>cedoxs</dc:creator>
				<category><![CDATA[Computer Related]]></category>

		<guid isPermaLink="false">http://cedoxs.wordpress.com/2006/12/21/multithreading-and-multicore-architectures/</guid>
		<description><![CDATA[The present-day CPUs can usually house more than 31 instructions in the pipeline because some of them are taking parallel paths. That means more than one instruction per clock cycle is executed and you have a super scalar CPU. Doubling the clock speed gets you more than twice the number of instructions executed. Just combine [...]<img alt="" border="0" src="http://stats.wordpress.com/b.gif?host=cedoxs.wordpress.com&amp;blog=567839&amp;post=24&amp;subd=cedoxs&amp;ref=&amp;feed=1" width="1" height="1" />]]></description>
		<wfw:commentRss>http://cedoxs.wordpress.com/2006/12/21/multithreading-and-multicore-architectures/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
	
		<media:content url="http://1.gravatar.com/avatar/773c2b58dd4d373b604e4e90fa0b7610?s=96&#38;d=identicon&#38;r=G" medium="image">
			<media:title type="html">cedoxs</media:title>
		</media:content>
	</item>
		<item>
		<title>a Pipeline Story</title>
		<link>http://cedoxs.wordpress.com/2006/12/21/a-pipeline-story/</link>
		<comments>http://cedoxs.wordpress.com/2006/12/21/a-pipeline-story/#comments</comments>
		<pubDate>Thu, 21 Dec 2006 07:50:41 +0000</pubDate>
		<dc:creator>cedoxs</dc:creator>
				<category><![CDATA[Computer Related]]></category>

		<guid isPermaLink="false">http://cedoxs.wordpress.com/2006/12/21/a-pipeline-story/</guid>
		<description><![CDATA[The pipeline is one of those CPU fundamental features which enable several other very important speed-up schemes. Keep in mind that the pipeline architecture wasn&#8217;t introduced until 1989, so the previous CPUs had more “primitive” ways to deal with processing problems. CPUs have to get instructions and data out of the memory (read cycle) and [...]<img alt="" border="0" src="http://stats.wordpress.com/b.gif?host=cedoxs.wordpress.com&amp;blog=567839&amp;post=23&amp;subd=cedoxs&amp;ref=&amp;feed=1" width="1" height="1" />]]></description>
		<wfw:commentRss>http://cedoxs.wordpress.com/2006/12/21/a-pipeline-story/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
	
		<media:content url="http://1.gravatar.com/avatar/773c2b58dd4d373b604e4e90fa0b7610?s=96&#38;d=identicon&#38;r=G" medium="image">
			<media:title type="html">cedoxs</media:title>
		</media:content>
	</item>
		<item>
		<title>about RISC and CISC</title>
		<link>http://cedoxs.wordpress.com/2006/12/21/about-risc-and-cisc/</link>
		<comments>http://cedoxs.wordpress.com/2006/12/21/about-risc-and-cisc/#comments</comments>
		<pubDate>Thu, 21 Dec 2006 07:49:56 +0000</pubDate>
		<dc:creator>cedoxs</dc:creator>
				<category><![CDATA[Computer Related]]></category>
		<category><![CDATA[Tech Talk]]></category>

		<guid isPermaLink="false">http://cedoxs.wordpress.com/2006/12/21/about-risc-and-cisc/</guid>
		<description><![CDATA[Reduced Instruction Set Computer (RISC) CPUs were introduced by a series of companies that liked to keep the instruction sets very simple. This was due to the belief that the RISC architecture could make the microprocessor perform faster by incorporating many reduced instructions. Intel and AMD chose to stick to the CISC (Complex Instruction Set [...]<img alt="" border="0" src="http://stats.wordpress.com/b.gif?host=cedoxs.wordpress.com&amp;blog=567839&amp;post=22&amp;subd=cedoxs&amp;ref=&amp;feed=1" width="1" height="1" />]]></description>
		<wfw:commentRss>http://cedoxs.wordpress.com/2006/12/21/about-risc-and-cisc/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
	
		<media:content url="http://1.gravatar.com/avatar/773c2b58dd4d373b604e4e90fa0b7610?s=96&#38;d=identicon&#38;r=G" medium="image">
			<media:title type="html">cedoxs</media:title>
		</media:content>
	</item>
		<item>
		<title>In The Beginning, There Was MMX</title>
		<link>http://cedoxs.wordpress.com/2006/12/21/in-the-beginning-there-was-mmx/</link>
		<comments>http://cedoxs.wordpress.com/2006/12/21/in-the-beginning-there-was-mmx/#comments</comments>
		<pubDate>Thu, 21 Dec 2006 07:48:34 +0000</pubDate>
		<dc:creator>cedoxs</dc:creator>
				<category><![CDATA[Computer Related]]></category>
		<category><![CDATA[Tech Talk]]></category>

		<guid isPermaLink="false">http://cedoxs.wordpress.com/2006/12/21/in-the-beginning-there-was-mmx/</guid>
		<description><![CDATA[In 1997, Intel introduced their MMX feature with the Pentium II microprocessor. This is a trade name for Single Instruction, Multiple Data (SIMD) capability. The MMX special instruction set was primarily aimed at the emerging complex multimedia features. 3D graphics processing stormed the second half of the previous decade and Intel thought it was nice [...]<img alt="" border="0" src="http://stats.wordpress.com/b.gif?host=cedoxs.wordpress.com&amp;blog=567839&amp;post=21&amp;subd=cedoxs&amp;ref=&amp;feed=1" width="1" height="1" />]]></description>
		<wfw:commentRss>http://cedoxs.wordpress.com/2006/12/21/in-the-beginning-there-was-mmx/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
	
		<media:content url="http://1.gravatar.com/avatar/773c2b58dd4d373b604e4e90fa0b7610?s=96&#38;d=identicon&#38;r=G" medium="image">
			<media:title type="html">cedoxs</media:title>
		</media:content>
	</item>
		<item>
		<title>a Little Story About Multitasking</title>
		<link>http://cedoxs.wordpress.com/2006/12/21/a-little-story-about-multitasking/</link>
		<comments>http://cedoxs.wordpress.com/2006/12/21/a-little-story-about-multitasking/#comments</comments>
		<pubDate>Thu, 21 Dec 2006 07:46:12 +0000</pubDate>
		<dc:creator>cedoxs</dc:creator>
				<category><![CDATA[Computer Related]]></category>
		<category><![CDATA[Tech Talk]]></category>

		<guid isPermaLink="false">http://cedoxs.wordpress.com/2006/12/21/a-little-story-about-multitasking/</guid>
		<description><![CDATA[Intel&#8217;s 386 was the first CPU to feature hardware and special instructions that supported true multitasking. Nowadays, it is common to see several applications running simultaneously. But this is only an apparent thing, as no more than one program can be executed at any particular time. This is due to the blazing fast speeds of [...]<img alt="" border="0" src="http://stats.wordpress.com/b.gif?host=cedoxs.wordpress.com&amp;blog=567839&amp;post=20&amp;subd=cedoxs&amp;ref=&amp;feed=1" width="1" height="1" />]]></description>
		<wfw:commentRss>http://cedoxs.wordpress.com/2006/12/21/a-little-story-about-multitasking/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
	
		<media:content url="http://1.gravatar.com/avatar/773c2b58dd4d373b604e4e90fa0b7610?s=96&#38;d=identicon&#38;r=G" medium="image">
			<media:title type="html">cedoxs</media:title>
		</media:content>
	</item>
		<item>
		<title>CPU-Memory Interaction</title>
		<link>http://cedoxs.wordpress.com/2006/12/21/cpu-memory-interaction/</link>
		<comments>http://cedoxs.wordpress.com/2006/12/21/cpu-memory-interaction/#comments</comments>
		<pubDate>Thu, 21 Dec 2006 07:44:52 +0000</pubDate>
		<dc:creator>cedoxs</dc:creator>
				<category><![CDATA[Computer Related]]></category>
		<category><![CDATA[Tech Talk]]></category>

		<guid isPermaLink="false">http://cedoxs.wordpress.com/2006/12/21/cpu-memory-interaction/</guid>
		<description><![CDATA[We still haven&#8217;t figured out how the microprocessor can keep track of all that memory capacity that put your wallet in some difficulty. To answer that, we need to talk about some of the components of a microprocessor. It&#8217;s time to zoom in inside the CPU and start looking for those legendary monsters with dark [...]<img alt="" border="0" src="http://stats.wordpress.com/b.gif?host=cedoxs.wordpress.com&amp;blog=567839&amp;post=19&amp;subd=cedoxs&amp;ref=&amp;feed=1" width="1" height="1" />]]></description>
		<wfw:commentRss>http://cedoxs.wordpress.com/2006/12/21/cpu-memory-interaction/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
	
		<media:content url="http://1.gravatar.com/avatar/773c2b58dd4d373b604e4e90fa0b7610?s=96&#38;d=identicon&#38;r=G" medium="image">
			<media:title type="html">cedoxs</media:title>
		</media:content>
	</item>
		<item>
		<title>Inside a Motherboard</title>
		<link>http://cedoxs.wordpress.com/2006/12/21/inside-a-motherboard/</link>
		<comments>http://cedoxs.wordpress.com/2006/12/21/inside-a-motherboard/#comments</comments>
		<pubDate>Thu, 21 Dec 2006 03:57:15 +0000</pubDate>
		<dc:creator>cedoxs</dc:creator>
				<category><![CDATA[Computer Related]]></category>
		<category><![CDATA[Tech Talk]]></category>

		<guid isPermaLink="false">http://cedoxs.wordpress.com/2006/12/21/inside-a-motherboard/</guid>
		<description><![CDATA[Ever wonder what&#8217;s inside your motherboard?? Well, here we go: The motherboard&#8217;s primary goal is to house the computer&#8217;s CPU chip and grant every other component quick access to it. Everything you see in your computer is somehow connected to the motherboard. Motherboards also have a standard form factor, but I consider this a minor [...]<img alt="" border="0" src="http://stats.wordpress.com/b.gif?host=cedoxs.wordpress.com&amp;blog=567839&amp;post=18&amp;subd=cedoxs&amp;ref=&amp;feed=1" width="1" height="1" />]]></description>
		<wfw:commentRss>http://cedoxs.wordpress.com/2006/12/21/inside-a-motherboard/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
	
		<media:content url="http://1.gravatar.com/avatar/773c2b58dd4d373b604e4e90fa0b7610?s=96&#38;d=identicon&#38;r=G" medium="image">
			<media:title type="html">cedoxs</media:title>
		</media:content>
	</item>
		<item>
		<title>RapidShare Wait Limit Hack by Changing Proxy</title>
		<link>http://cedoxs.wordpress.com/2006/12/14/rapidshare-wait-limit-hack-by-changing-proxy/</link>
		<comments>http://cedoxs.wordpress.com/2006/12/14/rapidshare-wait-limit-hack-by-changing-proxy/#comments</comments>
		<pubDate>Thu, 14 Dec 2006 13:02:16 +0000</pubDate>
		<dc:creator>cedoxs</dc:creator>
				<category><![CDATA[Blogroll]]></category>

		<guid isPermaLink="false">http://cedoxs.wordpress.com/2006/12/14/rapidshare-wait-limit-hack-by-changing-proxy/</guid>
		<description><![CDATA[RapidShare also limit free users, based on their IP address, to certain download limit, and after reaching the limit, RapidShare will block your IP address. To overcome RapidShare download limit, since it’s based on IP address, the techniques to change or mask the IP address will come in useful to hack the RapidShare.There are several [...]<img alt="" border="0" src="http://stats.wordpress.com/b.gif?host=cedoxs.wordpress.com&amp;blog=567839&amp;post=16&amp;subd=cedoxs&amp;ref=&amp;feed=1" width="1" height="1" />]]></description>
		<wfw:commentRss>http://cedoxs.wordpress.com/2006/12/14/rapidshare-wait-limit-hack-by-changing-proxy/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
	
		<media:content url="http://1.gravatar.com/avatar/773c2b58dd4d373b604e4e90fa0b7610?s=96&#38;d=identicon&#38;r=G" medium="image">
			<media:title type="html">cedoxs</media:title>
		</media:content>
	</item>
		<item>
		<title>Rapidshare Wait Limit Hack With Tix Now</title>
		<link>http://cedoxs.wordpress.com/2006/12/14/rapidshare-hack-with-tix-now/</link>
		<comments>http://cedoxs.wordpress.com/2006/12/14/rapidshare-hack-with-tix-now/#comments</comments>
		<pubDate>Thu, 14 Dec 2006 12:57:54 +0000</pubDate>
		<dc:creator>cedoxs</dc:creator>
				<category><![CDATA[Blogroll]]></category>

		<guid isPermaLink="false">http://cedoxs.wordpress.com/2006/12/14/rapidshare-hack-with-tix-now/</guid>
		<description><![CDATA[Does anyone know about Tix Now??? Well, Tix Now is a Mozilla Firefox extention that can cut down Rapidshare waiting time delay before download start. I myself using Tix Now to reduce the waiting time delay before download start for Free User. It usually reduce to 0.8 minute waiting time on each download. It said [...]<img alt="" border="0" src="http://stats.wordpress.com/b.gif?host=cedoxs.wordpress.com&amp;blog=567839&amp;post=15&amp;subd=cedoxs&amp;ref=&amp;feed=1" width="1" height="1" />]]></description>
		<wfw:commentRss>http://cedoxs.wordpress.com/2006/12/14/rapidshare-hack-with-tix-now/feed/</wfw:commentRss>
		<slash:comments>8</slash:comments>
	
		<media:content url="http://1.gravatar.com/avatar/773c2b58dd4d373b604e4e90fa0b7610?s=96&#38;d=identicon&#38;r=G" medium="image">
			<media:title type="html">cedoxs</media:title>
		</media:content>
	</item>
		<item>
		<title>Search Engine Positioning &#8211; SEO</title>
		<link>http://cedoxs.wordpress.com/2006/12/14/search-engine-positioning-seo/</link>
		<comments>http://cedoxs.wordpress.com/2006/12/14/search-engine-positioning-seo/#comments</comments>
		<pubDate>Thu, 14 Dec 2006 12:36:14 +0000</pubDate>
		<dc:creator>cedoxs</dc:creator>
				<category><![CDATA[SEO]]></category>

		<guid isPermaLink="false">http://cedoxs.wordpress.com/2006/12/14/search-engine-positioning-seo/</guid>
		<description><![CDATA[How about getting your site from page five to page one in Google? Here are a few tips to boost you on your way. 1. Clean Up Your HTML Neat up your html and wrap it up. Dreamweaver adds lots of extra blank space to HTML code, and breaks lines. This is especially irritating in [...]<img alt="" border="0" src="http://stats.wordpress.com/b.gif?host=cedoxs.wordpress.com&amp;blog=567839&amp;post=14&amp;subd=cedoxs&amp;ref=&amp;feed=1" width="1" height="1" />]]></description>
		<wfw:commentRss>http://cedoxs.wordpress.com/2006/12/14/search-engine-positioning-seo/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
	
		<media:content url="http://1.gravatar.com/avatar/773c2b58dd4d373b604e4e90fa0b7610?s=96&#38;d=identicon&#38;r=G" medium="image">
			<media:title type="html">cedoxs</media:title>
		</media:content>
	</item>
	</channel>
</rss>
