Stories
Slash Boxes
Comments

News for nerds, stuff that matters

Slashdot Log In

Log In

Create Account  |  Retrieve Password

Good, Affordable PC Diagnostic Software?

Posted by Cliff on Tue Feb 17, 2004 10:02 AM
from the thermometers-for-your-hardware dept.
RebornData asks: "I do freelance computer support for small businesses, and after running into a string of hairy hardware problems, decided to buy some generic PC diagnostic software. My searches turned up numerous vendors but very few independent or reputable reviews and comparisons, so I embarked on an evaluation of my own. What I found was an industry filled with con artists, bitter feuds, and outdated products. I'm now out $400 and am wondering whether my hope of finding useful diagnostic software was a naive dream. Has anyone found something that works for you?"

"The premise of PC diagnostics software is simple: provide an easy way to test for PC hardware problems, independent of software configuration. Some hardware vendors (like Dell) provide diagnostics with their systems, but they are usually model-specific and not even all major vendors provide them. Of course there are free utilities like the well-known memtest86, but I was wanted something more comprehensive.

So I started my research, and found a variety of packages, including PC Doctor, PC Check, Microscope, PC Certify, Tufftest Pro, among many others, ranging in price from $500 to $35. Some come with associated hardware, such as loopback connectors for parallel, serial, network or USB ports, or ISA / PCI cards that will show low-level POST codes for machines that appear completely dead.

Some of the vendors provided demos, but most were severely crippled. The cheaper software tended to be outdated and incomplete, lacking support for newer hardware features. Almost all practiced high-pressure sales tactics over the phone, and I discovered that one company was actually a spinoff of another by a disgruntled former employee, resulting in a bitter, lawsuit-ridden feud.

Microscope, by Micro 2000, seemed to have the most online feedback, mostly positive, but they didn't provide a demo. After contacting their sales, they suggested that if I bought a full copy for my evaluation, I could return it in 30 days if it didn't meet my needs. Well, it turned out to be buggy and missing important features found in other, cheaper products. When I called to return the product, the salesman disclaimed all knowledge of the promise they made, and they've refused to take it back. Some further digging found that I'm not the first person to be taken in by these tactics.

I still would like to find worthwhile PC diagnostics software, but the (a) lack of independent reviews, (b) shady industry sales tactics and (c) poor performance of a 'well regarded' package leave me wondering... am I a sucker for buying into the whole concept in the first place? Can anyone point me towards a reputable vendor, or an alternative set of independent tools that will do the same job?"

+ -
story
This discussion has been archived. No new comments can be posted.
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More
Loading... please wait.
  • Sandra (Score:5, Informative)

    by mekkab (133181) * on Tuesday February 17 2004, @10:03AM (#8304586) Homepage Journal
    SiSoft's Sandra [sisoftware.net] is good for some basic hardware info on the machine.
    It was nice finding out that the RAM I bought from Coast-to-Coast memory that I got a "deal" on was actually a step down in terms of speed (which they were selling for the "sale" price...so it all worked out).

    They have diagnosit tests, but I've only used the free version. But its a nice first-line strategy for sizing up machines.
    • Try AIDA (Score:5, Informative)

      by ziad (4839) on Tuesday February 17 2004, @10:40AM (#8304941) Homepage
      Hi, I recommend AIDA as a Sysinfo tool. Free and powerful, can even run in batch mode.
      http://www.aida32.hu/aida32.php [aida32.hu]

      Ziad
        • by dipipanone (570849) on Tuesday February 17 2004, @12:40PM (#8306249)
          Your interpretation is very different from mine. I read from this that they are no longer going to update AIDA16, but that they will continue to develop AIDA32, they just won't be providing free support for their free product -- other than on the discussion forums.

          That doesn't sound anything like being on it's last legs. It sounds like a sensible response for dealing with support for a free product.
    • Re:Sandra (Score:5, Informative)

      by Nintendork (411169) on Tuesday February 17 2004, @11:03AM (#8305180) Homepage
      I've ordered a good amount of memory from Coast to Coast [18004memory.com]. I've saved a lot of money for my friends/family/clients, especially when it comes to SODIMMs (Laptop memory) and router memory. I don't buy their memory because it's the best. I buy from them because I've only had one compatibility issue (Which was promptly resolved) and the price/performance ratio is tremendously in their favor. The relative running Windows XP on 128MB of RAM is in heaven when they get an additional stick thrown in, regardless of how fast it is. Before the upgrade they were running 1000 times slower on the pagefile!

      Going back on topic, let me share what I've learned about troubleshooting hardware issues. First, let me stress that it's usually not a hardware issue. Drivers, resource conflicts, and buggy BIOS/Firmware code is usually the issue. When it comes to "diagnostic" software for real hardware problems, there's little you can do. For memory, there's MemTest-86 [memtest86.com]. This program hasn't failed to spot bad memory for me yet. For hard drives, go to the manufacturer's web site to get a bootable diagnostic floppy. Usually the quick tests are all that's needed, but it could pay off to do the extended test if the quick one says everything's OK. Even if the extended test comes back fine, don't rule out the drive. The problem could be intermittent. For the rest of the hardware, simply swap components around until you narrow it down. Take out that video card and toss in a spare one that you've had for several years and know works. For the CPU, toss in any other CPU that matches the original's architecture (Just a different speed rating is OK). I think you get the idea on the (Swapping out) method. Also, never underestimate the crap a poor power supply unit (PSU) can throw at you! Stability issues could be coming from an unreliable current. Of course, temperature problems could also cause these same stability issues, but that's much easier to monitor. When you get to a point where you're truly stumped, some manufacturers have forums that you can go to for help. This is especially true in the homebuilt market with Abit, VIA, AMD, etc.

      Good luck and happy hunting!

      -Lucas

      • Re:Sandra (Score:5, Informative)

        by dreamt (14798) on Tuesday February 17 2004, @11:51AM (#8305728) Homepage
        As far as boot floppies, memtestx86, hard drive diagnostics, etc, I would send you to Bart's Boot Disk Creation [nu2.nu] site (the one mentioned the other day here for their Windows boot disk) and look into their "corporate boot disk" routine, especially the boot CD part of it. I heavily modified this (to allow the network and CD-rom to co-exist) and added things like hard drive diag tools from all of the major vendors (some were easier than others, some insisted on creating ISO images, so I need to mount that ISO, then extract their utils, etc). It already includes support for memtestx86, and I also added the off-line NT password editor (you can select multiple boot images, so just needed to add the linux one mentioned on other part of the site.

        It also uses some cygwin tools (dd, etc) to make it so that you can create a bootable CD by emulating the creation of a boot floppy via DD, so you can create one w/o the need for an actual floppy (I would recommend hacking it to create 2.88MB floppies rather than 1.44 MB floppies (need to search its config files to handle this)

        • Re:Sandra (Score:5, Insightful)

          by berzerke (319205) on Tuesday February 17 2004, @01:44PM (#8307074) Homepage

          I too have seen memtest fail to find bad memory, but only once so far. (I switched out memory and since then, no problems.) Also keep in mind, that due to the way it works, memtest errors could be power supply, motherboard, or CPU related in addition to memory related.

          I've also seen the hd tests fail to spot a hard drive that was bad too. I spent over a week on one of them trying to figure out why it kept having problems. Since it was in my possession, I didn't have to worry out the cleaning crew causing the problem (see this story [computerworld.com] under neat idea..)

          I've come to the conclusion that there is NO test that can say if the hardware is good, only tests that can say its bad. Between memtest and knoppix (and the hd tests), I can USUALLY spot faulty hardware quickly, but every so often..GRRRR

          BTW, I haven't seen it mentioned yet, but the ultimate boot CD [ultimatebootcd.com] (free!) contains lots of useful tools all on one CD. These include memtest, and the various hd manufacturer's tests.

    • Re:Sandra - NO GOOD (Score:5, Informative)

      by freeze128 (544774) on Tuesday February 17 2004, @11:27AM (#8305441)
      Sandra has some uses, but it, like a lot of other "hardware diagnostics" software, has a HUGE disadvantage.... It expects your operating system to be in good working order. It also expects that you have current (and appropriate) drivers installed for all your hardware. Any good technician already knows the tenet "Divide and conquer". When troubleshooting, you want to know if the problem is caused by the hardware or the software. If your software is screwed up, how can you trust the diagnostics to properly report that the HARDWARE is good?
      Likewise, anyone can write a driver bad enough to make the video tests fail, but that doesn't mean the video card is actually defective.

      Years ago, I worked at a PC manufacturer and we used QAPLUS FE. It was small enough to fit on a floppy disk, and had modules for all the independant subsystems: CPU, RAM, VIDEO, IO Ports, Timer channels, interrupts, Hard disk... You could select all the tests and let it run all night. If it failed on something, it actually gave you an idea on what might be the problem.
      I would recommend QAPLUS if they had an up-to-date version that booted from a CD and had it's own KNOWN GOOD drivers for hardware. A Plus would be some sort of modular technology that would allow you to add drivers for more hardware in the future.
  • Low Cost (Score:5, Informative)

    by derphilipp (745164) on Tuesday February 17 2004, @10:05AM (#8304596) Homepage
    A low-cost alternative is a bootable copy of Knoppix [knopper.net], escpecially usefull if equipped with a virus scanner - like
    http://www.linuxforum.com/linux_wallpapers_full/ 93.php>Knopicillin - sorry no ISO Image found - it was once in the C'T magazine [heise.de]...
    • Re:Low Cost (Score:5, Interesting)

      by etnoy (664495) on Tuesday February 17 2004, @10:11AM (#8304658) Homepage
      I totally agree. And the Gentoo [gentoo.org] LiveCDs all contain the excellent mentest86 program (type memtest on the boot command line) And also, the ISO is a lot smaller than the knoppix one (if you choose the bare-scraped one you'll just need 60 megs of downloading)
  • by watzinaneihm (627119) on Tuesday February 17 2004, @10:05AM (#8304602) Journal
    If you like dell diagnostics, then you should probably buy PCdoctor. Atleast some of the diagnostics in the earlier versions of Dell servers were sublicensed from PCdoctor. Just go into the installation folder and liik at the DLL names, or read a config file.
  • Excellent Software (Score:5, Informative)

    by r0wan (60177) <mlisaoverdrive@nospAM.gmail.com> on Tuesday February 17 2004, @10:06AM (#8304603)
    The Troubleshooter by SmartCertify direct. It comes as a bootable floppy, with a couple of dongles and a CD-ROM to test ports while in diagnostic mode. This has worked excellently for us...we were able to diagnose some odd, random computer issues as being caused by bad video RAM
    • by Evanrude (21624) <`david' `at' `fattyco.org'> on Tuesday February 17 2004, @10:37AM (#8304911) Homepage Journal
      I've used The Troubleshooter on numberous occasions and can attest to its ability to pinpoint most hardware related problems. It's a great program for anyone that does a lot of hardware maintenance.
    • by Anonymous Coward on Tuesday February 17 2004, @10:47AM (#8305013)
      I used troubleshooter for a couple years at a local hardware shop and we finally quit renewing our product license. There were just too many false-positives and missed errors. I don't know if that makes this one worse than the others, but we went back to simple by-hand replacement testing which worked quite a bit better. Of course we still used memtest86 and harddrive manufacturers' testers, those are invaluable.

      Also of note, troubleshooter comes on one floppy disk and one backup floppy disk; it cannot be duplicated by any means I could discover, even for backups. "Not that there's anything wrong with that!"
  • by pw700z (679598) on Tuesday February 17 2004, @10:06AM (#8304608)
    Nothing beats experience and a supply of 'known good' replacement parts. I have been out of the repair and troubleshooting business for years, but I always remember being frustrated at useless memory and system testing software that could not find anything wrong with memory chips, etcs, that were obviously bad. Even most hardware units (like ram testers) were almost useless. If the POST testing didn't find anything wrong, it seemed almost nothing else would either, most of the time. If you think the part is bad, swap it out with an equivalent and see if the problem goes away.

    • Agreed: Try known good parts.

      To prove to yourself that it really is fixed, use a memory tester, the hard disk manufacturer's disk diagnostics, and either a program that reboots an OS 20 seconds after it is loaded (on Windows XP, Wizmo [grc.com] from GRC.com and Sleep.exe from the resource kit) or, even better, some Linux or BSD build process that takes several hours.

      The biggest cause of failure in an old PC: Bad contacts. Just move every card and connector 2 millimeters out and in again. The rubbing of metal to metal creates fresh contact surfaces. Renewing the contacts should be the first step in fixing any PC.

      The biggest cause of real failure in a new PC: Infant failure. Components are more than 100 times more likely to fail in the first week than they are in the 100 weeks after that.
    • No kidding (Score:5, Insightful)

      by rs79 (71822) <hostmaster@open-rsc.org> on Tuesday February 17 2004, @11:21AM (#8305360) Homepage
      I used to write diagnostic software for computer companies in the early 80s. If the computer was together enough to run my software there was not that much that could be wrong with it and very little I could find.

      Keep in mind typical diagnostic sofware back then would test for things like memory not really being there (bad address or data line problem) or interrupts stuck on or not happening when they should or can't talk to the disk drive.

      None of this crap really helps is you have a bad scsi cable (ouch, that was a long drawn out pig) or a bad cable or the wrong cache controller chip (ouch) or a bad power supply or wrong speed RAM any of which will cause a system to beheva erratically and in a - and this is the bad part - non repeatable way.

      Back then almost every part was $8000, these days the answer to "how do I fix a flakey computer" is "buy a new one".
  • by HeX86 (536126) on Tuesday February 17 2004, @10:07AM (#8304618)
    And that's why... Most technicians do it by instinct and years of experience. If this peticular thing is happening, you know it could be one of x, y, or z.

    That's always worked better for me than anything else. Although it would be nice to have something tell me what's wrong :)
    • Magic Smoke (Score:5, Insightful)

      by Anonymous Coward on Tuesday February 17 2004, @10:27AM (#8304828)
      PC diagnostics are really two-part work. Part one is to fix the PC, and part two is to convince the luser that the machine is actually fixed. That's where the diagnostic software comes in handy. Run the software, show the luser the "problem", fix the PC, and show the luser that the problem is "fixed". I've found that a piece of paper in a luser's hand is worth hours and hours of post-fix re-diagnostics because "something" has changed.
  • by gtrubetskoy (734033) * on Tuesday February 17 2004, @10:07AM (#8304622) Homepage
    This is slightly OT, but I've found one of the best ways to test (as opposed diagnose) hardware is to install FreeBSD then run "make buildworld" on it... If it completes with no problems, it's a pretty good indication that the hardware is in good condition.
  • by Zog The Undeniable (632031) on Tuesday February 17 2004, @10:09AM (#8304642)
    Rather irritatingly, the free version has lots of menu icons that don't work, a bit like blanked-off switches in base model automobiles. However, it's a good tool for basic performance measurements and reassures you that your RAM/CPU etc are working at their rated speed.

    A tip: run it as Administrator or you'll get limited information out of the BIOS. And if you're using *nix, you'll have to look elsewhere.

    • by Tassach (137772) on Tuesday February 17 2004, @10:22AM (#8304778)
      Any diagnostic / troubleshooting software that requires that the computer boot into the operating system first is largely useless. It does nothing to help you fix a problem which is preventing the OS from booting.

      Generic tools like memtestX86 are a good start, but there is a limit to what you can do with generic tools. Ultimately, you need hardware-specific tests. Hardware manufactures need to do a better job of providing diagnostic tools for the things they sell. Yeah, you can test the gross functionality of any sound card by playing music, but to do a complete test you need something designed for that specific card.

  • by i)ave (716746) on Tuesday February 17 2004, @10:10AM (#8304651)
    stressing under the weight of years worth of hardware & software Bibles. If there is such a miracle as a good diagnostic program that can keep up with the daily onslaught of new hardware, protocols and standards, then I have wasted a lot of my time but wish you the best of luck on your quest.
  • memtest86 (Score:5, Informative)

    by DrMindWarp (663427) on Tuesday February 17 2004, @10:11AM (#8304660)
    The most common problems I encounter with PCs are memory related.

    The best tools for checking memory are memtest86 [memtest86.com] and the follow-up memtest86+ [memtest.org].

    Both of these are free to download and use. I usually leave them running for roughly 24hrs for a reasonable level of confidence. You should also burn-in the other major components too but memory is the best place to start.

  • by og_sh0x (520297) on Tuesday February 17 2004, @10:11AM (#8304662) Homepage
    #1 TuffTEST pro is a cheap, bootable, hardware-only diagnostic. It supports all current x86 processors. It does not work on top of DOS or Windows or anything, so it's convenient for eliminating the hardware as a problem. Works great, I use it all the time. As a side note, if you use it on Dell machines, Dell seems to have an internal loopback on the serial and parallel ports. It will report the ports are OK even if they're not. http://www.tufftest.com/ [tufftest.com]
  • ultimatebootcd (Score:5, Informative)

    by ggeezz (100957) on Tuesday February 17 2004, @10:12AM (#8304674)
    I use the ulitmatebootcd [ultimatebootcd.com]. It consolidates several good boot floppy images onto one cd, including many free hardware diagnosis programs.
  • by CodeRx (31888) on Tuesday February 17 2004, @10:12AM (#8304681)
    It is not possible to diagnose hardware by running software on it. At best you can determine if there is a hardware failure, but no software will be able to nail it down to a specific component all of the time.

    Consider a motherboard failure for instance - a failing motherboard can in effect emulate any other hardware failure - ide controller bad? Your software may blame the hard drive. Bus problems can cause memory checks to fail.

    I recommend you carry a simple bootable cdrom that loads the entire system (disk i/o, memory i/o and cpu load) and checks for errors. When a system fails these checks all it tells you is the problem is definately hardware and not a buggy driver or other software issue.

    See BartPE [nu2.nu] for a good free solution.
  • The state of PCs (Score:5, Insightful)

    by Threni (635302) on Tuesday February 17 2004, @10:12AM (#8304683)
    PC hardware is shit. Made as cheaply as possible, knocked out by the million. Nothing gets repaired - nothing is repairable. If it's broken, buy a new one.

    PC software is shit. Software is still in the dark ages. No qualifications to show who has the first clue about quality, security, extensibility etc.

    If you get any problem you can't fix in 30 mins, best to make sure you've backed up everything important (naturally you never need to ask anyone whether this is the case, because everybody always backs up their important data on a daily basis, right?), then just format or ghost the fucking disk. End of problem, and no tedious troubleshooting what happens when you try and get a LameSoft2000 graphics card working with a ShysterTronics printer.
  • F.I.R.E. (Score:5, Informative)

    by mahdi13 (660205) <icarus.lnx@gmail.com> on Tuesday February 17 2004, @10:13AM (#8304686) Homepage Journal
    Forensic and Incident Responce Environment [dmzs.com]
    FIRE is a portable bootable cdrom based distribution with the goal of providing an immediate environment to perform forensic analysis, incident response, data recovery, virus scanning and vulnerability assessment.


    Also provides necessary tools for live forensics/analysis on win32, sparc solaris and x86 linux hosts just by mounting the cdrom and using trusted static binaries available in /statbins.
  • diag software (Score:4, Insightful)

    by Steevee (75886) on Tuesday February 17 2004, @10:14AM (#8304703)
    ...the best software i've ever encountered was inside my skull....
  • by Anonymous Coward on Tuesday February 17 2004, @10:14AM (#8304704)
    I have yet to find diagnostic software that is more reliable than my own expereince/instincts. I haven't really done an exhaustive search, but the handful that I have used tend not to work well (and take...too...long...).

    Most OEM's are fairly accomodating if you describe problems in a decent amount of detail (and the machine is under warranty).

    If these are white boxes, you're probably better off keeping a pile of spare parts around. A quick swap can get a machine up and running quickly.

    Good Luck!

  • Aida32 (Score:5, Interesting)

    by lawpoop (604919) on Tuesday February 17 2004, @10:16AM (#8304716) Homepage Journal
    Aida32 [aida32.hu] is a great windows-based system information application. It's wonderfully complete --- I've used it countless times to find drivers for those 'unknown devices' (modems, sound cards, network cards) that windows can't recognize, and that I didn't want to take out of the machine. However, it doesn't really do diagnostics, such as checking memory or serial ports.

    Free for personal use, businesses must register. Well worth it.

  • SpinRite and Memtest (Score:5, Informative)

    by resonance (106398) on Tuesday February 17 2004, @10:18AM (#8304741) Homepage
    The only effective hardware tests I've used in the ten years I've been supporting all kinds of hardware and software have been SpinRite [spinrite.com] and Memtest86 [memtest86.com]. Between these two, I can check for the most insidious and hard-to-detect hardware problems; i.e. flakey hard drives and RAM. A cheap $20 POST card is highly useful for dead machines. You don't need all the extra features the Microscope card gives you unless you are designing motherboards or doing some other such serious work. No software will replace your own experience and ability to know where a problem is forming based on the specific failure of the machine. All the rest of the so-called diagnostic software is more or less useless from a practical perspective, aside from testing serial ports with loopback plugs and printing cute certification reports for anal customers. This is detective work. You have to suss out the exact problem based on clues left by the failure of the system. Learn how the hardware works, and it's easier than you think.
  • Flawed Concept. (Score:5, Insightful)

    by Sentosus (751729) on Tuesday February 17 2004, @10:18AM (#8304749)
    I have tried to find this, but the problem with getting flawed hardware to run software to detect it is flawed is just that in concept.

    First of all, if it is an issue with hardware, the machine may not boot at all. If it is a ram issue, the diagnostic software may generate errors.

    Second, even if it highlights an error in a configuration, it could be generated with the analysis software.

    Third is that failed hardware often will not register as failed unless it is operating. Such as, a failed modem will not become noticable until it is used and then it may lock the computer up which could stop the software diagnosing the issue.

    Your best bet is to use a cause and effect analysis. Then trial and error. The machine won't boot, find every possible cause of it not booting and eliminate each one as a possible cause. Continue on this until the issue is completely solved. Make a checklist for yourself so you don't forget anything.

    It is how I do freelance repairs and it has proven bulletproof compared to the Voodoo Computer Repair Experts that try random things in the hope that it fixes the issue. (Install drivers, reinstall OS, Check CPU)
  • Some products (Score:5, Informative)

    by wfberg (24378) on Tuesday February 17 2004, @10:21AM (#8304770)
    As others mentions, memtest86 and knoppix are invaluable tools.

    Other tools you might be interested in;
    Aida32 [aida32.hu] basically lists all of your devices, drivers, wmi software entries, pci devices, etc. for windows - needs an install, though.

    OnTrack [ontrack.com] sell Easy Recovery Professional; the "file repair" options are pretty crappy, but for serious, near-forensic recovery on fscked up filesystems, ERP is a fine tool. Some of OnTrack's software (i.e. SMART tests, usually) may be licensed by the manufacturer of your harddrive, so check those pages out.

    SiSoft Sandra is recommended a lot, but I don't find it offers a lot of diagnostics, though it is prone to crashing.

    On windows, you might want to check out the Event Viewer, hidden in the Computer Management section of the (classic) Control Panel -- it will list all sorts of errors and notifications, kind of like /var/log/messages ;-)
  • by fudgefactor7 (581449) on Tuesday February 17 2004, @10:23AM (#8304783)
    A great, free, Windows program is AIDA32 [aida32.hu]. It gives lots of valuable info. It's not perfect, but it's constantly in development and improvement. Up until about a week ago there was a DOS/16-bit version available, but due to lack of demand it was discontinued (sadly). Another ok program is PC-Config [holin.com], which is no longer being worked on, but it's pretty good. And NSSI [navsoft.cz] is really pretty nice as well.

    Check those out.
  • My advice (Score:5, Insightful)

    by dasunt (249686) on Tuesday February 17 2004, @10:23AM (#8304788)

    Knoppix - verify the part under another OS.

    Tomsrtbt - I forget if Knoppix has badblocks or not. If it doesn't, Tomsrtbt does.

    memtest86 - Memory tester.

    Spare HDD - good for having a clean install of windows to check things on.

    Spare low-density memory.

    Spare older computer for testing daughtercards.

    That's about it.

    Of course, sooner or later you *will* get the machine from hell with an intermediate fault that ends up locking windows for no damn good reason every so often. Then life will suck. But that's why they call it work.

  • by Lehk228 (705449) on Tuesday February 17 2004, @10:23AM (#8304791) Journal
    If you pay with a credit card and the vendor tries to screw you over you can contest the billing and return the unsatisfactory product, In fact I am in the process of cancelling an order i placed for Serif's Photoplus 7 because the site selling it never mentioned that it was old and shitty, but they were perfectly happy to tell me how bad it was when they called me asking if i wanted to pay $50-$90 to upgrade to version 8 or 9... obviously contesting the charge is a last resort but overall I feel much more confident buying software online because i know that i am not out the money untill i actually pay the credit card bill (for internet purchases there is no signature)
  • All those tools suck (Score:5, Informative)

    by foo fighter (151863) on Tuesday February 17 2004, @10:24AM (#8304792) Homepage
    I was a PC repairman for many years. I say from experience that all those software diagnostics suck.

    Microscope from Micro2000 is actually the best of the bunch, but that's not saying much. If your computer won't even post, non of these tools will do you any good. (They do have some good training materials for those wanting an A+ or N+ COMPTIA cert.)

    The PCI cards that display diagnostic codes are better than the software in those cases. They still aren't very helpful though. Basically they will tell you there is a problem with the memory, or the parallel port, etc., but they won't tell you exactly what's wrong so they aren't of much use either.

    Here's my advice:
    1. Get the power supply tester from PC Power & Cooling. It's $20, and in my experience most of the time the reason a computer won't even post is because the cheapass power supply that came with the case died.
    2. Carry a bunch of known good parts: an AGP and a PCI video card you know work, a PCI network card and PCI modem, some known good RAM (PC 100 and DDR), and a good hard drive. Ideally, these are all in a fully working computer you've brought to the site so you can swap between the working computer and the not-working computer and narrow down the problem. Resist the temptation to fix the system with your known good parts; make them buy new, name-brand components with a warranty.
    3. Bring a USB keyboard and mouse. I've seen lots of 3+ year old computers have their PS/2 connections short out or stop working but their USB ports are just fine. They can solve input problems.
    4. Have a Knoppix CD in your kit. The linux forensic toolkit can be of great use recovering files and finding problems.
  • by IWantMoreSpamPlease (571972) on Tuesday February 17 2004, @10:24AM (#8304796) Homepage Journal
    That the free stuff is just as good (if not better) than high-priced diag software.

    Allow me to give you some background:

    I have done IT work for 4.5 years. I work with Novell, RedHat, all (disgusting) flavours of Windows, BeOS, Sun, SGI, Apple (Mac) and QNX. I support everyone from Joe Grandma to major Universities and Medical Colleges.

    I have several CDs worth of useful tools at my disposal, all of them free:

    Ad-Aware: I consider this to be my single best resource in the fight against Windows NT (and up) flakery.

    www.trendmicro.com does an on-line virus scan. Not perfect, but usually finds the major ones.

    Demos of Anti-Trojan. Again, good enough for the closing of trojan ports left open.

    AVG Anti-Virus software. Good, free AV software, if Norton isn't available.

    Winzip: Obviously a good thing, many many drivers come zipped.

    A CD full of the most common NIC drivers from the biggest vendors.

    nVidia and ATI drivers.
    Via drivers

    All the latest browsers on another CD.

    MemTestx86 (as you have found): Allow me one point further int he favor of it, major memory makers will accept their RAM bad, no questions asked (in my experience) if you tell them it was checked and found bad, via MemTextx86.

    SiSoft Sandra, if for nothing else than the CPU-Burn wizard. If the CPU is bad, Sandra will find out.

    Emergency Boot disks and cd-rom access disks (sadly, the Win98 boot disk is pretty handy)

    A live Linux and live BeOS CD (very handy for recovering data of hosed systems)

    And last, but not least, a good Google search. Another thing that has saved my skin time and again is to input exact error messages and see what Google turns up.

    This whole cd-wallet has set me back perhaps $20, and does far more than "professional" diag tools can hope to accomplish.
  • by jandrese (485) * <kensama@vt.edu> on Tuesday February 17 2004, @10:28AM (#8304836) Homepage Journal
    In my experiance, the best hardware for diagnosing PC hardware problems is another PC that you know works. Quite frankly, the built in diagnostic capabilities of PC hardware is extremely poor, the only reliable way to discover if a part if bad is to replace it with a known good part and see if that fixes the problem. Don't blindly trust new or especially refurbished parts either, they need to be tested and known good. With experiance you will know what parts to try first, but it is still important to verify that replacing the failed component with a new part fixes the problem.

    I remember back at school where the tech support guys were ripping their hair out because a lot of the school issued PCs were coming back with random crashing problems. (I had a roommate who's machine would crash everytime the screensaver kicked in). They were replacing parts left and right and it never seemed to fix the problem. My roommate had everything replaced except the case at one part, and it still crashed on a vanilla Win3.1 install. It took them awhile to realize that most of the machines had bad memory, and the vendor supplied replacement memory for the systems was usually bad as well. I eventually loaned my roommate my memory sticks, and when his system didn't crash he went back to the PC guys and told them exactly what the problem was and made them continue swapping in RAM sticks until they finally found one that worked (apparently the RAM was OK in their hardware RAM tester, but failed once it was actually put in PCs. They suspected the same thing was happening at the vendors end. They would get bad memory, test it and not discover a problem, then ship it right back to the school.
  • by amightywind (691887) on Tuesday February 17 2004, @10:38AM (#8304924) Journal
    Has anyone found something that works for you?

    I have found variations of the Hopi rain dance to be effective in solving many PC hardware problems. Tibetan chanting also work well.

    • by liquidsin (398151) on Tuesday February 17 2004, @01:21PM (#8306787) Homepage
      A friend's (now ex) girlfriend had an issue with her computer a few years back. She'd had somebody try to fix some problem, which he fixed, but in the process managed to make the cd-rom and soundcard unuseable. So he and I set about trying to make everything work. A few hours in, we decided our brains needed a break, so we went swimming. Laying in the sun made us thirsty and lazy, so we started doing shots of tequila. Hours later, we drunkenly went back to work and decided wicca was the only solution. When we sobered up we had ashtrays full of burnt down incense sticks, candles melted into puddles in a circle around us, and a computer with a fully functional cd-rom and soundcard - and no fucking clue how it got that way.

  • Ultimate Boot CD (Score:5, Informative)

    by Anonymous Coward on Tuesday February 17 2004, @10:50AM (#8305054)
    www.ultimatebootcd.com

    Free and includes loads of software. .::Dread
  • by rneches (160120) on Tuesday February 17 2004, @12:15PM (#8305977) Homepage
    Have you tried using the Linux Test Project [sourceforge.net]? I administer a cluster of Linux machines, and use LTP as a pretty comprehensive test framework. Many of the tests are software related, but you can shut those off if they're not useful to you.

    I suggest you make a Knoppix [knoppix.org] CD with LTP installed. With a little configuration, that will take care of all of all your tests for the memory, disk, IO, and CPU. You might want to install America's Army [americasarmy.com] or something to test the video subsystem.

    If you put a little effort into it, you'll have a test suite as good as, and likely better than, anything you could pay money for. If you want to buy something, you can make a donation to the LTP and Knoppix projects.

    There are also simpler tools, like Memtest86 [memtest86.com]. I find this tool to be invaluable when I try to salvage old hardwar. I can't begin to tell you how much time it's saved me that I would have spent aimlessly swapping components around.

    • Re:to start you off (Score:4, Interesting)

      by mkettler (6309) on Tuesday February 17 2004, @10:11AM (#8304657)
      Memtest is a great tool, however it is specificaly mentioned in the article itself.

      If you read the article, RebornData is looking for something more comprehensive than memtest offers. (ie: more than just a memory test. I assume to include disk, bios, video, cpu information, and a variety of other system tests and checks.)

      I myself question the need for much more than a disk-surface-scan tool and a copy of memtest, but it's what RebornData is looking for.
    • WHat?! (Score:5, Informative)

      by Orien (720204) on Tuesday February 17 2004, @11:34AM (#8305535)
      I sure hope you are trying to troll, because I just don't get that at all.

      If you come to a computer that needs work and you boot into a Knoppix CD you get...a desktop. On the other hand if you boot on to something like the ultimate boot cd [ultimatebootcd.com] you get a nice menu broken down by category of things like "File system utilities", "Memory Tests", and "Hard drive cloning". I just don't see how Knoppix can compare to that. I'm willing to listen though, if you care to explain what makes it so great for this.