Sorry, i'm running behind, had a few urgent work projects lately but i'll get back to it this weekend. (tbh between work, house repair, books and saxophone it's getting tough to get any extra time)
No apologies! If you can pull it off it'll be fairly legendary

And if there's anything I can do to help, please let me know, I'd love to get involved but wouldn't really know where to start with getting OpenInkpot or their kernel compiled.
Grrr! I keep getting "corrupted octal value in tar header" - even when i'm just repacking your theme! I downloaded the theme, unpacked it, re-tarred it using: "tar -cf skin.tar skin.penguin-0.9" and gzipped it using: "gzip skin.tar" and renamed the file to skin.tgz, on restart it's always that error! Im using a macbook, any ideas?? Good work by the way!
Hey drcross.

I tar and gzip in one step using 'tar czf' - I think this might make a difference since tar just pipes it through gzip rather than gzipping the tar file.

If you've got a standard version of tar and gzip (preferably gnu tar for compatibility with the Cool-ERs busybox version of it) on your Macbook that should work.
Well, actually it's not that new anymore. Some may know it from the Dev Hub, I'm using it as example for the skin file anatomy.

I decided to finally present it "officially", that is, here. Originally I hoped to integrate it with a new versio of kewl-er, but it seems Codemonkey is on a hiatus. Well, no matter, should he find the time to work on it again I can always integrate it later.
The current installation procedure is taken from his kewl-er script. Without this, I would never have even started trying to manipulate the skin files :-)

In the meantime - why keep it from others, perhaps I'm not the only one who likes it? :-)

I suppose not everyone has read the text on the Dev Hub, so here are a few words about the theme:

It started as a try to create a klingon-like interface. Unfortunately, the system is far too inflexible to be useful for that.
However, a few things did work as intended, so while the result isn't all that klingon-like, it takes a few hints from klingons. :-)

Don't worry, I didn't just slap klingon symbols all over the place, nor is everything IN klingon.
The menus are the same as always too, as I didn't find a usable way to modify them without losing functionality or looking badly made, with mismatching colors all the time.

What I did change though is the status bar and a few pictures.

Here's a mock-up (including legend) for the status bar when you read a book:

image »

If you like it, download the full theme from here: KIDesign.zip.

You don't have to install it yet - just unzip and look at the startup/power-off pictures - they're nice, I think.

If there are problems with this theme, or you find an image missing(that is, an original showing through), just tell me. I'll try to correct it.

Installation instructions are within the readme file. It's easy and should work on any CoolEr, or perhaps even on non-CoolER devices, as long as they are EB600 and use a variation of the Netronix firmware.


If you give it a try, please remember - I did test it, and I am using the same files - but it still could happen that something goes wrong and you end up with a bricked device.
I don't expect this to happen, but you should backup all your files in any case. It doesn't hurt to be prepared, right?
Hey man. Yeah, sorry!
Work got hectic, then Interead went under. I got about 90% done on the new version, but with the lack of interest it hasn't really seemed worth the last bit of effort it would take for testing and things.
No problem, I guessed you'd have more important stuff to do.

I guess it would be time now to try to expand to non-CoolEr devices :-D
I got a Elonex device with the Cool-er firmware installed on it.

This is the error message i got when trying to install the penquin skin:

As far as I remember, codeMonkey only put that check there to make sure the versions match.

So this could mean you've got an older firmware version on your device - in which case I suggest you find a copy of the newer firmware and update it.
(Would be a good idea either way, I think.)

You probably could also modify the script to remove the check.


Bear in mind that there always is some risk involved. Do not try if you cannot accept this.

(Although I don't think it's much risk. But why should you trust my opinion, I've got nothing to lose if your device is bricked. Nothing to win either, of course.)