Homebrew Microcontroller Laptop, Made of Wood
Brietech writes "This is a homebrew laptop project based on a Picaxe microcontroller. It has 16kb of RAM, 256kb of storage, sound and a self-hosted development environment! It has a simple CLI, file-system, 'EMAXE' text editor and a programming language called 'Chris#.' Oh, and yes, it runs Linaxe."
CPU: Picaxe 28X-1 Microcontrollers. The main CPU runs at a blistering 16 Mhz, and has a whopping 4 kilobytes of onboard storage for the processorâ(TM)s firmware/OS.
That's faster than my 11 or 12 MHz 286... of course, that was 17 years ago.
At least, if this laptop catches fire, it won't burn black, toxic, smoke like most laptops do.
It looks like he tried to host the link from his laptop :(
---- I'll take you in a Hunt deathmatch any day.
I don't know much about the PICaxe, but for $8 (single unit qtys) you can buy an 80MHz MIPS microcontroller with a lot going for it. This one has 32KB of onboard RAM and 512K of flash.
Program Intellivision!
What a total waste of time. Don't they have better things to do?
He built a laptop with his time. All you've done is post a whiney comment on slashdot. On the whole, I think it's you who needs some better things to do with their time.
...if you were in the woods with nothing but a hatchet, how long before you could send an email?
Depends, how many people do I have to kill to get to the PC?
Oh, that would be doable fairly quickly.
First, you need to find some pigeons or some other suitable birds. You will also figure out how to make something resembling paper (shouldn't be too difficult with all the wood in the woods), and some means to write (something suitable should be available as well)
Once you managed to train some of them to deliver messages, you send one asking for RFC791 and RFC793, unless you're a networking expert and know them from memory. RFC 792 would be also recommended. You will also need RFC 1149, but that one is short and is best memorized before you get lost in the woods. Optionally, RFC 2549 could provide better service.
The next thing to do is to implement RFC 1149, and use that to talk to a mail server. Anybody with some mail experience should know how to use mail over a telnet session. Just make sure to memorize the IP addresses of a SMTP and a POP3 server (no problem if you run your own server and remember the address). Then just connect and send something like:
Then to read email:
Latency could be a bit annoying with having to send all those pigeons back and forth, and a good spam filter would be needed server-side if you don't want to spend weeks getting rid of it before you get anything useful, but in a couple of weeks it could be done.
Once this is going, the next step would be starting an open source project to implement IP over smoke signals, or optical telegraph, in case something happens to the pigeons, and to reduce latency. Also implementing DNS would help with talking to the rest of the net.
Once all this is working you can start really improving your tech, by requesting pages from wikipedia on anything you don't know enough about.