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

Profile for caliston2

ContactAbout me
Username: caliston2
Realname: Theo Markettos
About me:
Homepage: http://www.markettos.org.uk/
Comments posted:81 (show all)
Articles written:3 (show all)

All comments

On RISCWorld mag back-issues reprinted online for free:

Some good stuff there... eg the full text of the Archimedes Game Makers Manual, BASIC V: A Dabhand Guide, First Steps with RISC OS 4, ArtWorks Made Easy, Budget DTP, Graphics on the ARM and ARM Assembly Language Programming. And quite a few interesting articles.

Thanks, Aaron, for putting it online.

 is a RISC OS Usercaliston2 on 19/8/09 3:17PM
[ Reply | Permalink | Report ]

On NetSurf on RISC OS faces axe:

For better or worse, I imagine many home-grown RISC OS programmers followed something like the following sequence:

1. Learnt BASIC 2. Learnt WIMP programming in BASIC 3. Learnt portable-ish C 4. Programmed C in a BASIC-like way with a library like OSLib, DeskLib or (back in the day) RISC_OSLib 5. Programmed C with a higher-level toolkit like the Toolbox (or DeskLib to some extent)

(and if you go down the lower-level route, assembler and writing modules will fit in somewhere, but aren't of concern for someone doing WIMP stuff)

Now of course you can do these differently, or in a different order. But I think the biggest step is 2. Once you have some idea of how to program, learning how to interact with the WIMP is the main thing.

Having done that, switching language (especially if you've even seen other computer languages) isn't so hard... just takes a little while to get your head around new features like structures, a while until you stop making stupid typos, a while to iron out your silly bugs, and a while to develop a good coding style (peer review helps a lot with all this).

You can, of course, short-circuit this by going straight to the Toolbox. But sooner or later you'll need to interact with the WIMP directly. So it's worth knowing how the WIMP works even if you rely on something else to do the legwork most of the time. This is more the case than, say, Unix where there's not so much of a need to learn Xlib because libraries like GTK cover it more. But by all means start with the Toolbox and then fill in the detailed WIMP stuff later.

I think I would actually suggest BASIC is a better environment to learn WIMP programming than C as it's more dense. Especially with a library so you don't have to do all the q%!(q%?3) stuff. Then you can switch to C which will have a similar library, and better structure support for manipulating WIMP data.

 is a RISC OS Usercaliston2 on 15/8/09 8:05PM
[ Reply | Permalink | Report ]

On Your 60-second Wakefield 2009 preview:

Also there's a whisper there'll be RISC OS running on the Cortex A8-powered BeagleBoard: https://www.riscosopen.org/forum/forums/5/topics/166?page=4

 is a RISC OS Usercaliston2 on 25/4/09 12:43AM
[ Reply | Permalink | Report ]

On RISCOS Ltd's head licence with E14 leaked:

But to post to wikileaks you first have to port Tor to RISC OS :-)

 is a RISC OS Usercaliston2 on 20/12/08 10:25PM
[ Reply | Permalink | Report ]

On Using ROL's 4.02 ROM image in Linux RPCEmu:

I would come to help out, only I'm nowhere near London :)

Xandros on the eee is a slightly odd system. Not having used one, the main issues I anticipate might arise are: Installing a compiler and tools Installing the Allegro library (both the runtime library itself and the -dev package that allows you to compile things with it)

I can't seem to find a list of packages available in the eee Xandros, so first I'd try using the default install to grab the packages named in the RPCEmu guide. Here's the procedure: [link]

If that fails, you'll probably have to add some repositories. Try this: [link] That suggests that using vanilla Debian repositories isn't a good idea, but there are others listed.

Good luck! :)

Theo (who might be persuadable to be around on IRC at the time if someone points me at a channel)

 is a RISC OS Usercaliston2 on 15/12/08 2:55PM
[ Reply | Permalink | Report ]

On Building a RISC OS laptop out of Lego:

Quote from [link]

QUOTE: The Barracuda module runs Familiar Linux. Familiar Linux is a derivative of Debian Linux. Debian Linux has been ported to several ARM platforms, including bast . The reference platform for bast is the Simtec Electronics EB2410ITX Evaluation Board [SNIP] It seems that Reciva used the 'bast' ARM architecture as a base for their own development.

"Bast is a modern ARM 920 board with a 266MHz Samsung processor. It has integrated IDE, USB, Serial, Parallel, audio, video, flash and two ethernet ports. This system has a good bootloader which is also found on the CATS and RiscStation systems."

(bast, cats, and riscstation are evaluation boards by Simtec Electronics) ENDQUOTE

 is a RISC OS Usercaliston2 on 20/11/07 11:14PM
[ Reply | Permalink | Report ]

On Building a RISC OS laptop out of Lego:

On the subject of hardware, I'm rather amused that I picked up an internet radio based on the Reciva platform the other day. It's based on the same Simtec evaluation board as the A9Home, though has a bit less hardware (less RAM, more flash, no video, USB wireless not ethernet). Going at your local PC World for 40 quid. (Well they were, the price has now gone up again). They're choice of platform is not entirely surprising since the CTO of Reciva is one Phil Blundell of ARMLinux fame. Still, interesting to see what pricepoint an A9 system would be if it had the volume...

 is a RISC OS Usercaliston2 on 19/11/07 6:37PM
[ Reply | Permalink | Report ]

On New TechWriter features bonus style finder:

If you look closely at the screenshot there's a black line at the very bottom of the window then a white line to its right - they look like the dropped/raised shadows of another entry and button. So it seems there is at least one other button below it. There are desktop utilities to add scrollbars to windows that don't have them - can be useful for poorly designed apps. But if Martin doesn't know then I don't see who would!

 is a RISC OS Usercaliston2 on 23/10/07 11:32PM
[ Reply | Permalink | Report ]

On RISC OS 5 core source release imminent:

I've been having a brief poke around the source of ADFS, FileCore and FileSwitch.

Firstly there's a serious documentation need. All the documentation is in little text files scattered around - ideally it needs someone writing a basic overview of what happens where. Secondly FileCore and FileSwitch are inherently harder to understand (for me, anyway) because they do lots of structure twiddling which is harder to understand in assembler.

I'd suggest: Retaining ADFS as-is for its floppy support (on any machines that still have drives). All the floppy foibles take up a fair amount of code and I think it's best left alone. Re-implementing the hard drive support as a new IDEFS (davehigton and I had a go in 1997 - it wasn't too hard to get something working, the messy bit is coping with all the variations in drives out there) Bin RAMFS. Fix bugs in Memphis and use that instead. A new interface between block drivers and filing systems, with a FileCore 'personality' for compatibility. This might do disc partitions too. FileCore retained as-is, for supporting existing drives, but accessed through the new interface A module for a new disc format (FAT? NTFS? ext3?). If it can work on an extended image filing system API, so much the better (but would have to be reentrant) Lower priority: Rewrite HForm into a cross-platform FileCore filesystem generator - maybe plug it into acorn-fdisk that already exists.

Then it gets messy. FileSwitch is more closely tied in with the kernel, and there's no nice list of tie-in assumptions in the source as there is for ADFS. I'm not convinced rewriting FileSwitch would help - you'd have to rewrite bits of the kernel too. Extending to 64 bit addressing would be a must, perhaps at the same time simplifying the API and putting the old one in a 'personality' module for compatibility. Are there any other problems with FileSwitch other than the 32 bit file size issue? Could they be solved by helper modules intercepting calls between FileSwitch and the lower layers in the stack?

 is a RISC OS Usercaliston2 on 21/10/07 11:42PM
[ Reply | Permalink | Report ]

On June news in brief:

We have, of course, had a RISC OS search for over 5 years, namely acornsearch.com. Sadly that domain has gone to a cybersquatter, but the search is integrated at the top of this very page, as 'RISC OS Search -> Websites'

FWIW Rebecca seems to be aiming for a Yahoo style directory search, but without ability to browse the directory.

 is a RISC OS Usercaliston2 on 21/6/07 10:57AM
[ Reply | Permalink | Report ]

On Oregano 3 scrapped:

In terms of attracting new programmers, I think one way to do it would be to port an open RISC OS to some sexy new hardware. If you can say 'have a full desktop OS for your Nokia' then people will be interested. If they'll be interested, a few of them might be interested enough to get involved and start coding. The key is making RISC OS an interesting proposition (you might not use your mobile as your main OS, but Linux-on-Psions or similar generated enough interest to support developers). RISC OS from a developer's point of view is quite interesting... many of the challenges which are over-solved on other platforms (how many Windows unzip programs do you need?) aren't solved here (browser, VPNs, wireless, etc etc). The key is to make it attractive enough for people to use it - spending a fortune on hardware is a huge disincentive, emulators aren't really relevant (though writing them might be) but the ability to do something exciting for little cost will attract people.

 is a RISC OS Usercaliston2 on 28/04/07 00:25AM
[ Reply | Permalink | Report ]

On Select low-level emulator in development:

I've remembered the context now. I actually wrote it up for the StrongHelp manual a year or two ago, and confirmed the details with a RISC OS Ltd staffer. That being said, it's very much an internal interface and so subject to change (which is why there's no public documentation on it).

 is a RISC OS Usercaliston2 on 24/4/07 3:29PM
[ Reply | Permalink | Report ]

On Select low-level emulator in development:

I've written up my knowledge of ROL's OS_ClaimOSSWI API at: [link]

 is a RISC OS Usercaliston2 on 24/4/07 1:53PM
[ Reply | Permalink | Report ]

On File sharing Bit Torrent client ported to RISC OS:

Until the UPP servers are updated, I've linked in a temporary download to the page above so you can grab it now.

simo: Good question. My understanding is the faster servers will be more heavily used. If ROOL also provide a server (seed), it's not going to be any worse than everyone downloading from them directly (well, a bit of overhead). It has the potential to be significantly better for ROOL, especially at big release times (when lots are downloading at once). However if people can be convinced to run BT servers all the time, particularly those on 'unlimited' bandwidth packages, then that'd reduce the load on ROOL. You might end up getting 80% from ROOL (because they're so much faster), but it's still a 20% saving on their bandwidth bill. And there's nothing stopping people with colo boxes running BitTorrent there too :)

 is a RISC OS Usercaliston2 on 30/3/07 1:42PM
[ Reply | Permalink | Report ]

On Website launches 'help wanted' list:

flibble: Could you put up regularly-updated tarballs instead? A quick cron job running 'svn checkout' and then dumping it onto your server might suffice. It wouldn't protect against you doing occasional llame svn checkins, but that's the price we pay :)

 is a RISC OS Usercaliston2 on 30/3/07 10:32AM
[ Reply | Permalink | Report ]

On File sharing Bit Torrent client ported to RISC OS:

Bear in mind that RISC OS can't handle files greater than 2GB, so grabbing whole DVDs might not work. I don't know if anyone's come along with a commonly-accepted splitting workaround for this (I don't know quite what CDVDBurn does). Fixing the OS is probably a better plan.

 is a RISC OS Usercaliston2 on 30/3/07 10:19AM
[ Reply | Permalink | Report ]

On File sharing Bit Torrent client ported to RISC OS:

Once the official autobuilder version is ready I'll link to it from here: [link] where I can put other documentation and others can contribute.

ctorrent provides a -M max_peers option to control the maximum number of peers, so keeping within the socket limit should be possible. I haven't tried any very popular torrents as those tend to be large files and I'm a bit tight on disc space on my RPC. But BitTorrent is definitely a good way to stress test a network... it's the only application that's ever saturated my upstream and downstream bandwidth.

 is a RISC OS Usercaliston2 on 29/3/07 11:35PM
[ Reply | Permalink | Report ]

On Website launches 'help wanted' list:

Good points. I've just added details of how to subscribe to riscos.info's RSS feed, so you can keep track of updates without even visiting the site :) Peter's also made the Recent Changes link a bit more prominent, so it should be more apparent how much is going on.

 is a RISC OS Usercaliston2 on 29/3/07 5:56PM
[ Reply | Permalink | Report ]

On Firefox 2 install guide published:

One question we as RISC OS developers should be asking the community is: who out might be able to help out, but is being held back for one reason or another. For many the problem is time - sadly the TARDIS Porting Project hasn't progress too far - and the usual way to create time (in exchange for money) is one we're having difficulty with. However, are there people out there who have time, but not the skills? Is the problem that we're bad at passing on the skills? Are there people out there with time and skills but no necessary hardware or software? Is there some way they could be supported? Is there something others who don't have time could do to help out, bearing in mind the usual substitute for time (money) is pretty inefficient (pay someone to fix your car and it costs a fortune, do it yourself and it's a lot cheaper).

Is there enough willing out there to sit down and tackle the problems?

 is a RISC OS Usercaliston2 on 11/3/07 6:09PM
[ Reply | Permalink | Report ]

On Acorn PC card Linux files unearthed:

I ought to give Andrew Wickham the credit for unearthing the files, but otherwise claim responsibility for the wiki entry. If anyone has anything more related to Linux on the PC card(s) I'd be very interested to hear about it.

 is a RISC OS Usercaliston2 on 1/1/07 10:50PM
[ Reply | Permalink | Report ]

On ROS Open awaiting licensing wording agreement:

To show that vapourware in the Acorn market isn't new, I give you Mach Technology. They advertised all sorts of exciting hardware and software products (286 card for Archimedes, A300 RAM, hard disc upgrades, BASIC compiler) and then vanished with everyone's money. The Fraud Squad were involved - turned out they'd only developed one database program and the rest didn't exist. Pity, as most of the things they advertised did appear from other people eventually (I think they were the first to advertise an A300 4MB upgrade, for example).

 is a RISC OS Usercaliston2 on 1/12/06 12:06PM
[ Reply | Permalink | Report ]

On ROS mailing lists face closure:

Losing the archives is perhaps more annoying than having to move the list. Though HTLM format archives of some lists are available for recursive wget - grab them while you can.

 is a RISC OS Usercaliston2 on 6/11/06 1:32PM
[ Reply | Permalink | Report ]

On RISC OS Open needs your help:

hzn: Thanks for reporting what you didn't understand in the GCCSDK tutorial - that's exactly the sort of feedback we need. I've expandeed the 'Using GCCSDK' tutorial a bit more. If you try it again please let the GCCSDK developers know if there's anything you still don't understand. (Obviously more depth is still required)

 is a RISC OS Usercaliston2 on 08/10/06 10:40AM
[ Reply | Permalink | Report ]

On Iyonix banned by new EU green law:

The restriction is on "placing on the EU market of new electrical and electronic equipment". Not even importing for own use is allowed. So it's a level playing field - all equipment on the EU market is covered including imported goods. How enforcement will work in practice I don't know.

 is a RISC OS Usercaliston2 on 1/8/06 2:46PM
[ Reply | Permalink | Report ]

On ROS must open up to survive says Wild:

I think open source is a good idea /if/ there is someone to manage the project. Otherwise it becomes a hotchpotch of people working on bits that interest them rather than co-ordinated development on key areas that need work. The current situation with ROL and Castle driving things plus open source RISC OS would work, if (big if) they can come up with a funding stream.

I'm amused, though, that ROL are selling RISC OS specially for its closed-source-ness: [link] says:

> Proprietary code > RISC OS is based almost entirely on proprietary > code with no chance of hidden backdoors that > can arise from using Open Source software.

 is a RISC OS Usercaliston2 on 20/7/06 6:11PM
[ Reply | Permalink | Report ]

On Blogging helped me code says developer:

I've found it very useful blogging my PhD work - it's quite handy to remember what you were actually doing six months ago. And if you've written something it's extra documentation to help you recall how on earth that bit of code you wrote actually works. It's a bit different for a blog not intended for people who know the code intimately, but maybe using tags or filters would help there to not overwhelm newbies.

 is a RISC OS Usercaliston2 on 17/7/06 3:26PM
[ Reply | Permalink | Report ]

On News in brief:

Hmm... New Electronics magazine isn't very, umm, New. I work with Simon Moore who was interviewed in the article mentioned above. NE hadn't sent him a copy of the finished article, so he's just requested one from the journalist. It looks like they're sending it... by post.

Sigh, the 21stC digital connected e-economy strikes again.

FWIW an abstract is here: [link]

 is a RISC OS Usercaliston2 on 17/2/06 12:40PM
[ Reply | Permalink | Report ]

On PCI serial port card driver available:

Relevant to graphics cards, I notice Castle have released basic details of their 2D graphics acceleration API: [link]

 is a RISC OS Usercaliston2 on 30/1/06 5:58PM
[ Reply | Permalink | Report ]

On News in brief:

Thanks Richard

This isn't generally applicable, but if you knew you wanted to make an announcement on date X, could you send the announcement to 'news organisations' with a statement 'Embargoed until 00:00 on <date>'? Then the news organisations would know that you're planning publicity on a certain date. Otherwise they don't know if you are going to make an announcement soon.

They don't seem to have respected that in this case though (Chris H mentioned the details unofficially, and said an announcement would be forthcoming).

 is a RISC OS Usercaliston2 on 26/1/06 6:09PM
[ Reply | Permalink | Report ]

On 2006 predictions:

Indeed, VRPC will always be an ARM emulator. But the point I'm getting at is that VA don't want to release a Linux version of VRPC because of the support headaches. So I was thinking of ways VRPC could run on Linux by putting in another layer between it and the host OS. This means either tricking VRPC into thinking it's running on Windows (the WINE route), or coming up with a Linux version of VRPC which runs on one fixed OS installation on one fixed hardware platform (that 'emulated' by the virtualiser). Any support headaches are therefore transferred to the virtualiser, which has a much larger user base. And if the virtualiser is multi-platform, it'll run on other OSs (eg Mac OS X/x86) so VA only need release one version of VRPC.

(I suspect the WINE route is probably much less work)

 is a RISC OS Usercaliston2 on 10/01/06 12:43AM
[ Reply | Permalink | Report ]

On 2006 predictions:

That's emulation, not virtualisation. The difference is that virtualisation runs code on the processor it was designed for, so for example you might have an x86 PC running Linux, on which there was an x86 virtual machine running Windows inside. If you're just running straight user-land code (Firefox, say) it runs directly on the x86 processor as if the code were part of Linux. The only performance hit is that when the code tries to hit make operating system calls the calls get diverted to the virtualised Windows machine rather than the underlying Linux machine.

[link](virtual_machine_monitor) has a better (technical) outline of how one system works.

Another idea for VRPC on Linux... make the Windows version WINE friendly. (WINE is a program for Linux that runs Windows programs by emulating the full Windows API). If it only used Windows calls that were supported by WINE then it should run on Linux under WINE without any problems. And the same code would run quite happily on Windows by definition.

 is a RISC OS Usercaliston2 on 09/01/06 10:53AM
[ Reply | Permalink | Report ]

On 2006 predictions:

A new thought... virtualisation is quite good nowadays: you can run one OS inside another with relatively little hassle or performance hit. I've thinking of things like VMware, QEmu, Xen etc. How about if VirtualAcorn came up with a basic Linux distribution that ran VRPCforLinux? They would ship a CD with a disc image of this on. Also shipped would be emulators/virtualisers for a number of target platforms (Linux/x86, Windows, Mac OS X/x86). So you could either install the basic Linux distribution resulting in a standalone VRPC machine, or install the virtualiser and emulate Linux emulating RISC OS. That sounds slow, but modern virtualisers have little speed impact if they're on the same CPU architecture, and forthcoming processors will have specific support for virtualisation. Any changes to the underlying OS/libraries/etc just require an updated virtualiser which might even be part of the OS distribution (eg QEmu comes as a Debian package).

The problems I can forsee are graphics card and host access, but those aren't insurmountable.

 is a RISC OS Usercaliston2 on 08/01/06 5:44PM
[ Reply | Permalink | Report ]

On Archive booklets review part one:

mrchocky: I second that. I wouldn't mind too much if there was an 'it's unsupported, it's up to you to make it work' release that users could support themselves. Maybe as a supplement so you have to buy the Windows VRPC as well (which /would/ get support so you aren't completely in the cold). If there was enough documentation on exactly what is going on underneath so users would be able to understand the issues rather than make guesses (as is often the case with Windows) then user support should be feasible.

 is a RISC OS Usercaliston2 on 13/12/05 1:36PM
[ Reply | Permalink | Report ]

On Archive booklets review part one:

The trouble with doing published tutorials in C is that it's so verbose. So unless you have some Yellow Pages for listings with minute print it's hard to lay out an article on paper with the listing nearby. Even more so in A5 format. Either you write everything very compressed:

#include "window_defs.h" typedef struct window_size{ int minx; int miny;} Mine; int myfunc(Mine *awl){ return awl->minx*awl->miny+getwindowsize(ICONBAR); }

or don't define things properly as in BASIC

int myfunc(int *awl) { return awl[0]*awl[1]+gwindsz(-2); }

Especially if you're trying to program everything from first principles without using libraries. This is particularly bad in a magazine article, but less so in a book where there's hopefully more space. It depends how much effort has been spent reworking the original articles. I can't remember what the originals were like to comment on them specifically though.

 is a RISC OS Usercaliston2 on 12/12/05 7:08PM
[ Reply | Permalink | Report ]

On PC card software released under GPL:

Hah! Given the contents of that file are only: copy *.a* good copy armdrv.* good copy *.bat good I think your virus checker is mistaken :-)

 is a RISC OS Usercaliston2 on 3/11/05 8:07PM
[ Reply | Permalink | Report ]

On PC card software released under GPL:

bernie: I have no idea. Googling for bat/rb1 produces no information on what this trojan is. Says it dates from 2004 but all the files in the archive date from 2000 or earlier. I suspect it's a false positive.

 is a RISC OS Usercaliston2 on 3/11/05 3:48PM
[ Reply | Permalink | Report ]

On PC card software released under GPL:

wm: The Elvis schematics have a 486SLC, SIMM, IDE etc. I don't think the source to Elvis versions is included (it's just evolved so compatibility might have been broken). A binary can be found at: [link]

 is a RISC OS Usercaliston2 on 3/11/05 3:43PM
[ Reply | Permalink | Report ]

On PC card software released under GPL:

If anyone wants to poke around without downloading the whole thing I've put up the directory structure at: [link]

Note that it uses ,xxx filetype extensions and MIME types are broken, so everything will download as text - use 'Save link as' or whatever.

This structure may disappear without notice (though unlikely in the next few days) and will do so when Peter puts up a catalogued version.

 is a RISC OS Usercaliston2 on 3/11/05 1:35PM
[ Reply | Permalink | Report ]

On PC card software released under GPL:

It's a tar file which has been compressed with bzip2. You'll need a bzip2 decompressor - a command line version is in the Unix Porting Project.

It unpacks to about 90MB. There is indeed a Releases directory which contains various versions as shipped, including network links.

There is a /lot/ of source in there, including x86 assembler for the various PC-side drivers. Quite a bit of interesting documentation too - including full schematics of the Elvis (PC on podule) cards.

 is a RISC OS Usercaliston2 on 3/11/05 1:14PM
[ Reply | Permalink | Report ]

On News in brief:

It's been a decade since I looked at the PDF format, but is PDF significantly harder to create than Postscript? It seems to be that Draw maps fairly well onto PS - would ArtWorks too? If so, how much work would it be for AW to generate its own Postscript without using the printer driver? Then you could run this through ps2pdf - which has many, many options for things like ways to encode images, colour mopels etc, even if most people don't know they're there.

 is a RISC OS Usercaliston2 on 10/8/05 8:09PM
[ Reply | Permalink | Report ]

On 'Community' newsgroup proposed for RISC OS users:

steelpillow: No, I'm being serious. The point of hierarchies is to aid classification. alt.* is a hierarchy just as any other. We'd be flamed for suggesting comp.riscos.*, so I don't see why alt.* is any different. I only have experience of big-8 group creation, not alt.config, but I think any discussion in alt.config is going to ask why we want to create a new second level hierarchy. In fact, they specifically discourage second level group creation in the alt creation FAQ: [link]

Just because alt.archimedes.bugs exists isn't good precedent: its propagation was bad enough that I had to ask my newsadmin to add it last week. Getting servers to carry the new group is going to be the biggest problem, and that's more likely to happen if it goes through alt.config. Hence we need to listen to what the alt.config people say.

 is a RISC OS Usercaliston2 on 8/8/05 10:53AM
[ Reply | Permalink | Report ]

On 'Community' newsgroup proposed for RISC OS users:

Is it really necessary to create yet another second level hierarchy in alt.*? There's a perfectly good alt.comp.sys.* hierarchy there - what about alt.comp.sys.riscos.community?

 is a RISC OS Usercaliston2 on 7/8/05 2:29PM
[ Reply | Permalink | Report ]

On A9home form factor tempts DIY projects:


Funny you should mention putting an A9 in an A4 case, because about 3 years ago I was working on that. OK, so it was to be a custom ARM7500FE board instead of an A9, but the principle holds. I sorted out driving the mono A4 screen (see [link] ), the keyboard wouldn't have been too difficult (see [link] for the layout), and battery management could have been done with a bit of work (and an off-the-shelf charge controller from Maxim or similar). The same all applies to the A9, though I doubt the A9 could drive the rather strange A4 mono LCD panel without some extra logic, and I've yet to see whether the SM501's LCD outputs are wired anywhere. The A9 however is too large for the A4 case :( However it would be possible to design another carrier board to take Simtec's ARM9-onna-stick (you'd have to buy an A9 first to get the RISC OS licence anyway) that fit in the A4 case. With a bit of case fiddling you might get a colour LCD in there, but not more than 9" since that's the size of the case.

RISC OS 5, VRAM, USB2, DVDRW, GPS, surround sound etc are left as an exercise for the reader ;-)

 is a RISC OS Usercaliston2 on 18/7/05 10:17AM
[ Reply | Permalink | Report ]

On Cambridge RISC OS meet up planned:

Possibly to due the presence of silversmiths (well, someone had to make all that college silverware): [link] (page 9)

 is a RISC OS Usercaliston2 on 11/7/05 12:50PM
[ Reply | Permalink | Report ]

On CJE RAM special offer not so special:

Assuming it works in FPM as well as EDO mode, that should work in a Risc PC.

 is a RISC OS Usercaliston2 on 24/6/05 4:57PM
[ Reply | Permalink | Report ]

On Distributing software with RiscPkg:

Oooh, an example. I installed Adjust a few months ago. As a power user, did I a) want everything taken care for me by the installer or b) want to do it by hand? I prefer a) because it meant I didn't have to spend half a day tweaking things to bring over all my previous configurations manually. The installer just did what it was supposed to do and I could make a cup of tea. This is what computers are good at - tedious repetitive tasks - and whilst it's nice that it's transparent so I can see what's happened if I really want to, I shouldn't have to open the bonnet every time I want to drive the car.

 is a RISC OS Usercaliston2 on 24/02/05 11:23AM
[ Reply | Permalink | Report ]

On Distributing software with RiscPkg:

One way of looking at RiscPkg is it's a (semi-)centralised archive of software like HENSA was. But it just happens to be designed in such a way that it can also automatically install. So if you really want to install everything manually, it's no different from downloading stuff from HENSA or the author's website. It's just a bunch of zipfiles after all. But if you would rather your machine took charge of installation then you can do that too. It just means a reduction in the higgledy-piggledy way software is packaged and distributed at the moment.

Remember that you don't actually lose much control over the current situation. Applications are still applications and largely self-contained, and there's nothing to stop you deleting a RiscPkg managed application. You'll just have the same consequences as now if other things depend on it - in fact it's better than that because the database says what depends on it. Even if applications are forced to be stored in a certain place (perhaps not the case in future) then it's no too hard to create link applications (like AddApp does in Resources:Apps) that you can keep whereever you like to run the program. And at the end of the day the package state is still visible, so if you really want to convince RiscPkg that version 99 of GCC is installed, you just have to change the database textfile. Whilst none of these things are recommended, in the same way that fiddling witht the inside of !Boot isn't, nothing is stopping you if you insist.

 is a RISC OS Usercaliston2 on 24/02/05 11:14AM
[ Reply | Permalink | Report ]

Recent articles and quickies

  • Distributing software with RiscPkg
    Essential How-to for developers
     41 comments, latest by gdshaw on 25/02/05 6:59PM. Published: 22 Feb 2005

  • Select hardware profiles uncovered
    But it's elementary, my dear Watson
     5 comments, latest by caliston2 on 2/1/05 5:59PM. Published: 1 Jan 2005

  • Internationalising RISC OS
    Unicode, i18n and more explained
     30 comments, latest by caliston2 on 16/7/03 8:57PM. Published: 10 Jul 2003

  • Search the archives

    Today's featured article

  • Article graphics insight
    Easy when you know how
     10 comments, latest by thesnark on 21/8/04 10:59PM. Published: 18 Aug 2004

  • Random article

  • RISC OS 5.06 Release
    Bugs fixes and improvements
     6 comments, latest by mugent on 15/5/04 1:27PM. Published: 12 May 2004

  • Useful links

    News and media:

    Top developers:
    RISCOS LtdRISC OS OpenMW SoftwareR-CompAdvantage SixVirtualAcorn

    CJE MicrosAPDLCastlea4X-AmpleLiquid SiliconWebmonster


    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
    "We accept Drobe likes to be [controversial], no problem there - but a sinister pattern has appeared over the past year or so"
    Page generated in 0.4617 seconds.