Slashdot Mirror
It's Never Done That Before
Graeme Williams writes "I really need something that will help me diagnose and fix problems with Windows PCs. I provide occasional support for more than a dozen PCs at my local church, as well as the systems at home, and those that arrive in the wake of my children. I don't do it regularly enough to have a clear model of how I should go about it. I really wanted It's Never Done That Before to provide that clear model, but unfortunately I was disappointed." Read the rest of Graeme's review.
It's Never Done That Before / A Guide to Troubleshooting Windows XP
author
John Ross
pages
xix + 263
publisher
No Starch Press
rating
3
reviewer
Graeme Williams
ISBN
1-59327-139-5
summary
Not organized well enough to help in a real crisis
After reading It's Never Done That Before, I've got a pretty good idea of what I'm looking for in a book about PC repairs. The first part of my ideal book would provide background information about how a PC works. For example, if you wanted to diagnose a problem that occurred during booting, it would help to know what was involved in the boot process, from the power and power supply to the BIOS and MBR and ultimately to Windows, the registry and the desktop.
The second part of my ideal book would explain basic techniques, such as how to change your BIOS settings. These techniques would form a library which could be referred to later in the book without further explanation. The third part of the book would explain things you could do before disaster strikes, such as backing up your data, and writing down your network configuration parameters, and most importantly, making sure you can actually follow the recovery procedures you'll need when disaster does strike. If you can't change BIOS settings when your machine is stable, you're certainly not going to be able to do it when you're terrified that a hard drive failure has lost Auntie Edna and Uncle Norman's pictures. My recommendation would be to permanently set your BIOS boot settings so that your system looks for a boot CD before booting from disk, but if the extra delay bothers you, you can always change it back. At least you'll know what to do.
Evaluating It's Never Done That Before against my ideal, the real book does better on content than it does on organization. For example, it has a useful chapter on what you can do before disaster strikes, and it has a pretty clear explanation of how to change BIOS settings, but they're not in the same place.
The fourth and final part of my ideal book would explain how to diagnose and repair problems. One of the reasons this isn't trivial is that a book should necessarily focus on the most common problems, but has to leave open the possibility that something unlikely is happening. One of the problems I have with my laptop at work is that when I eat lunch at my desk, the touchpad will interpret dropped crumbs as a continual touch, which immediately makes the cursor uncontrollable. Touchpads are not mentioned in It's Never Done That Before – but that's not necessarily an issue. Many more people will, say, have a hard drive failure than will have crumbs on the touchpad, and the book has plenty of material on hard drive failures. But too much of the book assumes you know what the problem is, instead of systematically going through possibilities – and leaving open the possibility that something odd or unlikely is happening.
One of my systems at home is an old hand-me-down desktop from my son. He had installed a firewire card, which remains, and a sound card, which he removed. I put in a new disk, which I partitioned as a dual-boot Linux and Windows XP system, and attached a external firewire drive. The first problem I noticed was that when Linux boots, it changes the BIOS to disable on-board sound. Perhaps this is some kind of "phantom limb syndrome" for the missing sound card? Some time ago, the firewire card became less reliable – at least, if the drive is on, Windows will black screen during boot. This can be avoided by leaving the drive off until Windows has settled down after booting. Lately, when Windows boots it has started to reset the network file sharing settings for the external drive. I fear that the Windows system on this machine is disintegrating, perhaps in anticipation of Vista.
It's not that It's Never Done That Before doesn't cover any of these areas. For example, it has a considerable amount of material on boot problems, including black screens. The problem is that it's not organized as a fault tree, where you start with no knowledge other than the immediate symptoms and proceed to collect data and rule out possibilities until you're left with the precise cause. One of the benefits of doing this carefully is that you won't prematurely decide whether the cause is hardware or software. Unfortunately, It's Never Done That Before just isn't organized this way.
The lack of organization also manifests itself as unnecessary and sometimes irritating repetition. For example, you get to the Windows Advanced Options menu by pressing F8 during startup. On page 46, the instructions are "When the results of the POST [power on self test] appear on the screen, press the F8 key until the Windows Advanced Options menu appears". On page 48, the instructions are to "immediately press F8 a few times" POST is not mentioned. On page 60, the instructions are to "press the F8 key several times".
The book just isn't clear about how a PC connects to the Internet and how that can fail. One indication is that the material is split between Chapter 13, "Internet Connection Problems" and Chapter 15, "Dealing with Hardware Problems", when there's no way you can know a priori whether a problem is hardware or software. Or for that matter whether the problem is yours or your ISP's.
Figure 13-3 on page 147 is the first of two diagrams related to Internet connectivity. The diagram shows something called a Wide Area Network which you connect to that is separate from the Internet Cloud. I suppose this might refer to the BGP AS you're connected to, but that hardly matters to most people. And having introduced the idea that you're connected to some equipment at your ISP, the diagram doesn't make clear that if you're directly connected to the Internet (without a router), your PC gets an IP address from the ISP's DHCP server, but if you're connected via a router, the PC gets its address from the router, and the router gets its address from the ISP. How do you recognize when your PC hasn't got an IP address from the appropriate DHCP server? This is needlessly hard in Windows XP, because the OS "helpfully" defaults to something plausible and wrong, but the book offers no help in digging you out of this one.
Figure 15-1 on page 169 includes a DSLAM (a piece of equipment at the local telephone company), which is a fascinating detail, but not really something you need to know even if you have a DSL connection. At least in the US, the key thing to know is that DSL wiring problems belong to one part of the telephone company (because it's the same wiring as your telephone) but Internet problems belong to a different part. If you live in the inner city, you're quite likely to have wiring problems (based on my experience with a sample of two and a failure rate approaching one per year), but if you have a problem with your line and you're talking to the wrong group within the telephone company you'll be rebooting your PC and checking network settings until you're blue in the face.
The popularity of wireless LANs has introduced a whole new set of problems. At home, my POSSLQ uses a laptop with a wireless PCMCIA card. As the the wireless router got older, the wireless connection on the laptop seemed to get less and less reliable. After avoiding the problem for a while, I stumbled across the length argument on the ping command, and discovered that the packet loss rate depended on the packet length. I adjusted the MTU and things immediately got a lot better. It's Never Done That Before ignores ping in favor of traceroute (which I find confusing for basic connectivity problems) and so would never solve this problem.
Even a simple LAN requires several systems to be up and communicating in order to connect to the Internet. A short time ago I upgraded the wireless router in my home from 802.11b to 802.11g. By systematically going though all the incorrect combinations first, I was able to verify that the procedure given in the router manual was both necessary and sufficient: power off the cable modem, router and PC, and power up the cable modem, router and PC in that order. I also support a local church with a local area network of about a dozen computers, which seems to have an endemic problem with IP address conflicts. In this case, I leave the PCs on and power cycle the router. These rules and especially the reasoning behind them aren't included in It's Never Done That Before.
I'm a little mystified why the author doesn't recommend making a live CD of your favorite Linux distro. If you have a problem that prevents Windows from booting, it's an easy way to connect to the Internet to look for resources. It's also an easy way to confirm more serious problems. I recently had a computer with a motherboard problem go into a reboot loop with a live CD, which was sort of terrifying, but immediately ruled out Windows as the source of the problem
I guess it's clear by now that I don't like It's Never Done That Before. There's a lot of information in the book which many people may find very useful in understanding more about how their PC works and how it fails. The book may very well help people with simple problems. However, the experience I've had fixing PC problems suggests to me that the book is not structured well enough to lead you through the process of diagnosing and repairing an unknown failure."
You can purchase It's Never Done That Before from bn.com. Slashdot welcomes readers' book reviews -- to see your own review here, read the book review guidelines, then visit the submission page.
After reading It's Never Done That Before, I've got a pretty good idea of what I'm looking for in a book about PC repairs. The first part of my ideal book would provide background information about how a PC works. For example, if you wanted to diagnose a problem that occurred during booting, it would help to know what was involved in the boot process, from the power and power supply to the BIOS and MBR and ultimately to Windows, the registry and the desktop.
The second part of my ideal book would explain basic techniques, such as how to change your BIOS settings. These techniques would form a library which could be referred to later in the book without further explanation. The third part of the book would explain things you could do before disaster strikes, such as backing up your data, and writing down your network configuration parameters, and most importantly, making sure you can actually follow the recovery procedures you'll need when disaster does strike. If you can't change BIOS settings when your machine is stable, you're certainly not going to be able to do it when you're terrified that a hard drive failure has lost Auntie Edna and Uncle Norman's pictures. My recommendation would be to permanently set your BIOS boot settings so that your system looks for a boot CD before booting from disk, but if the extra delay bothers you, you can always change it back. At least you'll know what to do.
Evaluating It's Never Done That Before against my ideal, the real book does better on content than it does on organization. For example, it has a useful chapter on what you can do before disaster strikes, and it has a pretty clear explanation of how to change BIOS settings, but they're not in the same place.
The fourth and final part of my ideal book would explain how to diagnose and repair problems. One of the reasons this isn't trivial is that a book should necessarily focus on the most common problems, but has to leave open the possibility that something unlikely is happening. One of the problems I have with my laptop at work is that when I eat lunch at my desk, the touchpad will interpret dropped crumbs as a continual touch, which immediately makes the cursor uncontrollable. Touchpads are not mentioned in It's Never Done That Before – but that's not necessarily an issue. Many more people will, say, have a hard drive failure than will have crumbs on the touchpad, and the book has plenty of material on hard drive failures. But too much of the book assumes you know what the problem is, instead of systematically going through possibilities – and leaving open the possibility that something odd or unlikely is happening.
One of my systems at home is an old hand-me-down desktop from my son. He had installed a firewire card, which remains, and a sound card, which he removed. I put in a new disk, which I partitioned as a dual-boot Linux and Windows XP system, and attached a external firewire drive. The first problem I noticed was that when Linux boots, it changes the BIOS to disable on-board sound. Perhaps this is some kind of "phantom limb syndrome" for the missing sound card? Some time ago, the firewire card became less reliable – at least, if the drive is on, Windows will black screen during boot. This can be avoided by leaving the drive off until Windows has settled down after booting. Lately, when Windows boots it has started to reset the network file sharing settings for the external drive. I fear that the Windows system on this machine is disintegrating, perhaps in anticipation of Vista.
It's not that It's Never Done That Before doesn't cover any of these areas. For example, it has a considerable amount of material on boot problems, including black screens. The problem is that it's not organized as a fault tree, where you start with no knowledge other than the immediate symptoms and proceed to collect data and rule out possibilities until you're left with the precise cause. One of the benefits of doing this carefully is that you won't prematurely decide whether the cause is hardware or software. Unfortunately, It's Never Done That Before just isn't organized this way.
The lack of organization also manifests itself as unnecessary and sometimes irritating repetition. For example, you get to the Windows Advanced Options menu by pressing F8 during startup. On page 46, the instructions are "When the results of the POST [power on self test] appear on the screen, press the F8 key until the Windows Advanced Options menu appears". On page 48, the instructions are to "immediately press F8 a few times" POST is not mentioned. On page 60, the instructions are to "press the F8 key several times".
The book just isn't clear about how a PC connects to the Internet and how that can fail. One indication is that the material is split between Chapter 13, "Internet Connection Problems" and Chapter 15, "Dealing with Hardware Problems", when there's no way you can know a priori whether a problem is hardware or software. Or for that matter whether the problem is yours or your ISP's.
Figure 13-3 on page 147 is the first of two diagrams related to Internet connectivity. The diagram shows something called a Wide Area Network which you connect to that is separate from the Internet Cloud. I suppose this might refer to the BGP AS you're connected to, but that hardly matters to most people. And having introduced the idea that you're connected to some equipment at your ISP, the diagram doesn't make clear that if you're directly connected to the Internet (without a router), your PC gets an IP address from the ISP's DHCP server, but if you're connected via a router, the PC gets its address from the router, and the router gets its address from the ISP. How do you recognize when your PC hasn't got an IP address from the appropriate DHCP server? This is needlessly hard in Windows XP, because the OS "helpfully" defaults to something plausible and wrong, but the book offers no help in digging you out of this one.
Figure 15-1 on page 169 includes a DSLAM (a piece of equipment at the local telephone company), which is a fascinating detail, but not really something you need to know even if you have a DSL connection. At least in the US, the key thing to know is that DSL wiring problems belong to one part of the telephone company (because it's the same wiring as your telephone) but Internet problems belong to a different part. If you live in the inner city, you're quite likely to have wiring problems (based on my experience with a sample of two and a failure rate approaching one per year), but if you have a problem with your line and you're talking to the wrong group within the telephone company you'll be rebooting your PC and checking network settings until you're blue in the face.
The popularity of wireless LANs has introduced a whole new set of problems. At home, my POSSLQ uses a laptop with a wireless PCMCIA card. As the the wireless router got older, the wireless connection on the laptop seemed to get less and less reliable. After avoiding the problem for a while, I stumbled across the length argument on the ping command, and discovered that the packet loss rate depended on the packet length. I adjusted the MTU and things immediately got a lot better. It's Never Done That Before ignores ping in favor of traceroute (which I find confusing for basic connectivity problems) and so would never solve this problem.
Even a simple LAN requires several systems to be up and communicating in order to connect to the Internet. A short time ago I upgraded the wireless router in my home from 802.11b to 802.11g. By systematically going though all the incorrect combinations first, I was able to verify that the procedure given in the router manual was both necessary and sufficient: power off the cable modem, router and PC, and power up the cable modem, router and PC in that order. I also support a local church with a local area network of about a dozen computers, which seems to have an endemic problem with IP address conflicts. In this case, I leave the PCs on and power cycle the router. These rules and especially the reasoning behind them aren't included in It's Never Done That Before.
I'm a little mystified why the author doesn't recommend making a live CD of your favorite Linux distro. If you have a problem that prevents Windows from booting, it's an easy way to connect to the Internet to look for resources. It's also an easy way to confirm more serious problems. I recently had a computer with a motherboard problem go into a reboot loop with a live CD, which was sort of terrifying, but immediately ruled out Windows as the source of the problem
I guess it's clear by now that I don't like It's Never Done That Before. There's a lot of information in the book which many people may find very useful in understanding more about how their PC works and how it fails. The book may very well help people with simple problems. However, the experience I've had fixing PC problems suggests to me that the book is not structured well enough to lead you through the process of diagnosing and repairing an unknown failure."
You can purchase It's Never Done That Before from bn.com. Slashdot welcomes readers' book reviews -- to see your own review here, read the book review guidelines, then visit the submission page.
it'll do it again when the review is reposted in 3-4 days.
I was once looking for something similar and instead came across the book (Format C, Install Linux) which saved my life!
/sarcasm
If i wanted to hear bullshit, i'd go to church.
Buy my book, but do not open it right away. Put it on a shelf somewhere, or even in a cardboard box. Go use,break,fix, work on computers for about 3 to 5 years, then come get the book, if you can find it.
You will find the book to be completely worthless, same as if you had read it the first day you got it. But it will not matter, because more than likely the experience you got from owning it, and the years of working with computers will have given you the best "experience" possible.
I only look human.
My mother is a halfling and my dad is an ogre, so that makes me an Ogreling
Clue: It HAS done that before. Just ask Google.
[url=http://www.nu2.nu/pebuilder/]BartPE[/url] is the Windows equivalent, pretty nifty. Although something like Knoppix is infinitely more useful, BartPE is still neat.
Someone who basically knows what they are doing doesn't like a book targeted at the clueless masses. Well color me surprised.
Do not try to read the dupe, thats impossible. Instead, only try to realize the truth
What truth?
There is no dupe
Slashdot Burying Stories About Slashdot Media Owned
I don't know, but I know when the phrase "jump the shark" jumped the shark. It was the time it was used to describe an actual jumping of a shark. Its already hit its peak, please stop using it.
I still have more fans than freaks. WTF is wrong with you people?
I really need something that will help me diagnose and fix problems with Windows PCs.
:P
Just take the red pill: install an open-source OS. The answers will be revealead to you
I have discovered a truly marvelous proof of killer sig, which this margin is too narrow to contain.
I need a It's Never Done That Before: Bodily Functions. I can't go into detail.
Linux fails it, hard.
no its when that jumped the shark guy decided to make a career out of it.
music lover since 1969
"I provide occasional support for more than a dozen PCs at my local church"
;-)
Can't you just leave them switched on overnight and let God take care of things?
I'm SO going to get flamed for this...
PocketGamer.org - For the gamer on the go!
Whenever you work on computers, it does not hurt to take notes of interesting problems/solutions. This is even more true if you are working on Linux boxes and still a relative newbie. While relearning is sometimes necessary, the time to do it is not when you have a dead/dying machine to get back up.
Document what you do, and later with a little more experience under your belt, go back and see if you can improve upon what you did before.
And for those of you who are utter genious and have excellent memory, just wait. Funny how as you get older, it either gets harder to remember everything. Might be because there is more to remember, or your priorities change and how to fix random computer problem is no longer the highlight of your life.
I only look human.
My mother is a halfling and my dad is an ogre, so that makes me an Ogreling
"Its already hit its peak, please stop using it."
Please stop using "its" for "it's".
Not in the same place?!? Aren't these two different topics? Yes, it helps to know how to change BIOS settings when doing disaster prevention, but why would it logically be in this chapter?
The A+ Certification course at your local community college usually covers all but *nix.
"The lack of organization also manifests itself as unnecessary and sometimes irritating repetition."
Um, the phrase "jump the shark" came from an instance of "jumping the shark". It was "Happy Days" episode where Fonzi jumped a shark and came to be known as meaing "the series has really lost it..." because that's what people thought happened when that show reached the point of using that for a story device.
For those of us who wondered what the hell a POSSLQ is, I have good news. And I say good news because initially I thought it was some sort of gay thing... sorry =)
Web2.0: I love when people Flickr my cuil and digg my boingboing until my google is reddit and I start to yahoo
It's the same with fixing Windows PCs also and it's not something a book can tell you.
My advice to anyone with a Windows PC is to get it right from the word go. I still cannot believe PC vendors will sell a PC with a 300GB drive in it with just ONE (C:) partition - educate users to use D: and E: drives for their personal programs and files, then when Windows needs to be reinstalled, the process is less painful.
Also keep a recent Ghost image to hand - then if a problem persists more than half-an-hour, just reinstall the whole thing within an additional half hour.
And in the interim, install a virtually automated virus checker like AVG Free, put Spybot and Ad-Aware on, and make Firefox the default browser.
Gentoo Linux - another day, another USE flag.
Despite many objections, said textbooks are not worthless. I have a few myself, that I keep around for various things. A desk that is not quite level, needing to site in a scope on a rifle, mounting motherboard you do not have the right case for... all good uses of these books.
Though I have to admit, as I get older, sometimes I find math a bit more intersting than when I was required to take the courses. If I had to take them again, doubt I would do it voluntarily, I might well learn more the second ( okay more like 5th ) time around.
I only look human.
My mother is a halfling and my dad is an ogre, so that makes me an Ogreling
Patient: Hey dod, my arm hurts when I do this (swings arm back and forth).
Doctor: Then don't do that!
Seriously, if the problem is that your touchpad doesn't like having crumbs on it, don't eat over your touchpad/keyboard. Problem solved!
We will bankrupt ourselves in the vain search for absolute security. -- Dwight D. Eisenhower
or you can buy it here without giving the schmuck above a penny!4 50387-5183860
http://www.amazon.com/gp/product/1593271395/103-8
http://lxer.com/module/forums/t/23168/
Please stop using "it's/it is" for "it has".
Do you know what "jump the shark" means?
It's when you go way over the top to try to maintain interest in your content. Like having Fonzi jump a shark on his motorcycle. Or having a main character die (even if only in a dream sequence). Or getting stars of other shows to be on your show.
I had no idea that having a book review posted in the middle of the day was so... extravagant.
"Trolls they were, but filled with the evil will of their master: a fell race..." -- J.R.R. Tolkien on Olog-hai
"I really need something that will help me diagnose and fix problems with Windows PCs."
What would it be, exactly, that it's never done before? Worked reliably?
Couldn't resist.
It sounds like something you might hear in the same conversation as "It happens to a lot of men, honey!"
'IT' being following your own rule (ie #4).
It sounds to me like what you need is a broad, basic grounding in computers, and that means A+ and N+ classes. To be honest I haven't taken the N+ class but I took the A+ one for easy credits and it turned out to actually be a pretty comprehensive look at computing. I suspect N+ is more or less the same.
You could just buy the workbooks and study them, but to be honest, with the objections you in particular give to this book, I think actually taking the courses would be valuable.
The simple fact is that you cannot learn from a book what you need to know to work on PCs. You need hands-on experience. The A+ class will give you a bit of that.
"You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
/Mikael
Greylisting is to SMTP as NAT is to IPv4
Words of a non-programmer. Note taken.
110100 1101000 1101000 1100110 0 1101111 1101000 1100011 1
The extensively cross-referenced content of a true "how to fix it" encyclopedia may be desired, but the market for Windows PC's are a bit large for such an undertaking. Any author is going to approach with the "here's some background, check these categories" and leave you to discern the details.
From TFA:"How something connects to the internet..." is by no means a simple process, when actually debugging connections.
Overall, this review may be a bit negative because the reviewer did not have a fuller background in the technology. Perhaps a deeper "windows networking" textbook is a an overdue read before deciding if the networking chapter is too light.
...I think it was Computerworld, possibly Datamation... circa the early eighties.
The caption was: "So, how are your company's PC users doing?"
The picture shows a guy in a suit behind a desk. In front of him is some kind of PC which has more or less exploded; there is smoke coming from it, the top of the case has a jagged hole in it, there are fragments of something or other all over his desk.
He is showing not a sign of emotion: just a dispassionate poker face. There is a thought balloon over his head, and he is thinking "It's never done that before." No exclamation point, no italics.
IMHO it is very likely that the jacket illustration was, uh, "inspired" by that old Computerworld cartoon... which in my opinion, was funnier.
"How to Do Nothing," kids activities, back in print!
Actually, the Fonz jumped over a shark on water skis.
Comment removed based on user account deletion
I was going to mention that as well (your reply is to my post), but then I checked. To my surprise, "it's" has apparently suffered from 'language creep' since my school days and has become an acceptable contraction for "it has".
Anything less than 9 is trashing the book.
Once the book fails to get a passing grade, it doesn't matter by how much.
Why?
Karma: Incomprehensible (Mostly affected by posting at +5, reading at -1, and metamoderating everything unfair.)
http://www.amazon.com/gp/product/0789734044/ref=pd _sim_b_4/104-7384389-8873557?ie=UTF8 - Upgrading and Repairing PCs (Scott Mueller)
I had to buy this book for my CS pre-req "Introduction To Computer Technology" course at college. You would be surprised just how invaluable a book like this is for things like POST codes, the base 1MB memory map, peripheral IRQs and addresses, OS boot sequences, etc. If you work (as in tech) with PCs at all you should probably know this stuff.
I honestly can't think of anything that is better than experience, but this book comes very close for PC basics. As for XP specific books, I'd look at the MS Press book Windows XP Inside and Out Deluxe Edition: http://www.microsoft.com/mspress/books/7109.asp
There are only 10 kinds of people in the world. Those that understand binary and those that don't.
A book that would fit this guy's criteria would have to come in volumes, and be encyclopedia sized, and have updates every month to keep up to date. Its unrealistic.
For example, he talks about BIOS settings, and "not in the same place." I don't know if he means the BIOS settings aren't in the same place as his BIOS, or they are in a different section of teh book than he'd like. BIOSes are all different, settings are probably in different places. You can't expect to have a rundown of every single BIOS layout and settings. They also update settings over time, and you have atleast 3 or more ways to GET into the BIOS.
And when you talk about problems, do you know how many problems you could have with a PC? From having a USB disk attatched, to IRQ conflicts, to faulty hardware, to missing dll files, to just plain corrupt files, there are hundreds if not thousands of possibilities. And the solutions are not always very simple or easy. For basic and common problems, a book might give general tips and tricks. But I doubt a book could cover every contingency.
He even says the book relies on traceroute instead of ping for oen of the problems, and as such would never resolve the issue.
You know, if you are so smart as to ridicule a book, why not write your own? Its easy to complain about something that's missing or incorrect.
>> I really need something that will help me diagnose and fix problems with Windows PCs.
Its easy, just install Linux instead. Seriously.
what it means:
Jumping the shark is a metaphor that has been used by US TV critics and fans to denote the tipping point at which a TV series is deemed to have passed its peak.
BTW, I happened to see this episode about 6 months ago and it really did stink.
"Trolls they were, but filled with the evil will of their master: a fell race..." -- J.R.R. Tolkien on Olog-hai
"The fourth and final part of my ideal book would explain how to diagnose and repair problems. One of the reasons this isn't trivial is that a book should necessarily focus on the most common problems, but has to leave open the possibility that something unlikely is happening. One of the problems I have with my laptop at work is that when I eat lunch at my desk, the touchpad will interpret dropped crumbs as a continual touch, which immediately makes the cursor uncontrollable. Touchpads are not mentioned in It's Never Done That Before - but that's not necessarily an issue."
In other words, the reviewer should simply not be allowed near anything that is more sophisticated then a stone axe. I mean seriously the fix for that is soo easy:
(1) put laptop under broiler on high for 10 minutes to dry out the bread crumbs
(2) take out notebook (use bare hands--we don't want it to slip through gloves)
(3) blow off the crumbs.
Ok, lets use the infamous car analogy.
.... and speak in such a way ... and have everything that could be needed ... etc. In other words a recipe book for whatever can possiby go wrong and often does. I understand the concept. I just don't think it's attainable.
... but broken rods punched through the oil pan? Burn't valves? Fuel injector misfires? ... and so on and so forth .... I mean most people ricochet of the curbs at high rates of speed and thnk that's normal.
A person has a car and don't know how to drive and don't want to pay a mechanic to fix the breakage. They want a book that covers all features and all possibilities of anything that could possibly go wrong for all makes and models of automobiles AND it has to be clear, concise and perfectly attuned for any skill level from noob to nuts.
It has to be laid out in such a way
I agree that users should be able to change a tire... what changing a tire equates to in personal computer land is certainly up for debate
Lets face it. These books are for the rubes to spend money on and then pay a tech twice for fixing the original problem plus those they created themselves after reading the book.
I'm a tech with more years then I'd care to admit and have a large library that one time was indispensible. I do buy books on occassion but nothing like in years past. Today almost everything is on the 'net'. That's the primary resource now and I can't envision one lone book that would meet the needs of the target audience. If there was such a beast it would run ten thousand pages at least and nobody in the target audience would lift it. Would also be out of date the date it was printed.
Another thing needs acknowledged is that people who naturaly gravitate to computer level complexity are a distinct breed. Few actually, have the capacity or the natural inclination for it. The others can learn to drive, check the fluids and perhaps perform the most rudimentary of maintenance tasks but that is all. Maybe install software.
So the book is targeted at the would be mechanic?
Well ok then. It's a start... down a very long road.
Sorry, but am I the only one who found reading this review to be the literary equivalent of trying to hack through a jungle with a machete? I read this and I still don't know what the heck it's saying. I am asking myself if this is a joke or something? Or was the book so illogically arranged (I did get that about the book) that it scrambled the poor reviewer's brain?
blah blah blah
It is probably not the most popular subject on Slashdot, but the A+ training materials provide a decent fundamental knowledge of hardware, software, Operating Systems, and how everything works togather. It is where I started, and i now not only know how to work on computers but i get paid for it.
Crisis is the rule, not the exception.
As for XP specific books, I'd look at the MS Press book Windows XP Inside and Out Deluxe Edition:
Considering that Mr. Gates' own best technicians sometimes can't fix windows, I tend to have doubts that they could write a book to tell someone else how.
Which part of the first sentence:
"Jumping the shark is a metaphor that has been used by US TV critics and fans to denote the tipping point at which a TV series is deemed to have passed its peak"
did you fail to understand?
Provide any "witty" retort you want, but let me assure you that I will not read it. Life is too short for me to waste on trolls.
After reading It's Never Done That Before, I've got a pretty good idea of what I'm looking for in a book about PC repairs.
Then perhaps you should write your own?... No book will be ideal, but at least more on a topic is better than none.
The first part of my ideal book would provide background information about how a PC works. For example, if you wanted to diagnose a problem that occurred during booting, it would help to know what was involved in the boot process, from the power and power supply to the BIOS and MBR and ultimately to Windows, the registry and the desktop.
Seems like you've thought about a publication already. Good luck with it. But in the mean time, can we get back to this particular book--you know, the one you're supposed to be reviewing?...
The second part of my ideal book would explain basic techniques, such as how to change your BIOS settings.
*sigh* I guess not....as he contines to tell us what *he'd* put in the book.
These techniques would form a library which could be referred to later in the book without further explanation. The third part of the book would explain things you could do before disaster strikes, such as backing up your data, and writing down your network configuration parameters, and most importantly, making sure you can actually follow the recovery procedures you'll need when disaster does strike. If you can't change BIOS settings when your machine is stable, you're certainly not going to be able to do it when you're terrified that a hard drive failure has lost Auntie Edna and Uncle Norman's pictures. My recommendation would be to permanently set your BIOS boot settings so that your system looks for a boot CD before booting from disk, but if the extra delay bothers you, you can always change it back. At least you'll know what to do.
Evaluating It's Never Done That Before against my ideal, the real book does better on content than it does on organization. For example, it has a useful chapter on what you can do before disaster strikes, and it has a pretty clear explanation of how to change BIOS settings, but they're not in the same place.
Geez...just when I thought you were going to talk about THIS book, you go back to YOUR HYPOTHETICAL book!
The fourth and final part of my ideal book would explain how to diagnose and repair problems. One of the reasons this isn't trivial is that a book should necessarily focus on the most common problems, but has to leave open the possibility that something unlikely is happening. One of the problems I have with my laptop at work is that when I eat lunch at my desk, the touchpad will interpret dropped crumbs as a continual touch, which immediately makes the cursor uncontrollable.
Um, what the hell is wrong with you? Didn't you know not to eat over the keyboard? WTF, dude?
Touchpads are not mentioned in It's Never Done That Before - but that's not necessarily an issue. Many more people will, say, have a hard drive failure than will have crumbs on the touchpad, and the book has plenty of material on hard drive failures. But too much of the book assumes you know what the problem is, instead of systematically going through possibilities - and leaving open the possibility that something odd or unlikely is happening.
That statement is at least helpful.
One of my systems at home is an old hand-me-down desktop from my son. He had installed a firewire card, which remains, and a sound card, which he removed. I put in a new disk, which I partitioned as a dual-boot Linux and Windows XP system, and attached a external firewire drive. The first problem I noticed was that when Linux boots, it changes the BIOS to disable on-board sound. Perhaps this is some kind of "phantom limb syndrome" for the missing sound card?
What has that to do with the diagnosis of XP symptoms? It's not Microsoft's fault your Linux install is flaky.
Some time ago, the firewire card became less reliable - at least, if the drive is
True...but there was an episode where he jumped something on his motorcycle. Now I'm going nuts trying to remember what the hell it was. Thanks a lot.
Never let a lack of data get in the way of a good rant.
So, what's the Windows equivalent to the preview button? I thought for sure they would've included that feature, but hey, I've been wrong before!
wtf? is this?
Worst article ever.
"Nae Kin! Nae Quin! Nae laird! Nae master! We willna be fooled again!"
The Windows solution to problems: reboot
The linux solution to problems: be root
Oh, did I mention you sould get rid off Windows and install Linux?
What's up with people having a Tech IQ of 0 posting on slashdot. If you're trying to read a book to figure out how to fix a Windows machine instead of going straight to google, you're better off going to Frys or calling GeekSquad.
You do not learn how to fix computers by reading books.
The only reason that A+, N+, MCSE, CCNA books are so large is that they use 1 1/2 line spacing and 18 size fonts, plus extra "question" pages that tend to repeat the whole chapter in a cut and paste fastion.
Rather just buy / download Dive into Python and tinker around with motherboards for the heck of it.
As for the "there is a whole lot to learn" thing, how difficult is it to type up a google/wikipedia search or to follow howto's?
Stop learning and start living.
wouldn't just assume that PC == windows OS.
OSGGFG - Open Source Gamers Guide to Free Games
And I bet he built it himself...
If a computer malfunctions, simply inspect its source code to diagnose and correct the problem.
You're an idiot. Which part of the paragraph I qioted from your f-in link didn't you understand? Why didn't you ever bother learning to read comprehensively? You know, the little bit about a one-sentence tag line at the beginning of an article never being the whole truth?
And why are you using wikipedia as a definitive resource? Really, you need to get a clue.
"Trolls they were, but filled with the evil will of their master: a fell race..." -- J.R.R. Tolkien on Olog-hai
I have both certs. Those certs are all about rote memorization of hardware specs, and network protocols, and the like.
For example, which processors will fit into a Socket-7? Which level of the OSI model relates to routing? Which cables are rated for 1gbs data transfers?
Arguably good stuff to know, but not very useful when faced with a difficult trouble-shooting problem. Something like "Teach Yourself Network trouble-shooting" might be better.
I use debian myself.
But, I get sick and tired of zealots taking every opportunity to promote linux.
Okay, we get it, you use linux. We are all so proud of you. There, feel better now?
Back to reality, linux is not for everybody. If somebody is having problems with XP, saying "just install linux" will not make that person happy.
Thank goodness. IMHO it's at least as valuable for folks to post negative reviews of things to know what to avoid as it is to post positive reviews of things to know what to get.
jump the shark is the worst phrase.
it sounded stupid the first time.
it sounds stupid now.
"I also support a local church with a local area network of about a dozen computers, which seems to have an endemic problem with IP address conflicts. In this case, I leave the PCs on and power cycle the router."
Idly wondering how this fix can work....
If the router is serving internal IP's addresses via DHCP, power cycling shouldn't change anything since DHCP is pull-only by client request. If DHCP isn't in use, cycling the router wouldn't matter either (unless the router has some "feature" that causes it to lease an extra internal address for itself that conflicts with another IP that's in use but hasn't been excluded from the router's DHCP pool.)
Anyone?
Jim Shilliday
I recall that we covered some of the socketing stuff, but it wasn't on my final... and I didn't take N+. The point though is that knowing all this stuff helps you troubleshoot because you have some idea of how it works. (The OSI seven-layer-burrito is pretty useless, though.)
I'd suggest anyone into computers as a living or lifestyle take assembly programming, too. It gives you a much better idea of what's going on in the box.
"You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
lots of words.... where are the cliff notes for this post?
Now I can sleep at night.
Never let a lack of data get in the way of a good rant.
Not my original creation, it was given to me by my boss, a director of engineering, on hire in in '87. I coded to HTML about '94 or so. Still valid, still works :) Enjoy.
http://hypersynergy.com/home/matt/misc/start.htm
Wabi-Sabi
Matthew
WTF?
Reader's Digest doesn't seem to think so. They just paid some Big Bucks buying jumptheshark.com.