RISC OS 5 ROM image on ROOL site
Steve (ROOL)
Just to prove the progress we've been making in the source code publishing
process, we've put a RISC OS 5 ROM image onto our site for you to download
and play with. This is not complete or tested so reflashing your IYONIX with
it would be highly likely to brick your machine. The ROM image has been
built using only published sources and our BBE.
More information, along with the image itself can be found here:
http://www.riscosopen.org/content/downloads/other-zipfiles
Steve
--
Stephen Revill, Director Tel: +44 (0) 1353 740 267
RISC OS Open Ltd www.riscosopen.org
4 Townsend Mews, Wilburton,
Ely, Cambridgeshire, CB6 3SQ
David Given
[...]
> Just to prove the progress we've been making in the source code publishing
> process, we've put a RISC OS 5 ROM image onto our site for you to download
> and play with. This is not complete or tested so reflashing your IYONIX with
> it would be highly likely to brick your machine. The ROM image has been
> built using only published sources and our BBE.
Excellent news!
Is this able to be run on anything (including emulation platforms), or
is it simply a test run of the build system? I notice that the codename
seems to be Tungsten --- is this related to the Palm Tungsten?
--
David Given
d...@cowlark.com
Doug
>
> Excellent news!
>
> Is this able to be run on anything (including emulation platforms), or
> is it simply a test run of the build system? I notice that the codename
> seems to be Tungsten --- is this related to the Palm Tungsten?
>
No not Palm related but Tungsten was the name of the underlying product
that became the Iyonix AFAIR.
Doug
Ste (news)
Doug <doug....@btinternet.com> wrote:
> David Given wrote:
> > Excellent news!
> >
> > Is this able to be run on anything (including emulation platforms), or
> > is it simply a test run of the build system?
It's basically a test of the build system by taking the real IYONIX ROM
build and seeing just how much of it we can build using only published
sources - so it's also a test of what we've published vs what's left.
It won't run on an emulator unless that were to emulate the IYONIX hardware
(e.g. RPCemu emulates a RiscPC not an IYONIX).
We are about to release the source code to the Softload utility which can be
used to softload a ROM image. This was written for the RiscPC during the
development of Ursula (RISC OS 4) so that we could softload the OS to test
it without requiring the RiscPC II hardware (Phoebe).
So, if some brave soul were to take the softloader as it stands and modify
it such that you can softload onto an IYONIX, you would be able to test the
ROOL ROM by softloading there without risking bricking the machine.
> > I notice that the codename seems to be Tungsten --- is this related to
> > the Palm Tungsten?
>
> No not Palm related but Tungsten was the name of the underlying product
> that became the Iyonix AFAIR.
Correct, have a look at:
http://www.riscosopen.org/wiki/documentation/pages/Acorn+Project+Codenames
Steve
--
Steve Revill @ Home
Note: All opinions expressed herein are my own.
James Lampard
> In article <W9CdnbCEH9xo6ZrUnZ2dnUVZ8sLin...@bt.com>,
> Doug <doug.j.w...@btinternet.com> wrote:
[snip]
>
> We are about to release the source code to the Softload utility which can be
> used to softload a ROM image. This was written for the RiscPC during the
> development of Ursula (RISC OS 4) so that we could softload the OS to test
> it without requiring the RiscPC II hardware (Phoebe).
>
[snip]
I thought it already had been released, see
http://www.riscosopen.org/viewer/view/castle/RiscOS/Utilities/Debugging/SoftLoad/
I've definitely seen it already in the tarballs (and built it).
It has an unusual location being in RiscOS.Utilities instead of
RiscOS.Source.
--
James.
To reply use james underline lampard at talk 21 dot com
Ste (news)
<826eb090-7272-440c...@s9g2000prg.googlegroups.com>,
James Lampard <dontrep...@mailinator.com> wrote:
> I thought it already had been released, see
> http://www.riscosopen.org/viewer/view/castle/RiscOS/Utilities/Debugging/SoftLoad/
>
> I've definitely seen it already in the tarballs (and built it). It has an
> unusual location being in RiscOS.Utilities instead of RiscOS.Source.
So it has. That's one less job on my To Do list then :)
Stewart Brodie
That'll be because it's a utility and not part of the OS source. :)
--
Stewart Brodie
James Lampard
> James Lampard <dontreplytot...@mailinator.com> wrote:
[snip]
> > I've definitely seen it already in the tarballs (and built it).
> > It has an unusual location being in RiscOS.Utilities instead of
> > RiscOS.Source.
>
> That'll be because it's a utility and not part of the OS source. :)
Yes but Browse is under RiscOS.Sources, and I wouldn't describe it as
being part of the OS sources.
As a program to load the OS, sotfload has a much greater claim to 'be
part of the OS source' than Browse.
All the other RiscOS.* directories are stuff to do with the build
environment. RiscOS.Utilities is still a weird place to put sources.