Quicktech For Windows Iso File
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 ) 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, but I was wanted something more comprehensive. So I started my research, and found a variety of packages, including,,,,, 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., by, seemed to have the most online feedback, mostly positive, but they didn't provide a demo.
Jan 10, 2013. Mini windows has been further improved, Kaspersky Rescue Disk is finally perfected and boots equally well from DVD or USB. Are referring to the URLs listed at the bottom of this file. Burn (preferably at the lowest possible speed) the iso image to a dvd, insert the dvd in a computer and boot from it.
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 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?' I've ordered a good amount of memory from [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 [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!
As far as boot floppies, memtestx86, hard drive diagnostics, etc, I would send you to [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). [memtest86] Let me send you my IProc PC-100 SDRAM DIMM. The idiots put the wrong timing values in it's SPD. I've only found one machine, ever, to work properly with that damn thing. Tyan MB's tend to lock as soon as the POST is complete. Memtest86 ran for 7 days and could not find a problem with the DIMM.
[hard drive diag floppy] I just returned two Maxtor drives that passed multiple 'extended' tests with their diag utils. BOTH have entire tracks that aren't readable -- sector mark not found.
They aren't there anymore. Fifa 2004 Pc Game Full Version Free Download. Just because it passed a limited set of tests doesn't mean it's not broken. 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 [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 [ultimatebootcd.com] (free!) contains lots of useful tools all on one CD. These include memtest, and the various hd manufacturer's tests.
[memtest86] Let me send you my IProc PC-100 SDRAM DIMM. The idiots put the wrong timing values in it's SPD. I've only found one machine, ever, to work properly with that damn thing. Tyan MB's tend to lock as soon as the POST is complete. Memtest86 ran for 7 days and could not find a problem with the DIMM. I've had similar problems with RAM speeds.
A couple of years ago, a bunch of SiS shared video/system memory motherboards on FIDS (flight information display systems) that I was administering w. I have been in the PC service and repair field for over 15 years. I've worked with PC technicians for several companies in several states, in a wide variety of industries (some of the companies provide PC technical support to customers, but others were in-house).
It is a shame that most PC technicians don't actually diagnose problems. Instead, they guess and swap, until the system happens to work, again. They don't really know what was wrong (though they probably will claim otherwise), and they certainly don't know if they fixed the problem. I've met several technicians who claim that modern microchips are less-sensitive to electrostatic discharge than obsolete microchips were, but the microchip industry says exactly the opposite. Most PC technicians take very little, if any, precaution against electrostatic discharge. They assume that if the component works, it isn't damaged, and they lack the skills and tools to find any real damage.
Instead, they simply swap out parts if something stops working. I can't entirely fault the PC troubleshooting industry, though. Electronics are too cheap, most of the time, for technicians to spend very much time troubleshooting them.
Speed is the most important asset in the PC industry. It is better to be fast than correct, whether troubleshooting systems or writing software code or technical manuals. That might be reasonable for PC technicians, but one could find the same attitude in other troubleshooting industries. I just took my car in for repairs, because I often had to push-start it.
This after a week of repairs for various problems. In that week, the mechanics never found anything wrong with my car starting, and this last trip dedicated to that problem was no different. Until the mechanics got ready to return my vehicle to me. When they tried to drive back to the parking lot, my vehicle would not start. A new starter appears to have taken care of that problem.
Doctors are the same way. It costs far too much to find the real problem, I suppose, so doctors rely on rules-of-thumb and shotgun approaches. Many diagnosis are through the process of elimination; one treatment didn't work, so they try another. Doctors probably never know exactly what is wrong with the patient, but they often get close enough for the body to heal itself, to some degree.
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. Electronics 2nd Edition Hambley Pdf Reader.
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.
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!' I worked at a small repair shop in the back of a store that sold used computers and the like. The latest version of TS(troubleshooter) that we used was 6.54. We only really used it to 'test' machines that customers brought in to sell to us, and only so we had some paperwork to show the owner The consensus in the store was that we just replace components when something wasn't working.
We had a stock of 'known good' parts, and swapped out till we discovered who wasn't playing nice. We also had a test ma. This is a great little util.
I really like the burn-in tests, and the fact that it can test the different RAM slots independently (on most mobos). Trying to figure out which stick of RAM is bad in a 4 GB system using memtest86 takes too long, and involves too many stops to replace the RAM chip. This way, I just let it run overnight and remove the faulty chip when it's done. The other tests are nice, and useful as well.
And having it all on a bootable floppy is nice, as you don't have to worry about havi. 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, [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. 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'. Swapping out can really suck as a diagnostic technique. More precisely, it can really suck if not done very thoroughly. Horror story follows. There was this little mom and pop computer shop, where I bought some stuff, and my buddy bought a whole computer, circa 1993-94.
My buddy paid $800 for 16 megs of RAM. And he paid $250 for a honking big tower case, with wheels, and hinged panels, and almost a dozen external bays.
That honking big case was a honking big mistake. He never populated those bays, and it was too bulky to carry on public transit.
Well, I had a car, and he didn't. So, when he had hardware problems he would beg me for a lift. I can't remember how many trips we made to this store. A bunch of them concerned his flaky hard drives. The fellow replaced the drive, at least once. Well, one time my buddy asked me to take his computer to this store for him.
And this time I watched the owner's diagnostic technique. The first thing he did was take the drive out of the big honking case, and put it in his test rig. He also confessed to me that he wasn't replacing the drives any more, he would just test it, and if it was okay he was telling my buddy he had replaced it.
When I got the computer back to my buddy's place, I opened it up myself. I found that one of the pins on one of the power connectors had come loose. So it was only making intermittent connection. And this was causing intermittent problems. Diagnosis through swapping out components failed here.
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 [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. I agree, somewhat.
If the diagnostic tool takes a few minutes to run, it generally is not as effective as my eyeball diagnostics of banging on the keyboard and testing out normal programs. If the diagnostic tool is focused on specific tasks -- say memory or hard drive -- and it performs an exhaustive test, it will catch things I can't. Case in point: I've found that 1/2 of my computers have had RAM defects; some right out of the box, and some toward the end of life.
Sometimes, I suspect that a specific. 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.
I agree with i)ave. I am a technician for a Tech Support firm with a diagnosis program and just like other diagnosis programs, ours does not delve deep into hardware specific queries -- it goes by what Windows sees. There are several valid reasons for this. To catalog all of the custom driver interfaces that are needed when testing out the different types of hardware out there would be an immense undertaking. Another reason being Window's device interface is more than suitable to go. Don't recode the whe. 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 [nu2.nu] for a good free solution. 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. 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.
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.com] and [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. 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). I've heard and read great things about Spinrite from Steve Gibson, for hard drive diagnostics and I have friends that swear by it. The only drawback to his current version is that it won't do a thing for NTFS partitions. That being said, he is working on Spinrite 6.0 that WILL read NTFS partitions. This new edition is due out any time now.
If you buy Spinrite 5 you get a free upgrade to 6 when it becomes available. As far as a general software based, pc diagnostic tool, I've yet to see any that actually work with any degree of certainty. SiSoft Sandra, as others have mentioned, is pretty good at letting you know what hardware is in the box. That along with some available 'known good parts' is what I do to diagnose issues. I have also found the book Upgrading and Repairing PC's to be particularly valuable and a must have in my collection. As others mentions, memtest86 and knoppix are invaluable tools.
Other tools you might be interested in; [aida32.hu] basically lists all of your devices, drivers, wmi software entries, pci devices, etc. For windows - needs an install, though. [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;-). I've taken an ailing HP Omnibook 4150 laptop to my local computer repair place where I was told (in this order): 1.
I needed a new power supply. I needed a new motherboard. They didn't really know what was wrong with it. It suffers from intermittent power failure, otherwise it runs fine. I wish I knew how to locate the trouble or if I'm just wasting my time thinking this machine can be fixed.
I'm loathe to take it to another repairman, I'm already out some $$ that got me no closer to a real solution. I hope this is an appropriate question to ask, 'cause I like that machine and would rather not junk it. Any civil advice will be vastly appreciated (including suggested URLs for diagnostic tools such as those mentioned in the original article). Btw, the repair house told me that their 'diagnostics' consisted of letting the machine run for a day or two. I paid them their bench fee and swore I'd never take another machine there again.
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.
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). 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. 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.
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. Have a Knoppix CD in your kit. The linux forensic toolkit can be of great use recovering files and finding problems.
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. That whole string of stuff you listed is almost completely software-based, while the posting asks about hardware. Besides Sandra and memtest86, you've got nothing there that would be of any use. Software problems are generally easier to solve since you can always format the disk and start over anyway. Besides, is it legal to have a Win98 boot disk without having purchased Win98?
I wouldn't think so, and this makes your $20 price tag inaccurate, especially since you're implying that you have other Windows. 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. We are an IBM shop (By state mandate) so I am a bit biased. You said manufacturer versions are model specific, but I doubt IBM's is, because they use the same PC doctor program for the last 10 years worth of laptops, workstations and x86 based Servers. It comes on a bootable floopy (or on servers a bootable partition just for it). It does full HD, floppy, CD, and memory scans. It will test the standard AT external ports (Parallel, Serial, PS/2) It runs VGA mode scans, and will test some features of the AGP port.
Admittably it won't test stuff like sound cards, or many built-ins, but I doubt any Paid program would either. To find it go to IBM support pages and start looking for Diagnostics, you will eventually find it. 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.
[memtest86.com] gives you a bootable floppy that will scan *all* RAM in a system, and turns up the most obscure memory errors. Some errors are not consistent, they only appear in transitions from one bit pattern to another, for example. Or adjacent bit cells may bias the bit in question. That's all it does, but it's good.
And it's free. One other point, systems with mismatched parts (designed for different bus speeds or timings), and overclocked systems, may generate memory errors. Since I started using memtest86, I've stopped overclocking, as every single overclocked system I've checked has shown errors under memtest86! I'm lead tech at a smallish computer shop. Over the years we've used just about everything to aid us in diagnosing hardware issues.
The ones we use most are: QuickTech Pro - This is great for testing memory, serial ports, video RAM, and just about every other problem that you can experience. In the past we've had so many problems with recieving bad RAM from our vendors that we now run the quick memory test from QuickTech on every PC before it leaves our shop.
OnTrack is simply the best when it comes to data recovery. They aren't cheap, but for a small-medium business their software is well worth the price.
We've also purchased some of the MS Office add-ins to help us recover corrupted Word/Excel documents better. This program really works, and if it can't recover something off a failing drive (or something that a user deleted by accident) then Ontrack will almost certainly be able to recover the data at their facilities (for a steep price of course). I'm not a huge fan of the guy that wrote SpinRite, but if you've got a FAT(16/32) partitioned drive that seems to be failing, this tool is great. It will recover bad sectors off most drives (not seagate), especially the ones that happen when Win9x doesn't get shut down properly due to a power surge or the like. This software is free and takes a very long time to run at its highest level. Other than these 3 programs and a few other niche utilities we generally diagnose all other problems by having known good hardware and swapping out to see if the problem still exists. It is still, without a doubt, the best way to diagnose a hardware problem other than Technician's intiuition.
I'm surprised that no one has mentioned CheckIt Diagnostics from Smith Micro Software (You will find it on their website listed under the Utilities section. CheckIt Diagnostics only costs $70.
I bought my copy at a local computer store a few years ago. What I like about it is that in the same box you get both a version that boots and runs from a single DOS boot floppy, as well as a Windows version on a CD ROM. I almost never use the Windows version because the DOS version is very comprehensive. The only complaint I have is that I can't find a way in the DOS version to make the diagnostics run 'n' number of times. Their memory test is very thorough, but I'd like to leave the whole thing running for a few days. Maybe they've corrected that in newer versions? They don't have an eval version on their web site, but maybe you can contact their sales department about getting one.
Please note that they now have a product called CheckIt86 which has nothing to do with the DOS version (e.g. 8086) but is an ad-blocker.
Have you tried using the [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.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 [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.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. I've worked as a technician for about five years, both on-site and in-house, and I really haven't found any good all-around utilities.
Most of the diganostic programs mentioned here tend to test things that hardly ever test bad in reality, such as serial and parallel ports, timer chips, address lines, etc. The best thing to have around in case of a rather obvious failure (failure to power on, blank screen, beeping) is a collection of known good parts that can be swapped in to isolate the problem. They can also be useful in cases involving more subtle or intermittent problems, such as a CD burner that fails half the time or a computer that locks up after a few hours. Heat problems can be subtle -- I remember a friend telling me that the computer he shop didn't have heat for a while during the winter because of a bad relay, so there was a case where a computer with a slow fan worked at the shop, but didn't work when the customer took it back to their warm home. Sometimes a USB device a customer installed won't work because they plugged it in before installing drivers, and now it needs to be removed from the registry and installed again.
In Windows, sometimes certain programs don't play well together, and experience will tell you what programs to avoid, and which processes in your task list don't belong. The point is, certain utilities may have their place, but no utility can replace the ability to diagnose a problem through experience and process of elimination. A memory test utility may show that you have bad memory, but experience may tell you that it's bad anyway, even when the program says it's okay.
The good news is that I believe quality is improving again, after hitting a low in the K6-2 era, when cheap motherboard production proliferated, and the problem was compounded by the large increase in cooling needed for those chips (I'll never forget PC100 mainboards (yes, that was the company name, not the memory speed)). It's also pretty cheap nowadays to have spare parts on hand for quick checks.
This will work 90% of the time: Prerequisites: (1) GHOST'ed hard drive with Windows 2000 installed, and the Sysprep utility enabled on it (4) Processors: a Socket 7, a Slot A, a Socket A, and a Socket 478 (4*2) RAM modules: a couple of 72 pin SIMM's, a couple of PC-66 SDRAM's, a couple of PC-133's, and a couple of DDR's (3) Power supplies, an AT, an ATX, and one of those new ATX'es (2) Motherboards, 1 AT, 1 ATX (2) video cards, 1 PCI and 1 AGP Step 1: Replace user's HD with your SYSprep'd one. If you can boot, Win2K will do it's hardware detection routine. If it finishes, and boots to a 2K desktop, your problem is probably software and you have to narrow down from there. If it's using Windows, boot with user's hard drive in safe mode.
If problem does not occur, disable taskbar lint under HKEY_LOCAL_MACHINE/Software/Microsoft/Windows/Cur r entVersion/Run and from user's Startup folder. If the problem re-occurs, probably virus'd / spyware'd or corrupt Windows install.
Re install Windows. If it isn't fixed, follow step 2 Step 2: If the user's machine did not go past the Win2K hardware detection routine, then the problem is hardware. Go into the PC's CMOS and reset to Setup Defaults. If that doesn't work, CMOS is OK, it's a hardware component. The list of problematic components in a typical PC, listed in desending order of probability is: • RAM • CPU • Power supply (yes, power supply) • Motherboard • Add on cards, including video Go into the CMOS, disable L2 cache on the motherboard (common problem and you don't have to swap out anything). Try Win2K detection routine. If it works, motherboard L2 cache is the problem.
If it doesn't, swap the ram. If it works, it's RAM. If it doesn't, swap the processor. If it works, it's chip.
If it doesn't, swap the PSU. If it works, it's PSU. If it doesn't, take out all add-on cards and swap the video cards. If it works, swap back each add-on card one by one until the problem re-occurs. When it re-occurs, the last card you swapped back in was the problem. Replace it, and you are good to go.
Using this technique, I can troubleshoot 90% of PC's in 15 minutes or less, 90% of the time. First of all, why are CPU's so high on the list? I have found bad CPU's to be very rare, and the few that I have seen are the completely toast, computer will not even POST kind.
Also, what's with the Windows 2000? It would probably take atleast 15 minutes for Windows 2000 to get done installing all the drivers and rebooting several times before you'd get to a desktop. And that's assuming Windows 2000 even has all the drivers for whatever hardware you are going to run accross. Here's what I.
Our company swears by it. Every machine before it goes on the bench and after it leaves goes through fully automated and comprehensive 'Burn-In' process. I'm not sure how much it costs, but its definitely up there around $400 maybe? And comes with bunch of loopback interfaces. It's pretty up to date too, last version we have has serial ATA, athlon 64 etc support I can't even count how much time we saved when after initial burn-in we realized that the memory was set to CAS 2.5 instead of 3 causing timer problems and subsequent weird application crashes. A tool like this is very important if you have many crap machines coming from the street and you dont know who worked on them before (Joe Sixpack thought that lower CAS will make his computer go faster, but his el cheapo memory modules just wont take it).
I downloaded a diagnostic (DOS) program and it tested the memory for hours without finding a single problem. Yet when I changed the SIMM the problems when away. I remember similar results with motherboard errors. The only diagnostic program that I have found that actually do anything useful are the disk checking programs I had a piece of process control equipment where the vendor kept telling me to 'run the diagnostics. Run the diagnostics'.
I actually had the diagnostics up and telling me that everythin.
List 3 - grub2 menu system (for UEFI-booting of non-UEFI ISOs) Tips • For most ISOs (except Windows Install ISOs), just copy the ISO file to the _ISO MAINMENU folder. • Try to avoid spaces and special characters in file names - use _ instead of a space. If it works, then try it with spaces. • Some files may require the file extension to be changed (if so, it will be mentioned in the list below) • Some payloads may require you to add and edit a (if so, it will be mentioned in the list below). Sample.mnu files can be found in the E2B download in the _ISO docs Sample mnu Files folder.
Look also for sample.txt files. • Generally, if it works for one version of a distro, it will work with any version of the same family/type. • Turn the SCROLL LOCK LED on before selecting the ISO file to see E2B suggestions • If a.ISO file doesn't seem to work correctly or you want to UEFI-boot from it, use the and convert it to a FAT32. • It is possible to add multiple, fully-installed linux OS's (see ) and WindowsToGo OS's (see ) • If installing from a bootable linux installation ISO, specify /dev/sdX 4 as the cdrom source device (this will be the linux ISO- e.g. mount /dev/sdb4 /cdrom or sudo mount /dev/sdb4 /mnt/cdrom), where X is the USB drive letter, e.g.
Alternatively, try converting the ISO to a.imgPTN file using MPI_FAT32 (e.g. RedHat linux installation) and no special action should be required. For Debian, you may need to use -t vfat /dev/sdX4.
• For.ISO files that boot to DOS 7 or later - use. ISODOS01 file extension - the CD/ISO contents can then be found on DOS drive B: after booting. • Some DOS programs (e.g. BIOS updates, etc.) can be copied to the E2B drive and then run using the DOS - FreeDos menu entry to boot to DOS - drive C: will be the E2B USB drive (NTFS or FAT32 supported). See also the RMPrepUSB Tutorial #33 on how to make bootable FreeDOS floppy disk images. See E2B DOS page. • For Windows PE ISOs, try.
ISOPE01 (mounts ISO as Y:) (Removable USB drives or USB HDD + WinHelper flash drive). For E2B USB HDD drives, some WinPE ISOs may need to be converted to. ImgPTN for full functionality.
• For WinBuilder PE ISOs always use the. Iso file extension - see. • For WinPE UEFI-booting, convert to FAT32.imgPTN files. • If you get a syslinux boot: prompt instead of a syslinux menu - press [TAB] key and type one of the boot options shown. • If you still having problems and it is not in this list below, search this site first and then and I will try to help. Common 'gotchas': • Make sure all files are (Windows Installer ISOs and VHDs don't need to be).
• For Win 7/8/10 Install ISOs use a removable USB drive to avoid ' CD/DVD drive driver required' error (see for workarounds). You can check what type of USB Flash drive you have (Fixed or Removable) by using RMPrepUSB. • Many Windows Install ISOs require you to specify a Product Key or you will get a 'licence' error - even Evaluation versions which do not normally require a Product Key will give an error unless you specify the correct evaluation Product Key (tip: install it using some other method (e.g. Rufus or.imgPTNfile) and use ProduKey to find out what key it used). IsoPE01 file extensions require a Removable E2B drive or a WINHELPER USB Flash drive. • If using an E2B hard disk, convert Windows Installer Vista/7/8/10 ISO files to FAT32. • Use a USB 2.0 port if the correct USB 3.0 drivers are not contained in the ISO ( and some linux ISOs may not contain correct USB controller drivers for modern chipsets).
• Keep all files within the first 137GB if using a large USB HDD (due to a common ) • You cannot UEFI-boot directly from an ISO file using grub4dos E2B menu. To UEFI-boot, use a.imgPTN or the. • Special instructions for Windows 7 64-bit UEFI booting • See for more 'gotchas' and issues. The entries in bold type below have been tested by me personally. • WINDOWS INSTALLER ISOs - Windows Server 2003, XP Home/Pro must be copied to the correct _ISO WINDOWS xxx folder. Trial product Key 4GQ7-HG48K-7YP6R-6JM4C-33FMQ. For XP ISOs that contain a $OEM$ folder, some ISOs may work (e.g.
Windows 2000 is not supported - you can however make a - test it - and then convert the flash drive to a.imgPTN image for use with E2B. For others, use to make a USB Flash drive and then use the MPI Tool Kit to make a partition image.imgPTN file from the Flash drive (say Yes to combine menu.lst files). • WINDOWS INSTALLER ISOs - Windows Vista, Windows 7, Windows 8, Server 2012, Multipoint Server, Server 2K8R2, Windows 10, Server 2016 - must be copied to the correct _ISO WINDOWS xxx folder. For Win8/8.1/10 you must specify the correct Product Key or you may get a 'license' error or some other error.
Place Windows Multipoint Server ISOs in SVR2K8R2 folder. If using a Fixed-disk type of E2B USB drive, a is also required for Vista/7/8/10 - OR - convert to a.imgPTN file using the.
For all non-standard Vista/7/8/10 ALL-IN-ONE (AIO) ISOs, monkrus ISOs, WinPE, Windows Repair and Microsoft Deployment Tool (MDT) ISOs - convert to a.imgPTN file using the (use FAT32 if possible for UEFI boot support). Special instructions for Windows 7 64-bit UEFI booting. Note: Some Windows Installer ISOs (Vista/7/8/10) that don't require a Product Key may 'just work' if you rename them with a.isope01 file extension and place them in any 'normal' payload folder - e.g. _ISO MAINMENU. You must use a Removable flash drive so that you get the LOADISO blue console window or convert them to.imgPTN files or use a 'Helper' USB Flash drive. • Windows 8/10 Recovery - copy the ' _ISO docs Sample mnu files Windows Boot_Recovery_WIM.mnu' file to _ISO MAINMENU and you should be able to boot to the Recovery.wim file on any Windows 8/10 system disk without even needing a wim file on your E2B drive or a recovery partition on the target drive! • Windows Server 2003 Installer X13-04874.img - rename to.iso (use '2K3' in filename - e.g.
Windows2K3.iso) and place in the _ISO WINDOWS XP folder and treat as if installing XP. Usually will work using the DPMS2 mass storage drivers for XP.
• Windows Server 2013 - see blog post • Windows 98 Install ISO - rename to.isoDOS01 - CD files will be on B: drive. See RMPrepUSB - see blog post. Can also make a.imgPTN file. • Windows ME Install ISO - rename to.isoDOS01 - CD files will be on B: drive. See RMPrepUSB - see blog post. Can also make a.imgPTN file. • Tablet PC 2005 (XP SP2) and Media Center Installer ISO(s) - see blog post • Windows 7 Recovery CD (also try.isoPE01) • Windows 7/8/10 PE - use.iso or.iso01 - for WinPE's that require acccess to the WinPE CD once it has booted, if a removable USB E2B drive use. Note:.isoPE/.isoPE01 requires a Removable E2B drive or a WINHELPER USB Flash drive so that the ISO is loaded as a virtual drive - if a USB HDD E2B drive, try converting to a.imgPTN file.
• Windows 7/8/10 OS WinToGo.VHD or.VHDX files - the file does not need to be contiguous and can be on another partition (v1.69+) - for instructions see blog post and for a really easy method - see. Quick instructions for CSM MBR booting: use WinToUSB to make a bootable USB WinToGo drive (using a VHD) - boot from the USB drive and complete Windows Setup - copy VHD file to E2B's _ISO WIN folder.
• WindowsXPToGo from a.VHD file, rename to.VHDBOOT - see. • - improved Hirens miniXP - download from - see blog post. • Windows 7/8/10 single-image PE3.WIM files - e.g. Win8.1PESE boot.wim file - the file does not need to be contiguous and can be on another partition (v1.69+) • WinBuilder Win7PE-based ISOs - always use E2B v1.90+ and.iso file extension - see blog and instructions • ERD Commander 2005 or 2007 or MSDaRT 5.0 ISOs, Windows Recovery ISOs - use the.isomemF01 or.isomemwinv file extension or use the ERD5_DPMS.mnu sample file. See blog post and this website page.
• MSDaRT 6.0, 6.5 7.0 8.0 8.1 - Win 7 32&64-bit - rename to.isoPE or.isoPE01 file extension. See blog post. • - Forensic WinPE - rename file extension as.iso01 and place in root of E2B drive - see blog.
• Windows For Legacy PCs (winflp) - try.isofiramem or.isowinvmem file extensions for the install ISO. OpenDiagnostics_stable.iso • Pinguy Pinguy_OS_14.04.4-1-LTS-Mini_x86-64.iso • xpud xpud-0.9.2.iso • CMRR HDDErase.iso - erase modern HDDs quickly - use.
IsoDOS01 file extension and run B: HDDErase.exe. • Lightning Linux 3.2-amd64.iso • emmabuntus-de-i386-jessie-1.01.iso • hard disk diagnostic Hutil210.iso - rename as.isoDOS01 - once booted type B: [ENTER] and then HUTIL [ENTER] and Y to agree. • (inside security rescue toolkit) INSERT-1.3.9b_en.iso • Server2003 PE ISO pcunlocker.iso • min-7 tested • OI-hipster 2016-10 LiveDVD •.