Drobe :: The archives
About Drobe | Contact | RSS | Twitter | Webspace | Tech docs | Downloads | BBC Micro

Profile for riscosopen

ContactAbout me
Email:
info@riscosopen.org
ICQ:
AOL:
Yahoo:
Username: riscosopen
Realname: Steve Revill
About me:
Homepage: http://www.riscosopen.org/
Face/Logo:
Comments posted:74 (show all)

All comments

On RISC OS Open seeks rep for Acorn World event:

Hi. Here's where we at ROOL are: we fully intended to attend and do an informal talk/presentation plus some Q&A about the shared source project.

Since that time, one of our guys is in the process of moving to New Zealand and has to go over there for a month as part of that process - which we didn't have a date for when we booked the talk.

I'm having to attend something for my day job in Holland, so I've had to pull out.

Leaving our one remaining guy to do the talk. Except he has a close family member who has become seriously ill so he can't go either.

So it's not because we don't want to go, or because we don't think there's enough market or because we're so dumb we booked something we couldn't attend!

We really want to have some contemporary RISC OS presence at this show to illustrate that the sum total of Acorn-related contributions to the world of home computing doesn't start and end in the BBC era.

 is a RISC OS Userriscosopen on 1/9/09 1:07PM
[ Reply | Permalink | Report ]

On Five tips for ROL over the next five years:

That's something of an exaggeration - most things will still work perfectly well. After all, there hasn't been a vast amount of development in either branch in terms of updating existing modules and only a fraction of that development will have been divergent to such an extent as to cause failure.

However, the main problem is in all of those odd little edge cases. ROL would be mad to endorse a pick-and-mix solution because where would their support obligation to the user end?

And as the ROOL staff work for free, our support position would be no different to today: you get what you're given.

 is a RISC OS Userriscosopen on 4/6/09 8:53PM
[ Reply | Permalink | Report ]

On Five tips for ROL over the next five years:

> One way to achieve this would be to ensure Open and Select always have similar enough internal structure so that a pick and mix approach could be used.

Shudder. Support nightmare!!

 is a RISC OS Userriscosopen on 3/6/09 5:13PM
[ Reply | Permalink | Report ]

On Five tips for ROL over the next five years:

and TemplEd was replaced by the much improved WinEd.

 is a RISC OS Userriscosopen on 31/5/09 12:08AM
[ Reply | Permalink | Report ]

On First screenshot: Beagleboard runs RISC OS 5 desktop:

Did you see my comment about 15 mins ago?

 is a RISC OS Userriscosopen on 18/5/09 8:34PM
[ Reply | Permalink | Report ]

On First screenshot: Beagleboard runs RISC OS 5 desktop:

We just did a couple of very simple tests to compare an Iyonix against a RevB Beagle...

1. OS_CRC on the ROM (4MB)... took around 32cs on average on the Iyonix and around 36cs on average on the Beagle.

2. Copy a 6MB file from RAMFS to RAMFS... took around 51cs on the Iyonix and 21cs on average on Beagle.

So there are mixed results. However, I'm sure you'll agree that given the difference in cost and size, it's a very interesting prospect.

 is a RISC OS Userriscosopen on 18/5/09 8:01PM
[ Reply | Permalink | Report ]

On First screenshot: Beagleboard runs RISC OS 5 desktop:

Well, we're getting closer to the point where one could usefully start performing some performance tests on the Beagle board. I'm very interested to see what the early results come out like.

 is a RISC OS Userriscosopen on 18/5/09 7:29PM
[ Reply | Permalink | Report ]

On First screenshot: Beagleboard runs RISC OS 5 desktop:

On the plus side, there is no reason why apps bundled with a given RISC OS 5 platform couldn't use their own licence - it's only a problem if you want to include your module in the ROM build, or your code in with some application which is already released under the Castle licence.

 is a RISC OS Userriscosopen on 18/5/09 3:13PM
[ Reply | Permalink | Report ]

On First screenshot: Beagleboard runs RISC OS 5 desktop:

You mean advantages like being produced as opposed to no longer being produced? ;)

 is a RISC OS Userriscosopen on 18/5/09 1:44AM
[ Reply | Permalink | Report ]

On First screenshot: Beagleboard runs RISC OS 5 desktop:

Funny you should mention DisplayLink. Take a look at [link] which only went public today. And guess who wrote libdlo...

 is a RISC OS Userriscosopen on 15/5/09 6:40PM
[ Reply | Permalink | Report ]

On First screenshot: Beagleboard runs RISC OS 5 desktop:

Anyone fancy converting all of our pre-built downloads into RiscPkg packages? We've been thinking of this for a while but simply haven't had the time within ROOL.

 is a RISC OS Userriscosopen on 14/5/09 4:14PM
[ Reply | Permalink | Report ]

On First screenshot: Beagleboard runs RISC OS 5 desktop:

The XScale in the Iyonix is crippled by a fault in the CPU's memory system meaning you can only access RAM at about 10% of the speed you should be able to.

Cortex-A8 in the Beagle board has a dual-issue pipeline which means that two integer instructions can be executed in parallel, as long as there are no hazards stopping this (e.g. one relying on the output of the next).

You also have the new VFP stuff that, given some supporting module, would give a great improvement in FP performance over the FPEmulator.

Finally, the OMAP chip in the Beagle also has a DSP which could be used to farm-off intensive codec-type functions, such as video decode, VoIP, etc.

Over all, I expect the Beagle board will significantly out perform and Iyonix in a number of areas.

 is a RISC OS Userriscosopen on 13/5/09 10:09PM
[ Reply | Permalink | Report ]

On Is there a way out of RISC OS version number hell?:

Before attributing quotes to me, please reread what I said so you can at least get them right. I have said it is "impossible" not on technical grounds, but on other grounds. I have also stated it is "highly impractical" on technical grounds.

 is a RISC OS Userriscosopen on 4/5/09 8:49PM
[ Reply | Permalink | Report ]

On Is there a way out of RISC OS version number hell?:

Yes, my fault... I forgot I wasn't viewing in the threaded view.

 is a RISC OS Userriscosopen on 3/5/09 2:31AM
[ Reply | Permalink | Report ]

On Is there a way out of RISC OS version number hell?:

Your comment was not only libelous but was actually incorrect by law. Further to that, we at ROOL have 100% confidence that everything we're doing is legal and correct.

We didn't contact you directly because what kind of message would that send? "Back off or we'll set the lawyers on you!" - plus you have no ability to edit or remove your foolish statement.

So we reported it. That is what the "Report" mechanism is for, after all. Problem solved; you're no longer breaking the law or making false claims about myself and my colleagues.

I don't believe the Drobe edit (over which we had no control) changes the meaning of your statement much; it still says you think our unpaid efforts over the past few years are "irrelevant". We have no objection to you voicing that kind of opinion - that is the point of free speach.

 is a RISC OS Userriscosopen on 2/5/09 9:09PM
[ Reply | Permalink | Report ]

On Is there a way out of RISC OS version number hell?:

I'm not saying merging any single component as "highly impractical"; I'm saying merging the lot is. Any yes, the main blocker is other rather than the enormous technical challenge (think of how hard just the Kernel merge would now be).

 is a RISC OS Userriscosopen on 30/4/09 10:57PM
[ Reply | Permalink | Report ]

On Is there a way out of RISC OS version number hell?:

Yes, RISCOS Ltd and ROOL are often talking about how we can best resolve the problems that users and developers experience at a result of the branched development. That doesn't mean we are able to merge the two source trees back together - we have to think a bit more laterally, but we're pretty confident that there are still going to be ways to tackle these issues.

 is a RISC OS Userriscosopen on 30/4/09 10:34PM
[ Reply | Permalink | Report ]

On Is there a way out of RISC OS version number hell?:

Right, let's put this one to bed again. Merging the Castle and RISCOS Ltd branches of the RISC OS sources is _impossible_. It's highly impractical from a technical standpoint, but for other, it is simply NOT possible.

Therefor, someone has to show some leadership and make a choice between a number of bad options to try and arrive at the least worst solution. Inaction is not the answer.

 is a RISC OS Userriscosopen on 30/4/09 9:27PM
[ Reply | Permalink | Report ]

On RISC OS 5 spotted running on RPCEmu:

Right, the new A7000/RiscPC build is up on our site - hopefully it will be a bit more stable. Note: it's still very much a work in progress!

 is a RISC OS Userriscosopen on 30/4/09 2:48AM
[ Reply | Permalink | Report ]

On RISC OS 5 spotted running on RPCEmu:

I've posted to the RPCemu mailing list but I'll also say it here: we build the wrong (Iyonix to be precise) version of the FPEmulator into the A7000 ROM image so that is the main cause of crashes.

We'll be posting a fixed build with the correct FPE on our web site very soon.

 is a RISC OS Userriscosopen on 29/4/09 4:57PM
[ Reply | Permalink | Report ]

On Is there a way out of RISC OS version number hell?:

You need at least one new bit to be set for all modules supporting this new standard. Other bits could then indicate the branch but the first tells you that it's not just an old (32-bit) module which has a flags word.

 is a RISC OS Userriscosopen on 29/4/09 4:53PM
[ Reply | Permalink | Report ]

On Wakefield 2009 wrap-up, photos and video:

and you can find all sorts of other downloads, including the A7000 ROM image, here: [link]

 is a RISC OS Userriscosopen on 28/4/09 3:20PM
[ Reply | Permalink | Report ]

On Wakefield 2009 wrap-up, photos and video:

RISC OS Open (ROOL) are pleased to announce the immediate release of the very latest RISC OS ROM release from Castle Technology (Castle) for the IYONIX pc desktop computer.

This is an official release from Castle and represents the first formal ROM release to include changes and improvements which have been fed back into the shared source project.

 is a RISC OS Userriscosopen on 28/4/09 3:19PM
[ Reply | Permalink | Report ]

On RISC OS 5 pictured running on ARM Cortex-A8 kit:

First of all, why am I not surprised that half the comments here are negative even though what was demoed at the Wakefield Show was undeniably a positive step for RISC OS?

Next, we've done quite a few RISC OS ports in the past and to say that this is just a small step and all the hard work is yet to come is just plain wrong.

Getting _anything_ happening it the hardest part, especially if you don't have access to JTAG, MultiICE, etc. Then, you can get bits of the HAL working and maybe bits of the kernel. After that, you bung some more modules in and look for problems.

You might need to do a lot or a little work to get some peripherals working (e.g. USB).

Then, you bung the rest in and fix a few remaining issues. For the most part, that bit doesn't take much time or effort - it's very much an exponential graph of progress.

For someone who is new to the RISC OS sources and who has never done a RISC OS port before to have got things this far is both a great reflection of their skills and of the design of the HAL.

In the particular case of the Beagle port, I expect the most trouble from now on will come from strange effects of the subtle changes to the ARM instruction set in the V7 architecture.

 is a RISC OS Userriscosopen on 27/4/09 9:31PM
[ Reply | Permalink | Report ]

On RISC OS 5 pictured running on ARM Cortex-A8 kit:

He, he. That is about as negative a spin as you could hope to put on the possibility of RISC OS 5 for the RiscPC.

A slightly more balanced view would be:

* It's a big upgrade for anyone running RISC OS 4.02 or below * It's fully 32 bit so the 28 MB application slot limit is removed * Old 26-bit applications can be run with Aemulor (which is free) * Most software is 32 bit now anyway * You can have the same OS across your RiscPC and IYONIX (in the case where you own both) * It's free and future updates are free * If you're a programmer and find a bug, you can get at the source code and fix it yourself * There is a bugs database and active forum at www.riscosopen.org where you can discuss any issues if you want

Apart from that though, it's hard to see why users would want it.

 is a RISC OS Userriscosopen on 26/4/09 2:02AM
[ Reply | Permalink | Report ]

On What should be NetSurf's priority?:

Wow! When the topic of conversation is "What should be NetSurf's priority?" and I suggest one area where I find NetSurf is weak that could be improved, I should have expected a barrage of defensive flaming.

Of course it's my choice of browser, of course it's up to me. But hello! I'm one of _your_ users reporting a problem. NetSurf eats all your memory when used on RISC OS.

You guys are aware of the issue but don't want to spend your time on OS-specific stuff to fix this because you don't believe it is a priority or good use of your limited resources. Fair enough.

Your point about making life simpler for application authors is a complete red herring. Portable software stacks often abstract library functions such as malloc() and free() through their own veneer - primarily because you cannot rely on standard implementations doing everything you need (like helping you to debug memory leaks and crashes, for example).

Anyway, I've raised the issue and you guys quite rightly have more important stuff to work on so enough is enough.

 is a RISC OS Userriscosopen on 2/4/09 10:28AM
[ Reply | Permalink | Report ]

On What should be NetSurf's priority?:

All very worthy and architecturally beautiful, I'm sure. Back in the real world, cross-platform software has what we call a "porting layer" full of "glue code" which often boils down to exactly what you are brushing aside.

It's saddening that you are so quick to dismiss the very platform which gave birth to NetSurf, especially as that still (probably) represents a significant number of your users.

Stick to using Firefox on Ubuntu then, should I?

 is a RISC OS Userriscosopen on 30/3/09 8:46PM
[ Reply | Permalink | Report ]

On What should be NetSurf's priority?:

(I meant one DA per browser window, BTW.)

 is a RISC OS Userriscosopen on 30/3/09 3:51PM
[ Reply | Permalink | Report ]

On What should be NetSurf's priority?:

Fragmenting or leaking is an internal distinction; to the rest of the system, it's a memory leak. Browse/Phoenix had the same problem so it used a shifting heap - which has a performance penalty but you can limit the shifting to odd occasions (such as closing a window).

If you simply held all of the image data and raw HTML for each page in its own DA, then that could easily be discarded when no longer referenced. I bet it's images which cause the bulk of the fragmentation.

 is a RISC OS Userriscosopen on 30/3/09 3:50PM
[ Reply | Permalink | Report ]

On What should be NetSurf's priority?:

I voted for "Improve display of websites" because that's all browsers' priority, surely. However, what I'd actually want to see is better memory handling - it doesn't half leak memory... it's by far the leakiest RISC OS software I use - the only program I regularly quit and restart just to get my 256 MB of RAM back!

 is a RISC OS Userriscosopen on 29/3/09 11:16PM
[ Reply | Permalink | Report ]

On Drobe Awards 2008: The results:

Thank you all very much for the votes for RISC OS Open. I'm looking forward to some exciting developments in 2009.

 is a RISC OS Userriscosopen on 1/1/09 9:52PM
[ Reply | Permalink | Report ]

On Voting now open for the Drobe Awards 2008:

I should've nominated MoreDesk - I never remember :(

 is a RISC OS Userriscosopen on 22/12/08 8:58PM
[ Reply | Permalink | Report ]

On New RISC OS ownership claim may derail ROOL RiscPC ROM release:

For the record, RISC OS Open have declined the offer of a license from RISCOS Ltd. We are continuing with our work on behalf of Castle, publishing the source code and bringing RISC OS to a wider audience.

We are also fully committed to working with RISCOS Ltd to find ways of addressing the fork in the development of the OS, to make things easier for people on both sides of the divide.

 is a RISC OS Userriscosopen on 16/12/08 3:19AM
[ Reply | Permalink | Report ]

On RISC OS 5.14 softloaded on an Iyonix: first screenshot:

Top marks to Adrian! Thanks from the team at ROOL.

 is a RISC OS Userriscosopen on 16/12/08 3:04AM
[ Reply | Permalink | Report ]

On New RISC OS ownership claim may derail ROOL RiscPC ROM release:

There is a lot of speculation in the comments above. Let's be clear here; RISC OS Open and RISCOS Ltd are not waving their fists at each other. We've enjoyed open and clear communications from the outset and are continuing to talk. Finding the best way for all parties to co-operate for the good of RISC OS has always been one of our aims.

 is a RISC OS Userriscosopen on 10/12/08 2:33PM
[ Reply | Permalink | Report ]

On Upgrade to RISC OS 4 for twenty quid:

Aha. Thanks for the info - sorry about the gripe ;)

 is a RISC OS Userriscosopen on 8/12/08 9:40PM
[ Reply | Permalink | Report ]

On Upgrade to RISC OS 4 for twenty quid:

Am I the only one who finds it almost impossible to follow these conversations now that Drobe has decided to have "threaded" topics? Spotting new comments is, shall we say, tedious.

 is a RISC OS Userriscosopen on 8/12/08 6:58PM
[ Reply | Permalink | Report ]

On Community-produced RISC OS 5.14 in final testing:

I think if we put a copy of the 5.13 'products' file into cvs, one could diff the two in order to see what versions of which components have changed. Then, you could use that to extract the cvs logs for those changes.

It's something we don't have any automated facility to do right now but maybe someone out there might feel the urge to write a suitable tool...

 is a RISC OS Userriscosopen on 8/12/08 4:46PM
[ Reply | Permalink | Report ]

On Community-produced RISC OS 5.14 in final testing:

We're not going to call it RISC OS Iyonix when there's every chance of us building a version for the RiscPC - i.e. something which runs on RPCemu.

But I do agree with your general points.

Back to the original topic, yes we are working on the softloader and we will ask Castle what they do about JTAG to see if they have something they can put on our Wiki about it.

 is a RISC OS Userriscosopen on 8/12/08 1:42PM
[ Reply | Permalink | Report ]

On Wakefield 2008 show photos:

Has no one else got any photos from the show online? We've got some at www.riscosopen.org

 is a RISC OS Userriscosopen on 06/05/08 11:15PM
[ Reply | Permalink | Report ]

On NetSurf bags GBP10K investment from Google:

Great news! Congrats to the NetSurf team.

 is a RISC OS Userriscosopen on 21/4/08 9:48PM
[ Reply | Permalink | Report ]

On Using shared source to brighten up the desktop:

In your white desktop, what's the app for the icon to the left of the mode selector and the right of SpamStamp? Looks kind of virtual desktop-ish to me but I don't recognise it.

 is a RISC OS Userriscosopen on 6/3/08 7:54PM
[ Reply | Permalink | Report ]

On R-Comp rolls out product upgrades:

Still no MoreDesk alerts support in Messenger Pro :( Come on guys... it's a one-liner! :)

 is a RISC OS Userriscosopen on 24/2/08 12:50AM
[ Reply | Permalink | Report ]

On USB in latest RISC OS 5 source release:

It also includes a load of screen savers! :)

 is a RISC OS Userriscosopen on 23/2/08 3:34PM
[ Reply | Permalink | Report ]

On RISC OS 5 to support NetSurf printing:

We're hoping to update the pre-built binaries with various changes since the Batch Two release some time today. Documentation re the changes will be put on the RISC OS Open web site at the same time.

 is a RISC OS Userriscosopen on 6/11/07 12:20PM
[ Reply | Permalink | Report ]

On South East 2007 show report:

Although we published the sources to ChangeFSI, it won't currently build due to a library which is currently not present in the BBE. There are a couple of other components in the Batch Two release which are known to not build - these will also not be found in the pre-built binary archives.

Clearly, getting more libraries into the BBE is one of the things we're working on, as well as getting the sources to those libraries out, too, so less and less of the BBE will be supplied as a binary and more and more will be supplied in source form so you can build your own build environment (if you follow me).

We have to balance decisions like the above against the desire to get sources out there. For example, some components in Batch Two which are known not to build simply aren't a priority for us but you're more than welcome to fix them yourselves and feed the fixes back.

 is a RISC OS Userriscosopen on 22/10/07 6:13PM
[ Reply | Permalink | Report ]

On South East 2007 show report:

Thanks to all for putting this show together. We all enjoyed this one and are looking forward to next time.

On the subject of Browse/Phoenix vs Netsurf, I have used Phoenix for years now and I do like a lot of things about it but I have to say I primarily use Netsurf on RISC OS, only to fall back to Phoenix when I want to do certain things which Netsurf doesn't do. Hopefully it will give the NS guys a few new ideas.

 is a RISC OS Userriscosopen on 22/10/07 3:48AM
[ Reply | Permalink | Report ]

On RISC OS 5 core source release imminent:

@nijinski: What about burning DVDs? The ISO image for a single DVD is several GB in size, a compressed archive of all the RISC OS sources is over 2GB. Developers tend to have multiple build environments/source trees for different things and these aren't compressed so that's tens of GB. Then lots of us have tens of GB of digital photos from over the years plus tens of GB of audio files.

I do testing of digital set-top boxes, too. The average video test file is several of GB in size. It's _very_ easy to fill a >100GB hard disc nowadays for most of us.

 is a RISC OS Userriscosopen on 19/10/07 6:33PM
[ Reply | Permalink | Report ]

On PostScript overhaul project reports progress:

What are you all on about? In reply to hubersn:

No, I'm not getting confused about licencing and Copyright. ROL won't just give the sources to Martin et al; they must do so under some licence agreement - you yourself have said as much by talking about a "contract". That's what I'm talking about. You sound confused. When I've written code for a thiry party on their software stack, usually the contract states that they gain the IP - hence the copyright.

In reply to guestx:

What are you on about? If some source code belongs to Castle and they farm some development out to a thiry party, they will first get them to sign an NDA to ensure that those sources don't find their way anywhere else. It's how Acorn did it and it's how everybody else does it. Until those particular sources have been processed and released through our activity (and they are able to be developed under a more open model than the proprietary one as it stands), it will remain that way.

In reply to Stu:

It all depends upon the contract with ROL. I and others have worked on loads of great software which would be perfect for RISC OS but because it was for some other company, we can't just dump that intellectual property into the RISC OS sources. You cannot even use the same concepts - you have to achieve the same ends with a clean room reimplementation which experience shows you're not going to feel inclined to do.

Now, if this development were done on the ROOL-released sources in the first place, everyone would be free to download that updated stuff from our site free of charge. However, as this work is being done on source code which _isn't_ in the public domain, under unknown terms and conditions, it remains to be seen whether we'll all benefit *free of charge* from it.

Just saying "well, the Castle sources are very similar to the ROL ones" doesn't mean a thing unless Martin and John are free to take their work and cut-and-paste it from the ROL sources into the Castle ones.

Please re-read everything Martin has said thus far. All he has done is indicate that non-RO6 users (e.g. IYONIX users) will hopefully also be able to *benefit* from his work. He doesn't say at no cost to them, nor that they will have access to the sources to his work in order to maintain and improve it further in future.

 is a RISC OS Userriscosopen on 16/10/07 4:33PM
[ Reply | Permalink | Report ]

On PostScript overhaul project reports progress:

Thanks for the response, Martin. I'm still not clear whether this means you'll be able to add the same features to the printer sources which will very soon be in the public domain.

The alternative would appear to be that the sources have been licensed to you by ROL so you can add some features to _their_ stack (which may well end up being a separate commercial product for non-RO6 platforms) on the condition that your changes aren't published. Any similar changes to the public printer stack (available to every RISC OS user free of charge) would have to be "clean room" implementations.

 is a RISC OS Userriscosopen on 15/10/07 10:40PM
[ Reply | Permalink | Report ]

On PostScript overhaul project reports progress:

If they'd wanted access to the sources under a non-disclosure agreement in order to get started prior to it all being in the public domain (within the next week), I'm sure Castle would have agreed to that.

 is a RISC OS Userriscosopen on 15/10/07 7:49PM
[ Reply | Permalink | Report ]

On PostScript overhaul project reports progress:

Not that I have anything against Martin and John's contribution, I just hope this isn't RO6 only rather than for the benefit of everyone, which the sources we're releasing are. I suppose it all depends upon the terms under which ROL released the sources to Martin and John. We can only hope.

 is a RISC OS Userriscosopen on 15/10/07 6:14PM
[ Reply | Permalink | Report ]

On PostScript overhaul project reports progress:

If the source code is pretty much the same, it's because it's Castle's! This is reminding me of the way the !Printers source was released into the public domain, complete with all of the copyright notices saying it wasn't theirs to release (whoever it was that put it there).

Kind of makes me wonder why I'm working so hard to do this the right way.

 is a RISC OS Userriscosopen on 15/10/07 6:11PM
[ Reply | Permalink | Report ]

On ROOL aim next source release for October:

I won't tolerate insubordination like that. You're fired! ;)

 is a RISC OS Userriscosopen on 23/9/07 9:01PM
[ Reply | Permalink | Report ]

On New free MSN client available for all:

Out of curiosity, why does the copyright in the info window of the first release say 2005?

 is a RISC OS Userriscosopen on 20/9/07 2:56AM
[ Reply | Permalink | Report ]

On ROOL aim next source release for October:

For those who are interested, I had a look and these are the components which have seen useful changes since the release. Not bad considering it's not very much of RISC OS that is out thus far:

CloseUp, Paint, SrcEdit, Filer, Pinboard, SysLoad and ScreenFX.

Well done and a big thanks to those who have put their time into improving the stuff that is out there. We're really aiming at getting more "core" stuff out next time. Oh, and this year!! :-P

You can browse our live cvs repository to read the log files that say what people did and when (usually, you should look for a file called VersionNum in the root of the component you're interested in). Take a look at https://www.riscosopen.org/viewer/view/

 is a RISC OS Userriscosopen on 20/9/07 2:40AM
[ Reply | Permalink | Report ]

On Acorn football team plays on:

We meet on Fridays, 5pm at Cambridge Regional College. Emails to chairman@acorn5aside.co.uk if you're interested. Ex-Acorn and friends of Acorn welcome as long as you have fewer than three left feet.

There's also a spin-off game on Tuesday nights, 9pm at Cherry Hinton Village Centre (the traditional home of our Acorn games). Emails to cam5aside@yahoogroups.com.

All non-footballers can just content themselves with laughing at the photos.

:)

 is a RISC OS Userriscosopen on 3/9/07 12:50AM
[ Reply | Permalink | Report ]

On Top apps in first ROS 5 source release:

In case you didn't know, we have a discussion topic in our "Wish Lists" forum on the www.riscosopen.org site called "The Next Sources to Release". This is the place to request or suggest which RISC OS sources _you_ really want to see us release next. Include a reason for your request and it will help us to prioritise our work. Thanks.

 is a RISC OS Userriscosopen on 21/5/07 5:24PM
[ Reply | Permalink | Report ]

On ROOL mouse mat design revealed:

Yes. I was amazed with the response we did get and it kept me very busy. I can only try to guess at how much work is involved in organising a show like Wakefield. I'd rather the mouse mat idea not be used to single-out people who didn't get on it.

There was also quite a short time between the announcement (i.e. me having the mad idea in the first place) and the deadline for getting something to the printers so they would be ready in time for the show, which didn't help a lot of people. Maybe there will be a mouse pat part deux... ;)

 is a RISC OS Userriscosopen on 13/5/07 10:12PM
[ Reply | Permalink | Report ]

On ROOL mouse mat design revealed:

The mouse mats are back from the printers and look great! See you all at Wakefield.

 is a RISC OS Userriscosopen on 11/5/07 3:14PM
[ Reply | Permalink | Report ]

On ROOL mouse mat design revealed:

Thank you for all your support - I have to admit, I was getting worried about fitting all of the logos on there! :) I'm glad people like the design, it was worth learning how to use ArtWorks to do it - special thanks to Martin Wuerthner for a trial copy.

See you all at Wakefield, a user group meeting or maybe another show on the busy RISC OS calendar.

 is a RISC OS Userriscosopen on 2/5/07 5:03PM
[ Reply | Permalink | Report ]

On Select low-level emulator in development:

Can someone point me to the APIs for the ROL versions of the OS SWI claiming calls? It's possible that both could co-exist (the API I did has currently unused flag bits in it for just this sort of thing).

 is a RISC OS Userriscosopen on 24/4/07 1:30AM
[ Reply | Permalink | Report ]

On Select low-level emulator in development:

I implemented some SWIs for claiming OS SWI calls in a module called DebugTools. This is to be released in the Batch One sources (hopefully).

Ideally, I'd like to see that used on RO5 because it's a more useful API than the ROL one (you can claim, release or add to SWIs in the same way that software vectors work).

Of course, that wouldn't address the issue that there would then be two different APIs.

 is a RISC OS Userriscosopen on 23/4/07 6:55PM
[ Reply | Permalink | Report ]

On ROOL make 'market map' mouse mats:

In reply to EasyKeys:

We've got all your info, thanks.

To everyone else:

Thanks for all of the support! You've still got until midnight (UK time) before we stop collecting requests to go onto the mouse mat design.

 is a RISC OS Userriscosopen on 23/4/07 5:47PM
[ Reply | Permalink | Report ]

On How to build RISC OS 5 from shared source:

The document is still being worked on so don't be surprised if I change bits over the next few days/weeks.

 is a RISC OS Userriscosopen on 11/3/07 2:13AM
[ Reply | Permalink | Report ]

On How to port RISC OS 5 to the RiscPC:

Quite right. In the Set-Top Box (STB) world, we were usually aiming to get the bill of materials cost (BOM) for your basic ARM-based RISC OS STB down to under $100 - that's under £50 in today's money. But that's with volumes of, say, 50000 machines. If you want to produce the same thing in volumes of, say, 50 machines, you will find the BOM cost is painfully higher. And that was tried-and-true ARM9 based stuff so if you want to use whizzy new CPUs, RAM and other bits you'll be paying even more for them when placing small orders.

All that means you're highly unlikely to see a native RISC OS hardware design that's cheap so a port of shared source RISC OS 5 to some commodity ARM-based hardware would be the low cost solution.

 is a RISC OS Userriscosopen on 31/01/07 11:29PM
[ Reply | Permalink | Report ]

On Programming tools set for price slash:

Don't get carried-away with my "inline assembler" comment; some code does indeed use the unique inline assembler features in our cc but I'm not sure any of those modules are particularly significant to a RISC OS 5 ROM build. Other code uses other unique features or contains work-arounds for known compiler bugs, etc.

The bottom line is this: once you've built a ROM with a given toolset and put it into SQA (software quality assurance) and enter a bug-fixing cycle, you then end up with a known entity. To swap the toolset will invalidate all that testing because you're going to have no idea what new bugs that might introduce (it's unlikely to fix existing bugs because if they mattered, they would have already been fixed or worked-around in the bug-fixing cycle).

 is a RISC OS Userriscosopen on 30/01/07 2:58PM
[ Reply | Permalink | Report ]

On Programming tools set for price slash:

Take a look at www.riscosopen.org for the latest news. Note: the site is undergoing some work so may be a bit sluggish at the moment.

 is a RISC OS Userriscosopen on 25/1/07 10:48PM
[ Reply | Permalink | Report ]

On RISC OS Open website expands:

All domains apart from the .com domain are now pointing at the new RISC OS Open site so signing-up should be easy. The .com domain is taking longer due to problems at the original host.

Take a look at [link] for more info.

The forums and bugs database are open for business so feel free to start posting stuff - but as we're still working on the site, don't be surprised if it goes down occasionally ;)

 is a RISC OS Userriscosopen on 15/12/06 3:56PM
[ Reply | Permalink | Report ]

On RISC OS Open website expands:

We're in the process of getting our full, dynamic site up and running. As such, the domains are not all pointing at the new site so some things (the registration confirmation email, in particular) aren't fully working yet.

If you have problems with the email confirmation when you're creating an account on the site, edit the link in the email from www.riscosopen.org to www.riscosopen.co.uk and you should be able to follow that and complete the process.

A full press release about the new site will be made to Drobe and csaa in the next couple of days - once we're fully ready to go live.

 is a RISC OS Userriscosopen on 13/12/06 12:44AM
[ Reply | Permalink | Report ]

On R-Comp Dad suffers 'major' heart attack:

Best wishes for a speedy recovery from all of us at RISC OS Open.

 is a RISC OS Userriscosopen on 11/10/06 10:20PM
[ Reply | Permalink | Report ]

On RISC OS Open needs your help:

I don't need people; RISC OS needs people.

 is a RISC OS Userriscosopen on 4/10/06 12:52AM
[ Reply | Permalink | Report ]

On RISC OS 5 source code release revealed:

If you are interested in helping out with the RISC OS shared source project, take a look at the following page:

[link]

 is a RISC OS Userriscosopen on 03/10/06 3:11PM
[ Reply | Permalink | Report ]

On RISC OS 5 source code release revealed:

A couple of additional entries have been added to the shared source FAQ on our site which cover the following questions:

Why didn't we select the GPL? Why did you select those components to open first? What tools do I need to build the sources?

Hope that helps.

 is a RISC OS Userriscosopen on 02/10/06 11:27PM
[ Reply | Permalink | Report ]

Search the archives

Today's featured article

  • David Ruck comments on RM's decision to pull out of education in Northen Ireland

     1 comment, latest by AndrewDuffell on 5/12/03 7:44PM. Published: 13 Jan 2001

  • Random article

  • South West 2006 show exhibitors confirmed
    All the usual faces plus theatre presentations
     9 comments, latest by highlandcattle on 29/1/06 10:58PM. Published: 26 Jan 2006

  • Useful links

    News and media:
    IconbarMyRISCOSArcSiteRISCOScodeANSC.S.A.AnnounceArchiveQercusRiscWorldDrag'n'DropGAG-News

    Top developers:
    RISCOS LtdRISC OS OpenMW SoftwareR-CompAdvantage SixVirtualAcorn

    Dealers:
    CJE MicrosAPDLCastlea4X-AmpleLiquid SiliconWebmonster

    Usergroups:
    WROCCRONENKACCIRUGSASAUGROUGOLRONWUGMUGWAUGGAGRISCOS.be

    Useful:
    RISCOS.org.ukRISCOS.orgRISCOS.infoFilebaseChris Why's Acorn/RISC OS collectionNetSurf

    Non-RISC OS:
    The RegisterThe InquirerApple InsiderBBC NewsSky NewsGoogle Newsxkcddiodesign


    © 1999-2009 The Drobe Team. Some rights reserved, click here for more information
    Powered by MiniDrobeCMS, based on J4U | Statistics
    "...a somewhat shallow article intended only to generate some journalistic controversy"
    Page generated in 0.4159 seconds.