<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/css" href="/stylesheets/rss.css"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:trackback="http://madskills.com/public/xml/rss/module/trackback/">
  <channel>
    <title>ROOL News: Latest news: IYONIX pc 2012 date problem</title>
    <link>/news/articles/2010/01/05/iyonix-pc-2012-date-problem</link>
    <language>en-us</language>
    <ttl>40</ttl>
    <description>Recent developments</description>
    <item>
      <title>IYONIX pc 2012 date problem</title>
      <description>&lt;p&gt;Many of you will be aware of a bug in the handling of a year counter in the &lt;span class="caps"&gt;IYONIX&lt;/span&gt; pc which means that the date on some machines changes to 2012 when they are booted. This is a software problem and a number of work-arounds already exist.&lt;/p&gt;


	&lt;p&gt;However, Castle Technology feel that this is a sufficiently severe fault to justify starting work on the next official release of &lt;span class="caps"&gt;RISC OS 5&lt;/span&gt; for the &lt;span class="caps"&gt;IYONIX&lt;/span&gt; pc &amp;#8211; &lt;span class="caps"&gt;RISC OS 5&lt;/span&gt;.15.&lt;/p&gt;


	&lt;p&gt;The latest version will not only address the date problem mentioned above, but will include many of the changes and improvements implemented since &lt;span class="caps"&gt;RISC OS 5&lt;/span&gt;.14 was released back in April 2009. Once it is available, users should program the new release into their machines using a supplied flash programmer to ensure that the date bugfix is correctly installed.&lt;/p&gt;


	&lt;p&gt;Keep an eye on the &lt;span class="caps"&gt;RISC OS&lt;/span&gt; Open web site over the next week or two for further news on the testing and release process.&lt;/p&gt;


	&lt;p&gt;Note to developers: the development version of &lt;span class="caps"&gt;RISC OS&lt;/span&gt; will move to 5.16 (beta) as soon as the new official version is released.&lt;/p&gt;</description>
      <pubDate>Tue, 05 Jan 2010 01:22:00 +0000</pubDate>
      <guid isPermaLink="false">urn:uuid:36eb54c6-17b0-4369-8f79-e28d26a8f3a5</guid>
      <author>Steve Revill</author>
      <link>/news/articles/2010/01/05/iyonix-pc-2012-date-problem</link>
      <category>New product</category>
      <category>Community</category>
    </item>
    <item>
      <title>"IYONIX pc 2012 date problem" by Rik Griffin (98)</title>
      <description>&lt;p&gt;Right, sorry about that, I&amp;#8217;ll RTFM next time :)&lt;/p&gt;</description>
      <pubDate>Mon, 08 Feb 2010 14:21:39 +0000</pubDate>
      <guid isPermaLink="false">urn:uuid:ff0cfdbb-e8f7-4441-a5cc-ba7e675b2ff3</guid>
      <link>/news/articles/2010/01/05/iyonix-pc-2012-date-problem#comment-67</link>
    </item>
    <item>
      <title>"IYONIX pc 2012 date problem" by Andrew Hodgkinson (6)</title>
      <description>&lt;p&gt;It seems it wasn&amp;#8217;t made clear from the original press release but it is vital that you &lt;strong&gt;flash the ROM&lt;/strong&gt; to get the clock fix. Otherwise your old ROM boots, screws up the clock, then loads the new ROM, which by now only has the invalid clock data to go on. The result is the time ends up even &lt;em&gt;more&lt;/em&gt; distant from the correct value.&lt;/p&gt;


	&lt;p&gt;Rob&amp;#8217;s already moaned at us about the ambiguity &lt;code&gt;:-)&lt;/code&gt;&lt;/p&gt;


	&lt;p&gt;&lt;a href="https://www.riscosopen.org/forum/forums/2/topics/316" rel="nofollow"&gt;https://www.riscosopen.org/forum/forums/2/topics/316&lt;/a&gt;&lt;/p&gt;</description>
      <pubDate>Mon, 08 Feb 2010 10:34:23 +0000</pubDate>
      <guid isPermaLink="false">urn:uuid:3e4cbab5-0bdd-40e6-9c81-eb430f88150e</guid>
      <link>/news/articles/2010/01/05/iyonix-pc-2012-date-problem#comment-65</link>
    </item>
    <item>
      <title>"IYONIX pc 2012 date problem" by Rik Griffin (98)</title>
      <description>&lt;p&gt;Is it possible that there&amp;#8217;s still a problem with the RTC in 5.16? I&amp;#8217;m running 5.16 (softloaded) and this morning the Iyonix thought the year was 2110, until the Nettime module corrected it.&lt;/p&gt;</description>
      <pubDate>Mon, 08 Feb 2010 10:24:46 +0000</pubDate>
      <guid isPermaLink="false">urn:uuid:f368a6a1-a5ce-424d-b795-c36d315b7715</guid>
      <link>/news/articles/2010/01/05/iyonix-pc-2012-date-problem#comment-64</link>
    </item>
    <item>
      <title>"IYONIX pc 2012 date problem" by Steve Revill (20)</title>
      <description>&lt;p&gt;No word from Castle yet on branding.&lt;/p&gt;


	&lt;p&gt;Please note: the official release we are about to make will be 5.16. All development builds will then be version 5.17, until the following official release &amp;#8211; 5.18, and so on.&lt;/p&gt;


	&lt;p&gt;So: odd numbered versions are development and even numbers are official, tested releases.&lt;/p&gt;</description>
      <pubDate>Thu, 21 Jan 2010 19:05:05 +0000</pubDate>
      <guid isPermaLink="false">urn:uuid:53801fbe-c051-4d19-850d-4710208d6988</guid>
      <link>/news/articles/2010/01/05/iyonix-pc-2012-date-problem#comment-62</link>
    </item>
    <item>
      <title>"IYONIX pc 2012 date problem" by Michael Drake (88)</title>
      <description>&lt;p&gt;Was there any word from Castle Technology on whether we can alter the branding of ROOL ROM releases, as per &lt;a href="http://www.riscosopen.org/forum/forums/2/topics/209" rel="nofollow"&gt;http://www.riscosopen.org/forum/forums/2/topics/209&lt;/a&gt; ?&lt;/p&gt;</description>
      <pubDate>Thu, 14 Jan 2010 09:11:19 +0000</pubDate>
      <guid isPermaLink="false">urn:uuid:8345b868-c0a3-4063-b196-d5797664b881</guid>
      <link>/news/articles/2010/01/05/iyonix-pc-2012-date-problem#comment-61</link>
    </item>
    <item>
      <title>"IYONIX pc 2012 date problem" by Steve Revill (20)</title>
      <description>&lt;p&gt;5.15 shouldn&amp;#8217;t need the CMOS reset but if you have any problems, it&amp;#8217;s a good thing to try first. Of course, when you do that, you&amp;#8217;ll need to set the time and date! :)&lt;/p&gt;</description>
      <pubDate>Wed, 06 Jan 2010 13:25:08 +0000</pubDate>
      <guid isPermaLink="false">urn:uuid:02d6e831-d0d6-494a-9ecc-820d6ac8cbe5</guid>
      <link>/news/articles/2010/01/05/iyonix-pc-2012-date-problem#comment-60</link>
    </item>
    <item>
      <title>"IYONIX pc 2012 date problem" by Andrew Hodgkinson (6)</title>
      <description>&lt;p&gt;Jumping straight to 5.15 should be fine. I&amp;#8217;m sure Steve or Ben will correct me if I&amp;#8217;m wrong, but I think it would be wise to do a CMOS reset after the upgrade &amp;#8211; hold down Delete before powering on and wait until the start-up beep before releasing it.&lt;/p&gt;


	&lt;p&gt;I upgraded from 5.11 to 5.14 without trouble and didn&amp;#8217;t do a CMOS reset, but it&amp;#8217;s possible that modules have moved around a bit in 5.15 which could invalidate the unplugged module list. Doing a reset plays it safe.&lt;/p&gt;</description>
      <pubDate>Tue, 05 Jan 2010 20:15:34 +0000</pubDate>
      <guid isPermaLink="false">urn:uuid:0a423b0a-33a4-4b83-80a2-d69b56074a93</guid>
      <link>/news/articles/2010/01/05/iyonix-pc-2012-date-problem#comment-59</link>
    </item>
    <item>
      <title>"IYONIX pc 2012 date problem" by George T. Greenfield (154)</title>
      <description>&lt;p&gt;I&amp;#8217;m still running 5.13: will I need to upgrade to 5.14 before upgrading to 5.15 (once it is formally released) or will it be possible to jump straight to 5.15?&lt;/p&gt;</description>
      <pubDate>Tue, 05 Jan 2010 19:00:21 +0000</pubDate>
      <guid isPermaLink="false">urn:uuid:081993fe-ece0-4397-84e8-78cc11df78f8</guid>
      <link>/news/articles/2010/01/05/iyonix-pc-2012-date-problem#comment-57</link>
    </item>
  </channel>
</rss>
