Slashdot Mirror
Diagnostic Tools for Testing 2nd Hand Machines?
tom asks: "Buying second hand computers you always run a risk. I was wondering if the slashdot readers could suggest a toolbox of (preferably small) tools that you could take along with you on one or two floppy's so you could run some diagnostics on machines you would consider buying. I'm thinking of the checkdisks, benchmark programs, soundcard checks, USB checks etc."
How about a linux or freebsd bootdisk?
c0w goes moo.
Maybe one of href=http://slashdot.org/article.pl?sid=02/08/04/0 00205&mode=nested&tid=106
Do not confuse duty with what other people expect of you; they are utterly different.Duty is a debt you owe to yourself.
The best bet that I have found with buying systems that are used, in bulk is just to go ahead and assume that they are all broke. Assume nothing is going to work right, and factor in how much it is going to cost you in time to get something working and if it is worth it. I had the luck of running up on about 20 p2 systems a year back and purchased them for 30 bucks each, assuming that everything in them was hosed and the most I could get out of them was one or 2 parts on average. I got more on most, 1/2 had failed drives was the biggest problem. Followed by hosed motherboards. All in all I got about 12 full systems out of the 20, and gave them away like candy to people I knew that needed them. Ended up keeping 3 for myself. It all ended well, but assume they are hosed and you will not end up on the short end.
Good luck,
Neck_of_the_Woods
#/usr/local/surf/glassy/overhead
ZipSlack perhaps? http://www.slackware.com
WeRelate.org - wiki-based genealogy
see subj.
This will check the compuiter memory but may take a while.
Also you could LInux on a floppy or NetBSD/FreeBSD/Linux on a cdrom and see how it detects the hardware, by looking at the outputs of dmesg, and a few other things like that.
Only 'flamers' flame!
MemTest86
This is an memory tester that boots from a floppy. I use it frequently, and it works very well - a must-have for a testing toolkit.
If you manage to get a --on floppy or --on cd distro, make sure you have a compiler and enough room to extract the linux kernel sources, and watch out for signal 11.
It's usually a goot burn test/benchmark of disk/cpu/memory.[Pruneau
I don't know about it fitting on a floppy disk, but the best thing you can bring along is in your head already. Base the price you're going to pay on what the terms of the deal are. As is, no refunds? Assume they're all broken, and price accordingly. Guaranteed working? For how long? Again, base your price mainly on the terms, not on the equipment.
After that, there are some simple things you can do to find out what you're getting, assuming they'll let you test every unit. I've written some shell scripts the I've got in an initrd with busybox that I burned to a CD that tells you if the machine can boot, and if so, what hardwhere is in it. It looks for PCI devices, SCSI disks, IDE disks, memory... Basically any info you can pull out of proc. It formats it all nicely on a single screen, so you don't need to type anything, and you spend 45 seconds at a machine max. There's no need for a full OS with apps, or a bootable distribution. I have a single floppy version as well, but it won't find every SCSI device. If you'd like a copy, send me an e-mail.
Others might quibble about testing the existing (small) hard drives, floppy drive, and CD-ROM, but I'd just count on trashing these items. They're cheap and plentiful new. Besides, if you're buying massive numbers of machines to administer in a giant cluster, you probably don't need or want any removable media on each machine.
Same goes for whatever existing motherboards might be in the machines. If they're a couple years old you'd probably have to go hunting around the net to find BIOS updates etc. to make them work with your peripherals. It's not worth the time, especially with decent new motherboards available for a half-hour's pay.
Spin-Rite checks HD's
An older Norton Utilities (mid-90's) should do the trick for other items
Micro-Scope tool kit works great for most anything you can think of
Bring along a DOS 6.22 boot disk. It contains several useful commands, including chkdsk (check disk), dir (detect incorrect RAM), command (complete machine diagnostics) and fc (fix computer). Happy hunting!
example.org - powered by Linux!
Most of the posts that I've seen so far pertain to Intel based systems, but I know I've had this question a number of times when I was looking at systems that weren't Intel based. Does anyone have suggestions concerning the rest of the hardware out there???
'And all the monkeys aren't in the zoo Every day you meet quite a few...'
hey pruneau va licher canelle
If you have the time, try running the SETI@home-client for 24h - and then install FreeBSD, make world, compile KDE3, mozilla and OpenOffice from ports.
;-)
(>6 GB disk-space needed, though)
SETI will bring the CPU to the limit. If it's overclocked and/or badly cooled or otherwise unstable, you'll see that quickly.
The rest will stress-test your IO-capabilities
If it survives all that, then it looks like you can trust the system quite a bit.
Rainer
Windows 2000 - from the guys who brought us edlin
For my record: what's a signal 11?
plain unix method: dd if= bs= of=/dev/null is nice for a simple read test. Watch for console error messages. ;-)
BTW, what I've found is that a lot of IDE drive errors result from bad cabling, not bad drives!
The CPU stab test from jv16.org is also quite nice,sadly needs windows...
*use a dozen or so known good disks ;-)
Scrounge around the "sysinfo" and "sysutil" directories. There are a bunch of old utils that do what you're looking for.
There was a german DOS utility. I can't remember the name, but I think it was simply "config" (or was it "pcconfig" or "pcinfo"?). Anyway, that utility could identify damned near anything in a PC (CPU, chipsets, memory, motherboard, etc.) and it ran some diagnostics. I tried to locate it again for this post, but I couldn't find it. If anyone knows where it went...
Method of processing duck feet
I cary a 3.5" mini cd full of diagnostics programs for winblows, because god knows you need them when dealing with windows and windows users. Here is a list of what's on the disc. First of all it's a basic MS-DOS bootable disk with all the functionality of a regular MS-DOS boot CD (fdisk, format, edit, etc) and a few utilities such as
Fresh Diagnose
VNC server and viewer
NessusWX
Fresh Diagnose is an excellent benchmark/testing utility.
VNC is for accessing remote desktops (Great for lazy people such as myself)
NessusWX is a windows interface for Nessus security scanner. A must for checking default installations of any OS.
All the extra utilites are freeware. MS-DOS is of course copyrighted.
hth
Everyone is entitled to their own opinion. It's just that yours is stupid.
I use the dnetc client (distributed.net) to tax the CPU.
Method of processing duck feet
~$ gcc explanation_of_signal11.c
gcc: Internal compiler error: program cc1 got fatal signal 11
~$ damn. maybe he/she will follow that link and understand it, then.
sh: damn.: command not found
~$ exit
logout
--TheOrangeSquid Is it any wonder things seem so awry? We swim in a sea of confusion and don't have to think to survive
~$ make understand
make: *** No rule to make target `understand'. Stop.
here's an interesting one. let's say you (or someone you know) has just bought a brand new computer. or more or less new. or at any rate you know it works.
but the blarsted thing starts all this junk up when the machine boots! everything fFrom media players, to monitor controllers, to printer and scanner watchdogs, almost certainly some schedule apps, and maybe a couple virusscanners! untold ram is just being gnashed away by a string of programs sitting in the systray!
so, i always, when i go to look at a fFriend's new computer, take autoruns fFrom www.sysinternals.com . conveniently shows every thing which is scheduled to boot fFrom anywhere in the registry or startup directory. lovely lovely app.
that, and a nice task manager (there are many available.) i like A.T.M.
My suggestion is an ancient DOS program called Troubleshooter. (ts.exe)
It fits on a floppy, boots, tells you all sorts of stuff, including checking CD-ROM drives, multimedia, video cards, convergence and purity checks for monitors in various modes, everything.
Does memory, CPU, bus tests, hard disk tests.
The only problem is that it's older than Pentium MMX, and I've never seen a newer version. It identifies a Pentium, including the speed, but not MMX. I tried it on a 500MHz Celeron, and it told me that I had a 760MHz Pentium. I tried it on a 1.5 GHz Athlon and it told me that I had a 2500MHz K6.
It's less useful for IDing machines now, but it's still great for doing hardware tests.
Fire and Meat. Yummy.