Slashdot Mirror


Bringing Back the PDP8

Anne Thwacks writes " Andrew Grillet has decided that the Digial PDP8 - the first ever minicomputer, will rise from the dead. He is calling it the PDQ8. Sure others have done software emulations, and even hardware clones, but he is not just building a hardware clone, but trying to revive the whole idea of 12 bit computers!"

365 comments

  1. TRS80 by ClamClit · · Score: 5, Funny

    ...and I building a 3.5 GHz TRS80 with a GIG of RAM and 2 5 1/4" 80 GB floppys. its the cats ass

    1. Re:TRS80 by ch-chuck · · Score: 2, Interesting

      DOn't laugh - IMSAI, which predates the TRS80, is soon to sell, for under $1000, a series two with 20Mhz Z8S180, 1 meg static memory, AND toggle switches and flashing lights! CP/M never ran so fast.

      --
      try { do() || do_not(); } catch (JediException err) { yoda(err); }
  2. what for by neotokyo · · Score: 3, Insightful

    while the geek factor may be high, what sort of 12-bit software is it going to run ? linux?

    1. Re:what for by mirko · · Score: 3, Informative

      RT11, of course :-)

      --
      Trolling using another account since 2005.
    2. Re:what for by Detritus · · Score: 4, Informative

      Probably OS/8, which if I remember correctly, was a multi-user operating system. You can run a multi-user system on a PDP-8 with 32KW of core.

      --
      Mea navis aericumbens anguillis abundat
    3. Re:what for by rainwalker · · Score: 5, Funny

      Now, I'm no expert on legacy computers, but a machine with 32KW of core sounds dangerous...suddenly my 80W Athlon looks puny!

    4. Re:what for by Waffle+Iron · · Score: 5, Funny
      while the geek factor may be high, what sort of 12-bit software is it going to run ? linux?

      In the bottom of a box somewhere in my basement, I've still got the BASIC source code for the Star Trek game we used to run on our high school's PDP-8. For each player's turn, it printed out the map of the current galactic sector along with any Klingon ships on the line printer.

      It's funny, I remember when we played that game we felt like we had godlike control over a mysterious and powerful machine. Now when I play computer games, I mostly feel like a twitching moron.

    5. Re:what for by dhogaza · · Score: 4, Informative

      OS/8 was a single user system. I wrote a multi-user kernel that ran multiple copies of OS/8 customized to hook into device drivers supported by my kernel. It supported virtual paging using a hardware hack first suggested by Richard Lary (the author of OS/8). We ran four or five users on a 32KW 8/E with a couple of RK05 drives.

      We never distributed it because paging performance without the hardware hack was very bad (every CDF instruction needed to be trapped and mapped in software) and the hardware hack was only developed for the 8/E and piggy-backed on one of the system boards destructively (i.e. once modified your 8/E wouldn't run without our hardware).

      But it was used internally by the company I developed it for until about ten years ago.

    6. Re:what for by CoolVibe · · Score: 2
      BSD might actually have ran on it. The 4.4BSD, maybe Reno or Tahoe. Heck, the 2.x BSD's might even be supported as well.

      I could of course be wrong, but I really think these PDP's ran UNIX. RT11 seems unlikely, since that was a PDP11 OS. Either some V[something] or a BSD unix ran ot it, I am almost positive.

      Please do correct me if I'm wrong of course. It's been a while, ya know :)

    7. Re:what for by Strike · · Score: 1

      Another one for the "what for" column - DR-DOS 8.0 expected in spring 2003

      New DR-DOS, w00w00! MS DOS IS AS GOOD AS DEAD NOW!

    8. Re:what for by red_dragon · · Score: 4, Funny

      I remember when we played that game we felt like we had godlike control over a mysterious and powerful machine.

      That must've been a nice feeling, I bet. In these days, the mysterious and powerful machine has god-like control over you!

      --
      In Soviet Russia, Jesus asks: "What Would You Do?"
    9. Re:what for by Detritus · · Score: 1

      I used to use a multi-user BBS (Bernard Klatt's 8BBS) that ran on OS/8. I thought it was multi-user but that may have just been the BBS software, not the operating system.

      --
      Mea navis aericumbens anguillis abundat
    10. Re:what for by dhogaza · · Score: 2

      Right, OS/8 gave you full control over the machine so you could write multi-user applications.

    11. Re:what for by Anonymous Coward · · Score: 1, Funny

      In Soviet Russia...

      (this one actually makes sense)

    12. Re:what for by dhogaza · · Score: 3, Informative

      OK, you're corrected :)

      The PDP-8 never ran anything remotely resembling Unix. The very first version of Unix ran on the PDP-1/7/9/15 18-bit family (a PDP-7 IIRC). The architecture of this family was similar in many respects to the PDP-8 and indeed preceeded the PDP-5/8 family. You can think of the PDP-8 as being scaled down from the earlier family's 18 bits to 12 bits. To make it cheaper, of course.

      The original Unix-written-in-C ran on the PDP-11 (the PDP 1/7/9/15 family version was written in assembly, IIRC). The first BSD version of Unix was written for the VAX family ...

    13. Re:what for by limekiller4 · · Score: 1

      red_dragon writes:
      "Ah, kamisama! Ore no atama ni ono ga arimasu yo!."

      "Oh my god, my head has been opened!"?

      --
      My .02,
      Limekiller
    14. Re:what for by SigmundK · · Score: 0

      it's going to run netBSD probably, considering that netbsd runs on everything else

    15. Re:what for by dagnabit · · Score: 1

      Mmm.... TECO...

      I forget - does RSTS/E run on the -8? Or was it only on the -11s?

    16. Re:what for by Anonymous Coward · · Score: 1, Informative

      Welll, it looks like some of you young'uns out there need some educatin'. The PDP-8, first introduced in 1965 or so, came long before LINUX, in fact long before C's predecessor B, developed on a discarded Bell Labs PDP-7. It is a Good Thing for many reasons, though hardly novel. People have been inventing and reinventing the First Mass-Produced Personal Computer for years. Until the -8 was intorduced, no researcher who needed to directly record the results of an experiment every half a second could do anything but recruit an army of undergrads to listen to kludged-up data recorder results and punch same into paper cards, then wait in line for a few seconds of precious time on a university mainframe for meaningful information. At $18,000 (the price of a new single-family home or a top Rolls Royce), a researcher received a 250-lb 20x20x36" desktop box with front panel, 4 whole K-words of core, a Teletype to sit next to it with its paper-tape reader and punch + instructions on cobbling together interfaces to experiments and the Mainframe. Software was free and the company sponsored a club so anyone developing a useful program could get copies to the world. See Steve Levy's 'Hackers" for a result of the explosion of tech goodies this produced, including the beginnings of the Internet (just the concept of transmitting "hey look what I did" stuff to colegues was the original radical, exciting idea). Until 128-K DECTapes and 32K-word disks were tied to the PDP-8 and its successor 12-bit machines (why 12? Transistors cost $$2.50 each and adding a bit required at least 40 of them, a shorter word wasn't long enough and a longer word was too expensive for a *personal* computer), the PDP-8 had no operating system. You turned it on, toggled in the program (or a program sufficient to get it to read paper tape) into memory, 12 switches per word, hit the DEPosit key and do the next one, loaded the paper tape if need be and ran your program. The 8 was small but serious well-designed hardware. It was the first line of computers of which more than 100 machines *using* *the* *same* *software* were ever made! Until then, anyone with access to any two computers had to rewrite *everything* for even available high-level languages like FORTRAN and COBOL were not transportable. The 8 was so flexible and easy to use that it computerized the news wire services, Western Union, telephone switching, power plant (including nuke plant) operation, factories, basically the whole world (50K machines excluding the last 8's, based on the DEC/Intersil 6100 microprocessor). All with a design limiting total memory to 32K-words, 1K local pages and 4 K local address blocks. It shows you what people can do with a machine with SIX basic instructions, 4 "advanced" arithmetic statements , a group of 1 and 2-bit rotates and conditional executes , and a set of basic I/O instructions designed to send up to 7 instructions to each of 7 peripherals. So folks made the 1-microsecond clock PDP-8 do things today's programmers think require at least a 1 GHz 32-bit CPU, a quarter-GB of RAM and 4 Gig of disk space to do - and they did it in days, not months or years. Fact is that my Straight-8 is a curio, lovingly kept alive to provide people who learn beast through doing with the real thing (i.e. most of us if not all of us), a chance to get the look and feel of running a 1965-vintage computer. As for building a NEW system, I'd really like *every* would-be MicroSerf or even Linux project manager to spend their first year of learning to program hacking on a new PDP-8 - writing within the parameters of an existing machine with limits, instead of turning out flawed bloated garbage without shame, because they *know* that by the time their code gets published 2 years down the line, consumers will have already junked their inadaquate 3 Gig machines for 8-Gig machines with a 2GHz FSB connected to 4 GBytes of SuperRAM and a 3.5" 1 Terabyte drive. What's the old line about forgetting the lessons of history?

    17. Re :what for by Al+the+Traveller · · Score: 1

      I don't understand why but my long Re;WhatFor PDQ8 comment, ending with the line about the lessons of history was named to Anonymous Coward, not Al the Traveller, though I am he who wrote that stuff - points and comments on it here.

    18. Re:what for by Anonymous Coward · · Score: 0

      ETOS was another multi-user operating system that gave each user their own OS/8 playground. However, it was distributed.

      I'm not sure how it dealt with the CDF issue. There was a special piece of hardware to support ETOS, but I don't know what it did; it may have helped out with the CDF issue.

      The EE program at Utah State University used to teach BASIC on a pair of timeshared -8s running ETOS; one and 8/e and the other an 8/m, each with 32KW and a pair of RK05s. I once ran an experiment to see how many people could be logged onto a single machine. It thrashed horribly until I got the 13th user logged in, at which point it never left the idle loop. Presumably, it new there was no way it was going to get any work done with 13 users, so it didn't even try...

    19. Re:what for by Derleth · · Score: 1
      Now when I play computer games, I mostly feel like a twitching moron.
      That's called degenerative nerve disease.
      --
      How can you use my intestines as a gift? -Actual Hong Kong subtitle.
    20. Re:what for by Alien+Being · · Score: 1

      ETOS and EDUCOMP BASIC! I smell a wumpus!

      ^V halt

    21. Re:what for by AYeomans · · Score: 1

      But you might have to fix the date. As OS/8 used only three bits for the year, it experienced a preview of Y2K problems in 1978, when the date wrapped round to 1970.

      Not a record, though, the PDP-6 overflowed first.

      --
      Andrew Yeomans
    22. Re:what for by Empty+Threats · · Score: 1

      ITS!
      The Incompatible Timesharing System was THE OS of its day. When Unix was for newbies and wanna-be's, the hardcore hackers were having fun with their all-caps filenames on ITS.

    23. Re:what for by JebusIsLord · · Score: 2

      wasnt the original unix written in B?

      --
      Jeremy
    24. Re:what for by Anonymous Coward · · Score: 0

      A friend of mine and I wrote a humongous (for the PDP-8 under TSS/8 OS) Star Trek game in BASIC back in the late 70's when we were in college. It was the first program I ever sold, too. The program was about a dozen modules chained together, with the characters talking about the condition of the ship, the enemy, etc. Thousands of lines of code...probably the largest BASIC program for the PDP-8 ever written.

      I used the proceeds to have a pizza party for everyone in the computer lab.

    25. Re:what for by Anonymous Coward · · Score: 0

      OS/8 was a single user OS. Not a feature rich OS, but remarkably compact for its time. You are probably thinking of RTS-8 which was DEC's attempt at a multi-tasking OS for the PDP-8 sort of like RSX-11 became on the PDP-11's.

    26. Re:what for by just4now · · Score: 1

      Yes! You too can become President of the United States!

    27. Re:what for by WoodstockJeff · · Score: 1
      You can run a multi-user system on a PDP-8 with 32KW of core.

      I can speak with experience that the PDP-8 could run multiuser on EIGHT kilowords RAM, under DEC BASIC.

      I remember squeezing a 3-D space game into the smaller (1.5kw) user space, by using the random number function as a data statement, and replacing all the calls to it as READ statements...

  3. An idea by AppyPappy · · Score: 3, Insightful

    An idea whose time has passed. Maybe he can build an Edsel while he is at it.

    --

    If you aren't part of the solution, there is good money to be made prolonging the problem

    1. Re:An idea by idontgno · · Score: 1
      I don't know where your comment comes from. I guess if you don't get it, you don't get it.

      "Edsel" is a crappy comparison. The PDP-8 actually worked, and broke a lot of ground in computing and electronics technology.

      Maybe a '53 Corvette would be a more apt analogy in the car industry. But of course, no one would want one of those, since it's an idea whose time has passed.

      --
      Welcome to the Panopticon. Used to be a prison, now it's your home.
    2. Re:An idea by b0r1s · · Score: 3, Insightful

      Maybe a '53 Corvette would be a more apt analogy in the car industry. But of course, no one would want one of those, since it's an idea whose time has passed.

      A '53 vette can still drive on the roads, use normal gas from the pump, and hit speeds upwards of 100mph on the highway.

      The PDP-8 simply isn't capable of competing with any current hardware; most Palms are more powerful.

      --
      Mooniacs for iOS and Android
    3. Re:An idea by Gordonjcp · · Score: 2

      Neither is the microcontroller in your washing machine. Many PDP-8s were used for controlling complex machinery in a manner more flexible and customisable than that allowed by "traditional" relays and switches.

      So, what's your point, caller?

    4. Re:An idea by AppyPappy · · Score: 2

      Having been a programmer when a pdp8 was a hot item, I will say that I don't wish to return to those dark days. I've dropped enough punch cards and trimmed enough 9-track for a lifetime. And I don't want to return to calculating memory usage so I don't exceed the 48K allocated to me. I'm sure it is a good practice but I'm too old to do it now.

      Give me a 300mhz with 2 gig of RAM and a wide-open prairie.

      --

      If you aren't part of the solution, there is good money to be made prolonging the problem

  4. 12bit computers by Anonymous Coward · · Score: 0, Flamebait

    Personally I wouldn't mind to see it revived. I mean, anything has to be faster than an Intel Itanium.

  5. Woo! by foxtrot · · Score: 0, Offtopic

    Imagine a beowulf cluster of these!

    On second thought, naah, don't bother...

    1. Re:Woo! by Anonymous Coward · · Score: 0

      I'm visualising something like a VIC20.

    2. Re:Woo! by MarcQuadra · · Score: 1

      I think I have one here... on my wrist.

      --
      "Sometimes, I think Trent just needs a cup of hot chocolate and a blankie." -Tori Amos on Nine Inch Nails
  6. ENIAC by kaden · · Score: 3, Funny

    Anyone for hitting up the local vacuum repair shop and getting started on an ENIAC reconstruction project?

    1. Re:ENIAC by Ark42 · · Score: 2, Interesting

      Funny..

      I read this, then scrolled down to the bottom, and my quote of the moment said:
      "Just think, with VLSI we can have 100 ENIACS on a chip!" -- Alan Perlis


    2. Re:ENIAC by Anonymous Coward · · Score: 0

      Anyone for hitting up the local vacuum repair shop and getting started on an ENIAC reconstruction project?

      Vacuum bags != vacuum tubes!!

      ;),

      -yb

    3. Re:ENIAC by vizualizr · · Score: 3, Funny

      The vacuum repair shop?

      no, that idea sucks.

      --
      anything i tell you will cloud your opinion.
    4. Re:ENIAC by fishbowl · · Score: 2

      You're just kidding, but, I wonder if enough information about ENIAC
      has survived, to make a simulator for it?

      --
      -fb Everything not expressly forbidden is now mandatory.
    5. Re:ENIAC by crawling_chaos · · Score: 2
      The vacuum repair shop?

      no, that idea sucks.

      Bag it already...

      --
      You can only drink 30 or 40 glasses of beer a day, no matter how rich you are.
      -- Colonel Adolphus Busch
  7. Calling all Electrical/Computer Engineers by ekrout · · Score: 5, Informative

    Many of you probably have used Xilink's 1000, 2000, or 4000-series FPGA card during laboratories for your undergrad classes.

    Well, if you'd like, you can follow this design of an FGPA implementation of the original PDP-8 computer!

    If you've used Verilog (a hardware design programming language), like I have, you can even download all the code!

    --

    If you celebrate Xmas, befriend me (538
    1. Re:Calling all Electrical/Computer Engineers by Anonymous Coward · · Score: 0

      Not to nitpick, but that is VHDL, not Verilog :)

    2. Re:Calling all Electrical/Computer Engineers by Anonymous Coward · · Score: 0

      If you've used Verilog (a hardware design programming language), like I have, you can even download all the code

      Does that mean that if we haven't used Verilog we can't download the source code? Is that in the license agreement? How do they enforce that? Do you have to pass a Verilog proficiency test before you can download it? Do you get to learn a secret handshake if you pass?

    3. Re:Calling all Electrical/Computer Engineers by rusti999 · · Score: 1

      Actually in my hardware design class, the project was to design a PDP-8 computer using VHDL. We used an FPGA, although I don't remember the exact model. BTW, I believe BART still uses PDP-8 computers to control the signals in its system.

    4. Re:Calling all Electrical/Computer Engineers by shren · · Score: 1, Offtopic

      You mean FPGA, don't you?

      --
      Maybe the state's highest function is to grind out insoluble problems. (Zelazny, Hall of Mirrors)
  8. 12 bits by vasqzr · · Score: 5, Interesting


    I found that, where you are not primarily handling ASCII, 12 bits was a very good size.


    Maybe someone would enlighten the rest of us on why a certain bit size is better than another, and why we currently use 8/16/32/64, instead of 12/24/48/96 ?

    1. Re:12 bits by FauxPasIII · · Score: 5, Interesting

      >> Maybe someone would enlighten the rest of us on why a certain bit size is better than another,
      >> and why we currently use 8/16/32/64, instead of 12/24/48/96 ?

      Because powers of 2 are easier to work with in binary.

      --
      25% Funny, 25% Insightful, 25% Informative, 25% Troll
    2. Re:12 bits by oliverthered · · Score: 3, Interesting

      8 bit is base 2

      1 2 4 8 16 32 64 128 256 512

      So I suppose 12 could be ....

      1 3 6 12 24 .... hmmmmm..... now quite correct

      maybe
      1 2 3 6 12 24 ... 60 ... 420

      anyway

      12 is good because
      12/6 = 2
      12/4 = 3
      12/3 = 4
      12/2 = 6

      --
      thank God the internet isn't a human right.
    3. Re:12 bits by Viol8 · · Score: 2, Informative

      7 bits was used when the ASCII character set was initially devised (though 4 bit had been used before that) with the 8th bit being used for parity checks. At some point someone decided to hell with parity checks , lets use the 8th bit to double the number of characters available. And once 8 bit became standard in hardware then 16 bit narually followed as you could still divide a 16 bit word in 2 to get 8 bit characters. Similarly with 32 bit you can divide a 32 bit word to give two 16 bit words and hence can run 16 bit software on 32 bit hardware with a bit of help. Thats the gist of it anyway.

    4. Re:12 bits by Kibo · · Score: 1

      At the risk of being obvious. I'm pretty sure 2^8th and 2^12th are still powers of two. Binary being what it is and all.

      --
      --Jimmy has fancy plans; and pants to match.
    5. Re:12 bits by MioceneMan · · Score: 1

      Short answer: Octal Numbers

      If you are used to working on a ten key pad, octal numbers are much easier to enter than hexadecimal or anything else.

      It's just cool...

    6. Re:12 bits by rampant+mac · · Score: 1
      12 bits was a very good size.

      I'm sure most women computer scientists would argue otherwise. :)

      --
      I like big butts and I cannot lie.
    7. Re:12 bits by sporty · · Score: 3, Informative

      No.. not like that. 8 is a power of 2, 12 isn't :P

      --

      -
      ping -f 255.255.255.255 # if only

    8. Re:12 bits by sql*kitten · · Score: 5, Informative

      Maybe someone would enlighten the rest of us on why a certain bit size is better than another, and why we currently use 8/16/32/64, instead of 12/24/48/96 ?

      This article explains why base-3 systems are actually a lot better than base-2 from a theoretical perspective, but that it was much easier to design hardware in base-2, so base-2 became the de-facto standard. Nowadays we could probably fab base-3 hardware fairly easily, but it's not worth doing so with all the base-2 hardware already in existance.

      As for 16/32/64 instead of 12/24/48, it's just one of those things. IBM's earlier AS/400s ran on 48-bit processors (now they are 64-bit). 96-bit floating point is an IEEE standard. And do you know why file permissions in Unix are rwxrwxrwx? It's because they borrowed that idea from another operating system designed for 9-bit bytes and a 36-bit processor.

    9. Re:12 bits by corey_lawson · · Score: 1

      ...or even the 54-bits (56?) of the CDC computers...

    10. Re:12 bits by AlecC · · Score: 2
      If you are using Ascii, the 8-bit bytes are a good size. Of course, you really only need 7 bits, but no programmer is going to like that. Then you add the concept of byte addressable word space, so you use the byte address to address doublebytes (short) and quadbytes(longs).

      As to why 12 bits is good: simply 8 bits is a bit small for an awful lot of cases, so if you use an 8-bit fundamental word length, you are often into doubleword operations. Practically, a 12 bit word length, values +/2048 or 0-4095, seems to work out useful in a lot oc control applications. When the extra bits were expensive, the saving between 12 and 16 is relevant.

      First machine I worked on was 18 bits - all 8K words of it. Enough to run a very simple Fortran compiler. From paper tape, naturally.

      --
      Consciousness is an illusion caused by an excess of self consciousness.
    11. Re:12 bits by yomegaman · · Score: 1

      I think you (and almost everyone else) are confusing 8-bit word size with base-8 numbering systems. You can write 12-bit words in binary, octal, hex, or whatever just as easily as 8-bit words.

      --
      ...wearing a skin-tight topless leather jumpsuit, with cutaway buttocks and transparent crotch panel.
    12. Re:12 bits by lobsterGun · · Score: 2, Interesting

      This is a story that a wisened old timer told me at a convention (the guy had a whit bushy beard so you know it has to be true).

      Back in the day there were two schools of thought: the 8 bit byte and the 9 bit byte. The 9 bit byte school represented the same data as the 8 bit byte school (0 to ff), and used the extra bit for parity.

      8 bit bytes led to 16 bit words etc...
      9 bit bytes led to 18 bit words etc...

      My reaction to the old time was to ask WTH would anyone do this?

      His response was to go into a discussion of 36 bit computing. "Ya see son. When you have 32 bits you can divide those bits evenly 6 ways:
      32 single bits,
      16 2-bit groups,
      8 4-bit groups,
      4 8-bit groups,
      2 16-bit groups,
      1 32-bit group.

      With a 36 bit system you can divide those bits evenly 9 ways
      36 single bits
      18 2-bit groups
      12 3-bit groups
      9 4-bit groups
      6 6-bit groups
      4 9-bit groups
      3 12-bit groups
      2 18-bit groups
      1 36 bit group

      using 36 bits give you more flexibility in addressing."

      He went on to tell be stories about how they explioted the advantages of 36 bit computing back when he had worked at Compuserve and how sad he was that 36 bit systems had died.

      It could very well be that 3 12-bit bytes are used to make up a 36 bit word... ...or it could be that that old timer was full of crap or off his meds or something. The world may never know (Much like the number of licks it takes to get to the center of a tootsie pop).

    13. Re:12 bits by rplacd · · Score: 1

      I don't know anything about the PDP series, or how they utilized their non-power-of-2-size bytes, but some systems used such "non-standard" byte sizes to tag types. For example, if you have a 36 bit word, you can store a 32 bit value plus 4 bits to specify the type of that data. You can then check very quickly if a certain memory word is an integer, or float, or a pointer to a list (or whatever).

      The Symbolics Lisp machines used such a system. I haven't followed Squeak's development for a while, but I remember its 32 bit virtual machine used tagged types, and unfortunately that meant that they had to use 30 bit numerical and reference types. Several other languages/virtual machines use this feature.

      I put "non-standard" in quotes because in the past not everyone used (uses?) 8 bits. That's why if you read older RFCs, you'll find the term "octet" used where you'd normally expect to see "byte."

    14. Re:12 bits by Smallpond · · Score: 1

      Its mostly true. I remember spending a day trying to
      write a tape on a DEC-10 (36-bit word) and read it on the
      IBM 360 (32-bit word) and get the 6 characters/word
      to convert to 4/word. It eventually worked, thanks to
      creative use of the dd command.

      Here is a link on 36-bit computing.

      PS - I have gray hair, but no beard.

    15. Re:12 bits by AJWM · · Score: 2

      why we currently use 8/16/32/64, instead of 12/24/48/96

      Because we currently use 8/16-bit character sets. Blame it on ASCII and EBCDIC (and UNICODE). (Okay, plain ASCII is 7-bit, but in communications there was a parity bit too.)

      A lot of older machines use 6-bit character sets, that's all you need if you ignore case. There's the 12-bit PDP-8, the 36-bit DEC-10 and -20, the 48-bit Burroughs machines (which could handle both 6-bit and 8-bit characters), and the 60-bit Control Data machines. The PDP-8 was superceded by the 16-bit PDP-11, the DEC-10s were dropped (superceded by 32-bit VAX), the 48-bit Burroughs machines may well still be 48-bit (Unisys) for all I know, and the 60-bit Cyber series evolved to 64-bits sometime in the 1980s.

      --
      -- Alastair
    16. Re:12 bits by Anonymous Coward · · Score: 1, Informative

      This is part of the reason that the 'imperial' or 'standard' system of measuring length is still used in much of the construction industry here in America.

      A foot can be divided into 1/2 (6"), 1/3 (4"), 1/4 (3"), 1/6 (2"), and 1/12 (1") evenly and without fuss. This makes it much easyer to layout things than metric, where you can only divide by 1/2, 1/5, and 1/10. Seeing that being able to devide by 1/3 and 1/4 is a very common thing in construction, it still makes some sort of logic for building materials to be base tweleve rather than base ten, ala metric. For when you're trying to devide 60'-3" into fourths in the feild, a base 12 system is easyer to think about!

      Just a random thought from somone in the building industry...

    17. Re:12 bits by DaveAtFraud · · Score: 2
      ...or even the 54-bits (56?) of the CDC computers...
      60 bit words actually but don't ask me why. At the time I was doing number crunching and algorithm design so, unfortunately, I didn't get down to the hardware level and find out why they used a 60 bit word.

      The other interesting hardware architecture was Data General with their 36 bit words.

      --
      They that can give up essential liberty to obtain a little temporary safety deserve neither safety nor liberty.
      Ben
    18. Re:12 bits by oliverthered · · Score: 1

      The same is true with most (if not all) imerial measurements.

      Money is a good example,
      1 pound = 20 Shillings ( /5 /4 /10 /2)
      1 Shillings = 12 Pennies ( /3 /4 /2 /6)

      So you can easly devide a pound by 2 3 4 5 6 (not 7) 8 9 10

      Time's good as well,
      24hours in a day /2 /3 /4 /6
      60minutes in an hour /10 /5

      Why did we go metric, it's too hard and doesn't keep me doing base conversions all day, I feel deprived.

      Imperial measurements are also 'tangable' i.e. they are based on real, easy to measure things.

      1 Yard is from the tip of your nose to the end of your index finger. Very handy if your selling cloth or rope.

      --
      thank God the internet isn't a human right.
    19. Re:12 bits by CommieOverlord · · Score: 1

      1 Yard is from the tip of your nose to the end of your index finger. Very handy if your selling cloth or rope.

      If only measurements could be this standardized. A merchant with short arms could make a killing in textiles retailing. I'm generally in favour of any rules that hlep us short people.

    20. Re:12 bits by Anne+Thwacks · · Score: 1

      I worked on CDC 6400, 6600 and 7600 - they all had 60 bit words.

      --
      Sent from my ASR33 using ASCII
    21. Re:12 bits by oliverthered · · Score: 1

      a merchent with shout arms would employ someone with longer arms/ask the customer to measure or have no business.

      It's a good job I cary a meter rule with me when I go shopping.

      --
      thank God the internet isn't a human right.
    22. Re:12 bits by codeslut · · Score: 1

      1 meter is from the tip of your left shoulder to the tip of your right hand, if you hold your arm horizontally pointing sideways.

      --
      "Do you think there are answers to everything here? Is that true in the place you come from?" - Agia
    23. Re:12 bits by MioceneMan · · Score: 2, Insightful

      12 bits makes four octal numerals.

      In decimal you might type for example year 2002. In Octal that would type year 3722, in Hexadecimal 7D2.

      Some of us used to quite commonly enter utterly raw machine code or data on a ten key pad. It is very easy, if you have good ten-key skills, to enter 12 bit "words" in octal.

      If you have a minute, look at some 8080 family machine language in octal. You will notice the basic 8080 instruction format is centered on 3 bit fields!

      Heh, slashdot as always...

    24. Re:12 bits by AndrewRUK · · Score: 1

      Would you care to explain why you can't divide a metre into quarters? What's so hard about 25 cm?

    25. Re:12 bits by Luke · · Score: 2

      Yep this person is right on, since 12 is evenly divisible by many numbers.

      For those on the site who are musically inclined, note how often 12 and its divisors are used in music.

    26. Re:12 bits by pjrc · · Score: 2
      Before ASCII in the mid-60's, computers represented characters using 6 bits. 12 bit systems were common, since 64 characters are enough to represent A-Z, 0-9, and a handful of symbols and control codes, and a 12 bit number gives enough range for a lot of types of computation.

      Here's a really well written history by Tom Jennings of the early character codes and the two ASCII standards in the 60's. AT&T apparantly forced the world to use ASCII. ASCII required 7 bits, which was a huge departure from the previous 6 bit (and 5 bit, 2 set) systems.

      Tom's history doesn't mention the real reason we all have 8/16/32/64 bit machines today: IBM's Extended Binary-Coded-Decimal Interchange Code (EBCDIC) encoding, which spec'd 8 bits per character (how he could leave out EBCDIC is beyond me?) IBM forced the world to 8-bits to represent characters inside the computer, and AT&T forced the world to communicate them with 7 bits. ANSI recommented in the 1967 ASCII spec (X3.4... the one that added lowercase) to use the eigth bit for parity. ASCII was more focused on communication than storage of data.

      The thing I find interesting is that the old computer and telcom industry monopolies forced these fundamental architecture decisions on everyone, both discarding lots of established practice with little regard for backwards compatibility. But the modern computer and telcom monopolies have more or less adopted and adapted from existing technologies and have largely failed to push their own "standards" that discard backwards compatability, at least when it comes to how data is stored and communicated.

    27. Re:12 bits by bluethundr · · Score: 1



      Very interesting, and thought provoking. While we're at it, why qwerty and not Dvorak? Trinary may make sense, but we are to deep into binary to even think of changing. Interesting to think that the ENIAC was based on something called Bi-Quinary ( I think we've talked about this before). So apparently was the IBM-650.

      It seems that the debate between binary and bi-quinary was a topic of hot debate in the computing field as to the furutre of digital circuitry at one point in history. As the article states: "Each digit was represented in seven bit "bi-quinary" notation: one bit out of 5 represented a value from zero to four; one bit out of two indicated whether or not to add 5 to that value, giving the electronic equivalent of the abacus.

      --
      Quod scripsi, scripsi.
    28. Re:12 bits by thogard · · Score: 1

      1/4 isn't the problem. 1/3 is. Most angles in construction are 4:3 or 3:4 and a 12 minor units to a major one helps that out. The squares are all easy, its the angles that aren't. Here in Australia, roofers are still using the old imperial tools for their work but they are no longer using nice round numbers. I'm not sure why someone hasn't started selling materials by the "metric foot" which would be 30cm.

    29. Re:12 bits by Alien+Being · · Score: 2

      "12 bits makes four octal numerals."

      The toggle switches on the front panel were arranged in sets of three. The color of the switches alternated between sets.

      On our high school's PDP8m, you had to toggle in 5 or 6 4-digit numbers to xfer the boot loader from disk to core and set the program counter. Then you'd start the clock and the console teletype would come to life in standalone mode. From there, we would start ETOS (Educational Timesharing Operating System). ETOS was multitasking, and multiuser. IIRC, it required a special board that handled the context switches.

      Perhaps the coolest thing about ETOS is that it had a facility similar to VMware. Each user had access to his own virtual PDP8.

    30. Re:12 bits by thogard · · Score: 1

      Remember the Brits used a base 10 measuring system long before they switched to a base 12 system. Outside of the US most home construction is in units of 30 cm with newer items being in 1/2 or 1/4 meter units.

    31. Re:12 bits by thogard · · Score: 1

      the 60 bitness helped with their floating point and vector units

    32. Re:12 bits by Anonymous Coward · · Score: 0
      Really? Can you provide even a single practically meaningfull example of 8 bit bytes being "easier" to process than 12 or say, 17-bit bytes? Sure nowdays RAM and buses etc are all optimised for 8-bit bytes, but computers today would be just as powerfull had 12 bits become the prevalent system. It just happend that n*8-bits became the standard.

      Besides it's not true at all that CPUs use 2^n bitwidths for everything. Take IA64 for example: Three 40-bit instructions per bundle, each consisting of 13-bit opcode, 6-bit predicate and three registers addresses which are 7-bits each. How's that for powers of two? Or how about AMD's hammer with 51-bits worth of addressable physical memory. You think there would have been a large performance gain in full 64-bit addressabilty?

    33. Re:12 bits by Anonymous Coward · · Score: 0

      Which is, of course, meaningless in this particular context.

      There's no reason why LENGTHS of powers of 2 are easier to work with.

      i.e: a 12-bit byte isn't any harder to work with than an 8-bit byte just because 8 happens to be a power of 2. Powers of 2 are easier to work with in binary due to the nature of storing numbers in binary form.

    34. Re:12 bits by sql*kitten · · Score: 2

      Very interesting, and thought provoking. While we're at it, why qwerty and not Dvorak?

      QWERTY keyboards were designed for mechanical typewriters - the layout of the keys is designed to minimize the chance of two keys clashing, because on a mechanical typewriter, both keys will get stuck. In the old days, a computer keyboard was an electric typewriter (a tty), which had inherited its design from mechanical typewriters because they were already entrenched.

      Despite it being inefficient, and actually designed to slow typists, we're stuck with it - probably until the keyboard itself is superseded as an input device.

    35. Re:12 bits by Ed+Avis · · Score: 2

      Three-state or base-3 computing systems have nothing to do with it. 12-bit machines use 12 *binary* digits. They are still base-2 hardware.

      --
      -- Ed Avis ed@membled.com
    36. Re:12 bits by Ed+Avis · · Score: 2

      Yeah, as if it makes a difference whether your word size is a power of two or not. A 32-bit word is no 'easier to work with' than a 42-bit or 27-bit word. Lots of things in computing are most easily handled with powers of two, but bits-per-word is not one of them - either for hardware or software reasons.

      --
      -- Ed Avis ed@membled.com
    37. Re:12 bits by Anonymous Coward · · Score: 0

      60-bit words.
      Speed and precision of standard floating point. Too many bits, too slow. Too few bits, too inacurate. Tempting to make a variable word size, but when instructions are encoded in the same number of bits, you pick a size and do what you can with it. Problem is that everything that depends on the exact encoding is very non-portable.

    38. Re:12 bits by Anonymous Coward · · Score: 0

      I'm not stuck with it at all. Most modern computers switch easily or are network accessible. I'll type away at dvorak and watch you struggle with your carpal tunnel.

    39. Re:12 bits by KewlPC · · Score: 2

      Originally the yard was based on the length from the tip of the king's nose to the end of his index finger. Nobody actually measures things that way anymore, though, because we have an official yard length which doesn't change (it's locked away at NIST, I believe). No one is going to cheat you (although if you suspect that a store is using incorrect measurements, whether on purpose or not, give your state's Department of Weights and Measures a call).

      But the fact that the yard is close to the length between the tip of the nose and the end of the index finger for most people makes it easier in situations where you don't have any other way to measure, such as your yardstick getting lost.

    40. Re:12 bits by spitzak · · Score: 3, Insightful
      If the length is a power of two, than a "bit number" (a shift value, or an argument to a bit-test instruction, or anything else that identifies a bit by a number) will fit into a set of bits with no waste.

      This DOES make a difference. More important than the space savings is the ability to know that a pattern of bits could not encode any illegal instructions that had to be tested for.

    41. Re:12 bits by oliverthered · · Score: 2

      Well around 10years ago, 'when I were a lad' they used to sell cloth by the nose to index finger yard in markets. (they'd leave a bit of sag in the fabrick so as not the under measure)

      --
      thank God the internet isn't a human right.
    42. Re:12 bits by ChaoticLimbs · · Score: 1

      all the computers I've used had a bit size of 1. their byte sizes did differ, though.

    43. Re:12 bits by KewlPC · · Score: 2

      Really? I used to get dragged out to a lot of fabric stores with my mother when I was a little kid, and they all used either a yardstick, measuring tape, or one of those big white measuring boards.

    44. Re:12 bits by bluethundr · · Score: 1

      Thanks, that was my point. Since computer keyboards of today are not slowed by the clackity-clack of victorian age machinery, the only logical reason for using qwerty (which as you pointed out was to slow the user down to prevent the machine from seizing) is that it is a deeply entrenched habit of society. Dvorak style typing made sense since they did not realize the limitations of the machinery they were building. Not that those limitations are gone, the only reasons are socialogical, not technological.

      --
      Quod scripsi, scripsi.
    45. Re:12 bits by oliverthered · · Score: 1

      In the shops they used a measuring board, but in the market they still used the hand nose thing.

      --
      thank God the internet isn't a human right.
    46. Re:12 bits by rkoot · · Score: 1

      I recall a /. article from a few (3?) years ago, about a IBM research lab having constructed a BASE-4 circuit.
      that way you have 0, 1/3, 2/3 and 1 as states for your gates.
      I think the article said IBM wanted to have a first commercial product around 2004.
      anyone who knows more about this ?
      rkoot

    47. Re:12 bits by hplasm · · Score: 1
      Maybe someone would enlighten the rest of us on why a certain bit size is better than another, and why we currently use 8/16/32/64, instead of 12/24/48/96

      So as we kin count on the toes of one foot, duh-huh.

      --
      ...and he grinned, like a fox eating shit out of a wire brush.
    48. Re:12 bits by Anonymous Coward · · Score: 0

      Just as easily accomplished by only allowing three bits for a shift argument... you need to shift a 12-bit value by 10 bits? Do two operations.

  9. What good is it? by natron+2.0 · · Score: 1

    Since the site is already /.ed i cannot read more about this or see any pics, but I have to wonder what good 12 bit technology would still be good for. I guess perhaps you could run a basic linux system with it, but what else?

  10. This is great news :) by solostring · · Score: 4, Interesting

    I fondly remember the PDP8. My father had one installed in the garage when I was a kid, and had my first experience of programming on it when I was 8 or so.

    On the subject of PDP8's, I was surprised to hear that they were used in communications in Hong Kong up until at least 1999 for a number of financial institutions. I worked with an old computer technician who earned a fortune maintaining these beasts. I wonder if they are still being used in HK after the Chinese reclaimation?.....

    1. Re:This is great news :) by sczimme · · Score: 2

      I was surprised to hear that they were used in communications in Hong Kong up until at least 1999
      ...
      I wonder if they are still being used in HK after the Chinese reclaimation?

      Possession of Hong Kong went back to mainland China in 1997, so I would say yes, they were in use for at least two years after the changeover. (I don't know if they are still in use, though.)

      --
      I want to drag this out as long as possible. Bring me my protractor.
  11. Ouch! by stephenisu · · Score: 0, Offtopic

    Down in under 5 posts, that is almost a new slashdotting record..

    --
    Sigs? We don't need no stinking sigs!
  12. site down by alta · · Score: 0, Offtopic

    I guess he's using a DPD for his server.

    --
    Do not meddle in the affairs of sysadmins, for they are subtle, and quick to anger.
  13. Slashdoted already by Tassach · · Score: 2

    Apparantly, the PDQ8 doesn't withstand the /. effect very well. And of course, obBeowulf.

    --
    Why is it that the proponents of "one nation under God" are so eager to get rid of "liberty and justice for all"?
  14. Why? by BWJones · · Score: 5, Interesting

    but he is not just building a hardware clone, but trying to revive the whole idea of 12 bit computers!"

    So, after reading the article, I am still trying to figure out....Why revive the idea of 12 bit computers? Other than nostalgia (which is why people still drive Studebakers, old Ferraris and old Porsche's I suppose), what is the point?

    --
    Visit Jonesblog and say hello.
    1. Re:Why? by Kibo · · Score: 5, Funny

      I can't be sure about Studebakers but in the case of classic Ferraris and Porsche's I'm fairly certain the idea is still to get laid.

      --
      --Jimmy has fancy plans; and pants to match.
    2. Re:Why? by WinterSolstice · · Score: 2
      Having owned a classic (1973) Porsche 911t Targa, and currently owning a 1975 Corvette Stingray T-top, I can tell the idea is somewhere between getting laid, and the sheer fun of a classic performance car.

      Some people, (myself obviously included) think that the pre-gas shortage cars in the US were much better looking cars. The current models seem to still be recovering from the 80's and 90's ideas of "Box on Wheels" and "Wind Tunnel Styling". I wouldn't own a new Porsche.

      I think the idea with the PDP however, is not nostalgia. It was (and is) a very stable platform. Many companies either just left them, or are still using them. We just left the VAX platform not too long ago, despite having used Alphas concurrently for ages.

      After all, if it works, why upgrade?

      -WS

      --
      An operating system should be like a light switch... simple, effective, easy to use, and designed for everyone.
    3. Re:Why? by wcspxyx · · Score: 1

      Don't count those Studebakers short. Have you ever tried to get laid in a Ferrari or a Porsche? Personally, I'm just not that much of a contortionist.

      --
      Sig? What sig? Do I have to have a sig!?!?
    4. Re:Why? by rgmoore · · Score: 2
      which is why people still drive Studebakers, old Ferraris and old Porsche's I suppose

      People care about even stranger things than that. Just yesterday, I saw a group of Edsel fans driving their cars in the Doodah Parade. When I thought that was goofy enough, the people standing next to me pulled out their pictures from a trip to a Corvair fan get together (The Great Western Fan Belt Toss & Swap Meet). ISTR that there are even Trabant fan clubs, of all things. Name a piece of obsolete technology, and there's a good chance that some people will be fanatically devoted to it.

      --

      There's no point in questioning authority if you aren't going to listen to the answers.

    5. Re:Why? by image · · Score: 4, Funny

      > I can't be sure about Studebakers but in the case of classic Ferraris and Porsche's I'm fairly certain the idea is still to get laid.

      I'm rather sure it is easier to get laid in a vintage Studebaker than a Ferrari.

      More leg room and all.

    6. Re:Why? by Anonymous Coward · · Score: 0

      No. Driving a 356 has nothing to do with getting laid. If you have to ask don't bother - you wouldn't understand anyway.

    7. Re:Why? by Kibo · · Score: 1

      Well there are other factors to consider. Irene Ryan is dead, for instance.

      --
      --Jimmy has fancy plans; and pants to match.
    8. Re:Why? by Mogster · · Score: 1

      Why climb Mt Everest?
      Because it's there.

      To some people the challange is more exciting than the outcome.
      I remember making Windows 3.0 to work from 1.2MB FDD's on an 8086/640k with 360k drive, when Microsoft themselves told me it wouldn't work (they appear to have forgotten Real Mode). Why did I do it? Because it was there.

      --
      ACK NAK RST
    9. Re:Why? by Anonymous Coward · · Score: 0

      Possum Stew!

  15. replica computers ... its logical innit? by trash+eighty · · Score: 3, Interesting

    people have been building replicas of old cars, boats and aeroplanes for years. i suppose its logical that people would start building replicas of old computers sooner or later. much computer hardware is boring these days, generic MBs and computers. ahh the good old days when we had some variety ;)

    all power to him!

    1. Re:replica computers ... its logical innit? by plierhead · · Score: 2

      Yeah but I can't help feeling that old cars, boats and aeroplanes are very very sexy and likely of interest to most of the inhabitants of the planet, and, yeah, to be honest might well help get you laid...whereas consider whether you could muster quite the same charisma offering to show someone over your collection of rebuilt dental hygiene equipment (for example)...

      --

      [x] auto-moderate all posts by this user as insightful

    2. Re:replica computers ... its logical innit? by trash+eighty · · Score: 1

      depends why you make them. i think most people go to the trouble because they like making things rather than trying to get laid using an old ferrari replica.

  16. Interesting by GeckoFood · · Score: 3, Insightful

    It would be fun to play around with something cool like that, just for the sheer ability to say "Hey, y'all watch this!" (Oops, better watch that there accent, ya rekcon?) It would especially nice to have a C compiler or something to develop apps for it, again just for the coolness factor.

    With a twelve-bit computer, what is the address space, anyway? Something like 2048 words? Suprisingly, you can actually do a lot with that if you code it tightly. No, can't do weather map rendering too well or anything like that, but I bet you could pull off a stripped down version of NetHack or something...

    Coolness, regardless. :-)

    --
    Be excellent to each other. And... PARTY ON, DUDES!
    1. Re:Interesting by johnalex · · Score: 2

      Bad omen. Here in the South, "hey y'all, watch this!" are often the last words you hear.

      --
      JA
      http://www.johnalex.org/
    2. Re:Interesting by CoolVibe · · Score: 1, Offtopic

      Nope. Usually "Whoops!" is the last thing you hear. Or the often last head: "Shit!", "Uh oh!" or "Look out!"

    3. Re:Interesting by Anonymous Coward · · Score: 0

      Or "hold my beer" :)

  17. Just how big *were* these things? by ekrout · · Score: 4, Informative

    Well, I found this old link in my bookmark manager. It details the history of EMS (sound studio) in vivid detail, including a listing of all their original equipment.

    The interesting part is that they posted high resolution images of their setup, which includes PDP-8 microcomputers!

    The image: http://www.ems-synthi.demon.co.uk/studiopz.gif
    The PDP-8s:
    Left side - Teletype for PDP8
    Left bay - PDP8/L Computer ("Leo") 4K x 12 bits (=6K bytes) 1.3 s cycle (0.77MHz), 32K Hard Disk Store
    Center left bay - PDP8/S Computer

    --

    If you celebrate Xmas, befriend me (538
    1. Re:Just how big *were* these things? by dhogaza · · Score: 2

      The PDP-8/S was the serial version of the PDP-8, and the model I learned programming on in high school (we couldn't afford one by ourselves, it was owned by a consortium and travelled between about a half-dozen schools).

      The PDP-8/S took 36 microseconds to add two words. When I first got to play with a real, parallel PDP-8 (3 microsecond add time) I was in heaven. Man, that puppy seemed FAST!

  18. 12 bit is best for the US patriot by MosesJones · · Score: 5, Funny

    12 bit is much better for patriotic Americans.

    Think on it, power of two is a far to simplistic and dare I say it European system for the patriotic American. In Europe they use metres, kilometers, grams and kilgrams. All this regulation of structure around a number like 10 is typical of Europeans. Americans use sensible systems like 14 pounds (abbreviated sensibly to lbs as pounds clearly contains the letter l) to a Stone and 16 Ounces (again with a sensible abbreviation of oz) to a pound. Who needs these ridiculous regimented European systems that dicate that everything must follow a sensible pattern?

    Patriotic Americans arise. 12 bits to a byte, 7 bytes to a word, 13 words to a sentence and 1764 bits to a chain.

    --
    An Eye for an Eye will make the whole world blind - Gandhi
    1. Re:12 bit is best for the US patriot by marsbarboy · · Score: 2, Insightful

      no, 12 bit is best for the BRITISH patriot. Bring back the good old imperial measurements...It's only the EU making us use the french system.
      Why do you think the americans use imperial?
      Because we used it first.

      --
      The truth is rarely pure and never simple. Oscar Wilde (1854 - 1900)
    2. Re:12 bit is best for the US patriot by david+duncan+scott · · Score: 3, Informative
      You know, I have never, in 43 years, heard an American use "stone". That's a Brit thing.

      And of course we inherited the whole system. As I recall, the "lb." abbreviation has something to do with the French "livre", and also led to the the "pound sterling" symbol, that fancy-schmancy "L" that featured so prominently on the Commodore keyboards of yore.

      As for word width, well, there's nothing especially holy about multiples of 8. CDC used to make machines with a 60-bit word, because they mostly dealt with numbers, not text manipulation, and big fat words like that allow for big fat numbers, although storing an ASCII file in 60 bit words would be clumsy as hell (As a side note, I used to work with the CP1600, which was a real 16-bit machine. There was no way to address a byte, although there was an 8-bit shift so that you could pack ASCII into words to save space and slow down annoyingly fast programs.)

      --

      This next song is very sad. Please clap along. -- Robin Zander

    3. Re:12 bit is best for the US patriot by sql*kitten · · Score: 3, Informative

      And of course we inherited the whole system. As I recall, the "lb." abbreviation has something to do with the French "livre", and also led to the the "pound sterling" symbol

      Which is interesting because the word Sterling comes from starling, which meant "small star" in mediaeval English - it was the symbol on the coin for the unit of currency. So the currency symbol should probably really be a *.

      Lb is from "livre" (French for pound) and dollar comes from "taler", an old German currency.

    4. Re:12 bit is best for the US patriot by immanis · · Score: 1

      Patriotic Americans arise. 12 bits to a byte, 7 bytes to a word, 13 words to a sentence and 1764 bits to a chain.

      Speaking as a yank who favors logical measurements, that's pretty damn funny. I've never read the absurdity of our systems of measurements summed up so neatly.

      Wonderful things, scientific measuring systems and such. All units are nicely and neatly arranged, though not without their own random elements. Such units as:

      • liter - "a metric unit of capacity equal to the volume of 1 kilogram of pure water at 4 degrees centigrade and 760 mm of mercury (or approximately 1.76 pints)"
      • meter - "approximately the ten millionth part of the distance from the equator to the north pole, as ascertained by actual measurement of an arc of a meridian."
      • gram - "approximately equivalent to the weight in a vacuum of one cubic centimeter of pure water at its maximum density."
      • candela (my favorite) - "A unit of luminous intensity equal to 1/60 of the luminous intensity per square centimeter of a blackbody radiating at the temperature of solidification of platinum"

      Which of course explains why the pub still serves you all in pints. LONG LIVE THE DRAM!

    5. Re:12 bit is best for the US patriot by AlecC · · Score: 2

      Absolutely. 12 pennies to the shilling, old bean. One of the early British computers (?Leo?) used BCD arithmetic, but had a hardware switch so that the ls digit could be used in base 12 instead of base 10 for making the pennies into shillings.

      --
      Consciousness is an illusion caused by an excess of self consciousness.
    6. Re:12 bit is best for the US patriot by Anonymous Coward · · Score: 0

      You forgot "The Nibble" 4 bits.

      p.s. God wants us to have 12 fingers, (its a dominant gene) it makes math easier.

    7. Re:12 bit is best for the US patriot by Anonymous Coward · · Score: 0

      Kind of , wouldn't you say? Looks like a small star to me.

    8. Re:12 bit is best for the US patriot by JimPooley · · Score: 2

      The LEO (Lyons Electronic Office) was the first ever computer designed to be used by business, and was developed by Lyons Bakery.
      There's a site about it here.

      --

      "Information wants to be paid"
    9. Re:12 bit is best for the US patriot by Waab · · Score: 2

      I must respectfully disagree.

      While a measurement system based on powers of 2 seems fairly straightforward and intuitive to your average techno-nerd, it is still incomprehensible to the average Patriotic American. In fact, I would venture to say that 1024 bytes in a kilobyte is every bit as opaque as our beloved, patriotic, English units.

    10. Re:12 bit is best for the US patriot by Anonymous Coward · · Score: 2, Informative

      Actually, I must defend the American/British/Biblical system for a second. Granted, the metric system makes a lot of sense for modern science. But for simple math, using numbers like 12, 16, 60, etc. makes a lot of sense because they have a ton of whole number factors. For instance, if I want to divide 12 into 2, 3, or 4 different parts it's a lot easier than with 10. With modern computing devices, most people forget the ingenuity of this system when criticizing it.

    11. Re:12 bit is best for the US patriot by AJWM · · Score: 2

      although storing an ASCII file in 60 bit words would be clumsy as hell

      No kidding. In fact mostly they didn't. Even into the early 1980s, CDC Cyber machines stored (and maniuplated) text in one of two formats: 6-bit character, or 6/12-bit character, the latter being 6-bit plus an escape character for lower case. When they brought out the next series of machines the hardware could run in either 60-bit or 64-bit mode, and they introduced an 8-in-12 character set which was essentially 8-bit ASCII stored in 12 bits, wasting 4, until the OS was converted to 64-bit.

      Doing text processing/formatting was a royal pain on that system, so I ended up writing a clone of Waterloo Script (vaguely like 'roff) in Pascal (named "Formal") that internally treated everything as 7-bit ASCII and translated on input and output. Proved pretty popular, a number of other CDC sites bought it.

      (Side note -- the I/O on those 60-bit CDC machines was handled by 12-bit "PPU"s (peripheral processor units) to offload the CPU.)

      --
      -- Alastair
    12. Re:12 bit is best for the US patriot by thogard · · Score: 1

      If you average many of the quarts (all based on 1/4 of a gallon where the gallon varies by region and industry), you get 1 liter.

      At one point in the US there were over 20 different "miles" in use. Bridge builders had their own as did railroads when they wern't building bridges.

      One thing that I have noticed is that people who are used to feet can guess at the sizes of rooms and offices more accuraturately than thouse used to the metric system. Both groups of people tend to be within 2 units of the correct number so the imperialist seem to have 3 times the precision.

      I was talking to a cop who claimed that people giving heights in feet and inches were more accurate than those offering descriptions of crooks in meters or cm. This is a country where most women under 25 can't tell you what an inch is but still can describe some one as being 6 ft 4 and their description will still be within about 2 inches. I find it quite strange.

    13. Re:12 bit is best for the US patriot by Derwen · · Score: 2
      Americans use sensible systems like 14 pounds (abbreviated sensibly to lbs as pounds clearly contains the letter l)
      the "Lb" is short for Libra (Latin for pound), the same reason that the pound sign for British currency is a fancy L (crossed with one or two lines).
      - Derwen

      --
      http://fsfeurope.org/
    14. Re:12 bit is best for the US patriot by Derwen · · Score: 2
      no, 12 bit is best for the BRITISH patriot. Bring back the good old imperial measurements...It's only the EU making us use the french system.
      Napoleon introduced the metric system to Europe to replace the French imperial system. Nevertheless you will still find fruit sold by the pound in parts of rural France. :-)
      - Derwen

      --
      http://fsfeurope.org/
    15. Re:12 bit is best for the US patriot by CormacJ · · Score: 2

      You know, I have never, in 43 years, heard an American use "stone". That's a Brit thing.

      I once used that with my wifes family, and had to explain to them what 1 stone equals 14lbs. Later that same day I told we'd be back again in a fortnight. That really confused them. They'd never heard someone describing 2 weeks as a fortnight.

      That day I came to realise the truth of the quote that described the UK and the US as two countries seperated by a common language.

    16. Re:12 bit is best for the US patriot by david+duncan+scott · · Score: 2
      Now "fortnight" I know, but only because I read a bunch of Enid Blyton novels as a child (long story, but they were around the house and I'd read just about anything.) Of course, "fortnight" kind of makes sense, in the same way the "bedlam" does, whereas "stone" seems to be as arbitrary as any other unit, and therefore opaque to reason.

      Hey, sounds like you could answer a question for me: I sometimes watch those "World's Worst Drivers" shows (you know, when I'm feeling too smart and need to drain off a few IQ points.) Aside from driving on the wrong side all the time, which would qualify all of the UK for the show if you ask me, one other thing puzzles me. I see occasional jagged lane dividers, sort of saw-toothed or like lightning bolts. I'm guessing they don't mark the electric vehicle lane, but what do they mean?

      --

      This next song is very sad. Please clap along. -- Robin Zander

  19. What Gives? by SuperDuG · · Score: 4, Funny
    Everyone is waiting around for 64-bit chips to hit the home computer market at resonable prices, is this some kind of protest "bits, we don't need no stinkin bits".

    On a related note, I'm going to be designing my own 32 bit system. It's going to be pretty cool having an asthetically pleasing case, and run most all of the common software out there, but make the operating system run on top of bsd. Then I'll make really high-end systems, and education type systems, and laptops.

    Now I'm 95% of the way done with this whole project so I've hired an advertising firm to come up with some commercials. I figure I'll show joe average sixpack switching from the normal x86 windows machine, to my machine, I'll call them 'Switch-Ads'.

    My proprietary systems will never run on anything else, and you will be forced^H^H^H^H^H^H encouraged to only buy via our website.

    I'll call them MOC's ... and the company will be named Orange.

    --
    Ignore the "p2p is theft" trolls, they're just uninformed
    1. Re:What Gives? by rufo · · Score: 1

      Of course, then you run into the problem that you can't compare Macs to Mocs, since then you would be comparing Apples to Oranges, and we all know that's a no-no.

      --
      My English teacher once told me that two positives don't make a negative. Two words for her: Yeah, right.
    2. Re:What Gives? by Anonymous Coward · · Score: 0

      Macs are EASIER to use than linux or windows and thats why Apple is a multibillion dollar firm.

      Your logic needs to show where wase of use and consitent interface are employed or you will have no sales.

      Also, no mac running a webserver in BugTraq history, or certainly since 1995, has ever been remotely rooted or defaced running OS 8.x or 9.x (not the unix based os x).

      EVER, though one time a 3rd party utility addon was implicated with an exploit.

      Thousands of windows and linux exploits.... not one mac exploit ever. Thats why one time the US army switched to macs for some of its webservers after being defaced too may times. No more defacement on macs.... at least via the macs connected to the internet.

  20. Maybe... by Anonymous Coward · · Score: 1, Informative

    You need 7 bits for 128 characters symbols. With 6 bits you can have all capital letters, but not the lowercase.

    With an additional bit (totalling 8), you have all the ASCII 128 chars plus another 128 for special symbols (line-drawing semigraphical chars and accented chars).

    Once 8-bit memory modules (i.e., hardware chips) became standard, people joined two to build 16-bit memory words -- and then 32... 64... 128... ops, not yet :-)

    HTH.

    1. Re:Maybe... by Jhan · · Score: 2

      Well, with 6 bits you can have the capital letters and some punctuation.

      With 12 bits, you can have all the European alphabets, and Russian and (some) Japanese.

      With 24 bits, you can have Unicode. (No, you can't have Unicode in 16 bits. It's grown to 21 bits already (allthough only 2^20 code positions are actually in the code).)

      To conclude: 12 bits, 4096 characters, is a very good size for a rudimentary global character set. 24 bits lets you use all of Unicode (21 bits) and is a much better fit than 32 bits.

      --

      I choose to remain celibate, like my father and his father before him.

    2. Re:Maybe... by Anonymous Coward · · Score: 0
      With 6 bits you can have all capital letters, but not the lowercase.

      No you use a shift character to shift between upper and lower case, like you have on your keyboard!

      Really clever people have TWO shift characters - so where ever they started, they know where they are after a shift. SOme of us remember telexes starting with NUMBERS, NUMBERS, as the shift was often releated - I don't know why.

    3. Re:Maybe... by norwayjose · · Score: 1

      You only need 5 bits to code all the capital letters. Do a search on Baudot, the character set used by teletypes. It was quite innovative for its time and is still in use for TTY access if I'm not mistaken.

      By the way, 16 bit machines predate 8 bit memory modules (hardware chips) by quite a bit. The old Honeywell 316/516/716 series were 16 bit computers and used core memory. BBN used them to build the IMPs used for Arpanet.

  21. What for? by archeopterix · · Score: 3, Funny

    8 bits should be enough for everyone.

  22. Good genes! by ekrout · · Score: 2

    From: http://www.grillet.co.uk/biog.html

    "My mother was a Fortran programmer using computers that looked like this [picture of an ancient IBM 608-series supercomputer]"

    --

    If you celebrate Xmas, befriend me (538
  23. Intersil chip by Anonymous Coward · · Score: 0

    DIdn't Intersil make a single-chip implementation of the PDP8? As someone noted earlier, this should pose no problem anymore; even an undergrad should be able to tackle it.

  24. Big Deal by Anonymous Coward · · Score: 0

    I build the first mnemonic memory circuit using stone knives and bear skins.

  25. Text based games by Technician · · Score: 5, Interesting

    I remember playing the father of the Zork series of games on a PDP 11/35 which was the newer 16 bit machine. The game was called Adventure. We got the game on a 5 Meg 14 inch hard drive (RK05) and wasted a bunch of paper making moves on a keyboard/printer terminal. The scrollback feature of the hardcopy was great for finding your way out of a maze again. Adventure has since been ported to CPM and DOS. The game is still a great game and will challenge the thought process. Take a pencil and paper to keep from getting lost. There is no map. Do a google search to find this true classic game. You should be able to run it in a DOS window on Windows 95 before DOS and Windows 95 expire at the end of this year. I'm still trying to figure out who the shadowy figure is who tries to get my attention.

    --
    The truth shall set you free!
    1. Re:Text based games by richwmn · · Score: 1

      I was only able to play the original Adventure
      for a few minutes, but the BSD Games section of
      Slackware Linux install has an Adventure game
      that seems remarkably similar

    2. Re:Text based games by Arandir · · Score: 2

      It hasn't died. The C translation by Jim Gillogly is available in the FreeBSD source tree. The translation from Fortran to C was pretty basic. I've never seen so many goto statements since the days of BASIC.

      --
      A Government Is a Body of People, Usually Notably Ungoverned
    3. Re:Text based games by cburley · · Score: 1
      The translation from Fortran to C was pretty basic.

      What the heck kinda language is "pretty basic"?

      --
      Practice random senselessness and act kind of beautiful.
    4. Re:Text based games by Sri+Lumpa · · Score: 1

      There is a game called adventure in Debian; I think it is coming from BSD and is probably a port of the original. It says at the start:

      "This program was originally developed by Will Crowther. Most of the features of the current program were added by Don Woods. Address complaints about the UNIX version to Jim Gillogly."

      --
      "The obvious mathematical breakthrough would be development of an easy way to factor large prime numbers." Bill Gates,
  26. Wankel! by Anonymous Coward · · Score: 0

    Never mind a beowulf...Imagine a wankel engine in one of those!

  27. a PDP8 was my home machine in 1976 by MarkWatson · · Score: 3, Interesting
    But, it was just an Intersil Intercept Jr. single board version of a PDP - same instruction set though.

    It was fairly easy to program for - I wrote a simple cross-assembler on a Dec-10 that would print out my assembler source with machine code (in octal). For short programs, it was fairly quick to enter the programs in octal. Since the Intercept Jr. was all CMOS, the programs would stay in memory as long as I wanted without runnng down the batteries.

    Really, it was very cool, and fun.

    -Mark

  28. |337!!! by RAMMS+EIN · · Score: 1

    does that mean we get the PDP-endian nightmares back, too? And maybe ITS, too? (I'm quite sure I'm confusing PDP incarnations here, though)

    --
    Please correct me if I got my facts wrong.
  29. What a memory... by NormAtHome · · Score: 2, Interesting

    We had one of these in high school (25 years ago), looking back I thought it was pretty cool but man that single DEC tape drive was a royal pain. We also had an old teletype with a paper tape punch, haven't seen one of those since. In my junior year we got a grant from the state and got a PDP-11 with dual 8 inch single sided floppies, now that was living!

  30. Why cling to the past? by reitoei1971 · · Score: 2, Insightful

    I just dont see the point of resurrecting 12-bit hardware when we have 64-bit now. Why the nostaglia? PDP is dead! the world will never see another 12-bit. Is this guy a museum curator?

  31. Address Space by Detritus · · Score: 2
    The PDP-8 had a 4K (4096x12) address space.

    Somewhere I have an old DEC PDP-8 handbook. They released a native FORTRAN compiler for the PDP-8. It just shows what you can do with clever coding and lots of overlays.

    --
    Mea navis aericumbens anguillis abundat
  32. Didn't these things have selectable word sizes? by GreyPoopon · · Score: 4, Interesting

    I remember seeing one of these puppies when I was in high school. It was no longer in service, but still had most of its internal components. In fact, I still have one of the "flip chips" that I took from inside it. Anyway, I believe I recall a dial on the front of the main panel that allowed you to choose the word size. I can't remember whether 12 bits was the minimum or the maximum, though. Can anybody verify that this existed, or am I just remembering some strange dream?

    --

    GreyPoopon
    --
    Why is it I can write insightful comments but can't come up with a clever signature?

    1. Re:Didn't these things have selectable word sizes? by HotNeedleOfInquiry · · Score: 5, Informative
      "or am I just remembering some strange dream? "

      It's a strange dream. The only 8's that had a knob on the front were PDP 8/e, 8/f, and 8/m and they all shared basically the same front panel design. The knob selected the register that would display on the front panel. It had no effect at all on the operational mode of the machine.

      --
      "Eve of Destruction", it's not just for old hippies anymore...
    2. Re:Didn't these things have selectable word sizes? by Liquor · · Score: 1

      I think you may have been the unwitting victim of a fairly common joke that occasionally was pulled on the innocent visitors when I was working in a university computer lab in the early 70s.

      The lab had a PDP8M that was the controller for a prototype communications network between quite dissimilar computers. Due to the data sizes involved, the program counter register would have all it's bits flickering, but the accumulator would only have 8 bits flickering (it was exclusively handling octets of data all the time) and one other register - index? - I forget now - would only have 4 bits flickering (because this prototype network only had 4 nodes, numerically 1, 2, 4 and 8, so we could see the pattern in the lights to tell which nodes were using the network).

      So we used to tell visitors who didn't know better that the switch changed the word length from 4 bits to 8 bits to 12 bits, and we left it on 12 bits because it was obviously faster (the program counter changed faster than the other two as well.... and the machine was slow enough that you could see the difference.)

      Sorry about that :)

      --

      Liquor
      Sanity is a highly overrated commodity.
    3. Re:Didn't these things have selectable word sizes? by GreyPoopon · · Score: 1
      It's a strange dream.

      Please tell me that it could have been some piece of equipment connected to the machine that had the adjustable word size. If I were to have a dream *that* real, it had better not have anything to do with computers. ;)

      --

      GreyPoopon
      --
      Why is it I can write insightful comments but can't come up with a clever signature?

    4. Re:Didn't these things have selectable word sizes? by GreyPoopon · · Score: 1
      I think you may have been the unwitting victim of a fairly common joke that occasionally was pulled on the innocent visitors when I was working in a university computer lab in the early 70s

      Good joke, but I don't think this was the case. I never saw the machine in operation, and I distinctly remember one knob that was either labeled "word-size" or "byte-size", with a few numbers around it. I remember thinking how odd this feature was. Also, the only machine's I had been exposed to at the time had 8-bit bytes, so I really thought it was wierd. However, I'm thinking now that maybe this knob was part of some peripheral device that was configurable.

      --

      GreyPoopon
      --
      Why is it I can write insightful comments but can't come up with a clever signature?

    5. Re:Didn't these things have selectable word sizes? by dhogaza · · Score: 2

      Speaking of front panels ... the PDP-8's front panel was made of glass and the design was silk-screened on it by hand. The cabinet was a basic rack with plywood siding ... though they originally offered a transparent plastic case, too - cool case mod for the mid-1960s, eh? :)

      I still have the glass front panel from the PDP-8 that I worked on back in high school ... I snatched it when it was scrapped. We owned a five-cabinet beauty, 12KW core, four DECtapes, a high-speed paper tape reader, an original Centronics dot-matrix 120 CPS printer, an RF08 head-per-track system disk (full cabinet of its own) and the first Tektronix storage-tube monitor with joystick that was four feet long and weighed a lot ...

    6. Re:Didn't these things have selectable word sizes? by Gordonjcp · · Score: 2

      Many years ago, before I got kicked out of Uni for never turning up because I hung about in the computer rooms all day, there was a comms rack with a big slide switch on the front. A paper label had been stuck above it, covering the original markings, labelled "P-R-N-D-L"...

  33. Since China and Hong Kong unified in 1997.. by Inoshiro · · Score: 0, Offtopic

    Yes.

    --
    --
    Internet Explorer (n): Another bug -- that is, a feature that can't be turned off -- in Windows.
  34. PDQ8 = Pretty Damm Quacky by sifi · · Score: 1

    An interesting exercise for undergrads. If he used a Virtex II Pro he'd have upto 4 power PC 405's on a single chip (not to mention all that reconfigurable logic).

    Now some real nice research would be to see how to those processors could be combined with reconfigurable logic to give some real power.

    --
    Sig (appended to the end of comments you post, 120 chars)
  35. Only 12 bits? by r_j_prahad · · Score: 2

    How can they possibly expect us to use the efficient new Radix-50 character encoding to store text? RAD-50 requires 16 bits to compact characters.

    DeCastro was right, this 12 bit nonsense will never go anywhere.

  36. Resurecting old hardware designs by randomErr · · Score: 4, Insightful

    Some mentioned earlier on this thread jokingly about making a super fast computer based on old architecture.

    Has anyone actually done that? Has anyone actually taken say, a Tandy Color Computer 3's hardware and boosted it up to something approaching our current standards? I'm not talking emulation on a x86 platform. I mean fully working with a processor with a native OS.

    Those architecture are so simple, with kernels so small you could print the hex binary out on a couple of pages. Imaging how fast an accounting package would be on a 1 gHz, or even a 200 mHz.

    I know this maybe off topic, but if someone could resurrect a 12-bit system to a more modern standard, why not other system. DOS is still viable in certain circumstances, why not these platforms.

    Think about an 8-bit controller with a serial connection, flash memory, and a RCA video out jack that is based on a C64. There is a TON of documentation for programming on something like that. Linux guruâ(TM)s could use C/C++ and Windows users could use Commodore BASIC.

    Oh well thatâ(TM)s just my ramblings.

    --
    You say things that offend me and I can deal with it. Can you?
    1. Re:Resurecting old hardware designs by Richard_at_work · · Score: 2

      I used to work for a UK supermarket in the Cash Office, and the PC that ran all the Checkouts and the SSM system (stock management) was a lowley 486-66 pc with 48mb ram, and it crawled. It took 4 hours to do a standard end-of-week data compile. It ran some wierd IBM Dos OS, and used green screens etc.

      Then one day they replaced it with a PIII700 system, 128mb ram the works. Still ran this IBM Dos OS, but the end of week took seconds. Literally, we could no longer get away with a 4 hour break!

      The same supermarket is still using this Dos OS on p4s now, so i wonder what the speed is like now.

    2. Re:Resurecting old hardware designs by Anonymous Coward · · Score: 0

      Linux guruâ(TM)s

      Linux guru[a-circumflex][euro][trademark]s?

    3. Re:Resurecting old hardware designs by Anonymous Coward · · Score: 0

      I think you're on to something! I thought about this a few years ago with regard to handhelds. With todays manufacturing, you could probably cram the entire Amiga 500 chipset + supporting circuitry (video, audio filter, etc) onto a single piece of silicon. And if not one, at most three.

      Now, all the 'Amiga is Dead' comments aside, how fantastic of a handheld would one of the original Amiga 500's with a 640x400 LCD be? Give it a nice CF drivebay and we're talking about some serious flexibility. Lots of apps (and plenty of games!) would run on that bad boy.

    4. Re:Resurecting old hardware designs by Anonymous Coward · · Score: 0

      ...you could probably cram the entire Amiga 500

      Now that, I like! Stereo sound, good color performance (probably not use 4096 HAM, but maybe) great games, hmm...

      When can we get started?

    5. Re:Resurecting old hardware designs by pyrosoft · · Score: 1

      Try viewing in UTF-8 instead of ISO-8859-1. That fixed it for me (Linux/Mozilla 1.2b).

      --
      Great spirits have always encountered violent opposition from mediocre minds. Albert Einstein
    6. Re:Resurecting old hardware designs by pommiekiwifruit · · Score: 2
      Yeah but what's wrong with using ye olde apostrophe from ASCII? Will he be using the full-width japanese ROMAJI characters for normal text next? g...(TM)C--(TM) Z"!

      Much as I love utf8, I can't see in the source code where slashdot specifies that encoding.

    7. Re:Resurecting old hardware designs by SpitFU · · Score: 1

      Someone else has had to have done this but when i was 14 or so, I had an Atari 800XL not the pop top ones that fit two cartridges but the slot ones that only fit one cartridge.

      The point....

      I upgraded that sucker to 1 meg of memory by stacking and soldiering the old 64k memory chips near the back. I had to cut a hole in the top of the Atari's case to stack the chips. It protruded about 3 inches above case.
      In addition, I picked up one of those ATR8000 interfaces and hooked up a 20 MB, Seagate ST-525 or 255 (I forgot which?) MFM hard drive, and a 5 1/2 toshiba floppy which I think it was a 360k floppy at the time. Booted that sucker with SpartaDOS.

      You're probably asking why? Well I ran a pretty successful Wildcat BBS out in California on that sucker. Ran it for about 3 years. I paid less for it then my PC using buds. The thing rarely went down. I'd hazzard that it had less downtime then most IIS servers nowadays.

      --
      reassign null to be the tape device - it's so much more economical on my time as I don't have to change tapes_BOFH
  37. Not Bad for its day by Anonymous Coward · · Score: 2, Informative

    The PDP-8 wasn't bad for it's day. They even had a Time Sharing System that ran on it that gave each user a whopping 4 K of space do do whatever they wanted to do with it. It supported up to 16 simultaneous users. I know, I'm old enough to have gone to a college with one of those beasts as a shiny new grant from DEC. We had 2 high schools and one private school hoked up to us by the old 110 Baud ASR-33 teletypes. It was a hoot trying to make anything run on it. Assembler was about your only choice as Basic didn't have any file I/O until about 1973 - 1974.

    Why bring it back? Why not? It may not ever be used for much, however who says all the cool computers have to be uber-machines? This next comment isn't meant to start a flame war, but I'd like to see some of today's bloatware folks try and make a program of any substance work on one of those puppies. I've seen some code from folks used to huge addressable and virtual memories and YIKES !

  38. Because, as Tom Lehrer, formerly of MIT noted. . . by kfg · · Score: 3, Funny

    "Base 8 is just like base 10 really. . .if you're missing 2 fingers."

    KFG

  39. Six copies of Windows by Anonymous Coward · · Score: 5, Funny

    What else would be a 12-bit OS?

    1. Re:Six copies of Windows by MortisUmbra · · Score: 1

      .... I don't know whats worse....this joke or the fact that it got modded to +4....

      --

      "The saddest words of mice and men, are not those which were, but should have been."
    2. Re:Six copies of Windows by Anonymous Coward · · Score: 0

      It's pretty funny man.

      You need to have lived a bit to appricate that joke.

      It's based on another joke I think. The one about bill gates and his 0010 bit windows. :) Get it? duh if not.

      --
      Mirenda code baby

  40. XYZZY by MosesJones · · Score: 4, Funny


    And of course

    "with your bare hands?"
    yes
    you stand amazed as the dragon lies dead at your feet.

    Bugger graphics you can't beat a maze of twisty passages, all different.... or was it a twisty maze of different passages.

    --
    An Eye for an Eye will make the whole world blind - Gandhi
    1. Re:XYZZY by Anonymous Coward · · Score: 0

      It's "A maze of twisty passages, all different" and
      "A maze of twisty passages, all alike". The battery machine was in the "... all different" maze. The pirate's chest was in rooms reachable only via the "... all alike" maze.

    2. Re:XYZZY by serutan · · Score: 2

      It was, "a maze of twisty passages, all alike."

  41. Character Codes by Detritus · · Score: 3, Informative
    6-bit character codes were popular before the introduction of ASCII (7-bit) and EBCDIC (8-bit). The PDP-10 had a 36-bit word, which could hold 6 6-bit characters. It also supported other character codes, such as ASCII.

    If you look at old assemblers and compilers, the limit on the length of a symbol/variable name is often the number of characters that could be squeezed into a single machine word.

    --
    Mea navis aericumbens anguillis abundat
    1. Re:Character Codes by dhogaza · · Score: 2

      And the CDC 3000 series had 24 bits (4 6-bit characters) and the 6000 series had 60 (10 6-bit characters). CDC peripherals were sixbit, not 7-bit Ascii + parity.

      Of course the PDP-8 came with a TTY 33 or KSR 35??? whatever the hell the heavier-duty TWX teletype machine was called. These were 8-bit.

      TWX machines used 7-bit encoding with a parity bit that later was the basis for the standard Ascii/Ansi/ISO character sets we're all familiar with. I don't know if the standard was approved before or after Western Union deployed TWX machines (replacing the earlier 5-bit encoded Telex machines I believe? I'm not quite old enough to know for sure, TWX was in by the time I was in high school).

      Anyway these 7-bit + parity teletype machines originally made for use on the TWX network were pretty ideal for a low-cost computer made by what at the time was a very small computer company. Rather than develop their own terminals ala IBM or CDC, Digital just bought TTY 33s as the console.

      Despite the use of 7-bit Ascii using teletypes machines as consoles on the PDP-8 (and the 18-bit and 36 bit families as well), it was common to just use sixbit for many things. For instance OS/8 used six bit characters for file names - upper case only, six character file names and a two-character extension. But editors and many other applications allowed upper and lower case characters and packed 3 8 bit characters into 2 12-bit words ...

  42. Nostalgia by Anonymous Coward · · Score: 1, Informative

    I "fondly" remember this as my first system I worked on.... We had three. Two of them didn't have a boot card, so you actually had to toggle in a boot loader program (around 20 or so steps). It was like playing a piano. They had 3 RK05 disk packs (1.5M each), 32MB of Ram, and a 300 baud terminal. But it handled 16 simultaneous users. It put out our newspaper every day for many years. They punched paper tape for output that we would run into type typesetting machine.

  43. PDP8? How about a PDP11??? by Spatch3 · · Score: 2, Interesting

    You know, I work with PDP11's day in and day out. DEC's last PDP processor was, I believe, a PDP 11/93. It has a whopping 2 MB of RAM and 8 serial ports on the processor board! This was a double sized board only taking up 2 slots on the DEC backplane that took the function of 5 boards that took up 5 slots each. Of course the disk controller, clock card and other boards are separate. These boards are circa 1990. They are in a custom digital dictation system that can handle 64 simultaneous audio ports where people are either dictating or transcribing. The OS is the roll off your tounge: RSX11M+. These systems, which we are replacing slowly but surely, have been absolute work horses lasting for at least 10 years.

    I jsut had to reboot one this morning... :)

    Chris

    --

    Every rule has an exception, and this is the only rule with no exceptions! Huh? -- Spatch
  44. Because, as Tom Lehrer, formerly of Harvard, noted by Interrobang · · Score: 2

    ...well, you could just omit using your thumbs...but that wouldn't be as masochistic (tango-y goodness!)...

    Tom L. has always been a Haavaadite, not from MIT, as in the "Harvard Fight Song," and the lines, "These are the only ones of which the news has come to Haavaad/And there may be many others, but they haven't been discovaad." (Rhotic-lossy dialects bother me, since I speak one of the few English dialects that's fully rhotic.) I imagine it matters to some people (probably they go to Harvard).

    Also, as far as I know, he's still there, although long since an Emeritus.

  45. This is terrible by Punk+Walrus · · Score: 1
    ... ever have one of those nightmares that you are required to take a test back in college, and you realize, "Oh no! I haven't studied the subject in 20 years! And where are my pants?" Then you wake up, and you realize the silly and illogical nature of your dream. Ha ha... no one would ever bring back the PDP line. Ha ha ha... whew! Now I think I'll read Slashdot...

    Doh! [check] Whew... got pants.

    __________________________________________________ _
    I smell a Wumpus! Shoot or move? [S/M]

  46. PIC is a bit more practical by Bruce+Perens · · Score: 4, Interesting
    If you want to program old microcomputer architectures, learn the PIC microcontroller, which is based on some Control Data Co. Peripheral and Input Controller (I may have the "I" wrong in that acronym). It's available in 12, 14, and 16-bit flavors. It doesn't have much of a stack. And it has the virtue that, as a $1 microprocessor, it's still practical for many projects, while a PDP-8 is really an intellectual exercise at this point.

    Bruce

    1. Re:PIC is a bit more practical by gTsiros · · Score: 1

      PIC stands for Programmable Interrupt Controller.
      It really is a very minimal CPU.

      --
      Looking for people to chat about multicopters, coding, music. skype: gtsiros
    2. Re:PIC is a bit more practical by mesocyclone · · Score: 2

      I still do a lot of programming for embedded applications in an older 8-bit computer architecture (Motorola 6800). They are still selling millions of the embedded versions of this (MC68HC05...).

      It ain't purty, but it's amazing what you can do with a 8 KBytes of EEPROM and 384 bytes of RAM!

      This programming, of course, is in assembly language, because C has too much memory overhead.

      Oh, btw, the typical machine executes under 1,000,000 unstructions per second.

      --

      The only good weather is bad weather.

    3. Re:PIC is a bit more practical by homemademissiles · · Score: 1

      The PIC microchip is also quite a bit smaller than a PDP-8. The PIC being not much bigger than a postage stamp, has the advantage of being useable in hand held, battery powered equipment. A PDP-8 based on FPGA's may well be much smaller, but is unlikely to ever approach the tiny dimensions of the smaller PIC's. Additionally there is a ton of projects available for the PIC's on the web including an awful lot of free development software. If you want to dabble in funny bit-widths, the PIC approach is certainly easier...

    4. Re:PIC is a bit more practical by Bassman59 · · Score: 2, Informative

      gTsiros:

      PIC stands for Programmable Interrupt Controller.

      When talking about the 8254, yes (but that part's not really not a "CPU"), but in this case, we're talking about something like Microchip's PIC family of gizzies, which are usually called "Programmable Integrated Controllers" or "Peripheral Integerated Controllers." ahhh, acronyms...

    5. Re:PIC is a bit more practical by gTsiros · · Score: 1

      oh. that's good to know.
      thanks.

      --
      Looking for people to chat about multicopters, coding, music. skype: gtsiros
    6. Re:PIC is a bit more practical by Gordonjcp · · Score: 2

      Programmable Interface Controller, actually... It is indeed a fairly minimal CPU, but is nonetheless extremely powerful.

  47. Will the French OS wave a white flag? by Anonymous Coward · · Score: 0

    Instead of a BSOD?

  48. Re:I'd rather they by Anonymous Coward · · Score: 0

    that's beautiful, man.

  49. Stupid Question by Anonymous Coward · · Score: 0

    YOU FOOL!! This is slashdot. All you need is Linux.

  50. Reminds me of... by Tsali · · Score: 3, Funny

    a rough quote from Monty Python...

    "I built the castle in the swamp. They said it would fall over but I did it anyways. Sure enough, it did. I build a second castle and that one fell into the swamp as well. But the third castle stayed."

    Looks like he needs another iteration.

    --
    This space for rent.
    1. Re:Reminds me of... by Jhan · · Score: 2

      Less rough, though still offtopic quote:

      When I first came here, this was all swamp. Everyone said I was daft to build a castle on a swamp, but I built it all the same, just to show them. It sank into the swamp. So I built a second one. And that one sank into the swamp. So I built a third. That burned down, fell over, and then sank into the swamp. But the fourth one stayed up. And that's what you're going to get, Son, the strongest castle in all of England!

      (No longer to-the-word-)But I just want to sing: ... And no singing!

      --

      I choose to remain celibate, like my father and his father before him.

    2. Re:Reminds me of... by Jogar+the+Barbarian · · Score: 1

      You've almost got it.

      Listen lad. When I came here all these lands were swamp. The king said I was daft to build a castle in a swamp, but I built it all the same! Just to show him! It sank into the swamp. So! I build a second one. That sank into the swamp. So I built a THIRD one! That one burned down, fell over and then sank into the swamp. But the fourth one... STAYED UP! And that's what you're going to get, lad... the strongest castle in these isles!

      --
      3. Profit!
      2. ???
      1. On Soviet Slashdot, a Beowulf cluster of alien Natalie Portman overlords welcomes YOU!
    3. Re:Reminds me of... by Tsali · · Score: 1

      I knew I blew a lot of it..... and to think I've got the DVD at home without any dust on it....

      --
      This space for rent.
  51. Re:Because, as Tom Lehrer, formerly of MIT noted. by oliverthered · · Score: 2

    Wow, 10 fingers, how many thumbs do you have?

    --
    thank God the internet isn't a human right.
  52. I blew up a PDP8 - and survived by Ella+the+Cat · · Score: 3, Interesting

    I'm old enough to have done an electronics project building a joystick interface for a PDP8 as an undergraduate. I spent ages soldering TTL chips and after a few weeks plugged the card in, to a strong smell of fish and burning insulation. It wasn't my fault, the slot in the edge connector was too wide, and every single connector on the backplane had shorted to every other. It was 6 months to get the machine repaired, so someone figured out they could take out the power transformer, scrape off the burnt mess, figure out how many primary and secondary turns were needed on the transformer, then wind them on using a reel of wire and a lathe. They go the machine going, someone else filled the board slot with epoxy and cut a new slot. My project was saved! A few weeks later i reached round the back of a PDP8 to unplug a power connector, grabbed the live pin, but was saved because my arm was earthed to the PDP8 case. I love that machine, I still have the instruction set on a sheet of paper.

  53. Just use the history simulator by ch-chuck · · Score: 3, Informative

    run your very own pdp8, pdp11 or even an Altair with disk basic or cp/m - here. I've recently completed some serious z80 assy projects using simh on my Linux notebook. Works great w/o having to mess w/ flaky hw.

    --
    try { do() || do_not(); } catch (JediException err) { yoda(err); }
  54. I loved the PDP-8 but I'm not convinced... by dpbsmith · · Score: 4, Interesting

    Until I actually started programming a PDP-8 (in assembly language, of course), I would never have believed that you could program comfortably in such a seemingly restricted instruction set. And, conversely, when I moved to a PDP-11, I thought I was going to revel in the freedom and power of all those instructions, all those registers, those addressing modes, those index registers... and the ability to access 65536 bytes directly.

    If C is "high-level assembly language," then the PDP-11 is "a computer that directly implements C."

    To my surprise, though, I didn't really find that a lot was gained. Programming a PDP-11 didn't really FEEL much easier or more powerful than programming a PDP-8. And it was amazing how much every program expanded in size. It's been said that the PDP-8 instruction set was the most core-efficient ever devised, and I'd believe that.

    On the other hand, when I tried programming a 6502, which on the face of it doesn't SEEM that much more restricted than a PDP-8, I just about went bananas.

    Having said all that, I'm still not sure I see the point. The sweet design for a computer has to depend on the economics of the hardware around it. Who cares? Even IF the "core-efficiency" thing were true, and even IF you could use standard RAM with a 12-bit processor and not waste any bits, and even IF it turned out that the PDP-8 design were, say, 30% faster and used 30% less RAM for a given program than x86... how could it matter?

    If the Alpha, which really WAS a superior design, wasn't superior enough to overcome Intel marketing, customer inertia, and only the normal amount of mismanagement, how can a PDP-8 be anything more than a curiosity?

    1. Re:I loved the PDP-8 but I'm not convinced... by dhogaza · · Score: 4, Insightful

      If C is "high-level assembly language," then the PDP-11 is "a computer that directly implements C."

      Actually it's fair to say that C was developed as a "high level assembly language" for the PDP-11, in other words you've got it slightly backwards. The postfix "++" and prefix "--" operators correspond to the PDP-11's autoindexing mode and when applied to a dereferenced pointer map directly to "(Rn)++" (once the pointer's been moved to a register.

      I doubt C would have these constructs if the PDP-11 didn't provide the corresponding register mode.

      As far as the PDP-8 being perhaps the most core-efficient design ever, speaking as someone who once developed system software for the PDP-8 and afterwards compilers for the PDP-11, yes, I'd say you're right.

      As long as you could fit program and data into 4096 12 bits words, that is. If your program could fit into 4096 12 bit words accessing data in the remaining 28KW was relatively easy due to the semantics of the CDF instruction. But once your code itself outgrew the first 4096 words things got bad in a hurry, because cross-bank subroutine calls using the CIF instruction were fairly expensive.

      Gordon Bell designed both the PDP-8 and the PDP-11, and they were designed with different goals in mind. The PDP-8 was designed to be programmed in assembly code - the page and memory bank addressing structure made the development of efficient compilers impossible (it's not an accident that no system programming language like C was never implemented for the PDP-8 architecture).

      The PDP-11, on the other hand, was the first minicomputer designed with the compiler writer in mind. The instruction set was very easy to generate code for, much easier than for many mainframe machines that in those days still often had a single accumulator and some auxillary special-purpose registers. The PDP-11's clean, general-purpose register design and (relatively) orthogonal instruction set made compiler writers like myself almost faint in anticipitory pleasure when the design was first announced.

      While Gordon Bell designed the PDP-8 and PDP-11, the original engineering plans for the PDP-8 are signed by DeCastro, who did the implementation. He submitted a rival design for DEC's 16 bit minicomputer that was no where near as clean or compiler-writer-friendly as Bell's PDP-11 design.

      When the PDP-11 design was chosen, DeCastro left and started Data General, and his 16-bit design became the oft-loathed Nova.

      CDC's 12-bit PIC design was much inferior to the PDP-8's, IMO ... the PDP-8 still serves as a great example of minimalist design in an era where each bit of the accumulator was implemented by a double-width card (each BIT, thirteen of these cards in all, 12 for the accumulator bits and one for the overflow LINK bit).

    2. Re:I loved the PDP-8 but I'm not convinced... by dpbsmith · · Score: 2

      'Actually it's fair to say that C was developed as a "high level assembly language" for the PDP-11, in other words you've got it slightly backwards.'

      Quite right. I DID know that. Really I was making a joke. I should have put in a smiley.

      Although I do think one of the things I like best about C was recognizing that "increment" and "decrement" are fundamental operations of their own that are NOT well represented by the assignment statement a = a + 1, and deserve a special notation.

    3. Re:I loved the PDP-8 but I'm not convinced... by Ungrounded+Lightning · · Score: 2

      Gordon Bell designed both the PDP-8 and the PDP-11, and they were designed with different goals in mind.

      Actually Gordon Bell designed the PDP-5 (same instruction set as the PDP-8), then DeCastro did the PDP-8 hardware implementation.

      The PDP-8 was designed to be programmed in assembly code - the page and memory bank addressing structure made the development of efficient compilers impossible (it's not an accident that no system programming language like C was never implemented for the PDP-8 architecture).

      The actual target of the PDP-8 was to be tiny and cheap (yet powerful enough to be useful). Thus the RISC-anticipating instruction set. ... DeCastro ... submitted a rival design for DEC's 16 bit minicomputer that was no where near as clean or compiler-writer-friendly as Bell's PDP-11 design.

      When the PDP-11 design was chosen, DeCastro left and started Data General, and his 16-bit design became the oft-loathed Nova.


      What happened was IBM was moving from 6-bit to 8-bit bytes. DEC realized that powers-of-two word sizes was the way of the future - making the next logical minicomputer a 16-bitter. So they put their two star architects to proposal writing.

      Gordon Bell said that the thing to do was to write a couple languages to simulate the hardware and software, co-develop the instruction set and a compiler to tune up the instruction set, co-design the processor, memory, backplane, and peripheral card skeletons to optimize the hardware design, and generally do things efficiently and beautifully - after which you'd have an inexpensive, powerful machine that would take over the market for the next generation of minis and easily evolve to handle larger tasks.

      DeCastro said you could quickly hack up a 16-bit followon to the PDP-8, hit the market a year earlier, sell a bunch, enable a lot of embedded apps, and make a lot of money.

      Of course they were both right.

      DEC went with Bell's proposal. So DeCastro went out and founded Data General. And the Nova got to market sooner, enabled a lot of embedded applications, sold a lot of units, and made a lot of money. Then the PDP-11 came out and was also a big hit. And the PDP-11 was easier to program and easier to upgrade, so after a couple generations it took over.

      The original Nova had its points. Like a very efficient hardware design. (Cute use of a single 4-bit ALU slice and a single 4-bit register file chip, 4 times as fast as the RAM's cycle, to build a 16-bit processor running at the RAM rate. Reminicent of the stuff Cray did while still at Control Data.) But the Nova was a "16-bit PDP-8" thorugh and through - with the control lines of that ALU chip showing up in the "operate" instruction's microcode bit pattern. It just didn't scale well, and compilers for it were a pain. Meanwhile the PDP-11 scaled very nicely (as a microcoded machine after the first PDP-11/20) and was a breeze for writing both compilers and multitasking OSes. So a DOS, RSX-11, and then Unix were written for it, the followon VAX fixed the few design flaws that eventually put a crimp in its ability to scale, and the Nova became a dinosaur.

      --
      Bantam Dominique roosters crow a four-note song. Once you've heard it as "Happy BIRTHday" you can't NOT hear it that way
  55. Don't Post "why?"!!!! by screwthemoderators · · Score: 1

    I am really sick of /.ers asking "why do this?" Why don't you actually use your overstuffed, overeducated brains and IMAGINE SOME USES FOR IT, YOURSELF! Isn't that part of the idea behind open source? You build something for yourself, and then let others improve upon it. Why should it be so different when the project isn't implemented in software? It shouldn't. If you can't figure it out DON'T POST

    1. Re:Don't Post "why?"!!!! by Anonymous Coward · · Score: 0

      A real nerd wouldn't need to ask. A real nerd would already have thought up a hundred possible uses for it. Good luck finding any real nerds on slashdot. Any place that would make fun of the way Taco looks isn't very nerd-a-rific in my eyes.

  56. More power to 'im by Angst+Badger · · Score: 2

    Sounds cool, and reminds me of a project I've been tinkering with for about a year now -- a multiprocessor system based on the 6502 (actually, the 65c02), the same chip as was in the Apple II, Atari, the C64, and the original NES, among others. Problem is, my electronics knowledge at this point is not good enough to get beyond a good theoretical knowledge of what would be involved, though my 6502 assembly language skills are still sharp enough to write the firmware and software.

    I only mention this because I hope someone who does have the requisite electronics skills will email me so we can join forces.

    As for the earlier post to the effect of "what is it good for?", I can only say that it's fun to do, and old computers are good for the same things they were good for when they were new. One may as well ask what a 1965 Mustang is good for.

    --
    Proud member of the Weirdo-American community.
    1. Re:More power to 'im by Anonymous Coward · · Score: 0

      The automobile industry had reached a degree of refinement by 1965 such that great leaps forward had ceased. A serviceable '65 Mustang is a practical everyday driver, support is a breeze, and the operations and maintenance cost is quite modest.
      Computers are now where cars were in about 1920.

  57. Re:Because, as Tom Lehrer, formerly of Harvard, no by Anonymous Coward · · Score: 0

    (Rhotic-lossy dialects bother me, since I speak one of the few English dialects that's fully rhotic.)

    I'm assuming that the word Rhotic means including 'r' sounds in words. The definition couldn't be found on dictionary.com. Under that assumption:

    Here in Picksburgh, all yins Stiller Fans know how ta wursh yins dishes, right ya jagoff??

  58. DecMate word processor by jhines · · Score: 2

    The PDP-8 had a long life as the Decmate word processor, the 12 bit word did very well, as it could handle text, with bold, underline, etc directly.

    The 3rd party service man at a VAX site I worked at in the early 90's had a PDP-8 (W/ RK05's!) still under contract in a big milling machine at a local heavy manufacturor.

    1. Re:DecMate word processor by oh · · Score: 2

      I know of a site that still ahs several PDP-11 (actualy PDP-11 clones) in production. This is in 2002!!!

      They control a specific piece of hardware, and since they still use that hardware, the PDP's are still in use. Trouble was, when they had a disk failure, they had to find some one who could rebuild a RSX-11 system.

      --
      Democracy isn't about no one telling you what to do. It's about everyone telling you what to do.
  59. KW == "kilowords" by red_dragon · · Score: 4, Informative

    Back then, the size of core memory was generally measured in machine words, thus in the case of a 12-bit machine like the PDP/8 with 32 k-words, the core would be: 32 x 12 bits == 384 k-bits, or 48 k-bytes.

    --
    In Soviet Russia, Jesus asks: "What Would You Do?"
    1. Re:KW == "kilowords" by lfourrier · · Score: 2

      If I remember correctly, at the time, a byte was a proceessor word long. Only ecently the meaning changed for eight bits. so 32 kw would have been 32 kB.

    2. Re:KW == "kilowords" by red_dragon · · Score: 1

      Yes, that's how it went. IIRC., it was IBM that introduced the notion that one byte is exactly eight bits, and the meaning has stuck since then. Along with that, PCs introduced the notion that one word is two bytes (16 bits), causing lots of confusion and the use of the term "machine word" to avoid ambiguity.

      --
      In Soviet Russia, Jesus asks: "What Would You Do?"
    3. Re:KW == "kilowords" by KewlPC · · Score: 2

      Actually, IBM had nothing to do with the "a word is 2 bytes" thing. That was Intel, because the 8086, 8088, 186, and 286 all had a word that was 2 bytes long. But few people actually still go by the notion that a word is 2 bytes long, since even Intel processors now use a word size of 4 bytes (they have since the 386).

  60. Brings Back Memories by pdp11e · · Score: 1

    The very first computer i have ever played with was PDP-8/e. It was "loaded" machine with 16 k words of RAM (magnetic core of course). The front panel of the machine had a row of switches that enabled direct, true "machine language programming". You were able to manually deposit words, both in registers and memory. Since PDP-8 was 12 bit machine it was natural to represent the machine word in Octal.
    In order to boot system from scratch, you needed to deposit in memory ~20 word program called: "RIM" (Read In Mode). Once RIM is loaded it started punched tape reader in teletype in which you hopefully loaded "BIN" tape. Once The BIN program is started you had rudimentary OS for reading and running whatever programs you had on paper tapes. Most often we used "Focal", the interpreter very similar to BASIC. Later, we bought PDP-11 with 80 MB hard disk and multi user OS (note my user id), but "Eight" was the machine that hooked me for life.

  61. PDP-8 was not the first minicomputer by starling · · Score: 2

    That was the PDP-1, released in 1960, 5 years earlier.

    The PDP-8's distinction was to be the first mass-produced minicomputer.

  62. Measurements by Dom2 · · Score: 1
    What I want to know is, which fuckwit invented the stone? How many pounds are there in a stone? 14? Pass the crack pipe!

    Thank $DEITY for kilograms, a sensible unit.

    -Dom (an anti-imperial uk denizen)

    1. Re:Measurements by Chandon+Seldon · · Score: 2

      Tell me something. The atmospheric pressure at sea level is 15 psi using imperial measurements. Using metric, how would you specify that figure?

      --
      -- The act of censorship is always worse than whatever is being censored. Always.
    2. Re:Measurements by pommiekiwifruit · · Score: 2

      ~1000 millibars or 100,000 Newtons per square metre or 100 KiloPascals. What could be easier? But it varies quite a bit around 1013 millibars. (It's 999 millibars just south of Sardinia at the moment. Alas the weather map doesn't show psi or inches of mercury - do US ones?)

    3. Re:Measurements by swillden · · Score: 2

      The atmospheric pressure at sea level is 15 psi using imperial measurements.

      14.7 psi is closer to the average value. It varies a bit, of course.

      Using metric, how would you specify that figure?

      1 bar.

      --
      Note to ACs: I usually delete AC replies without reading them. If you want to talk to me, log in.
  63. you meanie... by Anonymous Coward · · Score: 0
  64. There's nothing to see here. Move along. by N2UX · · Score: 1

    This is by no means a new or unique project. PDP-8s have been cloned using various chips for years. There is the SBC-6120, the PDP-8/X and many others.
    Of course, none of these are as much fun as the real PDP-8/E and PDP-11 I have in my basement.

  65. You speak heresy, Grasshopper by kfg · · Score: 3

    C compiler indeed.The PDP-8 was natively a FORTRAN machine. Apps can be developed perfectly well in FORTRAN. . . and the coolness factor is higher.

    King Arthur: Noble FORTRAN compiler, although you are a dead language. . .

    FORTRAN compiler: I'm not dead yet sire.

    King Arthur: Although you are a mortally wounded language. . .

    FORTRAN compiler: Actually sire I'm feeling a bit of all right.

    Again, C compiler indeed. Gag my PDP-8 with a spoon. ( Actually, that would be 'anatomically' possible)

    Here's an interesting little page on the history of the PDP-8 OS's and languages:

    http://www.cs.uiowa.edu/~jones/pdp8/history.html

    And here's an interesting computer history page with several FORTRAN links ( as well as UNIX and C links):

    http://www.fortran-2000.com/ArnaudRecipes/CompMu se um.html

    C compiler. . . phbbbbbt!

    KFG

    1. Re:You speak heresy, Grasshopper by dhogaza · · Score: 2

      Well, damned few people used DEC's FORTRAN compiler for the PDP-8, and it was hardly "natively a FORTRAN machine". The FORTRAN compiler was a pseudo-code compiler, and the reasons for this are easy to see if you study the PDP-8 instruction set for a few minutes.

      The higher-level languages most frequently used on the PDP-8 were FOCAL and BASIC.

  66. Call it the QED8 by TheAwfulTruth · · Score: 2

    Let it RIP.

    --
    Contrary to popular belief, coding is not all free blow-jobs and beer. Those things cost MONEY!
  67. Emulators are the way to go. by Anonymous Coward · · Score: 0

    I would love to see someone put together a CDROM or a DVD of emulators and the history of the original harware complete with pictures. Can you imagine being able to browse through a history of 1000's of machines and actually be able to run an emulator for any of them.

    It would be like a digital museum of the history of computing. Wouldn't that be appropriate?

    I have an emulator for the C64 so that I can play a lot of the old games. I also have put together a mame based video game box, full sized. The thing stands 6 feet tall. Inside is a pentium 100 running an emulator so it will play old games like star defender and Q-Bert.

    As far as hardware goes, I believe that if I had an 8-way AMD sledge hammer with 32 GB of RAM and 100 Terabytes of RAID drive space then I would never need another new machine again. I just need smart terminals that all hook into the central computer to display results and control events.

  68. Re:PDP-8 was not the first minicomputer-Alleleuia by mikewhittaker · · Score: 1

    ... someone's noticed !

    In any case, wasn't Conway's original Life written to run on a PDP-7 ?

    I did write some s/w for that very machine - in BCPL - had to take the paper tape down to the machine room containing said PDP-7 and a couple of Data General Novas (Novae).

    Its attraction was that it had a vector graphics display, presumably why Conway used it to run Life.

    Kids of today ? Don't know they're born !

  69. taler by wiredog · · Score: 2

    and "taler" comes from the town of Joachimsthal, where the silver was mined.

  70. Actually 128 is here already by Anonymous Coward · · Score: 0

    Transmeta uses a VLIW (Very Long Instruction Word) technology. How long I did not see in a brief glance, but according to this article they have used 128 and 256. They do this as a way of encoding parallelism. Graphics processing also tends to have a lot of implicit parallelism which long instruction words help with. Both dedicated game consoles (eg the playstation) and graphics cards migrate to longer words much faster than general purpose computers. Years ago the 64 in Nintendo-64 was because it was a 64-bit computer. These days 128 and 256 bits are commonplace, and at least one 512-bit GPU exists.

  71. Re:Read the frickin post by buzzsport · · Score: 1

    I recall that OS/8 failed horribly on the Y2k testing front.. wonder if he's got to set his clock back to the 70's all the time?

    This configuration sounds amazingly like the priceline.com supercomputer that Capt. Kirk's been seen with recently...

  72. ENIAC On A Chip by Stephen+VanDahm · · Score: 2

    These dudes beat you to it.

    Steve

    1. Re:ENIAC On A Chip by Amazing+Quantum+Man · · Score: 2

      Yeah, but how do you replace the microscopic vacuum tubes (valves, for you Brits) when they blow out? That was one of the things about ENIAC, IIRC... the tubes kept blowing!

      --
      Fascism starts when the efficiency of the government becomes more important than the rights of the people.
  73. W95 and DOS will not expire at the end of the year by kfg · · Score: 3, Interesting

    Only official support for them will. DOS will never 'expire.' It's done. Of course you can't buy MS-DOS anymore, but there's always DR-DOS and FreeD0S, both still supported.

    W95/98, on the other hand, will actually expire some years in the future. I discovered this on a reinstall that went bad. Windows simply refused to install. Having a Gateway at the time I called tech support and the issue was tracked down to a buggy BIOS (gotta watch for those updates) that had reset my system clock to a future time.

    "Ah, there's your problem. Windows has a 30 year time bomb built in so it thinks it's expired."

    Ummmmmm, good to know. I guess that's how long we've got to port all our favorite W95/98 games to Linux ( or maybe Plan 9).

    KFG

  74. 12 by whos standard? by Anonymous Coward · · Score: 0

    12 bits is about the least you can get away with and have a usable computer.

    Tell all the former 8bit CPU (6501, Z80, etc) users that they did not have a usable computer?

  75. It's like English Measurements by hey! · · Score: 2

    I don't think there's any fundamental DISadvantage to using 12,24,36 and 48 bit words and addresses. The question is not whether the memory addresses will be in terms of some power of two (of course they will), but whether the sizes of words used to hold values and addresses should likewise be an even power of two. Even numbers, surely, but not necessarily a power of two bits wide.

    At the time when things pretty much fell into the currently accepted pattern, word sizes that were even powers of two happened to be convenient:

    2^8: enough to hold the complete latin alphabet
    2^16: Enough bits to handle the entire address space of a 1980s microcomputer
    2^32: Enough to handle almost any day to day integer calculation

    It's like the inch-foot-yard-furlong-mile of English measurements. These are well suited to the kind of day-to-day measurements that people make, as inconvenient as they are for calculation. Eight, sixteen and thirty two bit words and addresses were big enough in the 1980s, but not so big as to be wasteful.

    It's interesting to speculate how things might have been different had the industry settled on twelve and twenty four bit word sizes. It may have been more convenient for people with non-latin alphabets, although not as commodious as a sixteen bit per charcter system. And a lot of effort was wasted in the nineties with the limitations of sixteen bits address spaces (the segmented memory architecture, near and far pointers etc). The need for a larger flat, memory space might have been staved off for several years until 16MB chunks were too small.

    I don't know if that's a good thing or bad thing. We might be struggling with a 24-48 bit conversion today instead of happily using our P4s and Athlons and waiting for the high end users to hash out the 32-64 bit conversion.

    --
    Post may contain irony: discontinue use if experiencing mood swings, nausea or elevated blood pressure.
    1. Re:It's like English Measurements by ChrisMaple · · Score: 1

      Not necessarily even numbers. Honeywell used 9 bit bytes circa 1970.

      --
      Contribute to civilization: ari.aynrand.org/donate
    2. Re:It's like English Measurements by hey! · · Score: 2

      But was it 8 bits plus parity?

      --
      Post may contain irony: discontinue use if experiencing mood swings, nausea or elevated blood pressure.
    3. Re:It's like English Measurements by Malcolm+MacArthur · · Score: 1
      No, I think it was a machine with a 36-bit word length. Now, 36 bits gives you a few different options for encoding text (note, I do not say ASCII :):

      • SIXBIT. CAPITAL LETTERS ONLY (sorry ;), numbers and some punctuation characters. Greatest data density, but of course it can't handle the full ASCII character set.
      • 7-bit bytes. 5 bytes of 7 bits, giving 35 bits in total. The extra bit is either unused or can be used for a parity check. Allows full 7-bit ASCII.
      • 8-bit bytes, using one of two methods:
        1. 4 bytes per word, 4 parity (or wasted, depending on implementation) bits.
        2. 4 and a half bytes per word. Or, rather, 9 bytes per double-word. This is more space-efficient.
      • 9-bit bytes, 4 per word. Which is probably what the Honeywell did. The 9th bit is usually unused; I believe the Honeywell might have used it to support various functions.

      36 bits used to be quite common in larger systems. See 36bit.org for more information on 36-bit computers.

      The only ones I really know much about are the PDP-10s.

    4. Re:It's like English Measurements by pjrc · · Score: 2
      At the time when things pretty much fell into the currently accepted pattern, word sizes that were even powers of two happened to be convenient:

      IBM's EBCDIC (8 bits) and AT&T/ANSI's ASCII (7 bits + parity) has a lot more to do with it than what "happened to be convenient". Before EBCDIC and ASCII, 6 bit encodings were "what was convenient". Both IBM and AT&T were huge monopolies in the 60's, so whatever they implmented was what the rest of the world had to live with. That is why computers today use 8 bit bytes. It's mostly IBM's doing, with some help from AT&T. Luckily, AT&T was generous to take the standard-based route and a fairly good encoding resulted. Heaven forbid we'd all be stuck with EBCDIC otherwise.

      Of course, I'm repeating myself (a more detailed explaination awaits if you follow that link).

    5. Re:It's like English Measurements by Anonymous Coward · · Score: 0

      The question is not whether the memory addresses will be in terms of some power of two (of course they will)
      The IBM 7070 and 7074 (2nd generation mainframes) were DECIMAL (base 10) machines. 10,000 10-decimal-digit words. Digits were bi-quinary (2 of 5) which gave exactly 10 possibilities per position. Locations 1-99 were 99 index registers, which had both start and stop addresses. Floating point 1234.5678 (5412345678) mapped exactly to storage range 1234 thru 5678. (Very) non-portable of course.
      You have a problem with fixed word sizes. If the size is large and the values are all small, you waste a lot of bits. If the size is too small, you get your own version of Y2K or a buffer overflow. AFAIK, Lisp is the only language that can smoothly and somewhat efficiently handle a vast range of sizes.

    6. Re:It's like English Measurements by some+guy+I+know · · Score: 1

      Honeywell used 9 bit bytes circa 1970

      I remember using a CDC 6400 in the mid-70s.
      IIRC, the CPU had a 60-bit "long" word size, and a 15-bit "short" word size.
      The OS used 6-bit character encoding, so ten characters fit into a long word.

      --
      Those who sacrifice security to condemn liberty deserve to repeat history or something. - Benjamin Santayana
  76. Odd way to go about it by SpinyNorman · · Score: 2

    The Harris HD-6120 "PDP-8 on a chip" is still available, and is what this guy is using:

    http://www.sparetimegizmos.com/Hardware/SBC6120- 2. htm

    The only point I could see in using FPGAs would be if you were trying to rectreate an early MSI PDP-8 (these things existed before the single-chip microprocessor).

  77. On the other hand. . . by kfg · · Score: 2

    why disdain the past? Who knows, maybe your grandma knew something about sucking eggs that you don't.

    If nothing else the guy is obviously having fun. Believe it or not when you get to be Eleventy years old your own hobby just might turn out to be keeping 16 bit Intel stuff alive.

    I mean like, why ride skateboards when we have bicycles now? Why, because you *want* to.

    KFG

  78. Re:W95 and DOS will not expire at the end of the y by JimPooley · · Score: 2

    But why the hell would anyone still be running Windows 95 in 2025? Or running games which run on Windows 95 in 2025?

    Much better things will be available by then.

    --

    "Information wants to be paid"
  79. Give me 18 bits or give me death! by xtheunknown · · Score: 1

    Forget the PDP-8, give me a PDP-15 any day!

    Talk about geek factor. We had a PDP-15 in the sub-basement of our Math building collecting data from a Van der Graf accelerator.

    Then I would have a use for my HP-16C Computer Science calculator, you know the one that did conversions to/from Octal/Decimal.

    Those were the good old days.

    Those were the good old days.

    --

    They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety.
  80. DECMate by FeatherBoa · · Score: 1

    I remember the place I was working in the mid '80s had a boatload of DECMate systems. They used a microprocessor based on a PDP-8 architecture. I bet you'd still find one of these in the junk bin at your local computer recyclers.

    1. Re:DECMate by Anonymous Coward · · Score: 0

      Yeah, as I recall, the chip was made by Intersil. Its main selling point to OEM's was that universities and industrial labe were already littered with old PDP8's that could be conscripted as development platforms.

  81. Well, not to put too fine a point on it, but . . . by kfg · · Score: 2

    the upgraded CoCo was called. . . a Mac. You can still buy 6800 series chips, although you have to hunt around a bit. They're still very usful for a lot of things.

    On the other hand the venerable Z80 not only has never gone out of production but is being updated just as you suggest:

    http://216.239.39.100/search?q=cache:vPeP4Ne7p1A C: www.ebnonline.com/story/chipwire/OEG20000927S0018+ z80+chips&hl=en&ie=UTF-8

    There are an awful lot of uses for small, fast, cool running, general purpose and cheap as penny candy chips.

    "Charles Luther" in "Runaway" understood this full well when he used 8088's to power his nefarious robotic killing machines.

    KFG

  82. Daler by bstadil · · Score: 1
    It spread to other countries in addition to US. In Denmark a golden coin worth 2 Kroner was called Daler.

    It existed until the 60's. There was a fair amount of Lore around the Daler, notably used at Brothels for depositing payment at a certain part of the girls.

    --
    Help fight continental drift.
    1. Re:Daler by david+duncan+scott · · Score: 3, Informative

      In fact, reaching deep into my trove of useless trivia, I seem to recall that we in the US snitched the term from the Spanish, along with an arcane bit of slang: the Spanish dollar, circulated in the old West, was often broken into 8 pieces (it may even have been scored to facilitate this, but I may be making that up.) One quarter of a dollar was, therefore, two of these bits, leading to such Americanisms as "two-bit whore" and the ever-popular secret knock pattern, "Shave and a Haircut, Two Bits".

      --

      This next song is very sad. Please clap along. -- Robin Zander

    2. Re:Daler by zulux · · Score: 2


      And of course Doller is a basterdised version of the Thaler wich is a basterdised version of Joachimsthaler.

      more info

      --

      Moneyed corporations, non-working 'poor' and criminal prisoners are turning productive citizens into tax-slaves.

  83. Re:W95 and DOS will not expire at the end of the y by chas.capwell · · Score: 2, Insightful
    But why the hell would anyone still be running Windows 95 in 2025? Or running games which run on Windows 95 in 2025?

    Much better things will be available by then.

    You say this in a thread talking about a game that was developed around 30 years ago that has gone offtopic from an article about an architecture that is at least as old. Are you on crack or something? :)
  84. Instruction sets are a matter of taste by metamatic · · Score: 1

    I loved programming the 6502, but could never stomach the crappy x86. The best environment for programming assembler, however, was the 68000 series...

    --
    GCHQ Quantum Insert installed. If only our tongues were made of glass, how much more careful we would be when we speak
    1. Re:Instruction sets are a matter of taste by dhogaza · · Score: 2

      And the 68000 was simply a beefed-up rip-off of the PDP-11, extended to 32-bit addressing.

      It didn't include the PC as a general purpose register because that was one of the design innovations in the PDP-11 that Gordon Bell/DEC patented ...

    2. Re:Instruction sets are a matter of taste by Amazing+Quantum+Man · · Score: 1

      Zilog Z8000/Z80000 anyone? I never particularly liked the 68K's distinction between A and D registers.

      --
      Fascism starts when the efficiency of the government becomes more important than the rights of the people.
    3. Re:Instruction sets are a matter of taste by aschlemm · · Score: 1

      For 8 bit micro processors I have programmed 6502, 8080 and Z80. IMHO the Z80 was the best 8 bit processor I ever programmed when I was doing assembly language. The 68000 looked pretty decent too but I only used it for writing an operating system in college and a majority of the OS code was in Modula-2 with some small use of embedded opcodes in the code. Because I was using a high level language, I wasn't doing vast amounts of assembly language coding like I had done previously with 8bit processors. I still had to understand how the 68000 worked for my OS to work with it.

  85. Historical inaccuracies by John_Sauter · · Score: 2, Informative

    The PDP-8 was not the first minicomputer. As its name implies, it had predecessors, including the PDP-7, PDP-5, PDP-4 and PDP-1. I nominate the PDP-1 as the first minicomputer.

    Also, the IBM System/360 was not the first computer with variable-length instructions. The IBM 1401 also had variable-length instructions, and I am not sure it was the first.

    John Sauter (J_Sauter@Empire.Net)

    1. Re:Historical inaccuracies by dhogaza · · Score: 2

      Well, the earlier 18-bit models weren't marketed as mini-computers. Tney were marketed as Personal Computers, though :) For lab scientists ...

      The PDP-1 was pretty huge and was the first general purpose computer sold in the US for under $100,000 (back when that figure was real money!). The 12-bit PDP-5 was the first sold under $40K and the PDP-8 the first under $20K.

      The PDP-6 was older than the PDP-8 and was by no means a minicomputer, being a 36-bit predecessor to the PDP-10!

      Anyway ... the term minicomputer came into common usage because of the PDP-8. It was small enough to sit on a desktop and didn't need a rack in its basic configuration. The earlier models you mention, i.e. the 18-bit family PDP-1/4/7/9/15 and the PDP-8's immediate predecessor the PDP-5 were all required standard 19-inch racks.

      The table top configuration was the distinction the PDP-8 brought to the market, though nearly all were sold in racks because you couldn't really expand the desktop version.

    2. Re:Historical inaccuracies by John_Sauter · · Score: 1

      The PDP-8 was, as you point out, distinguished by its marketing. My favorite PDP-8 advertisement showed the tabletop model with a teddy bear.

      John Sauter (J_Sauter@Empire.Net)

  86. Why we use base 2 instead of base 3 by Anonymous Coward · · Score: 5, Informative

    As nice as a base-3 system my be in theory, there are very good reasons for sticking to a base-2 system in hardware. As we are moving to smaller and smaller fabrication processes, it is necessary to lower the supply voltage Vdd. For example, now that we are approaching the 0.1um and 900nm levels (at least in research labs), Vdd is getting down around 1 Volt. However, the Vt (the threshold voltage needed to turn "on" a MOS transistor) stays the same, because it is determined by physical properties of silicon (mostly). That means we're losing headroom. To implement ternary logic, we would need 3 different voltage levels. We're simply running out of room to do things like that. You need to leave a noise margin around your "1" and "0" values for reliable operation. (For example, if Vdd=1V, you might consider 0.0-0.4 = "0", 0.6-1.0 = "1". Then a logic gate that "sees" 0.0-0.5 interprets it as "0", etc. If you had a "0" that was really 0.4V, you would hope that "noise" wouldn't bump it up above 0.5V, or else it would look like a "1".)

    The threshold voltage for transistors is somewhere under 0.2-0.3V usually (depening on the technology & lots of other parameters). So, you absolutely need a 0.6V supply. (0-0.3 = "0", 0.3-0.6 = "1".) Unfortunately, even with Vdd=1V, you'll get voltage drops happening throughout the chip ("IR drops" - as in I=current times R=resistance) so that the 1V may only look like 0.8V to some parts of your circuit.

    From the above discussion, it should be obvious that there really isn't room to shoehorn in a third voltage level. Also, a nice feature of CMOS design is that when a gate is sitting in a "0" or a "1" state, it is drawing no (well, negligible) power. Power is only dissipated while a value is switching from a 0/1 or vice versa. Off hand, I can't think of a way to do that with a third logic-value. Consider drawing even a tiny amount of current while a gate is sitting at logic "2" (or whatever you want to call the 3rd value). 1mA (milliAmp) times 1 million transistors on a chip = 1000 Amps. That chip's going to get a little hot!

    Ok, so you've probably got at least two questions, which I will try to answer in advance. If you've got other questions - I'll just let someone else tackle those.
    Q1) Why don't we just use a higher Vdd (supply voltage)?
    A1) If you're using smaller transistor widths, you simply can't. When you use a really thin gate (i.e. 0.1um) on a transistor, the breakdown voltage of the gate is reduced. If you use a higher voltage, the transistor melts. (You could use larger transistors, but that kind of defeats the whole purpose! We make transistors smaller because we can fit more on a chip, and they operate faster and use less power.)

    Q2) Can't we lower the threshold voltage?
    A2) Yes, to some extent. (It's not always easy.) But we don't want to. Even when a transistor is "off", there is still a very small amount of leakage current flowing through it. If you reduce the Vth, you also increase the amount of leakage current. In older technologies, this hasn't been much of a problem, because the leakage current was so small in comparison to the dynamic power consumption. But as we are putting more and more transistors on a chip, the leakage power consumption in modern chips can easily add up to 30%-40% of the total power consumption. There's also another reason. If you did that, you would be lowering your noise margin. And you don't really have much control over the noise (which is why it's called that). If you reduce noise margins too much, you'll find it almost impossible to create a circuit that actually functions reliably.

    Well, I hope that satisfies some of you (and doesn't get the rest of you too upset). VLSI circuit fabrication is a really neat field. Some of the tricks that are being used these days to fabricate that chip sitting in your computer and get it running at 2GHz (or aren't they up to 3GHz now?) are quite amazing - they're doing their best to cheat physics! Using a ternary counting system to build computers may have a lot of nice theoretical properties, but I can't see it displacing binary any time soon, except possibly in some really specialized applications. (There are always exceptions.)

    That's my $0.03 worth. (Hey, I typed a lot. I think that's worth at least $0.01 extra. Maybe $0.025?.) Any errors in the above are mine, but I won't admit it.

    1. Re:Why we use base 2 instead of base 3 by pjrc · · Score: 4, Informative
      Off hand, I can't think of a way to do that with a third logic-value. Consider drawing even a tiny amount of current while a gate is sitting at logic "2" (or whatever you want to call the 3rd value).

      It could be accomplished (fully static CMOS, no steady state current to maintain a 3rd logic level) with a second power supply, and circuitry designed to connect the output to either Vss, Vdd or Vmm (m for middle, for lack of any other name.. hmm) Brian Hayes's flawed assumption is that circuit complexity increases linearily with the number of logic levels. He writes "An obvious strategy is to minimize the product of these two quantities", refering to the radix and number of symbols to represent a number... but he just pulled that out of a hat. The required circuit complexity is not linear function of the radix, and a realistic model would quickly prove that binary is the most efficient. A fully static ternary output requires a minimum of four transistors, whereas binary requires only two.

      That chip's going to get a little hot!

      With a static CMOS circuit designed this way, power consumption would be approx 0.5 * C * f * V^2 (as it is in normal binary circuit). C will probably increase somewhat, as nearly twice as many transitors would be needed per circuit, yet fewer trits are needed that bits for the representing the same numerical range, so the increase in C probably wouldn't be by a factor of two. Presumably f (the clock frequency) would stay the same (well... I'll get to that...), and V stays the same (50% of transitions in binary are full supply voltage, in ternary 33% are full voltage and 33% are half voltage). Power comsumption would probably be similar.

      Saddly, f probably won't stay the same. C gets larger on each signal, and when driving to half voltages, the transistors that would connect to the Vmm supply get only half the effective gate voltage applied. So doubling the load and cutting the drive significantly is really going to hurt the circuit's speed.

      Dynamic logic tricks (pre-charged busses) and bicmos circuits add another interesting dimension that's too complex to worry about, though it'd be important for any microprocessor.

      But power consumption isn't likely to be a problem.

      Getting back to the old PDP-8, as I recall it was a binary machine. The motivation behind 12 bits was that 6 bits was ideal to represent both upper and lower case characters and plenty of symbols, and 12 bits (two chars) was plenty for useful math. I don't recall the popularity of 6/12 bit systems having anything to do with base-3 signaling.

    2. Re:Why we use base 2 instead of base 3 by lindsayt · · Score: 2

      I'm a sysadmin and not an electrical engineer, so I may be far afield here. But why does everybody talk about ternary as being 0 voltage, full voltage, and some random number in between? Why do both non-zero values have to be on the same side of zero? Wouldn't it make more sense to have zero for one state, and then the same voltage for each of the other two states, just with opposite polarity? That way, there would be no reduction in signal-to-noise level, and trits could be determined by separate presence-or-absence of voltage on either side of zero (+- of course). There's probably some obvious reason why this wouldn't work, but the whole point of digital circuitry is to not have to measure the exact voltage of the current to work (as analog equipment does). This would then be a simple two-step process - absence or presence of voltage, and polarity. No reliance on measure amount of voltage.

      Ideas? I've always been intrigued with digital (non-analog) techniques at determining ternary states...

      --
      I did not design this game/I did not name the stakes/I just happen to like apples/And I am not afraid of snakes-AniD
    3. Re:Why we use base 2 instead of base 3 by Anonymous Coward · · Score: 1, Informative

      Well the way a gate works it's just not made to go in reverse, you could make a gate with some pertrickery that would go both ways, but since it would probably take up more space you'd be losing ground on another aspect. Nice idea though, makes me want to play around with it myself.

    4. Re:Why we use base 2 instead of base 3 by quasi_steller · · Score: 1
      Brian Hayes's flawed assumption [sigmaxi.org] is that circuit complexity increases linearily with the number of logic levels. He writes "An obvious strategy is to minimize the product of these two quantities", refering to the radix and number of symbols to represent a number... but he just pulled that out of a hat.

      Nowhere in the paper could I find that Brian Hayes claimd "that circuit complexity increases linearily with the number of logic levels." He was being theoretical about the whole issue. In other words, if hardware was not an issue, then the trinary number system is the most effecient numbering system. He was not stating that a trinary number system is beter because the circuit complexity is less. In fact, Brian Hayes goes on to state that:

      Base 2 dominates computing technology because binary devices are simple and reliable, with just two stable states--on or off, full or empty. Computer circuitry also exploits a coincidence between binary arithmetic and binary logic: The same signal can represent either a numeric value (1 or 0) or a logical value (true or false).
      Brians claim was that, mathematically speaking, the best numbering system is the trinary number system, and his claim that the mathematical complexity of a numbering system increases linearly with the number of logic levels makes sence.

      I would find it interesting to see how well a trinary computer performs compaired to a binary computer. It would also be interesting to compair the complexity involved in bulding each machine and decide which numbering system is practally best.

      --
      ...interesting if true.
    5. Re:Why we use base 2 instead of base 3 by pjrc · · Score: 3, Informative
      Nowhere in the paper could I find that Brian Hayes claimd "that circuit complexity increases linearily with the number of logic levels."

      In the paragraph just above figure 2:

      Everything hinges on the assumption that rw is a proper measure of hardware complexity, or in other words that the incremental cost of increasing the radix is the same as the incremental cost of increasing the number of digits.

      Scroll back up to figure 1, and the third paragraph up is where the assumption is first made:

      By one plausible measure, it is the most efficient of all integer bases; it offers the most economical way of representing numbers.

      How do you measure the cost of a numeric representation?

      [snip, absurd cases of base 1 and base 1e6]

      Evidently we need to optimize some joint measure of a number's width (how many digits it has) and its depth (how many different symbols can occupy each digit position). An obvious strategy is to minimize the product of these two quantities. In other words, if r is the radix and w is the width in digits, we want to minimize rw while holding rw constant.

      So what he's saying is that the "cost" of a representing a number is the cost per digit multiplied by the number of digits required. But he makes the assumption that the cost of each digit is a linear relationship with the radix, which is simply not true in almost any system (certainly not in electonic circuitry nor in telephone menu systems).

      Speaking mathematically, r is the radix, and w is the number of digits (or symbols, words, or whatever you call them) required using that radix. The cost is F(r) * w, where F(r) is some model for the cost to implement that radix.

      The words "An obvious strategy" are plain wrong. It's not obvious at all. It's simple-minded and ignorant. It's devoid of any anaylsis or thought about any real system. Even from a purely theoretical standpoint, it's academically dishonest to gloss over this critically important point rather than write "r * w" instead of "w * F(r)" and state the assumption of a linearly increasing cost per digit as the radix changes.

      Well, maybe that's a bit strong. Who am I to judge what's academically proper. But the paper clearly begins by saying:

      People count by tens and machines count by twos ... I want to offer three cheers for base 3, the ternary system ... They are the Goldilocks choice among numbering systems: When base 2 is too small and base 10 is too big, base 3 is just right.

      The general arguement that base-3 is actually superior for computer arithematic is also quite evident in the "Trit by Trit by Trit" section (just below figure 1). I'll avoid quoting much of it, but at the conclusion he writes:

      Why did base 3 fail to catch on? One easy guess is that reliable three-state devices just didn't exist or were too hard to develop. And once binary technology became established, the tremendous investment in methods for fabricating binary chips would have overwhelmed any small theoretical advantage of other bases.

      Now the rhetorical question "Why did base 3 fail to catch on?" is answered by postulating (not even any real knowledge) that way-back-then it was too tricky to design and base-2 gained so much momentum and became so well established that base-3 never caught on. Notice how he concludes with the words "overwhelmed any small theoretical advantage of other bases", reaffirming once again the standpoint the base-3 has some advantage, if small, over base-2, theoretically speaking. He's clearly talking about implementation of circuitry.

      The ugly truth is that rolled up in the theoretical advantage of base-3 for circuitry is that assumption that the "cost" is "r times w" (r for radix, w for number of digits). Any engineer can tell you that cost has units of dollars, and r and w are both unitless quantities. To compute the cost of using a particular number system, you need to use a function (above I called it "F(r)") that transforms the abstract number "r" into the cost of implementing that radix. The unitless number of possible digits needs to be turned unto a quantity in units of dollars (or some other currency) before it can be multiplied by "w" to obtain the cost of implementing that radix.

    6. Re:Why we use base 2 instead of base 3 by hristrdingslshdt · · Score: 1

      Although I agree with most of what you said, I'm not sure that I would call it a "flawed assumption" exactly. In principle there might exist physical systems that obey such a law. You are making the implicit assumption that all computers must use transistors, i.e. logic level depends purely on the voltage. There exist other physical quantities which might not require 4 elements to handle ternary outputs, such as polarization states for optical systems, or even electron spins for electron systems. Not that there have been workable schemes for this sort of thing (to my knowledge), but that doesn't mean that they don't exist.

  87. Tomcat by eGabriel · · Score: 1

    There was a Coco 4, sort of. I don't remember much about it, I think it was the Tomcat, and I seem to remember Frank Hogg Labs having something to do with it. IIRC it had sort of a backplane, like a super multi-connector.

    There was a class of 68000-based machines that ran OS/K, which was the 68k version of OS/9, or OS/9 was the 6809 based version of OS/K. Maybe it still runs on newer 68k architectures... that would be your Super Coco.

    I have often thought of just running CP/M natively on my P4, just for kicks, but then I begin to realize how much that idea sucks. It gives you that feeling for a moment that you can start over from the point in time just before Microsoft subverted CP/M (ok, actually MS-DOS was somewhat of an improvement,) and let CP/M re-evolve into something you could really use.

  88. Even older.. by pigeon · · Score: 2

    And I thought I was old fashioned, owning a PDP-11..

  89. Re:Because, as Tom Lehrer, formerly of Harvard, no by kfg · · Score: 2

    Tom has always been a *student* of Ha'vard, Tom's spelling, ( as has been most of my family, I'm the "black sheep" and went to Bard), but he spent some years teaching at MIT. He also spent some time teaching at UC Berkeley, where he not only taught math but. . .musical theater.

    I chose to highlight the MIT link because of their infamous connection to the PDP line of computers.

    And yes, he's still at Ha'vard.

    KFG

  90. dead horse by Anonymous Coward · · Score: 0

    You are beating a dead horse if you think anyone would look forward to such a venture. This looks like a lame ploy to get some VC fundage. This might have worked 2 years ago, but it's not going to work now. 8bit is already entrenched, and is here to stay. Who would want a 12bit computer when you can get a 32bit one for cheaper and runs faster? 12bits had its day with the PDP when all that was done was text processing, but I fail to see the relevancy of bringing back the 12bit processor of the PDP.

    1. Re:dead horse by Anonymous Coward · · Score: 0

      another thing, no hardware is compatible with it, nobody would know how to support it, and nobody has a need for it. So, unless you are working on your 'job security' project, give up.

  91. Believe it or not. . . by kfg · · Score: 2

    an object may have a proper noun all to itself and still retain membership in a larger general class.

    Just as a "Seacock" and a "Butterfly," despite having proper nouns of their own are, nonetheless, still just valves.

    Draw the Venn diagram, you'll figure out the set/subset relationship eventually.

    In short, I have just as many thumbs as I have "pinkies."

    KFG

  92. I suppose for the same reason I still play. . . by kfg · · Score: 2

    Chess, Checkers and Go, even though "better" games have been available for thousands of years.

    And by the way, Infocom rulz d00d!

    KFG

  93. Specialized Tools by Anonymous Coward · · Score: 0
    The specialist approach is to use the tool (Ferrari) for acquiring pussy. Once you have acquired it, you use different tools (bed, pile of $100 bills, etc) for the laying.

    The Studebaker only makes sense when you want to use one general-purpose tool both for the acquisition and the laying. This does work, but the acquisition performance is inferior.

  94. PDP-8 microprocessors by panurge · · Score: 4, Interesting
    This is so long ago I can't even remember the manufacturer, but there were at least 2 CMOS implementations of a PDP-8 processor. Has anybody observed that the instructions were based around core memory, so the accumulator was cleared when it did a store? If you could get the core again, a home computer with a PDP-8 processor and core memory would really benefit from a modbox with windows and lights.

    For some industrial control jobs, something like a PDP-8 or PDP-11 is in many ways ideal because you can see everything that goes on. It is actually possible for one person to understand the hardware, the microcode, and every single bit of the software. For me, that is the great pleasure of small embedded designs. I really think it would be good to have a teaching tool for CS that actually meant that the student could do a project and have a complete overview of the entire thing in this way. I'm far from knocking progress, but there are comments on this thread that are a bit about the kind of alienation we have now between hardware and software - most people have no real idea at all what the hardware does, and use terms like "cache" without even stopping to think about what is going on. So yes, let's have someone build an understandable modern PDP-8. It's less weird than the RCA1802 and easier to get your head around than the 8080.

    --
    Panurge has posted for the last time. Thanks for the positive moderations.
    1. Re:PDP-8 microprocessors by Anonymous Coward · · Score: 0

      Ahhhh... the RCS 1802 (aka Cosmac)... fond memories.

      And an 1802-based system gathers dust on a closet shelf above the BAUDOT (5 level code 60Ma current loop pre-teletype) holds down the floor. That was going to be my "home" computer following college and introduction to the IBM 11/30, the PDP-8 (programmed "Sailor's Hornpipe aka Popeye's Theme Song on it), and the ill-fated Xerox 530 we bought 2 weeks before Xerox exited the computer business.

      Anyone wanna buy a box of punch cards (used on a DEC shoebox card reader... or 3 reels of DECtapes?)

  95. Joachimstal. by Grendel+Drago · · Score: 2

    Hey, did you watch "Connections" too? That's kind of an obscure factoid, and I'm wondering where else it shows up.

    --grendel drago

    --
    Laws do not persuade just because they threaten. --Seneca
    1. Re:Joachimstal. by wiredog · · Score: 2

      Got it from "Making of the Atomic Bomb" by Rhodes. It was mentioned in passing when he was talking about Oppenheimer's visit to Joachimsthal. Which is also a source for pitchblende, btw.

  96. Meter. by Grendel+Drago · · Score: 2

    Actually...

    Here it says:

    The meter (m) is the Si unit of length and is defined as the length of the path traveled by light in vacuum during the time interval of 1/299792458 of a second.[3] This replaces the two previous definitions of the meter: the original adopted by CGPM in 1889 based on a platinum-iridium prototype bar, and a definition adopted in 1960 based on a krypton86 radiation from an electrical discharge lamp. In each case, the change in definition achieved not only an increase in accuracy, but also progress toward the goal of using fundamental physical quantities as standards, in particular, the quantum mechanical characteristics of atomic systems.

    --grendel drago

    --
    Laws do not persuade just because they threaten. --Seneca
    1. Re:Meter. by Amazing+Quantum+Man · · Score: 2

      Wasn't the meter originally defined as the 1/10^8 the distance from the North Pole to the Equator along the meridian passing through Paris?

      --
      Fascism starts when the efficiency of the government becomes more important than the rights of the people.
    2. Re:Meter. by Grendel+Drago · · Score: 2

      *shrug* All I did was google for it. But it seems plausible that that distance was measured and the platinum-iridium bar was created to match it---it would be much, much easier to go by a canonical bar than a measurement of the planet, I suppose.

      --grendel drago

      --
      Laws do not persuade just because they threaten. --Seneca
    3. Re:Meter. by Sri+Lumpa · · Score: 2

      Yes, From http://physics.nist.gov/cuu/Units/meter.html

      "The origins of the meter go back to at least the 18th century. At that time, there were two competing approaches to the definition of a standard unit of length. Some suggested defining the meter as the length of a pendulum having a half-period of one second; others suggested defining the meter as one ten-millionth of the length of the earth's meridian along a quadrant (one fourth the circumference of the earth). In 1791, soon after the French Revolution, the French Academy of Sciences chose the meridian definition over the pendulum definition because the force of gravity varies slightly over the surface of the earth, affecting the period of the pendulum."

      --
      "The obvious mathematical breakthrough would be development of an easy way to factor large prime numbers." Bill Gates,
    4. Re:Meter. by Derwen · · Score: 2
      Some suggested defining the meter as the length of a pendulum having a half-period of one second; others suggested defining the meter as one ten-millionth of the length of the earth's meridian along a quadrant (one fourth the circumference of the earth). In 1791, soon after the French Revolution, the French Academy of Sciences chose the meridian definition over the pendulum definition because the force of gravity varies slightly over the surface of the earth, affecting the period of the pendulum.
      "And so in June 1792, just as the Terror was beginning to crank into its dreadful gear, two eminent French astronomers set out in opposite directions from Paris. Their aim was to measure the distance of the meridian arc between Dunkirk and Barcelona: once obtained, this distance would be divided by 10 million to give a definitive and utterly impartial length for the new metre. Pierre Méchain travelled south to Barcelona, while Jean-Baptiste Delambre went north to Dunkirk. The savants were to work towards each other, reunite in the middle of France, do their sums and present the revolutionary government with the most classless unit of measurement conceivable. The whole business was to take them no more than a year."
      But of course it went wrong:
      "Somewhere near Barcelona, at the very start of his triangulations, Méchain made a small error of computation. Once this error had entered his system, it was impossible to eradicate it. For years the knowledge of this error haunted Méchain - the thought that he alone had managed to falsify what was intended to become 'the fundamental scientific value, the measure which would for ever more serve as the foundation for all scientific and commercial exchange'. In 1804, suffering from acute depression apparently brought on by guilt, Méchain returned to the Valencian coast to try to atone for his error. There he caught malaria and died."
      Read more in The Measure of All Things: The Seven-Year Odyssey that Transformed the World by Ken Adler
      - Derwen

      --
      http://fsfeurope.org/
  97. Visit the computer history musuem (see URL) by Geekonomical · · Score: 1

    I visited them recently, and it is wonderful to see all these PDPs restored. I havent seen a PDP-1 before! I suggest computer history museum in silicon valley for you all. Check out their website.

    http://www.computerhistory.org/

  98. PDP8 instruction set by Anonymous Coward · · Score: 0

    on what other computer can you have this instruction, given you have a memory location with the right label:
    TAD POLE
    ha!

    1. Re:PDP8 instruction set by scharkalvin · · Score: 2

      spy this instruction, CIA. Then again the PDP 10 had a 'floating add register triple' or FART instruction.

    2. Re:PDP8 instruction set by twrake · · Score: 1

      The pdp-8 had one 12 bit register the accumulator and "link bit" flag, the instruction DCA (Deposit and Clear the Accumulator) was the only instruction to write memory. There was no instruction to load the accumulator from memory rather you always added to the accumulator by TAD instruction. Of course all other these were *features*.

      You could normally keep the loader in core. But it a program trashed it you needed to enter it from the switch registers word by word.

      And we were lucky in those days, too. I had to walk to school on a barb wire fence with two bobcats under each arm. So sonny quit your moaning!

  99. pdp8 microprocessor by scharkalvin · · Score: 2

    Intersil used to make a CMOS microprocessor chip that used the pdp8 instruction set. It was a 12 bit micro processor. They also made a chip that acted as the memory address extension controller. You still might find some of these chips for sale someplace. DEC even used the 'cmos 8' inside one of their terminals to run pdp8 based word processing software. If you want to build your own pdp8 today, I'd look for some of those old intersil chips.

  100. Re:Because, as Tom Lehrer, formerly of Harvard, no by Amazing+Quantum+Man · · Score: 2

    He's been at UC Santa Cruz since the early '80s. He teaches "The history of the American Folk Musical", IIRC.

    --
    Fascism starts when the efficiency of the government becomes more important than the rights of the people.
  101. Re:FRED DURST FOUND DEAD AT AGE 32!!!!!! by SpitFU · · Score: 1

    Who??????
    Back up that "True American Hero" statement with facts that those of us who are unfamiliar can understand.

    --
    reassign null to be the tape device - it's so much more economical on my time as I don't have to change tapes_BOFH
  102. Re:PDP-8 was not the first minicomputer-Alleleuia by starling · · Score: 2

    I used to repair PDPs and Novas for a living before I got into programming (MUMPS, in case anyone remembers that), so I have a certain interest in this story.

    Still got the scar from a Nova 4 power supply which zapped me - geek chicks dig that sort of thing :)

  103. Unix by mrclmn · · Score: 0

    I'm surprised nobody has mentioned the fact that Unix was first developed at Bell Labs, by Thompson and Kernigan on a PDP 8.

    Sandy

  104. Re:Because, as Tom Lehrer, formerly of Harvard, no by kfg · · Score: 2

    Yes, but he's bicoastal, just as in his UCB days. His home remains in Mass. and last I knew he still maintained "ties" with Harvard ( but then one of the problems with becoming an old fart is that "last I knew" turns out to be about 1980 which you think of as "just a while ago").

    I could recall this wrong, but I think at one point he was, at least officially, teaching at Harvard, MIT and UCB all at the same time.

    ( And note that I make no claims to know the man, I just know several people who know/knew him)

    KFG

  105. Bringing back DEC field service too? by dagnabit · · Score: 1

    We had an -8 and an -11 at my high school back in 1981-1985. We used to sing the Batman theme music whenever the service guy showed up to do PM on those washing-machine sized disk drives (RK07? gawd it's been a long time...):

    Na-na na-na na-na na-na, DEC-Man!

    Guess if it's the PDQ now, it'll have to be DEQ-man...

  106. Re:Because, as Tom Lehrer, formerly of MIT noted. by buswolley · · Score: 1

    Fuck the people who decided our thumb is not a finger. Who are THEy to decide this? The every day person throughout the every day world considers it a finger. so fuck them who decided we are stupid if we consider it a finger.

    --

    A Good Troll is better than a Bad Human.

  107. Another point... by TheConfusedOne · · Score: 2, Funny

    I'd say your chances of getting laid are better if you tell 'em you're resurrecting a '53 Corvette than a PDP-8.

    --
    --- I wish I could hear the soundtrack to my life. That way I'd know when to duck.
    1. Re:Another point... by cburley · · Score: 2, Funny
      I'd say your chances of getting laid are better if you tell 'em you're resurrecting a '53 Corvette than a PDP-8.

      I dunno; sing a few verses of "Old MAC Hacker" ("Old MAC hacker had an '8, EAE IO...") and you've evened the odds, I'd say....

      --
      Practice random senselessness and act kind of beautiful.
  108. I overspoke when. . . by kfg · · Score: 2

    I termed FORTRAN "native" to the PDP-8 ( and I suppose it would only be correct to term the appropriate assembler "native").

    It would be more correct to merely note that FORTRAN was the first 'higher' language for which a compliler was available.

    I've at least seen FOCAL. I've *never* seen BASIC on a PDP-8 ( thank God), but my experinece with the machine was strictly in a hard science academic setting where FORTRAN was King.

    Don't get me wrong though. I'm no FORTRAN zealot. I'm an APL zealot who always resented the forced move from one to the other.

    KFG

  109. PDP 8 first mini? NOT by gordona · · Score: 1

    The LINC computer (http://www.mit.edu:8001/people/ijs/epl/LINC.html) preceeded the PDP. We had one in a lab at the Northwestern School of Medicine. We used it for fourier analysis with output to a Calcomp plotter. Sixty four data points, took 5 minutes! Those little DEC tapes sure were churning! Also, used it to emulate a computer of average transients. fun machine to play with. 4K of memory with only 2K that could be used for program.. With creativity, one could do a lot with that machine! :)

    --
    "Gentlemen, you can't fight in here! This is the War Room!" -- Dr. Strangelove
  110. David Conroy's FPGA PDP-8 by Tuck · · Score: 1
    David Conroy's PDP-8/X

    "The PDP-8/X is a reimplementation of the PDP-8/I, with 32K words of memory (all the memory you can put on a PDP-8/I), an extended memory control, an interface to an RS-232 terminal, and an interface to an IDE disk, which I built just for fun.

    I consider this machine to be a new model compatible with something from the past, as opposed to a clone of the past, so I feel no shame in introducing new model-specific variations. The PDP-8/X, therefore, uses IDE disks with a new disk interface, because I thought that it would not be unreasonable for a new model to come out with a new disk controller, especially considering that customer-written PDP-8 device handlers were both common and encouraged."

    He also did a PDP-4/X.
    --
    $ find /pub -beer "James Squire Amber Ale" -drink
  111. Re:Read the frickin post by Anonymous Coward · · Score: 0

    OS/8 couldn't possibly have failed on the Y2K front; it had no concept of time. The operating system even ran without interrupts.

  112. Secret knock by Anonymous Coward · · Score: 1, Funny
    "and the ever-popular secret knock pattern, 'Shave and a Haircut, Two Bits'."


    Now you've gone and done it! Our knock is no longer a secret!

  113. Re:Read the frickin post by Anonymous Coward · · Score: 0

    Whoops; forgot that OS/8 did have some support for the date. You could issue a command to set the date and it would tag the files it created with the date.

    However, OS/8 failed the Y2K problem in 1978. That's why OS/78 was created; it basically moved the epoch to allow dates in 1978 and beyond to be represented.

  114. Re:what for? POWER. by lenski · · Score: 1
    Agreed to both comments. When I was 16, a human soul wasn't worth the cost of the most "basic" computer; having access to a real computer was the dream of geeks everywhere. About 8 months after I ascended the throne of computer access for the first time, the university bought a 2.5 Mbyte RK05 and it was acres of storage, impossible to use fully... That feeling doesn't occur much anymore, even with my current PC:
    Shuttle XPC (nice and quiet)
    Apple Cinema (only the 22-inch version)
    2.4-GHz P4 (performance is OK)
    1 Gbyte RAM (a reasonable amount)
    80 gbyte disk (plenty for now)
    Nice and cheap...

    I still have several plots generated on a PDP-8/L, drawn on a Hewlett-Packard X-Y recorded through the D/A outputs.

    <slightly offtopic>I stay away from WinXP for the second reason: I will not allow someone else any sort of control over my machine, especially god-like without explicit direct authorization! In exchange for which, I recognize the rights of authors and work accordingly.
    </offtopic>

  115. It had a -Core- Memory !! by ishmalius · · Score: 1
    I was amazed the first time I took apart a PDP-8 and saw a real "core" memory... a pc board with a grid of vertical and horizontal wires, with a tiny magnetic toroid at each crossing. I believe the one I was holding stored 1kb, although I might be wrong. But imagine, if you have a PDP-8, it might still remember what it was doing when it was turned off.... years ago!

    Was the story a myth, that these boards were knitted together by hand on the Navajo reservation?

  116. Knob on the front? by serutan · · Score: 2

    Hey I remember that, but I always thought it was the choke.

  117. 900 nm, wow! by Anonymous Coward · · Score: 0

    Those darn researchers, what will they think of next.

  118. bi-quinary by Anonymous Coward · · Score: 0

    bi-quinary is 2 bits on of 5 bits total which gives exactly 10 valid combinations.
    IBM 7070 and 7074 (2nd generation mainframes) were bi-quinary, 10,000 10-decimal-digit words with THREE signs (plus, minus, and alpha)
    IBM 650 IIRC had 2,000 10-digit words on a magnetic drum.
    A long time ago I had an HP 55 which IIRC almost exactly matched the specs of the ENIAC, something like 20 words storage and 50 programming steps.

  119. What the Hell? by lvdrproject · · Score: 1
    At $18,000 (the price of a new single-family home or a top Rolls Royce), a researcher received...

    Ok, i don't know anything about Rolls-Royce cars (or houses, either), but what the Hell, $18'000 seems JUST a touch too low for a "top" Rolls-Royce. An entry-level Beetle costs $18'000.

    :Lav

    1. Re:What the Hell? by KewlPC · · Score: 2

      I think he may have meant $180,000. IIRC I read somewhere that the PDP-1 cost $100,000 and the size of a refrigerator, yet for the time was dirt cheap and incredibly small.

      I actually have an emulator for a PDP-11 around here somewhere (don't remember if it's still on disk or on a backup CD-R in the closet). SCO used to offer an "Ancient Unix" license, where you could get it and then download old versions of Unix (actual Unix, not BSD or Linux or whatever). I used to run Unix on it (not sure what version it was anymore, probably V or VII) just for kicks.

    2. Re:What the Hell? by Anonymous Coward · · Score: 0

      Actually, $18,000 in *1965* bought you a whole lot of stuff, not like the watered down money y'all are thinking of..

  120. Form factor by Ed+Avis · · Score: 2

    If this thing fits on a single FPGA, then it could be made into a handheld called the PDA8.

    --
    -- Ed Avis ed@membled.com
  121. I hate to break it to you... by twoslice · · Score: 2

    I used to work for Digital before Compaq took us over and the Digital name died right there. Now that HP has taken over Digital - Digital is deader than dead!

    Perhaps it is time for a new logo for the topic (RIP comes to mind)

    NB: Digital was the best company to work for...

    --

    From excellent karma to terible karma with a single +5 funny post...
  122. PDP 8 in pedagogy by dpreformer · · Score: 1

    We used the PDP8 as a learning tool in a hardware class. Built a PDP8 using wirewrap and Programmable logic arrays, then tore it down and rebuilt it using Microcode. It was pretty cool - had a variable clock, single step for debugging, serial i/o.

    Course number used to be C421/422 at Indiana University. Text was "Art of Digital Design" by Prosser and Winkler. Kits may still be available.

  123. Defining a byte by mobilityguy · · Score: 1

    One of the cool things about TOPS-10 was that it allowed the programmer to define the bytesize for each program. There was nothing sacred about 8 bits. You used whatever size fit your datatypes best, even if it wasn't a factor of 36. Even 36 bit bytes were possible, although kind of pointless.

    Tying byte size to datatype made byte instructions much more versatile, and made for much more efficient use of memory at a time when people spent as much time making their programs fit as they did making them work.

    Another cool feature of the 36-bit instruction set was that every instruction was one word long. Made for very elegant programs. It was RISC back in 1964 - maybe there'd be a place for a 36-bit RISC system today?

    Our DEC-10, s/n 2393, regularly supported 70 to 100 simultaneous users, with half of them running database searches most of the time, and with response times below one second most of the time. That's from a processor that would be rated at 1 MIP by today's metrics, and 4 megawords - about 18 megabytes - of memory. Imagine what could be done with that kind of efficiency on today's machines.

  124. Re:W95 and DOS will not expire at the end of the y by Anonymous Coward · · Score: 0

    Why would anyone be running Windows 95 in 2025?
    Everyone, no.
    Anyone, why not. Why would anone be interested in a thousand year old garbage dump?
    Time bombs may have uses, but eventually they will bite back in places you didn't know you had places. With a time bomb built into W95, you have to wonder what Microsoft has built into XP and successors.

  125. Beetle by Detritus · · Score: 1

    You could buy a Beetle for less than $2000 back then. A Rolls Royce started at about $20,000, about the same price as a new single-family house in what was to become Silicon Valley. Isn't inflation wonderful?

    --
    Mea navis aericumbens anguillis abundat
  126. Re:W95 and DOS will not expire at the end of the y by Zaiff+Urgulbunger · · Score: 2, Funny

    But why the hell would anyone still be running Windows 95 in 2025? Or running games which run on Windows 95 in 2025?

    Ask the man with the beard and the Dec-PDP8. He speaks in 12 bits. He knows everything!

  127. And change the logo on the top link by Anonymous Coward · · Score: 0

    Any proper thread about DEC PDP gear should not have the **SILLY** 1990's logo from the Palmer era, but the original "real" Digital logo - just the way KO created it.

    -AC-

  128. Just think... by Anonymous Coward · · Score: 0

    ...Imagine a beowulf cluster of those!

  129. Alpha Microsystems! by Zaiff+Urgulbunger · · Score: 1

    Does anyone run these any more?

    I'm still scared from years of having to "support" a few of these things.

    To refresh the memory of anyone who cares, they from an OS called AMOS (the company was called Alpha Micro, okay) and they were 68000 based multi-user (clears throat) "mini" computers.

    Oh, and they crashed quite a lot too.

  130. Microscopic Vacuum Tubes by ni5mo · · Score: 1

    The Fall issue of Invention & Technology has an excellent article on the rise and (not so) fall of vacuum tube technology. It also mentions the possible use in the future of nanotriodes: a vacuum tube-like structure a millionth of a millimeter across. So there ya go, ENIAC on a chip may be possible, complete with 'tubes :)

  131. Tape! by Charlie+Bill · · Score: 1
    Highspeed papertape reader punch and TTY, so I can boot from tape after keying in the boot loader.

    Dude...keying in the boot loader is krusty, though I was much dissapointed to read that he won't be gen'ing up the tape machine as well...pussy.

  132. Bring back the Linc-8 / PDP-12 instead by Anonymous Coward · · Score: 0

    Dec also had a variant of the PDP-8 known as the Linc-8. It had a different instruction set but had built ADC/DAC/display and two Linctapes (which were like Dectape except they ran the other direction). It was intended for lab instrument monitoring etc. I ran one doing nuclear medicine image processing for perhaps 10 years in the 70's. We had 2 Diablo 33's for disk drives (like RK05's)and about 70 mb of offline disks stored in a cabinet. We discarded the ASR-33 and had an industrial strength ASR-35. Programmed in assembler on it for many years---ahhh the memories!!

  133. A tiny OS for 8080s by Ungrounded+Lightning · · Score: 2

    Those architecture are so simple, with kernels so small you could print the hex binary out on a couple of pages. Imaging how fast an accounting package would be on a 1 gHz, or even a 200 mHz.

    If they do reconstitute the 8080 and a couple peripheral chips for it (like clock, uart, parallel-port), I recently found the source listing of an RTOS I did for it.

    - ROMable
    - Real-time
    - Preemptive multitasking (arbitrary number of priorities)
    - Reentrant code
    - Application and driver tasks are "actors". (Think "objects" where each instance of a task object subclass is a thread of execution).
    - Intertask communication supported by the kernel was:
    - Semaphores
    - message queues ("communicating semaphores")
    - freespace memory allocation queues
    - Written in assembler, but with a system service calling convention compatable with the CP/M compiler output's subroutine calls.

    The kernel, queueing system, idle task, init routine, memory allocator, and an "empty" (just the idle task and stop flags) task & preallocated memory table totaled a few bytes under a half-K. (Yes, Virginia, all that in less than 512 bytes.) Or a few bytes over if you want to keep some extra per-task state so a debugger can figure out what a task is up to.

    The size was very important, because the system it was written to run in had only 8K of ROM available, max. This had to hold a complete energy management system, including OS, device drivers, real-time task debugger, com stack, real-time clock handler, schedule handler, command interpreter, data collector, thermostat input, relay contact input, event counters (watthour meter data collectors), relay drivers, relay logic simulator (ladder-diagram interpreter), and a table of relay logic to simulate. The total software came in under 4K, leaving one of the two ROMs available for the relay logic, sensor, and other configuration definition tables. (At a couple bytes per relay contact and a bit per interconnect you can define a VERY complicated hunk of relay logic in 4K. B-) )

    The trick was the insight that adding Mark Weiser's "T" (non-blocking "P") to semaphores' "P" and "V" lets you use communicating semaphores for EVERYTHING, including communication between the below-the-line interrupt routines and the above-the-line part of device drivers (which compete with other real-time tasks in the normal scheduling process). Think "message-passing minikernel", with a vengance.

    Religiously using communicating semaphores, in a handful of idomatic ways, for all intertask communication (and even some task-internal functions), makes the tasks themselves tiny, and leads to a software organization that amounts to object-oriented programming. (I believe that this effect, in a direct ancestor of this operating system, IS the origin of OOP.)

    I kept the rights to the supervisor core and tools, and had been thinking of open-sourcing it if I ever found it again (which I now have - at least the hardcopy version). Let me know if anybody needs it and I'll get in touch.

    --
    Bantam Dominique roosters crow a four-note song. Once you've heard it as "Happy BIRTHday" you can't NOT hear it that way
  134. Re:f1rst p0st!? by [Baka] · · Score: 1

    whatchoo talkin bout, foo?

  135. re: your sig by nentwined · · Score: 0

    thanks, I didn't know about the | in vi. learn something new every few weeks, still... [and it's been about 3 years]

    --
    heaven
  136. CommodoreOne by RasmusW · · Score: 1

    You might be interested in taking a look at the CommodoreOne project:

    http://www.commodoreone.com
    http://www.geocitie s.com/cm_easy/comone.htm

    It's a modern C64, but perphaps the most interesting fact is that it can be modified with different CPUs.

    From http://www.geocities.com/profdredd/commodoreone/cm drone.html:

    "What's this I hear about a 6510 being used as a second processor?

    I've added a port that a cpu card will plug into on the new revision and someone can plug a 6809, 6502 or what ever into it. The CPU card will be able to carry the 65816, 6502, 65C02, Z80 and 6809. This will enable the C-One to act like nearly any computer of the 80s just by exchanging the CPU card and the program in the CF card. And yes, the 6510 ports are simulated, and yes, it's possible to add interfaces on the CPU card. The slot will be documented, so third party companys can produce hardware for it"

  137. You haven't got a clue. by Anonymous Coward · · Score: 0

    Now that's just sad.

  138. Open Source? It's not even an open web page! by Anonymous Coward · · Score: 0

    You need a password to even access the site, making the links worthless. That just proves the stupidity behind this scheme.

  139. OK then...THERE IS NO USE FOR THIS! by Anonymous Coward · · Score: 0

    There, I didn't bother to ask "why?". I conclude that there is no useful purpose for this so it should be abandoned.

    If you can't figure that out DON'T POST!

  140. Re:Because, as Tom Lehrer, formerly of MIT noted. by oliverthered · · Score: 1


    Officer: "How many fingers am I holding up"
    Drunk: "Well I've had about 20 fingers, and your holding me up, so I guess 20"

    --
    thank God the internet isn't a human right.
  141. Last Post! by alpg · · Score: 1

    The Commandments of the EE:

    (9) Trifle thee not with radioactive tubes and substances lest thou
    commence to glow in the dark like a lightning bug, and thy wife be
    frustrated and have not further use for thee except for thy wages.
    (10) Commit thou to memory all the words of the prophets which are
    written down in thy Bible which is the National Electrical Code,
    and giveth out with the straight dope and consoleth thee when
    thou hast suffered a ream job by the chief electrician.
    (11) When thou muckest about with a device in an unthinking and/or
    unknowing manner, thou shalt keep one hand in thy pocket. Better
    that thou shouldest keep both hands in thy pockets than
    experimentally determine the electrical potential of an
    innocent-seeming device.

    - this post brought to you by the Automated Last Post Generator...