RISC OS licence?

Hi,
I was looking at the RISC OS OEM licence stuff [ https://www.castle-technology.co.uk/secure/licence/shop/catalog/index.php?action=CallCalculator&vars=1,1,3 ] and I have two questions:

1. Is this priced per unit? I’m not making anything, but if I was, would I need to buy (devices x price)?
2. I see the price depends upon feeding back IP (within 2 years = £10; within 30 days = £3 (!)). What if you only plan to run an application on top of RISC OS and don’t really have (or plan to have) any intellectual property to feed back into RISC OS?

Not bad pricing, considering it is said that Windows 8 RT may cost as much as $85 per device. I looked for Windows XP OEM licencing to get an idea of that, but the first two official distributors I tried (one in Shropshire, one in Basingstoke) required you to log in prior to being given any hint of a price. While RISC OS may be simpler than the likes of XP, you do get access to the source which allows a high degree of customisation. We shouldn’t forget the Bush internet box (which perhaps suffered from being dumbed down a little too much) as an experiment in what RISC OS could be used for. Moreso now with complete source access, as things could be highly cutomised for the platform/concept in question.

I’d compare to Windows CE (erm, Windows Embedded Compact 7), not XP. And then, it’s shared source (under much, much more restrictive terms than Castle’s license, though).

Licensing costs there are $995 for the development tools, and between $3 (for the stripped down version for navigation devices) and $16 (for the full version) per device.

Is this priced per unit? I’m not making anything, but if I was, would I need to buy (devices x price)?

First of all, I’m not representing Castle here so ICBW, but I think you have to pay for the number of units you think you will ship. If you end up looking like going over (say you only bought 100 licences), then you need to buy more to cover yourself.

What if you only plan to run an application on top of RISC OS

You still need to buy the licence(s) if you’re planning on including bits of Castle-licenced code with your release. But because you’re not modifying the code (or you’ve fed any changes straight into the CVS repository) you get the cheapest rate (i.e. feeding back your changes within 30 days). I did argue with Castle that we need a “I’m not changing the Castle code” option, but they felt it’s clear enough as-is.