ROOL News: Latest news comments

"IYONIX pc 2012 date problem" by Rik Griffin (98)

Mon, 08 Feb 2010 14:21:39 +0000

Right, sorry about that, I’ll RTFM next time :)

"New IYONIX ROM release (version 5.16)" by Andrew Hodgkinson (6)

Mon, 08 Feb 2010 10:37:29 +0000

I’ve updated the article text to stress the importance of programming the ROM into Flash if you want to fix the 2010 date bug on your Iyonix.

"IYONIX pc 2012 date problem" by Andrew Hodgkinson (6)

Mon, 08 Feb 2010 10:34:23 +0000

It seems it wasn’t made clear from the original press release but it is vital that you flash the ROM 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 more distant from the correct value.

Rob’s already moaned at us about the ambiguity :-)

https://www.riscosopen.org/forum/forums/2/topics/316

"IYONIX pc 2012 date problem" by Rik Griffin (98)

Mon, 08 Feb 2010 10:24:46 +0000

Is it possible that there’s still a problem with the RTC in 5.16? I’m running 5.16 (softloaded) and this morning the Iyonix thought the year was 2110, until the Nettime module corrected it.

"New IYONIX ROM release (version 5.16)" by Steve Revill (20)

Sat, 23 Jan 2010 23:13:31 +0000

Here is a brief overview of the changes since the previous official ROM release, in plain English:

Alarm:

updated templates (including German translation) and tweak to avoid a known bug

Filer:

added -NoShift parameter to Filer_Run
added Filer_DClickHold command
can now sort objects in reverse order
updates to templates (including German translation)

FileCore:

minor performance improvement
various minor bugfixes

FileSwitch:

bug fix to SWI OS_File 5

DMAManager:

various fixes and improvements

FPEmulator:

fix significant bug #225

PCI:

no longer crashes on machines with no PCI bus

NetBSD:

miscellaneous improvements and bug fixes

Territory Manager:

corrected the notation in the timezone syntax message

Kernel:

fix error handling with sparse dynamic areas
fix bug in OS_SetVarVal for creating code variables
fixed RTC bug leading to incorrect dates (2012 rather than 2010)

SharedCLibrary:

bug fix to kernel.s.k_body

Unicode:

fix bugs and inconsistencies in encoding handlers
fix inconsistency in handling illegal byte sequences
convert surrogate codepoints and U+FFFE, U+FFFF to U+FFFD
added some extra mappings

LanManFS:

lots of bug fixes and significant improvements

PDumpers:

eliminated clash with 3rd party module that had an unallocated name

Debugger:

lots of improvements, including support for ARMv5TEJ / ARMv6 CPSR flags

ColourTrans:

performance improvement and bug fix

Draw:

bug fux #193
fix of pointer corruption in Draw_ProcessPath

Font Manager:

Font_EnumerateCharacters bug fix
now validates paths to *FontInstall and *FontRemove

SpriteExtend:

performance improvement (doesn’t thrash OS_CLI when plotting JPEGs)

"IYONIX pc 2012 date problem" by Steve Revill (20)

Thu, 21 Jan 2010 19:05:05 +0000

No word from Castle yet on branding.

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 – 5.18, and so on.

So: odd numbered versions are development and even numbers are official, tested releases.

"IYONIX pc 2012 date problem" by Michael Drake (88)

Thu, 14 Jan 2010 09:11:19 +0000

Was there any word from Castle Technology on whether we can alter the branding of ROOL ROM releases, as per http://www.riscosopen.org/forum/forums/2/topics/209 ?

"IYONIX pc 2012 date problem" by Steve Revill (20)

Wed, 06 Jan 2010 13:25:08 +0000

5.15 shouldn’t need the CMOS reset but if you have any problems, it’s a good thing to try first. Of course, when you do that, you’ll need to set the time and date! :)

"IYONIX pc 2012 date problem" by Andrew Hodgkinson (6)

Tue, 05 Jan 2010 20:15:34 +0000

Jumping straight to 5.15 should be fine. I’m sure Steve or Ben will correct me if I’m wrong, but I think it would be wise to do a CMOS reset after the upgrade – hold down Delete before powering on and wait until the start-up beep before releasing it.

I upgraded from 5.11 to 5.14 without trouble and didn’t do a CMOS reset, but it’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.

"Award for RISC OS port to Beagle Board" by timofonic (358)

Tue, 05 Jan 2010 19:54:26 +0000

What about a Pandora port?

I also posted this news on the Pandora forums of GP32X.

Award for Risc OS port to Beable Board at General Pandora forums at GP32X.