Hardware Hacking

Blaine Hilton writes "Hardware Hacking starts by going over the basics of electronics, just enough so you can understand what is happening later in the book. This gentle beginning means the book is great for people who work with computers on the software side, or people who like to play with electronics. You do not need to be an electrical engineer to understand what they are talking about in this book. As the title suggests, the authors walk you through different methods and processes of modifying common hardware." Read on for the rest of Hilton's review of Hardware Hacking.

The authors' explanations of many of the terms and concepts used in the book are very good. For example, the description of "power" on page 20 is the best description of the term that I've ever heard or read. From first-hand experience trying to explain this concept to others I wish I'd known such a lucid explanation -- it explained the concept much better than longer, dryer text would have.

Another positive point to this book is the pace and order of the book. It starts with part one, which is an overview of working with hardware; part two is a collection of hacks that one can do on different devices. If, like me, you never really did any thing with the Atari, you could skip those chapters and still proceed with the book. This book is easy to carry because there the authors frequently provide directions to other resources rather than trying to cram everything into this one book.

Like I said, I'm not too interested in Atari hacking, but the idea presented in this book (in an Atari-centric context) for a standard power connector is good for other things too. This is one of the biggest strengths of this book: The examples themselves are highly specific, but the thinking behind them can easily be generalized.

The first part of the book briefly explores tools that are going to be used later in the hacks and how to use them. However I found it a bit odd that the authors tell you to use a heat gun and heat-shrink tubing, but do not list these items in the tools section.

The fun really begins in part two with the actual hardware hacking. I have never really done anything with hardware before. It seems like whenever I took something apart I could never get it back again, and that those times that I did get something back it would never quite work as it should again. Those experiences have taught me to not mess with things I shouldn't and, this is why I think it's great that part two begins with the ubiquitous and cheap CueCat. I had a couple of these lying around and didn't really care about them so I jumped right in, following the many clear explanatory photos.

Starting with something like this gave me the confidence that I can take stuff apart, and if I'm careful, it will go back again.

The order of chapters seemed a bit odd in part two, though. A book must be arranged in some type of order, and my gut feeling is that it should be by order of difficulty. The second part started off great, going over tools and then the CueCat, but then it seems like the chapters that follow are tossed in at random. This could be from my lack of hardware experience, or that the chapters were designed to be random. This fact really didn't distract from anything though. Just don't expect a linear progression.

I was able to appreciate the integration between the hardware and the software. Hardware Hacking also goes over the software side of the hardware involved.

One of the areas I wish they had given more attention to was in the chapter on the Macintosh where they are hacking a CRT monitor. I believe that the safety warning should probably be a bit bolder, especially considering the earlier, prominent advice about static energy and grounding.

The authors have used part three as a technical reference, including some frank talk about Linux vs. Windows in chapter six. Sure, many people like Linux better, however you have to take into consideration who will be using the system. In a system the whole family uses, it has to be user-friendly enough for the whole family to use.

If changing hardware to better suit your needs sounds like something you would like to try, but you don't know how and are worried about what might happen, then this book may just be able to convince you go for it, along with enough information to make your next warranty-voiding attempt a success.

---

You can purchase Hardware Hacking from bn.com. Slashdot welcomes readers' book reviews -- to see your own review here, read the book review guidelines, then visit the submission page.

Good review

[Bill, Shooter of Bul (629286)]

I might just have to pick it up and brush up on my electronics skills. I'm sure it would come in handy someday.

Good review - NOT

[Rick the Red (307103)]

What are these hardware hacks? What is done with the CueCat? Are they removing the serial number chip from the CueCat or are they turning it into a laser pointer or what? What did they do to the Atari, and which Atari? Mod it to play Xbox games? Turn it into a general purpose computer? A home automation control center? What? What other hardware is hacked, and will I need to do the hacks? If I can buy something cheap on eBay and turn it into something cool, great, but if this is just about adding expensive components to expensive or rare stuff, forget it.

A review should tell me why I might want this book; this review did not.

Re:Good review - NOT

[Anonymous Coward]

Table of Contents [grandideastudio.com]

Ok, my bad.

[Bill, Shooter of Bul (629286)]

To be honest, I quickly skimed the writeup because I was in a rush to see if I could manage to get a fp. At least I didn't troll. I was actually suprised I wasn't modded down. In any case its not the best review. I also went down to B&N and reviewed the book myself. Its not good. The Cue cat is "hacked" to remove the unique identifier. The Atartis are "Hacked" to modify their controllers ( 2600 is rotated 90 for lefties, they modify a nintendo (NES) controller to work with it, make a 5200 paddle wheel, and replace a red led with a blue one. Other chapters are equally disapointing. The one on Tivo replacements is a simple myth tv howto and a section on doing the same on windows. The Terrabyte drive was by far the coolest hack, but I wouldnt' consider it very cool simply because of the high cost of the supplies. For some unknown reason the last chapters are on Operating system archetecture ( where they reveal that drivers are used to control hardware!) and an intro to programming (variables are used to store data in memory!). Craptacular. On the front their is a quote from mitnik that makes absolutely no sense he's quoted to the effect "If I had this book ten years ago, the FBI never would have caught me". WTF? Was he captured using the UID of the Cue Cat? Or maybe it was because he couldn't use the right handed 2600 controler! So unless you want to build a terrabyte firewire raid drive, I wouldn't reccomend it.

Re:Good review

[ejaw5 (570071)]

A good book to pick up is _The Art of Electronics_ by Horowitz and Hill. It goes over a lot of circuit theory and digital computer architecture. It's straightforward and easy to read. I recently checked it out from the library and it covers a lot of things I've learned in my theory classes. It gives many examples of good circuit design ideas and bad ones. I may end up buying a copy to keep as reference.

Re:Good review

[the morgawr (670303)]

I'll second that is's a good electronics book. The one place it's lacking is it's coverage of the newer GaAs and InP transistors (mostly MESFETS used in communications). Then again I don't know of a book that DOES cover that stuff well....

Also if you need a general EE reference (circuits, filtering, fields, compatability, etc) I'd go with Kaiser's Electromagnetic Compatibility Handbook. It's not released yet but I have a pre-press edition for review and it is THE most thorough book on basic EE that I have

Re:Good review

[ajs318 (655362)]

I'll second that. Horowitz and Hill is the book for anybody wanting to learn about electronics. If you can find a copy at the right price, buy it - you'll never regret it.

Sample Chapter

[ryanr (30917)]

Sample chapter here [syngress.com] if you're interested (.pdf). That's Joe's intro chapter. I did the HTPC chapter (the Linux vs. Windows Chapter 6 mentioned.) :)

more info

[Anonymous Coward]

this review needs more specific info on the different hacks

This smells like a repeat review..

[Anonymous Coward]

.. same book, but reviewed by someone different. I didn't read today's review and I'm too lazy to do a search (Slashdot's search engine sucks), but wasn't this same book reviewed by someone else not too long ago?

Re:This smells like a repeat review..

[ryanr (30917)]

No, that was the O'Reilly book with a very similar name: http://books.slashdot.org/books/04/02/23/2036241.s html [slashdot.org]

Because the target audience isn't thick??

[adamofgreyskull (640712)]

However I found it a bit odd that the authors tell you to use a heat gun and heat-shrink tubing, but do not list these items in the tools section.

Because the kind of people reading Hardware Hacking will probably extrapolate that "heat-shrink" requires you to apply "heat" to it in order to make it "heat", using some kind of "heating" apparatus.

But you're right, it is a pretty big leap to expect people to grasp what the "heat gun" does...

What a dick I am...

[adamofgreyskull (640712)]

'in order to make it "heat"'

Should of course be: 'in order to make it "shrink"'.

Good for beginners

[Grant29 (701796)]

While it's always good to learn some of the basics, the real hardware hackers have a drive that most people don't have. You have to be willing to break a few things beyond repair while making mods. Also, the creativity of some of the hardware hacks I've seen is outstanding. You can't learn the truely unique hardware hacks from a book. The unique ideas are often the hardest part.

--
Hot Deals [retailretreat.com]

Re:Good for beginners

[dslbrian (318993)]

Actually for relatively small scale projects, and working with embedded controllers (from "basic stamps" to 8/16/32-bit controllers, ie. 8051 and such) I've found that Circuit Cellar [circuitcellar.com] is a pretty good magazine. They've had articles on wireless apps, robotics, and other stuff with a focus on hardware and practical details. A pretty fun read if your into tinkering with hardware (disclaimer - I'm speaking as a EE, so your definition of "fun" may differ).

atari hacking

[millahtime (710421)]

Like I said, I'm not too interested in Atari hacking,

Who wants to hack an Atari. They are so hard to come buy that if you screw it up you'll be kicking yourself for months. Trust me, I know.

Book Breakthough?

[jkitchel (615599)]

Another positive point to this book is the pace and order of the book. It starts with part one,...

That struck me as kind of funny. I'd hope that all books start out that way. God help us when books start at part two.

Re:Book Breakthough?

[Mateito (746185)]

> God help us when books start at part two.

Or when movies start at Part IV.

Re:Book Breakthough?

[jkitchel (615599)]

touché

Re:Book Breakthough?

[SteveM (11242)]

Isaac Asimov wrote a scifi novel that started at chapter six. I think it was The Gods Themselves.

Chapters one through five did eventually show up.

SteveM

Re:Book Breakthough?

[the_mad_poster (640772)]

Of course, were you a true geek, you'd know that it should have started at Part 0.

We're going to have to revoke your Slashdot ID now...

Re:Book Breakthough?

[djeaux (620938)]

God help us when books start at part two.

Go check an organic chemistry textbook. They generally start with part twenty-six...

Mitnick

[vasqzr (619165)]

I seen his name, instinctivley picked the book up, and read a few chapters, spent nearly an hour leaned up against the shelf and Barnes and Noble. I guess they have chairs there for a reason...

It's a pretty good read, but it's not quite for the 'Tech TV' crowd, it's actually kind of advanced and detailed.

How about wetware hacking?

[linzeal (197905)]

Personally I think the far more interesting engineering that geeks forget to study is the human one [amazon.com]. As we have evolved larger brains most humans have neglected to study some of the proposed methods [amazon.com] one can learn to change it with. Besides the obvious future augmentation with nanotechnology or its ilk we have a scant few that have pondered its intracies. Most of them are flakes, all of them are partially 'out there' but maybe you have been a little 'out there' to get 'in here'.

Hardware hacking of all kinds is cool, but as I more intimately familiar with mechanical engineering and know that I have to take electrical engineering courses beginning next year perhaps this book will help. Can anyone second the review?

This book is a walking DMCA violater's manual!

[Anonymous Coward]

I had to take a shower after handling this book at my friendly Bookstar, so dirty I felt just from reading these recipes for being an ILLEGAL COPYRIGHT and PATENT violating criminal! I see nothing but wicked intructions on violating the legally and rightly conferred DMCA rights of the benevolent corporations of this country. I will be referring this unholy tome to the proper authorities so that this matter is handled promptly.

Re:This book is a walking DMCA violater's manual!

[Dr. GeneMachine (720233)]

Friend computer strongly encourages you to turn in mutant commie traitors who even think about modifiying the sacred hardware of friend computer. This is solely reserved for programmers with ultraviolet clearance. As for your contact with this abomination, friend computer requires you to visit the next confession booth to receive proper reward for your information...

All hail friend computer!

Thanks for all the comments!

[joespandex (759954)]

Thanks to Blaine for the no-nonsense review. It's nice to hear people's thoughts without being sugar-coated.

For what it's worth, the full title of the book is "Hardware Hacking: Have Fun While Voiding Your Warranty".

As for the real mindset of a (hardware) hacker, true, that cannot be taught. But, it doesn't mean that more mainstream readers are not curious about tinkering with hardware. Getting people to think outside of what they are normally taught is the important thing and hopefully they'll benefit from the book.

I wanted to try and include something for everybody in this book. So, the introductory EE, coding, and OS chapters are for people who might not have a sense of those things (to tell you the truth, I use the EE chapter, which I wrote, as a reference guide all the time). The hacks range from easy (changing the LED in a Macintosh mouse or Atari 7800 Power indicator) to complex (Marcus Brown's Playstation 2 Independence Day hack). And, there's a wide range of hardware to play with, too.

I'd like to think there is something for everyone (well, almost everyone). You don't have to have extreme hardware skills or have an engineering degree to enjoy the book and rip your products apart. The worst you can do is break something, but that's part of the fun! :)

Joe

PS - PDFs of the TOC, Foreword, and Introduction can be found here [grandideastudio.com].

Re:Thanks for all the comments!

[Violet Null (452694)]

Those are guidelines for graphics. Text will wrap just fine unless you tell it not to. Instead of a fixed width and height, you could use, say, 90%, still get the border effect (if desired), and not have to worry about the resolution of the display at all.

Electronic Grounding Helps Technically

[Jonah Hex (651948)]

I've been a long time OS tech, working my way up since the days of DOS and BBS's, etc. After I took a 6 month course in the basics of electronics and TV/VCR/Computer repair back in the early 90's I've found that diagnosing and/or understanding how the underlying hardware works helps greatly. I'd definately recommend to all you puter techs out there to learn the basics of electronics, if it be via this book or a cheap course at the local CC. (of course my best advise for aspiring techs is to learn the scientific method and good troubleshooting skills)

Jonah Hex

Why I've never been a hacker of hardware

[dmorin (25609)]

I remember my first job out of college where they made their own circuit boards for a medical device. While something compiled on my 286, I watched the EE do all kinds of tests and simulations at his desk. Finally I said, "That looks boring. Fire that bad boy up and see what happens."

He looked at me, pointed at a chip and said "See that? Those cost $100 apiece. I have 4 of them, and they take 3 weeks to order. I can't afford to blow it up." And went back to his work.

I always remembered that as the best demonstration of the difference between hardware geeks and software geeks. Software geeks abide by neither the laws of physics nor economics.

Did some say ATARI?

[AtariDatacenter (31657)]

So which Atari hacking are we talking about? Arcade PCBs, 2600s, home computers, Atari Calculators, Atari UNIX boxes [!]. what?

Regarding hardware hacking in general, I think one of the best ways to get started is with a BASIC Stamp, like from parallax [parallax.com]. It really lets you expore the interface between software and hardware.

I kind of wish the review gave me a better feel for the book. I'm getting better in my hardware, but I'm not beyond a good textbook to lean on for some things.

Re:Did some say ATARI?

[Dun Malg (230075)]

So which Atari hacking are we talking about? Arcade PCBs, 2600s, home computers, Atari Calculators, Atari UNIX boxes [!]. what?

For those who think a mere link to the books TOC isn't actually an answer to the question, the book seems to concentrate on mods for the early Atari consoles, like the 2600, 5200, and 7800. Other notable devices listed as subjects in the TOC include:

PlayStation 2
802.11 devices
iPod
Nokia 6210
Palm devices

Chapter on the DMCA?

[David Hume (200499)]

From the Publisher [barnesandnoble.com]:

Modern game systems, too! Hack your PlayStation 2 to boot code from the memory card or modify your PlayStation 2 for homebrew game development

Which makes me ask, is there a chapter on your potential liability under the DMCA? [eff.org] --

Section 1201 Impedes Competition and Innovation.

Rather than focusing on pirates, many copyright owners have chosen to use the DMCA to hinder their legitimate competitors. For example, Sony has invoked section 1201 to protect their monopoly on Playstation video game consoles, as well as their "regionalization" system limiting users in one country from playing games legitimately purchased in another.

* * * *

Sony Attacks Playstation "Mod Chips"

Apart from using the DMCA against vendors of personal computer emulators of Sony's Playstation, Sony has sued a number of manufacturers of so-called "mod chips" for alleged circumvention under the DMCA. In doing so, Sony has been able to enforce a system of geographical regional restrictions that raises significant anticompetitive issues.

So-called "mod chips" are after-market accessories that modify Playstation consoles to permit games legitimately purchased in one part of the world to be played on a games console from another geographical region. Sony has sued mod chip manufacturers in the U.S., the U.K., and Australia. In the U.S., Sony sued Gamemasters, Inc., distributor of the Game Enhancer peripheral device, which allowed U.S. Playstation users to play games purchased in Japan and other countries. Although there was no infringement of Sony's copyright, the court granted an injunction under the DMCA's anti-circumvention provisions, effectively banning the use of a technology that would permit users to use legitimately-purchased non-infringing games from other regions.

Drinkers Purgatory [purevolume.com]

Then again, does the book violate the DMCA?

[David Hume (200499)]

No mod chips were used in the book, at least from what I can see. So maybe you should stop jumping to conclusions and do some research before spouting your mouth off.

Thanks for the calm, rational and respectful reply. Did more research. Turns out that, at least as far as Sony is concerned, the presence of a "mod chip" is not necessary to allege a violation of the DMCA. Indeed, as noted by Prof. David S. Touretzky at Carnegie Mellon University [cmu.edu], merely publishing information aiding circumvention of a

Mental image

[computational super (740265)]

... hacking a CRT monitor. I believe that the safety warning should probably be a bit bolder, especially considering the earlier, prominent advice about static energy and grounding.

I suddenly have this mental image of Wile E. Coyote standing over an open monitor, covered in black soot, smoke swirling off of his head...

The XGameStation

[Langley (1015)]

Check this out some time: XGameStation [xgamestation.com].

This may have been posted to Slashdot before, but it is worth bringing up again since its been at the "Pre-Orders Coming Soon!" stage to quite some time now.

This is Andre LaMothe's little project (little?), that when it comes to fruition will be a bad-assed tutorial on not only hacking together your own computer but all the neat programming that goes into getting it up and running as a fully functional console game system.

Anyway, I can't wait to get my hands

Mod chips?

[NineNine (235196)]

I'd *love* to see a nice, step by step explination as to how to mod my PS2, speaking of hacking. As is, I had to ship it to a guy who did it (and he did a perfect job putting in a DMS3 chip), but I would've liked to be able to do it myself. As is, there's virtually no information on how to solder those little tiny connections yourself out on the web that I could find.

furby?

[nappingcracker (700750)]

if this is the book im thinking of, it will tell you how to hack a "furby". pretty slick. turn your furby into funzo!

Re:somewhat misleading..

[Schweg (730121)]

That's a little harsh. There are always levels of understanding about any concept. Just a few of them:
1. Enough understanding to use an item. This can be rather little, if the internal details are encapsulated well enough.
2. Sufficient to interface to or enhance an item. This requires more information, but the interfaces generally mean that you need less information about the internal details as well.
3. Sufficient to build an item. This requires significantly more knowledge, but depending upon the state of the art attempted, may not require a professional practitioner.
4. Sufficient to design an item. This is really where professional training and practice come into the requirements, but this level is not required to be able to do interesting things with most hardware!

Re:somewhat misleading..

[syslog (535048)]

Don't be so patronizing. The review's author clearly said that he was talking about understanding how "computer hardware works," not "how to build your own computer in 21 days."

I have a MS in CompSci and a few electrical eng. courses. I certainly don't have the skills to build a computer, but I most certainly understand how it works.

Regards, naeem

Re:w00t!!!!

[idontgno (624372)]

I'm not quite sure /us is ready for Paris Hilton hacking our hardware.

I'm just sayin'.

Re:w00t!!!!

[Paulrothrock (685079)]

Blech. Paris is a retarded blonde idiot. Why would I want her? Geekgrrls make better sex partners because of their inherent curiousity.

Re:Amazon has it cheaper...

[ryanr (30917)]

And Bookpool cheaper still:
http://www.bookpool.com/.x/ierdixxv34/ss/1?qs=hard ware+hacking [bookpool.com]

Disclosure Note: I wrote part of the book, and the deal the publisher has with Bookpool sometimes results in slightly higher royalties for me. They do often have the best price, though.

You can do your own comparison shopping, of course:
http://isbn.nu/1932266836/shipover/ [isbn.nu]

Your best deal usually depends on shipping.

Re:Shrink Tubing

[Cpt_Kirks (37296)]

Dammit, it's not harware hacking without electrical tape. Lots of it. Rolls of it. I buy the tubes of 5 rolls.

Heatshrink is a *BITCH* to remove. It tends to harden when heated so a razor will barely cut it.

Re:Shrink Tubing

[mangu (126918)]

Also, you can use tape in places where heatshrink won't fit. Ever seen any Y-shaped heatshrink? No, I dont'think so...

Re:Shrink Tubing

[Grishnakh (216268)]

Ever seen any Y-shaped heatshrink? No, I dont'think so...

Actually, yes, I have. It was used in some mil-spec fiber-optic connectors. But you certainly won't find any at Radio Shock.

Re:Kev's an author?

[joespandex (759954)]

Kevin was the technical reviewer for the book. Since he has a technical background, but not specifically related to hardware/engineering, we thought it would be fun to get a different perspective. He gave us some extremely useful comments but didn't write any of the text.

If you didn't notice, his tagline on the cover is obviously tongue-in-cheek, as there is nothing illegal in the book.

And yes, his name does help sell books. But no, he doesn't get a cut. :)

Joe

Re:"Hacking" in title

[DoraLives (622001)]

Engineer Your Way Out of the Nursing Home

The sins of your youth shall be visited upon you with redoubled fury in your old age.

Re:Mouse hack

[microTodd (240390)]

Here's [penny-arcade.com] a good one for hacking your game boy advance.

Re:Power

[PetWolverine (638111)]

Previous replies have pointed out that your formula is wrong. I would also like to point out that not everybody knows the definition of "work" used in physics, and many people have trouble grasping it when it's explained. You may know that work = force * distance, but do you know, conceptually, why this particular formula is how physicists decided to define the word "work"?

My high school physics teacher warned his students of the pitfalls of trying to use this term as if it were intuitive with the following example. When you lift a weight, you do a certain amount of work. When you hold the weight in place at a certain height, are you doing work? Most people will answer "yes", because it's hard to hold the weight there, so they feel that they would be doing some "work" by doing so. The proper answer, from a physics perspective, is "no", because while you're applying a certain force to the weight to hold it up, the distance through which you move it is zero, so that work = force * 0 = 0.

Just a little reminder that the physical definitions of common terms can't always be used intuitively. By the way, if I remember correctly, the answer to the question I posed in the first paragraph is that force * distance has the same units as energy, so that work can be seen as a quantity of energy being transferred.