<?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>Jordan Hall &#187; PlayStation 3 leap year issue</title>
	<atom:link href="http://jordanhall.co.uk/tag/playstation-3-leap-year-issue/feed/" rel="self" type="application/rss+xml" />
	<link>http://jordanhall.co.uk</link>
	<description>Jordan Hall - programmer and geek</description>
	<lastBuildDate>Thu, 19 Jan 2012 11:36:06 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>PlayStation 3 2010 Leap Year Issue</title>
		<link>http://jordanhall.co.uk/general-articles/playstation-3-2010-leap-year-issue-0903601/</link>
		<comments>http://jordanhall.co.uk/general-articles/playstation-3-2010-leap-year-issue-0903601/#comments</comments>
		<pubDate>Thu, 04 Mar 2010 20:13:09 +0000</pubDate>
		<dc:creator>Jordan Hall</dc:creator>
				<category><![CDATA[General Articles]]></category>
		<category><![CDATA[leap year issues]]></category>
		<category><![CDATA[on-board clock]]></category>
		<category><![CDATA[PlayStation 3]]></category>
		<category><![CDATA[PlayStation 3 leap year issue]]></category>
		<category><![CDATA[PS3]]></category>
		<category><![CDATA[Sony]]></category>
		<category><![CDATA[system testing]]></category>
		<category><![CDATA[system updates]]></category>

		<guid isPermaLink="false">http://jordanhall.co.uk/?p=601</guid>
		<description><![CDATA[So, it turns out that the PlayStation 3 problem (or PlayStation 3 &#8216;blackout&#8217; as it has come to be known) on the 1st of March 2010 was resolved on the turn of midnight on the same day. To resolve this issue, it turns out Sony did&#8230; nothing. As assumed by many PlayStation 3 users, the [...]]]></description>
			<content:encoded><![CDATA[<p>So, it turns out that the <a href="http://jordanhall.co.uk/tag/playstation-3/">PlayStation 3</a> problem (or <a href="http://www.cad-comic.com/cad/20100303">PlayStation 3 &#8216;blackout&#8217;</a> as it has come to be known) on the 1st of March 2010 was <a href="http://blog.us.playstation.com/2010/03/playstation-network-service-restored/">resolved on the turn of midnight on the same day</a>. To resolve this issue, it turns out <a href="http://jordanhall.co.uk/tag/sony/">Sony</a> did&#8230; nothing.</p>
<p>As assumed by many PlayStation 3 users, the issue was not related to the PlayStation Network but was, in fact, an issue with the hardware in the (non-slim) PlayStation 3 models. The on-board clock on the PlayStation 3 assumed the date on the 1st of March was in fact, the non-existant 29th of February. At the same time, the operating system clock believed the date was, as it actually was, the 1st of March.</p>
<p>We can assume Sony believed the best option was to merely await this automatic &#8216;fix&#8217; that occured at midnight, rather than to develop, test and release an emergency update to all old model PlayStation 3 models. This is most likely due to a strict policy on testing such system updates. This choice to delay may be looked at as a bad action by some people, however imagine the dangerous alternative. If Sony were to have released a rushed update to all old PlayStation 3 models&#8230; and it bricked the consoles (i.e. made them inoperable) &#8211; imagine the up roar then?</p>
<p>What do you think Sony should have done?</p>
<p>Frankly, I think they should have been more thorough in the initial testing of the PlayStation 3 components, such as, perhaps, the on-board clock&#8230;</p>
]]></content:encoded>
			<wfw:commentRss>http://jordanhall.co.uk/general-articles/playstation-3-2010-leap-year-issue-0903601/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

