Slashdot Mirror


Contiki Ported To x86

lt writes "The ultra-small Contiki OS has now been ported to the x86. This should give those of you who have an old x86 PC that is too small to run even the smallest of Linux variants, a chance to browse the web, set up a web server, and doing other essential stuff. If you're curious to see how it looks, there is a live VNC demo running."

61 of 243 comments (clear)

  1. No wonder by Anonymous Coward · · Score: 3, Funny
    1. Re:No wonder by -brazil- · · Score: 3, Informative

      Nope, "US billion" was meant to clarify that it's 10^9; in other countries 1 billion = 10^12.

      --

      The illegal we do immediately. The unconstitutional takes a little longer.
      --Henry Kissinger

  2. VNC by jrockway · · Score: 5, Interesting

    I have to say that running VNC on an 8bit computer is amazing. I would have looked at the screenshots, but actually playing around is so much more fun! It makes me want a C64 or old intel computer to run this on :) Does anyone know how to enter an arbitrary URI though, I couldn't do it.

    On another note, for those who thought VNC over 100BaseT was slow, it's even slower when running at 3KiB/s :) Oh well, this will be the first article to ever slashdot a VNC server, I think.

    --
    My other car is first.
    1. Re:VNC by usotsuki · · Score: 3, Informative

      8086 is 16-bit ;)

      Interestingly enough I (in the past week) have thought about implementing Contiki on top of CP/M-86 4. CP/M-86 4 is a rather small OS, and can optionally run DOS programs (the infamous DOSPLUS), and I think, with tools I can easily find for free, I can code low-level stuff for it.

      It can be done. IWBN, too.

      -uso.

      --
      Dreams, dreams, don't doubt dreams, dreaming children's dreaming dreams. Sailor Moon SS
    2. Re:VNC by iantri · · Score: 2, Informative

      Whoops.. my mistake.

      The 8086 came first, and was 16-bit throughout.
      The 8088 was designed to be cheaper, as it had an 8bit external data bus.. but the processor was 16-bit.

      http://firstpc.no-ip.com/en/8086/page02/x86c.htm

      That page is running on an 8086, BTW.

    3. Re:VNC by ajs318 · · Score: 2, Informative

      No, you're wrong. The 8088 has a 16-bit internal architecture, however, it only brings out 8 data lines - so "word" transfers take 2 clock cycles, but you needed only 8n one-bit-wide RAM chips and one 8-bit-wide *ROM chip for the memory. Bear in mind memory was expensive when these things reigned supreme! The 8086 requires 16-bit-wide memory, hence 16n one-bit-wide RAM chips and two 8-bit-wide *ROM chips. I think it has a compatibility mode whereby it can access memory and I/O devices in 8-bit bytes rather than 16-bit words.

      --
      Je fume. Tu fumes. Nous fûmes!
    4. Re:VNC by gearry · · Score: 2, Informative

      Just to clarify, they say that it CACHES 10 lookups in the table, and that the size of this table is configurable at compile time. So, you can lookup any domain, but it will slow you down, and on this system the difference between a cache hit and a lookup will probably be significant. However, as the link you provided states, their DNS implementation is not heavily tested, so some domail lookups may fail unexpectedly.

      --
      like g-a-r-y, only different
  3. As it will be slashdotted... by Anonymous Coward · · Score: 3, Informative

    Some info before it gets toasted

    The web pages you are watching are served by a web server running under the Contiki operating system on an an Ethernut embedded Ethernet board, which consists of a 14 MHz AVR Atmega128 microcontroller with 32 kilobytes of RAM and 128 kilobytes of flash ROM, and a RealTek RTL8019AS Ethernet chip.

    Local Remote State Retransmissions Timer Flags 80 210.214.211.245:1166 FIN-WAIT-2 0 91 80 210.49.61.249:4000 ESTABLISHED 0 3 80 216.15.124.126:61657 FIN-WAIT-2 0 25 80 209.210.4.252:54730 ESTABLISHED 0 1 * 80 200.164.245.202:33548 ESTABLISHED 0 3 * 80 216.15.124.126:61654 FIN-WAIT-2 0 21 80 217.72.69.144:1077 SYN-RCVD 0 3 * 80 208.191.17.177:1937 ESTABLISHED 0 3 * 80 172.137.24.29:3071 SYN-RCVD 6 43 * 80 208.19.133.132:38209 ESTABLISHED 0 1 * 80 192.35.35.35:35197 ESTABLISHED 0 3 * 80 66.32.100.20:57348 ESTABLISHED 0 1 * 80 160.36.251.198:56226 FIN-WAIT-2 0 4 80 160.36.251.198:56225 ESTABLISHED 0 3 * 80 160.39.180.236:53790 FIN-WAIT-2 0 36 5900 67.82.242.97:27960 ESTABLISHED 0 3 * 80 200.164.245.202:33549 ESTABLISHED 0 2 *

  4. story translation by circletimessquare · · Score: 5, Funny

    the smallest os for the weakest puniest computers still in existence goes live.

    click on this vnc link here to blow to smithereens.

    --
    intellectual property law is philosophically incoherent. it is your moral duty to ignore it or sabotage it
  5. Live VNC by alta · · Score: 5, Funny

    Why don't you go ahead and say, "There was a live vnc running", or maybe "or maybe there might be a live vnc running in the distant future" but never say "there is a live vnc running..."

    --
    Do not meddle in the affairs of sysadmins, for they are subtle, and quick to anger.
  6. Re:Heh by rtaylor187 · · Score: 3, Funny

    Yep /.ing is a cross-platform "feature" - works against Windows, Linux, and Contiki servers!

  7. Specs, just in case by Cali+Thalen · · Score: 4, Informative
    The web pages you are watching are served by a web server running under the Contiki operating system on an an Ethernut embedded Ethernet board, which consists of a 14 MHz AVR Atmega128 microcontroller with 32 kilobytes of RAM and 128 kilobytes of flash ROM, and a RealTek RTL8019AS Ethernet chip.
    I'll be seriously impressed if this thing survives the morning
    --
    Chaos, panic, disorder...my work here is done.
    1. Re:Specs, just in case by JukkaO · · Score: 2, Funny

      Dolt...maybe the REST of the post was a little informative, not just the tiny comment at the end?

      No, the rest was redundant :)

      --
      .SIGSEGV
  8. New headline for article by BillBrasky · · Score: 5, Funny

    This just in!

    14 MHz web server Slashdotted! Oh the humanity!

    1. Re:New headline for article by suwain_2 · · Score: 3, Interesting

      I'm real impressed. It's 14 MHz and it's still running for me. Slashdot can bring down a top-notch server running a fine-tuned install of Linux, but not a 14 MHz box?! It's showing 17 current connections.

      Having a 14 MHz box survive a Slashdotting is a _real_ good ad for the OS it's running. :)

      --
      ________________________________________________
      suwain_2 :: quality slashdot p
  9. Re:Wow! by UnknowingFool · · Score: 3, Funny
    This should run like the clappers on my old 486/25sx

    What the hell is a 486? :)

    --
    Well, there's spam egg sausage and spam, that's not got much spam in it.
  10. holy melted silicone, batman! by Lord_Slepnir · · Score: 5, Funny
    live VNC demo running.

    What kind of sick bastard would slashdot a VNC connection? It's bad enough when you do it to an image file server or a site with a video or ISO, but a VNC CONNECTION on a computer that is too low powered for even Linux? What is wrong with you people?

  11. A Post-Modern Cool Idea by rwiedower · · Score: 3, Informative

    Here's a link to a screenshot of an old /. entry about said OS. It would've been cool if the "live" VNC shot was of this slashdot discussion, eh?

  12. Pushing the limits of computing by groove10 · · Score: 5, Insightful

    Kudos to Adam Dunkels for pushing the envelope of 8-bit computing. Many people will say "whats' the point of this." or "This has no application whatsoever and is a waste of time." but I disagree. Adam is making software and designing methods of programming to run internet based programs on chips and systems that where never designed for it, like the Atari Jaguar the Atari 8-bit console not to mention the C64. This work will allow others to get the motivation to push the envelope in other areas of computing as well.

    It seems Adam has what was once prevailant in the computing and electronics industry. Tinkering and programming for the sheer joy of creating something new. In this way, programming and building systems like this are very similar to creating a piece of art, contrary to public opinion and modern developments in computing. Keep up the good work Adam. You are an inspriation to hobbyists in all fields.

    --
    MMORPG fan-boy? Prove your worth
    1. Re:Pushing the limits of computing by Anonymous Coward · · Score: 4, Interesting

      I think it also shows what can be done with limited resources. The deverloper has to create more efficiant code. In today's OSes, the bloat of the code is horrendous, ala windoze. Even the "cooler" OSes, like Linuz, have much code that is sub-optimal.

      They say with faster CPUs and more memory will take care of that. Therefore, they can just keep piling on the crap code without thinking of resource constraints, i.e. - memory, cpu power. How long can this really last?

      I commend the people who have worked on this OS. Some may see it as useless, I see it as hope that there will be better OSes built in the future, once the physical limits of the modern computer are reached.

    2. Re:Pushing the limits of computing by k98sven · · Score: 2, Informative

      Steady on old boy. The jaguar was a 64-bit console, and a damn fine one at that.

      Well.. let's be really correct here, it was a 32/64-bit machine.
      (32 bit processor)

      In my book it counts as a 32-bit machine, but in any case, it's quite a far cry from an 8-bit machine.

    3. Re:Pushing the limits of computing by Enonu · · Score: 4, Insightful

      Those who think paying attention to resource constraints is useless are frankly a danger, and shouldn't be near a compiler. It's like haphazardly designing a car, and thinking that the airbags will save the passengers if there is an accident.

      However, there's a limit to optimizing code for efficiency's sake (both size and speed). From years of experience developing software, assembler up to Java, keeping your algorithm general allows it to be adaptable and maintainable. Nothing sucks more than spending days rewriting code because one number changes in the spec (yes, you can optimize that far).

      As for writing "bloat" code, writing huge software systems in a timely manner in today's marketplace **implies** this situation. When you don't have to perform mundane chores in your code, you are free to produce more faster, and this is what companies want, and in fact, pay you for. It's a sad situation, but it's a dog-eat-dog world, and the consumer cares less about quality these days.

      You also bring up an interesting point about when we'll hit the ceiling for computing power. I'm sure there's a real physical OPS/cm^3 limit (the only way to make it faster is to make it larger) but who knows what that is, or when we'll hit it. It'll be interesting to see how it'll affect the code produced. I'm hoping it's some type of golden age, where everbody has the same amount of standard computing hardware, and all code is made to this perfect, end-all spec.

      -- If you optimize everything, you will always be unhappy. (Knuth)

  13. Neat, now let's talk practical. by stratjakt · · Score: 4, Interesting

    Besides the nostalgia/geek factor of running a web browser on your C64 (which I've been doing for years, well cheating by using the 64 as a dumb terminal and running lynx)

    Maybe a Contiki based PDA? Contiki based email stations? Seems you could make such things dirt cheap using this as the OS.

    --
    I don't need no instructions to know how to rock!!!!
    1. Re:Neat, now let's talk practical. by Bonker · · Score: 3, Insightful

      Practical? How about a good solution for impoverished communities worldwide that need web access to do things like report on the ways they're being repressed, tortured, enslaved, etc?

      If a community can buy a single 386 and accompanying network setup for $100, then they can probably get a c64 quality computer for around $20, saving $80 of those dollars for things like food and bromine tablets for water purification.

      --
      The next Slashdot story will be ready soon, but subscribers can beat the rush and slashdot the links early!
  14. Birds sing words and the flowers croon... by smittyoneeach · · Score: 3, Funny

    ...in Contiki, tiki, tiki, tiki, tiki room!

    --
    Get thee glass eyes, and, like a scurvy politician, seem to see things thou dost not.--King Lear
  15. Pre-emptive multitasking? by Daniel+Phillips · · Score: 3, Informative
    From the FAQ:
    Does Contiki support pre-emptive multitasking?

    No, Contiki does cooperative multitasking. The reason for not supporting pre-emptive multitasking is that it would unnecessarily increase the complexity not only of the operating system, but also of the applications that would run under it. Pre-emptive multitasking is primarily useful in general purpose multiuser operating systems such as *nix, or in real-time systems where response time is critial. Contiki does not fit in either of those categories.
    Hah, apparently this didn't stop the Geoworks people from pulling off a fully preemptive OS on the lowly 8088.
    --
    Have you got your LWN subscription yet?
    1. Re:Pre-emptive multitasking? by mirko · · Score: 2, Informative

      Pre-emptive multitasking indeed costs more in system resources than cooperative.
      Compare the fluidity of RiscOS with the fluidity of a Linux machine.
      The first is used in many real time applications, like datacasting, black boxes, etc. while the second is good for server and desktop but not really for real-time demanding apps.
      Simply because in a cooperative system, you know when an event shall occur.

      --
      Trolling using another account since 2005.
    2. Re:Pre-emptive multitasking? by david.given · · Score: 4, Informative

      Also, preemption on some processors is an incredible pain: for example, the 6502 has a single, fixed address, 256-byte stack. In order to preempt a process on the 6502 you'd have to manually copy the entire stack somewhere else in memory, and copy another process' stack in. Not pleasant.

    3. Re:Pre-emptive multitasking? by Daniel+Phillips · · Score: 2, Informative

      ...the 6501 chip in the C64 limited you to 127 byte either direction relative branching. Anything else had to be handled by an explicit jmp, which meant you couldn't dynamically load your program into other areas of memory (unless you had isolated branch instructions within 127 bytes of every call and didn't use a single jmp - *nearly* impossible) - which kind of blows serious multitasking!

      You are talking about relocation, which has nothing to do with multitasking

      Anyway, even code with absolute branches can be loaded wherever you want in memory, it just means the loader/linker has to be able to do the necessary fixups.

      --
      Have you got your LWN subscription yet?
    4. Re:Pre-emptive multitasking? by johannesg · · Score: 2, Interesting
      AmigaOS manages to multitask, preemptively, using very few system resources, and still have excellent real-time characteristics. So does QNX. The secret is that both AmigaOS and QNX use a microkernel instead of a monolithic kernel.

      I don't see how you can reasonably do real-time computing without preemption. It would mean timeslicing each process by hand, which (especially for large tasks or tasks that scale to large datasets) is nearly impossible to get right. RiscOS, I believe, moved to a preemptive model later in its life (correct me if I'm wrong) for precisely this reason.

  16. Great VNC link! by not_a_george · · Score: 3, Funny

    wow that OS kinda looks like a page full of characters.. oh wait
    poor little server
    {meanwhile, somewhere else in the worl)
    wow, we have a link on slashdot!
    QUICK, WHO WANTS TO ROAST SOME MARSHMALLOWS!

    --
    Linux: Helping nerds look smarter since the late 90s.
  17. Hack gratia hacking by Futaba-chan · · Score: 3, Interesting
    Somewhere in the depths of my basement, I have an old AT&T 7300 (MC68010-based "Unix PC") with an on-board 8088 PC emulator card that can run old DOS programs. I used the 7300 and some low-level hardware libraries that another hacker wrote in the late 80s/early 90s as my target machine for OS hacking back before I got scooped by Linux. I'm tempted to haul the thing out, snag the Contiki x86 distro, and hack something together to make the two talk to each other.

    Hmm, and with a StarLAN to 10baseT router, I could get the resulting beastie on the net. Hmm....

  18. Am I the only one by miyako · · Score: 2, Interesting

    who's first thought was to try and install this OS on a 3gz system with like a gig of ram?

    --
    Famous Last Words: "hmm...wikipedia says it's edible"
    1. Re:Am I the only one by AT · · Score: 4, Informative

      Since it runs on an 8088, it must use the x86 "real" mode, instead of protected mode. Which means that only 1MB of memory is addressable, so the gig of RAM is irrelevent. Contiki would only use the first 1MB.

      I'm sure it would be plenty fast at 3ghz though :)

  19. Re:Wow! by Urkki · · Score: 3, Informative

    Linux should run pretty well on that too, even with X if you have enough memory.

  20. Not the first.. by iantri · · Score: 5, Informative
    These people were long beaten.. you can run a server on an XT with EZNOS (it also acts as an LPD print server!) or one of serveral other packages..

    http://www.eznos.org

    Here's an XT running EZNOS.. there's also other 8088/87 projects, a 386 and other stuff.. neat.

    Also, a web server running on the original IBM PC.

    I've been wating to get these people slashdotted ;)...

  21. Re:Wow. by larien · · Score: 2, Insightful
    Depends what you want to serve up. Sure, it won't be much use for a fully featured e-commerce site, but for a small document server (e.g. for FAQs) I'm sure it'll do fine.

    Bear in mind the first web servers in the early days of the web were probably running on something of a similar CPU power to a 386.

  22. damn! No Sinclair ZX80 port!! by pair-a-noyd · · Score: 2, Funny

    I've got a mint condition ZX80 that I want to run a webserver on. Man, all my hopes and dreams dashed to hell.

    Oh well, the CoCo will handle it though, all is not lost!

  23. What about Minix by RevMike · · Score: 2, Insightful
    Kudos to the Contiki folks. I don't think this is useful, but if they enjoyed themselves doing it, all the better for them!

    This should give those of you who have an old x86 PC that is too small to run even the smallest of Linux variants, a chance to browse the web, set up a web server, and doing other essential stuff.

    If you have an old pre-386 machine around, why not run Minix? That should make a far more useful machine.

  24. If you want something more useful by edwdig · · Score: 4, Informative

    If you'd like to do something more useful with an older system, check out GEOS. It's currently being maintained by Breadbox, who has a demo available for download. Full preemptive multitasking. Comes with a web browser (HTML 4.0, no CSS or JS), email (POP3), AIM, FTP, News Reader, and a roughly MS Works level office suite. More software is available from it at Tva Katter.

    Older versions would run on an 8086 (one of the original design goals was that the WYSIWYG word processor could keep up with your typing on an 8086). The current version requires a 386. 2 megs of RAM should be fine for most things (even 1 will work ok), although you'd probably want at least 4 or 8 megs for browsing the web.

    1. Re:If you want something more useful by drinkypoo · · Score: 2, Informative
      Just some random babbling on the subject of GEOS; Palm Computing's first PDA was the Tandy/Casio Z-PDA 7000 Zoomer. It was Palm's in the sense that the entire software 'suite' was their work. They used PC-GEOS, the zoomer was a V20-powered PC with an LCD display. It also came with (or you could at least buy this separately) PC-GEOS with a file link feature.

      It's possible to load PC-GEOS onto a GRiDPad 1910, which is another ancient machine, then load Graffiti handwriting recognition from Palm for Zoomer on it, and get a large PDA. Now if only I had all the applications from the Zoomer. (Mine died some time ago.)

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
  25. Re:neat but seriously how useful? by pdbogen · · Score: 2, Informative

    What Linux distro is similar to Contiki?
    Linux From Scratch.

    like RedHat, Gentoo, Suse that runs on a 486 with superior performance and uses virtual no resources like Contiki?
    Yes.

    but what REAL available distros are available?
    Linux From Scratch.

  26. Hold your misspellings, Robin! by swb · · Score: 4, Funny

    Silicone is for making tits bigger and keeping water in the tub.

    Silicon is what chips are made of.

    1. Re:Hold your misspellings, Robin! by -brazil- · · Score: 5, Funny

      Ha! Everyone knows chips are made from potatoes.

      --

      The illegal we do immediately. The unconstitutional takes a little longer.
      --Henry Kissinger

    2. Re:Hold your misspellings, Robin! by kin_korn_karn · · Score: 2, Funny

      you just took the starch out of THAT argument.

  27. Nooo!!! by Zebra_X · · Score: 3, Funny

    Haven't we abused this poor machine enough. Just several weeks ago it was the victim of a slashdotting. Now once again the moderators seek to wipe it's presence from the net.

    Silly embeded computer, web serving is for servers.

  28. Implement this in a wristwatch/ring anyone? by janimal · · Score: 2, Interesting

    Whoever said this has to do with old computers?! How about getting this running on a PIC? Having a wristwatch (a SMALL one!) or a grad ring act as a web server or some real functional computer would be really cool.

  29. Re:Wow! by Wumpus · · Score: 3, Funny

    It's a 386 compatible CPU featuring pipelined execution and an onboard FPU. Pretty neat, huh? Those puppies can be pushed to speeds in excess of 100MHz.

  30. Java port to C64!! by henriksh · · Score: 4, Informative
    Ok, this seriously made my day! From the Contiki web site:
    [...]it should be noted that Brian Bagnall actually is working on porting/implementing a Java virtual machine for the C64.
    A Java implementation on the C64??! I'm speechless!
  31. Re:I just hope ... by brakett · · Score: 2, Interesting
    When I was a child (1990 give or take) there was an norwegian computer brand called tiki. Rumor had it that they originally called it kon-tiki, but because Thor Heyerdahl owned that name they had to change it.

    This is just vague memory thou....

    What i do know is that the tiki 100 was popular in norwegian schools in the 80s....

  32. 1541? by rabidcow · · Score: 3, Interesting

    So if it'll run on a C64, will it run on a 1541 disk drive? A GUI would obviously be out, but the processor is essentially the same as the C64 (6502 vs 6510), and it would be amusing to have a web server running on a floppy drive.

    1. Re:1541? by yomegaman · · Score: 4, Funny

      Yeah, if only that processor in the 1541 had some sort of mass storage device attached to it...

      --
      ...wearing a skin-tight topless leather jumpsuit, with cutaway buttocks and transparent crotch panel.
  33. From BEYOND THE GRAVE!!! by digitalgiblet · · Score: 4, Funny
    I just hope Thor Heyerdahl doesn't slap him with a patent suit.

    MAN! Everybody's suing these days. Old ladies who pour scalding coffee on their crotches, smokers, gun nuts, now DEAD anthropologists? Where will the madness end?

  34. It's still alive! by Steeltoe · · Score: 3, Informative

    It's still running. I didn't download their client since I have both TightVNC and ordinary VNC from before. And it worked!! I just had to reconnect after one failed attempt.

    These guys know what they're doing. Impressive indeed!! I got to change Window, and delete some text, then go to the addressbar and delete some more and trying to write in an address. But there were 7 other people connected too, doing other things. If I were alone, I bet I could've used the machine just fine.

    Come to think of it, I still got my old dusty C64.. Maybe it's time to revive it ;-)

  35. Re:Cute! by 1u3hr · · Score: 2, Informative
    As for old x86 systems, 19K2 modems didn't even properly work with those, so it's going to be fun to have internet with those things

    RTFA: "An RS-232 (serial) card or Ethernet connection is required for Internet connectivity" so it should be fast enough.

  36. Not really by Sycraft-fu · · Score: 4, Insightful

    It shows that you can make a simple OS with minimal space. That does not mean that one could do the same of Windows (please, it just looks immature to name call) or Linux. They have far more features, and make far less assumptions, the this OS.

    A big one would be preemptive multitasking. All modren OSes have it, Contiki does not. Why not? To quote them "The reason for not supporting pre-emptive multitasking is that it would unnecessarily increase the complexity not only of the operating system, but also of the applications that would run under it." Ahh, so it would make things more complex (and also larger and less efficient) to use PMT. Ok, fine, but CMT makes the assumption that all the apps running are going to be well behaved, will not use more than their fair share of time, there will be no critical evens that need to interrupt them, and that an app won't hang and take the system down with it. Fine, but for your standard desktop or server, that's not a valid assumption.

    Or how about features like 3d graphics? I want to be able to use a 3d accelerator. Oooo, well now here's a whole different can of worms. All the 3d accelerators speak a different language, so we need to implement a common apstraction layer, like OpenGL. Then we need to have drivers to interface with that. Here we are talking tons more complexity and size, and much larger programs to boot. This is not even to mention the many other features most OSes have that it does not.

    See you can do a lot of huge optimization on a general purpose design by making assumptions and optimizing for it. Like a memory manager. Linux, Windows, etc all have fairly complex memory managers these days. It virtualizes memory for programs and juggles the actual RAM, it changes allocation in real time and protects programs from interfering with each other or the system. However, that wastes space and CPU cycles. It would be much more efficient to assume that all programs are going to play nice and know how much RAM they need. Then when a progam starts, it tells the OS what it wants, and the OS tells it what range of memory it may use. It is then up to the program to keep within its borders. MacOS actually used to use a system much like this. Efficient? Yes, however many problems. The fact aside that a program might want more memory later, this is a huge stability and security hole. Any program can bring down the whole system by accidently writing to system memory, but mroe scary is the security implication. All you have to do is get a service, ANY service on the system to execute code for you and you are in will full permissions.

    So there are plenty of things that mainstream OSes provide that a tiny OS like contiki cannot and willnot provide. This is not to bag on their accomplishment, it is a really cool OS and does get a lot out of old hardware. However do not assume that because they can make a simple CMT OS that runs a basic webserver on old hardware they could make an OS as powerful as a full featured Linux or Windows system fit in a couple MB. Not happening.

  37. No obsolete computers by Cyburbia · · Score: 2, Insightful
    These antique computers are as useful today as they were when they were first manufactured. I visited plenty of bulletin boards with my Atari 400, so text-based Web browsing really isn't something that's beyond the pale for old boxen.

    Do you really need Contiki to surf with an old X86? An 8086-based PC could be used to dial into a shell account, where you could use Lynx, telnet, and so on. College computer labs of the early and mid-1990s were filled with 286 and 386-based PCs, 68XXX-based Macs, and Sun Sparcstations, equipped with Mosaic and capable of surfing at decent speeds.

  38. Re: kudos to Adam Dunkels by King_TJ · · Score: 2, Insightful

    I completely agree! When I started realizing how many different platforms he has this OS running on, it hit me that this might finally allow cross-platform compatibility on all of these classic 8-bit systems that always wished for it, and never got it in their heyday.

    In a strange way, it's almost like completing unfinished business from the 80's!

  39. You are both wrong. by default+luser · · Score: 2, Informative

    The 8086 and 8088 are both 16-bit processors.

    They have 16-bit internal registers ( and utilize one 16-bit page register and another offset register to acheive 20-bit memory space ). The data bus is insignificant to the definition.

    The REASON "8-bit" is associated with the x86 architecture is BECAUSE the 8086 and 8088 are backward-compatible with the 8080, an 8-bit processor with a 16-bit address space.

    Remember folks, the general definition of the "bits" attribute of a processor is how many bits wide the main instruction path(s) is / are.

    Example: 80286: 16-bit registers, 24-bit address space, 16-bit memory bus.

    Example: 80386SX: 32-bit registers, 24-bit address space, 16-bit memory bus.

    Address space, memory bus width and instruction path width do not have to be the same. Do not assume they are tied together.

    --

    Man is the animal that laughs.
    And occasionally whores for Karma.

  40. Not quite: by turgid · · Score: 2, Interesting

    The 386 had no hardware floating-point. For that you needed an 80387 coprocessor (c.f. 80287, 8087). The "sx" in 386sx denoted "single word exchange" and dx "double word exchange". The 386sx had a 16-bit bus, so that it could be used in cheaper motherboards (basically 286 motherboards) and the original 386, later renamed the 386dx had a 32-bit bus. The original 486 was, like someone already said, an optimised 386 core (better pipelining, introduction of an 8k L1 cache, some instructions optimised for single clock-cycle execution etc.) with a built-in optimized 387. The result was a proecssor that was about twice as fast as the saame 386/387 combination at the same clock frequency. The 486sx was a marketing exercise to use up 486 cores with broken FPUs. The 487 "coprocessor" for these machines was really just a proper 486 with an extra pin which disabled the 486sx already installed. You could actually buld a PC with only a 487 using certain motherboards if you knew what you were doing.

  41. Re:Great Idea! by kasperd · · Score: 2, Informative

    And...some things won't work on a conventional turning machine, at least not in polynomial time.

    You are wrong about that. Anything that can be done on a conventional computer (or a RAM if you want a theoretical model) in polynomial time can also be done on a TM in polynomial time. However it will be a different polynomial. AFAIK at most you will add one or two to the degree of the polynomial. But in the real world it is less than that which seperates feasible from infeasible algorithms. Sorting slower than O(n^2) really makes the TM look slow.

    --

    Do you care about the security of your wireless mouse?