Slashdot Mirror


Apple I Replica Creation

Ken Hansen writes "It was with great anticipation that I pre-ordered Apple I Replica Creation by Tom Owad -- I'd always been interested in 'classic' hardware, and the Apple I came just before I got interested in computers (the late '70s -- timeshare terminals, TRS-80s, and my first computer, the SYM-1). I'd seen the story on Wired about Vince Briel's Replica 1 project, and wanted to try it out. When the book arrived, I quickly scanned it, and it looked pretty good: sections on the history of the Apple I, instructions on how to build the Replica I from Vince Briel, programming the Replica I in both BASIC and 6502 assembler, and some details on how the actual Apple I and Replica I hardware works. Then I started reading the book ..." Read on for the rest of Hansen's review. Apple I Replica Creation: Back to the Garage author Tom Owad, John Greco pages 416 publisher Syngress Press rating 4 reviewer Ken Hansen ISBN 193183640X summary A confused book that is thin on details.

I read the Foreword and was put off -- it had no discussion about what to expect in the book, nothing about Tom Owad, or even Vince Briel; it seemed to be a letter from Steve Wozniak discussing the Apple I and its place in history.

Moving on into the book, in the first chapter I read about several people that own (or have owned) genuine Apple I -- and while this was interesting, and helped to get me in the mindset of mid-seventies computing, I felt this too had little to do with the stated purpose of the book -- building an Apple I replica. Personally, I would have put this chapter in the back of the book, most likely as an Appendix, since the reader must have some knowledge of the Apple I before they picked up the book, and these stories do little to describe the hardware we are going to build.

The next two chapters -- "Tools and Materials" and "Digital Logic" -- provide thin overviews on building electronics projects in general, and an overview of Digital Logic. I contend that if you've never picked up a soldering iron, you shouldn't make your first effort a computer, no matter how "simple" this one is (and it is pretty straightforward, just a handful of chips with no tricky analog "adjustments" to make), and if you want to learn about Digital Logic, you'd be well served to focus on the material as covered in Charles Petzold's classic tome Code.

Next we have a chapter on building the Replica I -- there are no real insights provided, no hints or tips that relate to the reader that the author even built his own Replica I. In fact, the author includes a quote from someone who built his own Replica I, but by the end of the included story, this person hasn't gotten it working yet. Since this story was (apparently) written well in advance of the book being published, why not include an update indicating that Vince was able to get his Apple I replica up and running? (By all accounts, Vince is very helpful to those that buy his kits.)

There are almost 4 pages dedicated to the McCAD program included with the book on CD-ROM, but unless you are familiar with CAD/circuit design software, you will finish the four pages with precious little understanding of how to actually use the software, or how to turn the circuits you designed into actual printed circuit boards.

Moving on, we have a chapter on programming the Replica I in BASIC -- this chapter provides only the barest minimum information on the BASIC included with the Replica I. This BASIC is Integer only, and was written by Steve Wozniak personally. While BASIC once was a very common language (it used to be included in ROM on almost all consumer and business personal computers, before Disk Drives became commonplace), it merits a better overview than the author provides. The original Apple I BASIC Manual (available from Vince Briel's website) does a better job describing the language. The author includes an extensive dissection of a larger BASIC program (a simple text-based role-playing game), but gets lost in describing how the program works. I was left with the feeling that the larger BASIC program was included to pad the section on BASIC programming.

Then we move on to programming the Replica I in Assembler -- here the author cuts so many corners (he even reduces the now-obligatory "Hello, World" program to a much shorter text message "H W" to save space) that the reader is left with only a hint of what can be done with the Replica I in assembler. Again, material appears to be added to the book to pad out the chapter, including one of three separate ASCII Character charts, all the Op Codes of the 6502 CPU listed in several different ways (both in this chapter and in the Appendices), and the thinnest of details in the "detailed" views of each Op Code (Op Codes are the instructions used to build a program in assembler).

Next we come to a chapter entitled "Understanding the Apple I" -- what this chapter is doing in the back of the book is beyond me, since understanding the Apple I is, you know, the whole point of this book, right? The information provided is fairly technical, but does little to provide the reader with the information needed to actually design/build anything based on the Apple I design. Note that while this book is about building an Apple I replica, it is not a "clone" -- where the original had 8K of RAM, this unit has 32K of RAM, provided by one chip instead of the original 16 chips on the Apple I. This unit is functionally identical to the Apple I, but the circuit design is greatly simplified over Woz's original design (based on about 30 years of progress in the computer industry). As a concession to the realities of the current computer market, the Replica I also uses an "AT" power supply, and can use a PS/2 keyboard in place of the ASCII keyboards popular in the mid-seventies. These changes make the Replica I a more convenient project to attempt, while retaining the original programming environment of the Apple I.

Now we enter into the Appendices -- we have another ASCII Character Chart as Appendix 1 (there are three total, if memory serves me correctly), then three appendices which simply list all the Op Codes of the 6502 processor three different ways. Again, these appear to be added simply as filler material to add heft to the book -- the author adds nothing to these sections, and they repeat information covered elsewhere in the book.

Next we have an Appendix on "Hacking Macintosh": this is the clearest case of padding a book I've ever seen -- the author describes how to take a Macintosh SE and replace the case with "Lego-type" blocks -- a trivial hack, unrelated to the Apple I in any way, and a potentially dangerous activity, because you are exposing high voltage electronics by removing the manufacturer's original case with its shielding and protection. Then we have a slightly more technical hack in the "UFO Mouse" hack -- adding an LED to the original iMac UFO mouse. Then we have our final Mac Hack -- wrapping the interior case of a Mac Cube system with decorative wrapping paper and placing the now "beautiful" system back in the clear plastic case. This is a hack? How does this relate to the Apple I?

The final appendix is titled "Electrical Engineering Basics" -- and while it does a reasonable job of describing what various components do (like resistors, capacitors, diodes and transistors), there is no reference to take the reader to a place where they can learn to build things of any sophistication (like, say, a computer, perhaps?). I was left asking the question, if this material is needed by the target reader, why are they attempting to build a Replica I computer? If the target reader doesn't need it, why is it included? We also are treated to our second set of instructions on how to solder -- again, why was this included in the book?

In the end, I have no idea who the target audience market is for this book, and I felt the book had no central theme -- it seemed to be a bunch of material culled (I can only assume) from the author's Apple Fritter web site. This book was too "light" to be of any real use to an experienced electronics person looking to design an "Apple I-inspired" system, and there is precious little material for the electronics novice who wants to build Vince Briel's Replica I kit that isn't provided by Vince either on his site or in the included assembly instructions and original Apple I documentation.

I noted numerous errors in the book, and attempted to forward them to the publisher for inclusion in the next printing of the book, but after finishing the book, I suspect there will be no need for a reprinting. I say attempted, because my email to the publisher bounced, but I was able to send my notes to the technical reviewer of the book, and I have sent my notes to Vince as well, for his reference.

I found this book to be confused (no clear narrative/theme/idea), cluttered (why three ASCII charts? Why Mac Hacks?), and to contain many typos/errors. In the final analysis, unless you simply have to have this book because it is about the Apple I, I'd say save yourself the cost of the book, and simply order a pre-assembled Replica I from Vince Briel -- the money you save by not buying the book ($39.95 Suggested retail price) will almost exactly cover the price difference between the unassembled Replica I and the the assembled version (currently $40 US).

You can purchase Apple I Replica Creation: Back to the Garage from bn.com. Slashdot welcomes readers' book reviews -- to see your own review here, read the book review guidelines, then visit the submission page.

7 of 163 comments (clear)

  1. Re:My take... by eviltypeguy · · Score: 2, Insightful

    Uh, all you did was paste the last paragraph of this article into a slashdot comment...hello moderators. Read before moderating :)

  2. Re:Apple marketing has improved by Jozer99 · · Score: 2, Insightful

    Not really. They just sued a 19 year old college student who runs spymac for $1 damages, and refuse to settle. That means that he, win or lose, is stuck paying thousands of dollars for a lawyer.

  3. Reviewer review by ryanr · · Score: 5, Insightful

    I find the reviewer to be confused, unclear, and unnecessary.

    He seems unclear on what is typically said in a foreword, especially by someone like Woz. He doesn't seem to understand why an unrelated Mac chapter might be added as an appendix.. it's there because Apple hackers might find it entertaining. It's a free bonus.

    I found the first chapter, the one about the Apple I history, to be essential and appropriately placed at the beginning. I started with the Apple ][, and I had always assumed that the Apple I was similar, i.e. standardized, came with basic, etc... instead, Chapter 1 has cleared up the fact that nearly all owners customized their Apple Is. It also tells why the serial board was popular, and hence why you might want one for the Replica I. It tells what was up with the different RAM amounts, BASIC, and so on.

    To be fair, I only got a couple of chapters into my copy before I had to give it away to a Mac enthusiast (who used to work at Apple) who wanted it to have an electronics project for his kids. My replacement copy is on the way, maybe I'll write a proper review and see if Slashdot will take it. Note: for the conspiracy theorists, I often write for Syngress, though I had nothing to do with this book. Assume I'm a shill if you must.

    Also, I see a few talking about Apple suing and such. I doubt that will happen. Syngress is generally pretty careful about that. Woz gave his blessing for the use of the ROM monitor, and the book states that Apple had given over support of the Apple I to the Apple I Owners Club anyway.

  4. What's it worth now? by mahju · · Score: 5, Insightful

    If you brought an Apple 1 in 1977, would it have been expensive?

    According to here this can be translated (into 2003 dollars) as follows;

    In 2003, $666.66 from 1977 is worth:
    $2,023.56 using the Consumer Price Index
    $1,647.39 using the GDP deflator
    $1,947.17 using the unskilled wage
    $2,733.51 using the GDP per capita
    $3,605.56 using the relative share of GDP

    Which I guess means that the relativelty the Apple 1 was expensive compared to a mini at $500 USD, but about the same as a top line G5 dual 2.5G at $3,000 USD

    But I doubt I'll be whacking together a dual G5 in 23 years for only 100 bucks

  5. How about an Apple II+ or IIe clone? by leereyno · · Score: 3, Insightful

    The schematics for the II+ are readily available as well. In fact the manuals that Apple shipped with the II and II+ had not only the schematics, but a hex dump of the roms. And to think, they were actually surprised when people started cloning their systems....

    As for whether Apple would sue, I don't really think I care. Last time I checked there was nothing illegal about implementing a hardware design that one has the plans to. Selling it would probably violate IP laws of one sort of another, but then I'm not advocating that. As for the ROMS, there are II+ and IIe systems for sale on ebay all the time. There are also several Apple II series emulators that include dumps of the roms. These have been around for many a year. If Apple cared they'd have rattled their cage by now.

    Lee

    --
    Muslim community leaders warn of backlash from tomorrow morning's terrorist attack.
  6. Re:So basically you recommend the book then? by squiggleslash · · Score: 3, Insightful
    Says you! I remember back then you'd get a pile of circuit diagrams and a book on programming (a good book on programming) with every computer. I remember pouring over the instructions and diagrams for the Sinclair ZX81, and the fantastic Steve Vickers BASIC manual that came with it.

    Then the BASIC manuals kind of went. By the late eighties you often got circuit diagrams, and some introduction to the OS but nothing on programming. My Amiga 500+ was typical, including a little booklet that included circuit diagrams for the entire thing, and a walk-through of Workbench 2.

    Now you get... pretty close to nothing. My PowerBook (and the Jaguar and Panther boxes I got) came with an advertising brochure. You're lucky if you get something describing what plugs into what.

    As the computers have been dumbed down, there's been an assumption nobody actually wants to know how the machine works, how to program it, how to understand it. I think that sucks personally.

    --
    You are not alone. This is not normal. None of this is normal.
  7. Reviewing reviewer review by ggvaidya · · Score: 2, Insightful

    Well, I for one am glad somebody finally came up with a "this book sucks, don't touch it with with a ten foot pole" type review, after the boring slashvertisements we've been seeing lately.

    I do agree with the reviewer review that the review was confused, spending way too much time talking about how he would have prefered the book to be organised, rather than just telling us how it was and letting us make up our minds (or bringing his own feelings up in the conclusion).

    Other than that, I'd say the review was interesting. Also, the reviewer review was fair and balanced, correcting the reviewer's mistakes without too much flaming. Kudos.