I can't be bothered replying to all the questions individually on the list about these two topics, so I'll combine them all into one email. Firstly, Z80.. ELKS used to support Z80, however support was dropped in about version 0.0.12 (IIRC). There is no reason at all why the code shouldn't be possible to reduce in size. Infact, 'reduce' isn't even the right word. There's no reason we shouldn't be able to patch up and not save space. Z80 doesn't need most of the bloated features that ELKS has at the moment. Things such as hard disk support and printer support simply aren't of much use on an embedded Z80 machine. Personally I believe that it's possible to make ELKS back into what it was originally targetted as (an embeddable OS). There is a list setup for z80 development, but it's been virtually dead for a while, despite a couple of attempts to revive it. It's on the same majordomo as the development list, and it's called "elks-z80". (email me if you need subscribtion instructions). Next, X.. Once again, X shouldn't be impossible to get working on a 'slow' system. Maybe we don't support every single feature, maybe we run daemons to handle things such as the fonts, colors and authentication. It should still be possible to get at least a reduced subset working. When I was in college a couple of years ago, we had an XT setup running windows, and the microsoft terminal program under it. Now, if MS can write an OS that'll do graphics and have a full UI (w/mouse) and so on, on an XT, a group of hackers from an Embedded Systems list should be able to shit all over that setup. (to put it bluntly) Davey
