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

Reply to thread

1. I don't see why it's in their interest to make a statement, except possibly to refute petty claims of 'lack of vision' and the like. It wouldn't be unknown for a RISC OS company to make a press statement just to make a petty refutation of a petty comment though. 2. You mean, beyond breaking the terms of their license, according to Castle? 3. Castle claim they were trying to negotiate. 4. Probably not, if they're not doing whatever it is they're legally meant to do. 5. Good question. On the surface it looks like simple frustration. 6. Is there a lawyer in the house? 7. I'd have thought that'd be unlikely, though it's possible they'd be equivalent. 8. Shareholders? Do you mean sublicensees? It doesn't say they've been talking with them, just notifying them and trying to find a solution for them (with unnamed parties) 9. I'd personally think you need things like TV out (in the case of an STB) or other hardware features to make a system (borderline) embedded. ROL licensed RO4 for specific systems which were known not to be embedded, but they didn't know what system VA would end up on. At a guess. 10. Depends on the terms they contracted their software engineers under. And depends on what happened to the RO 3.8 and beyond changes that Pace sold to ROL. 11. That could be argued all day. I don't think it's actually relevant though, since nothing says ROL has to supply post Select 2 core changes to anyone anyway (unless the contract has specific clauses covering breach of contract, which is possible). 12. Almost certainly not. 13. See above. Either they couldn't afford to upgrade their license so their actions complied, or they thought Castle were just bluffing.

While we're missing some important facts, they're only really questions 2, 6 and 10. Everything else falls into place if we know those. However, noone we can explicitly trust is going to tell us immediately, though comments from ROL and other may shed light.

 is a RISC OS Userninja on 16/06/04 1:58PM
[ Reply | Permalink | Report ]

Please login before posting a comment. Use the form on the right to do so or create a free account.

Search the archives

Today's featured article

  • Brush up your ARM coding skills with Matthew Bloch's assembler guide

     Discuss this. Published: 27 Feb 2001

  • Random article

  • How to spot a drobe editor
    Firstly, you have to be at the South East RISC OS show
     11 comments, latest by quatermass on 4/11/02 10:14AM. Published: 2 Nov 2002

  • 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
    "Admittedly, that might contradict some editors' strongly held beliefs..."
    Page generated in 0.0238 seconds.