MINDPRIDE Computer Services

Home | About Us | Our Services | Contact Information | Tutorials, Articles & Dictionaries | Site Map



About Us



Virus Alerts




Refer A Friend

Site Map



Privacy Policy







From: Robert P Mulhearn, Jr


Use Steve Gibson's spinrite on a quarterly basis to keep track of HD condition and recover bad drives as long as they are recognized by OS.


From: Kevin Flateau


First of all, is the drive alive?

When you turn on the machine shortly after a quick ticking noise (watch the memory count on the screen), then you'll hear the floppy do a quick click and the light on the front will go on, then you'll hear some short clicking from the hard drive and its name will appear on the screen. If you don't hear anything and the period after the floppy and before the notification of hard disk failure is more than 20-30 seconds, then your drive has most likely run out of gas. If it did make a noise (hum type) odds are the drive is still alive so let's try to wake it up.


This is my methodology for firing that sucker up to breathing again.

1. Identify the drive and its parameters. You'll probably need to take it out of the case. On the outside is a label with a model number, cylinders, heads, sectors, and landing zone (usually not necessary). The model number may be necessary to seek out the parameters of the drive if they are not readily available. The PC Pocket reference manual has an extensive list of older drives. Newer drives are labeled with specs.

2. With the parameters in hand, boot the machine and enter the bios. Go to the Drive 0 settings and enter the cylinders, heads, and sectors in there appropriate areas.

3. Hit escape, F10, and answer "Y" to the “Save?” question.


From: Shadow



You get a call from a user at work, a consulting client, or a neighbor who's found out you're "a computer person." (Sometimes they all call on the same day, don't they?)


Maybe you're lucky. When you get there, the machine boots just fine. The user says, "That computer doesn't like me." You tell the user to back up important files while the system is running because you're going to order a new hard drive so this doesn't happen again.


But then there are the times you aren't lucky. You get messages like "disk 0 error" and "invalid drive specification." I recently got those errors trying to revive the hard drive of a Compaq Prolinea 4/66.


It doesn't matter what the box is, though.


The circumstances are all too familiar:

The data isn't backed up.

The problem came out of nowhere.

The user had accessed Setup and tried to manually enter the settings for the drive type when "Auto" didn't work.

There was no startup disk made by this machine.

Reviving a drive like this one—even if only long enough to copy its data before you put it in File 13—is a tough challenge. How would you approach it?




Before going on-site I would be sure to have my various boot disks available (DOS6.22, Win9x, WinNT and AntiVirus) containing the usual disk and file utilities, a spare hard drive and a small hammer.


When I arrive on-site, I would first reset the CMOS settings to factory default. There can sometimes be corruption of the CMOS and can cause drives to seem to have "failed". Then I would go over the CMOS settings and make the appropriate changes for that particular system, including setting the primary HD to AUTO. If this fails, then I would boot to floppy and determine if FDISK can see the drive. If not, then it’s time to open the case. With the PC turned off, I would first check the drive cables to verify a solid connection to both power and data cables,and install my spare drive (to save data with). With the case still open, I would power-on the machine and listen carefully for the drive to spin up. If I cannot hear the drive spinning up, then I would remove the drive (with power off of course). Then with the drive in my hand and still connected, I would power up the PC again, feeling for the centrifugal force the drive would create from the spinning platters. If there is no torsion effect felt, then this would mean that the platters are not spinning and that the heads may be '”stuck.”


This is where the hammer comes in. Power up the PC again and LIGHTLY tap the drive case edge once or twice with the hammer handle. This will usually unstick the heads from the platter and allow me to copy the data (or whole drive depending on the situation) to the spare drive for safekeeping until the user can purchase a new drive.


If this also fails, then once again the hammer comes into play...this time to allow the user to beat the crap out of the old drive and relieve the frustration of having lost everything because they thought "backups are for sissies."


From: Carla Maslakowski


Boot PC into setup and restore drive settings. CMOS battery must be dead which is why setup lost settings. Replace CMOS battery in this PC and drive should keep settings.



From: Todd Layland


Pull the jumper on the motherboard that will reset the settings (bios, password, etc.) of the system. If it boots, you know it was a config setting that screwed up. If it doesn't, well HD are cheap.


From: Dale


First things...first:

·         I would flush CMOS and then look at the drive and write down the correct drive settings for Cylinder, Heads, and Sector.

·         I would manually enter this data if auto detect could not figure it out.

·         If unable to boot after manually setting up the drive, I would check settings in CMOS and then boot from a floppy (THAT I WOULD HAVE BROUGHT WITH ME!) that contained sys.com, fdisk.exe.

·         After a successful boot to a floppy, I would do an FDISK/MBR and then reboot the system and let it fallback to a backup MBR.

·         If that failed, I would boot to a floppy and do a sys c: then reboot.

·         If unable to access the drive after the mentioned steps, I would boot from floppy, change to C: and attempt to recover as much as possible to floppies.


From: Ken Beckett


I would take the drive out of the PC it is in and take it to another PC put on the secondary IDE. I would look up the drive parameters and enter those parameters in the bios. Start the PC and hope to get the drive to run as a secondary drive.


From: NetMarkC


I've lost my "C: drive before and was able to get it back by removing and reinstalling the CMOS battery.


From: dmo


Find out from user which OS he was running on the hard drive. Install a new drive as Primary and the damaged drive as secondary. Install the same OS on the Primary drive and you should be able to see all or most of the data on the second drive. Copy all data from secondary to the Primary drive.


From: David Knapp


Oops, didn't read the question close enough. In order to revive a hard drive that won't boot, I do the following.

·         Boot to floppy that has the basics on it—fdisk, edit, sys, format, command.com. Fdisk to see if the drive is being recognized by the system.

·         If the drive shows up and has a valid partition, then try to access it from dos.

·         If you can't access it from dos, I would basically give up, but you can try to sys it too. Depends on the problem.


From: DKauschjr


·         I would first go into the bios and attempt to redetect the hard drive.

·         If I was unable to get the bios to detect it, I would then go to the drive manufacturer’s Web site and get the manual settings for the drive.

·         Next I would get a boot disk from another machine nearby and do a format /s on the drive to bring the operating system back up.

·         After fixing the machine, I would then lock the bios and then proceed to flog the user with rubber bands and paper clips for even looking at that enter setup option.


From: David Knapp


We have about 4 standard ghost images that we base most of our machines (Dell) on. We have a boot disk that has NetWare drivers for all the network cards we use. We boot the floppy, login, and re-image the machine once the new HD has arrived. Then we configure networking, printers, capture batch file, and install custom software. If they want their data backed up, then they should keep it on a server.


From: LByer1


Reboot the machine hitting delete key entering into the cmos setup.


Then click on the restore default values to allow hard disk to reboot by itself again.


From: Chris Draper


When you support any number of users, hard drive failures are an unfortunate fact of life. I have had users cry in front of me when I have had to tell them that all of their data has gone to "data heaven.” Recovering data from corrupt or failed drives is more of an art that a science.

·         Far and above, the best thing to try first is the old FDISK /MBR command.

·         This will rebuild the master boot record. Although not always successful, it has recovered many drives that were not at all readable. However, drives that have experienced head crashes refuse to spin up and need much more attention.

·         In these cases, method is critical. Set up the machine with a second hard drive.

·         Boot to dos and try to copy the data off the drive using XCOPY. This way if you do run into bad sectors or a crashed head you can simply stop the copy by hitting [Ctrl]C.

·         I have even been able to get some drives to spin up by "gently" tapping on them with a screwdriver while they were powered up.

·         Please keep in mind that this is a last resort technique.

·         I have even frozen a few drives to less than 40 degrees below zero. This will sometimes allow them to spin for long enough to get some data from the drive.


From: Avraham Schkloven


Firstly, I check all my cables (data, electric). Is the disk spinning does it make those little noses at startup? If NOT, I try a little tap with the back of a screwdriver. If it comes to life and boots, I make backups and replace the disk. If not, well all disks die—it’s just a matter of when.


If the disk is spinning at startup:


Be aware that many older viruses effect the boot sector and fats of hard drives and give errors "invalid drive specification." a good DOS antivirus should be used.


Then I try to reset the setup to the proper numbers and boot from a floppy disk with the proper operating system. On this disk is FDISK. I personally use a program call RESQDISK from Invircible Anti Virus. It has saved my skin many times in rebuilding the boot sector and fats (one could try the FDISK /MBR command).


Norton DISK EDITOR for DOS fits on a floppy and once you boot from a floppy you use it to dump the content of the C drive off to another drive.


If available I use a new hard drive. Making the bad drive the slave and the new drive master and try dumping the disk. This works only after access has been restored.


Unfortunately, some patients do not survive.


From: KrisMHorn


At times, the hard drive has lost its Master Boot Record (MBR). Sometimes it will work to type fdisk/mbr at the dos prompt (usually from a system  bootable floppy).


Other times, you may want to use the old handy command, SYS a: c: (Re-creating the system files on the C drive).


Usually, if these don't work, your drive can be sent to a data recovery center (if the data is just so critical that they can't live without it.) Usually, this costs hundreds of dollars.... And you would still have to replace the hard drive in order to obtain the data back from the recovery center.


From: Denford L. Owens


I use DrivePro by ForeFront Direct. It analyzes problem areas, can find and repair MBRs as well as repair them.


From: David Crocker


·         I always start by booting from a floppy and seeing if I can access data on the failed hard drive.

·         If you can, I then do a sys.com to c: and reboot.

·         Once you are back to a c prompt, back up all the crucial data and start over by installing a new hard drive.

·         Since this does not always work, more drastic measures have to be taken. I use several different utilities that may be useful.

·         If dealing with a windows operating system, I first try scandisk. Obviously if you cannot see the c: prompt, then this does not work.

·         I would use Norton’s Disk Doctor first, then would try using Spindoctor.

·         I only use this program as a last resort because I have lost the drive in some rare instances.

·         Your data is usually still on the failed drive, the problem is the boot sector.

·         If these programs do not work to restore the boot sector then, I would try and use Drivecopy to get the data to a good drive and start from there.

·         As we all know sometimes all your best efforts are in vain.

Good luck with your test drive.


From: FS296


If the drive just does not boot to C and it appear that it is spinning and responds to C prompt commands, I would slave it to another drive and drop and drag files to safe location, i.e. external hard drive, Zip drive.


From: Norton Seron


1. Disconnect CD-ROM drive and/or 2nd HDD.

2. Remove HDD and read label regarding "jumper" position for master (without slave) if necessary.

3. Check power cable plugged into HDD properly.

4. Check data cable plugged in properly on HDD and Motherboard.

5. Reboot PC and verify that problem is still present.

6. Replace HDD data cable.

7. Change power lead for another lead (test for voltage with multimeter).

8. See 5.

9. Connect different HDD to PC and see if bios can pick it up.

10. See 5.

11. Check CMOS chip is plugged in firmly.

12. If any of the above result in function, then boot onto system floppy and "fdisk/mbr" to fix master boot record and then fdisk to check partition, followed by DOS scandisk and surface scan to check for bad sectors on HDD. If bad sectors are found, then back up needed data and replace and reinstall HDD and OS and APPS.


From: Gilbert Betancourt


Here’s one solution I am using out in the field. I see many brands out there. The most popular in my area are Quantum Big foot, Western Digital, and Seagate .


I carry about 2 logic boards of each brand (popular in my area) and when I see init problems not relating to crashed heads, or burnt motors…


I just replace the board and backup the data for the customer. In many occasions, I sell them the logic board by itself… send board back to factory to get exchanged for a reasonable price....


Out of all my customer hard drive problems, 70 percent are taken care of this way.


Hope this might get some techs out there thinking about implementing something similar.


From: Dave Rutherford


You need to first figure what is not (or is) happening. If the drives are just not spinning, you might be in luck. Otherwise, you had better be carrying the 'toolkit' (mostly software these days).


Drives not spinning? Open the box, and check the cards and cables. Does the floppy ”seek.” If it should and should not, check the power +12v is required mostly for motors...


Nothing loose, then pull and reseat everything—esp. the memory. Watch it, make sure you are grounded... you left the system plugged in right? No plug, no ground.


Still nothing? Here’s one Seagate tech support told me in the early 80's… it still works like a charm. Pull the hard disk from the chassis and plug the power and data back in. Then holding the drive in the left, with the CABLE end towards you, BUMP IT with the HEEL of your right hand. ONCE medium hard (this will unseat magnetics, release brake mechanisms, and even pull heads stuck in soft platter coatings.... I've looked).


Still no go, try one more bump WHEN you first turn the power on.… Sometimes stuck heads need the motor to move before they will spin.


LAST ATTEMPT to spin, pull the cover (This will not destroy data recovery service offerings. Just make sure nobody smokes around you and it’s fairly clean.) off the drive. CAREFULLY with power on, push the platter to spin it.


Finally, do you have another drive same model? You can swap logic boards...just don’t leave it that way. The read/write electronics are balanced to the heads inside the drive. This MAY work if you have a bad motor chip, etc.


Now you can send the drive to the service for data recovery and the big bill.


IF IT’S NOT A SPIN PROBLEM, use a drive id software (many available) to check how the drive SAYS it’s set... even though the bios does not get this report does not mean the drive is dead to this question...! No answer, you can use some software (like Disk Mangler–—commercial) to rewrite track 0. THIS IS dangerous, so know what you are doing. I practiced on bad drives that I had first.


Other things not quite right, swap the PLACEMENT of RAM in the system... surprised? Shouldn’t be. Ram is used for just about anything, right from the start. Check the POWER. Use a good meter.


From: David C. Projansky


With all troubleshooting, you have to have a logical approach and be able to eliminate problems. When I get a call from end users that a hard drive has failed I first ask several questions that will help determine the course of my actions.

1. I first ask what were they doing before the failure, i.e. did the PC perform and illegal operation in an application and have to be rebooted? Did the user just turn the PC on and nothing would happen? Is the hard drive making any kind of unusual sounds?

2. I've found most supposed hard drive failures are really operating system problems, and can easily be repaired without taking the case apart. I usually like to turn the PC and pay close attention to any error messages that come up. Since I always have a Win95 boot disk with me, I usually boot to DOS so I can at least attempt to recover any data by copying data files onto floppy disks.

3. Then I usually reinstall Win95. In worst cases, I have to fdisk the hard drive a reinstall the OS and all applications.

4. On the other hand, I've had disk drive fail because of bad cables (a good indication of this is if the BIOS can't detect the hard drive), power supply problems, and bad power cables.


It's important to work logically and try to eliminate the easy stuff before you have to replace a hard drive.


From: Steve Schoenecker


After questioning the user to eliminate the upgrade/jumper issues or other changes such as playing with encryption/privacy utilities, etc.


·         I'd boot from a clean floppy (watch closely for indication of an overlay program which might say "to boot from a floppy, hold the spacebar down." This can really eat your lunch!) and then run a dos-based virus scanner such as FPROT or something like that just to be sure.

If the drive is not detected or can’t be accessed at all:

·         Look inside and see if the drive configuration specs are on the drive or look them up... make sure power is connected securely data cable etc. Make sure drive is spinning up, verify cmos settings for HD type, and boot order, etc. Visually verify which devices are on which IDE channel etc.

·         If I fix the cmos settings, then the system boots okay but not after being turned off...suspect cmos battery...drive is probably okay–good idea to backup important stuff at this point anyway!

·         If I cant get to c: drive, I'd probably run fdisk and look at the drive information to see if it thinks that the drive had partitions defined, how many, what size etc. I've seen the fdisk table scrambled mess because of a virus... I have fixed this problem a couple of times... OS2 fdisk utility can help here sometimes... (more of a last resort) best to get important data (if I get it running) and then start over with fdisk/format/reinstall....

·         I think I would isolate it on the bus and set the cmos and jumper settings accordingly just in case the other device is disrupting everything

·         At some point I would probably replace the drive with a drive known to work normally, and run it to eliminate other system, problems cable problems, etc.

·         If another drive works but not this one, and I still cant access the drive at all....punt.

·         If critical, consider sending to a data recovery specialist.

If drive is detected but won’t boot:

·         Start the system and watch to see how far it gets. If possible boot to c:\ prompt.. if not, boot from floppy.

·         If I can access the stuff on the drive, I'd back up. If drive is accessible but won’t boot, I'd check the version of OS then sys the c: drive with an appropriate boot disk. If this doesn't work, maybe fdisk /mbr will help.

·         If the OS dies while loading drivers etc.. look there...


Hope I haven't forgotten anything obvious... each one is different and I usually win! I have a couple of dead drives in a box... I'd love to hear some new tricks to try on them!




Order a new identical drive and swap the controllers.


From: hotmail


Unfortunate the box does matter!

1) Open the box and check for HD's model; go to manufacturer’s Web page; find out the details (Heads, Cylinders, sectors per track) and use those at setup, configuring manually the HD's params; download specific software (EZdrive, etc.) for the HD's model.

2) Check for OS the user is running.

3) If OS is MS-based (excluding NT), then get a boot disk under Win95b/98; start the machine and use the program you've downloaded or if the HD is old, try to use NDD (only if OS is MSDOS or Win95 do not try to use it if there is a possibility to have VFAT32 installed).

4) Usually most of us do carry with them some startup diskettes with an antivirus, so USE IT FOR BOOT (I myself use an emergency Boot Disk made with the help of McAfee AntiVirus since it's very usual to run up to a virus).

5) If all the above are pretty hard to do, then try to install the new HD, and OS; connect the old HD as a secondary master (or primary slave if that's easier) and start the computer booting from new HD and try to access the old one.

6) If the old one is inaccessible then be sure that the drive was installed through BIOS without using any overlay driver to expand BIOS's addressable HD capacity; If there was, try to get from Web the latest update of that driver and install it temporarily (Use a boot diskette rather then installing at Primary Master's Boot Sector) and boot from that diskette.

7) Hopefully you've been able to access HD. If not there may be some tools in the manufacturer's soft you've downloaded; otherwise ... try to stay calm!!! and proceed with some Web searching. There are some good tools to access the partition and try to fix it manually (If you Dare) using a disk editor to repair boot partition. Well it 's much more complicated sometimes but you may try it at your own risk. Or you may just say " Hmmmm..... Told you so... Sorry there is no way out... you should keep backups!" (an easy solution :->)


From: Doug Wood


I have found that if you cannot hear the drive spinning by putting your ear next to it, try removing the drive from the computer and twisting the drive rapidly in your hand in the plane of the drive. This will sometimes unstick a bad bearing and allow the drive to spin up.


From: Bill Chomik


What I do in this situation is as follows.


·         I always have a spare hard drive with me. I hook this drive up to the computer in question making it the primary drive. The drive that doesn't work, I change the jumper to become a secondary master and attach it to the same ribbon in the computer.

·         The computer is then booted up with the good hard drive. In a lot of cases, I then have no problem accessing the bad drive. All necessary files can then be backed up to tape, or copied to the good drive.

·         Once this is done, a new drive is put in as the primary drive. The O/S is then loaded on with all other necessary software. The spare drive is then connected as the secondary master and booted up again. All files that were recovered are then copied back to the new drive.

·         If the above doesn't work where the bad drive cannot be accessed, any and all loses are accounted for. The old drive is thrown away and replaced with a new drive. The person who doesn't take the responsibility for backing up his data has to learn to live with the consequences of these actions. A lot of times, I'm the one that ends up getting blamed, but you learn to take this with a grain of salt and brush it off.


From: Billy Dunn


The first thing I do is boot on a boot disk and fdisk/mbr if the computer can see the hard drive but can't boot after you sys C:.


From: Ben Hardman


Lets see...

·         First, I would see if I could see the disk in the BIOS.

·         If the HD is visible in the bios, I would try something like fdisk/mbr.

·         I would view the partition info and see if it was showing the correct partition info.

·         Assuming all of that is correct, I would try running microscope diagnostics and see what kind of errors it is producing—whether it be a seek error or an actual damage to the drive.

·         I would first get another drive preferably the exact same model drive.

·         I would try and run Symantec Ghost on it and write a script file telling it to ignore bad sectors and continue copying anyway.

·         It may not be able to recover all files but this sometimes works. If that still did not work to recover the data portion of the drive...

·         I would probably take the new drive that I ordered and take the controller off of it and put it on the failing drive. Many HD situations is not actually a failure in the surface of the HD but in the controller failing due to the fact of the IC chips and many surface mount resistors and capacitors which many times are already failing somewhat before leaving the manufacturer.

·         They allow functionality for sometimes several years but you are tossing a coin with each boot of the machine.

·         But I digress, back to the controller... After switching controllers see if the drive is visible and the data is in tact. If that does not work verify the drive is spinning up.

·         If the drive is not spinning sometimes you can open the drive up and take a pencil eraser and give the platter a little push and the drive will spin up. Of course, this is a last resort option because you will void any warranty that is on the drive.

·         I have even gone as far as taking a bad drive whose drive head was bad and removed the platters and put them in a new drive's platters place.

·         I had to do this with a UNIX server once because the company had not backed up any data on its servers drive.


From: Zlito


·         I always try to reset the defaults in the setup first.

·         Then reboot see if the computer holds the info to see if the on-board battery is dead. It’s simple to replace and could save a lot of time.

·         If not, maybe a voltage surge hit the cmos and cleared it. This could take some time to find the settings the manufacturer used.

·         Or find out if the hard drive had an overlay on it—older proprietary systems used them a lot. If so, try reinstalling the overlay and see if that brings back c:\. If not, leave it with me for a week and I will have it working at full steam.


From: Sasha Baer


I have just had this exact problem. I had a drive with an NTFS partition and a FAT partition. The NTFS partition was my boot partition. Anyway, the sorry story was that my girlfriend hit the power cord accidentally while doing the vacuuming and the resetting of the computer caused the boot sector and the MFT to corrupt.

After much searching, I found a helpful article (http://support.microsoft.com/support/kb/articles/q153/9/73.asp) on the MS site describing how to repair the boot sector.

I built a new NT machine and went through this process. I could then mount the partition but it still showed up as unknown in Disk Administrator.

I looked for ages on the net and the only thing I found (over and over) was a program called RecoverNT. I downloaded this and went through the instructions. It said to format the drive (that is for my symptoms) and it then searched the entire drive cluster by cluster to find the files.

The only real annoying this is that the demo copy only allows for 3 files to be restored and it costs US$250+ to buy). Even though it's expensive, I must say it does a great job, both for NTFS and FAT. Unfortunately for me, I still was not able to recover my PST file and Tracker DB–both of which must be corrupt badly as they were open at the time).


From:Jim Claypool


Start with the basics:


·         Reseat the IDE cable at all connection points, checking for bent pins.

·         Use a different power connector to the hard disk and make sure it is the only device connected to that branch.

·         Clear the BIOS settings.


If the above three did not bring it back:

·         I'd look at next trying a different IDE cable.

·         If that didn't help, try slaving the drive to another hard disk.

The big problem in the way you described the failure is that there is no communications between the hard disk and the IDE interface. However, if your new master drive does not autotype (even when by itself), look into getting that old drive onto a different IDE interface (like a different machine).


New master did autotype but still can't see the old drive? During power up, use the fat end of a screwdriver to gently tap the outside of the suspect hard disk. Sometimes the arm gets stuck and a gentle tap will free it.


From: Salvatore Valela


I saw this problem once before. The monkey b virus will take a piece of your boot sector and move it at an unspecified location on the hard drive. I would run a virus checker software program to see if you have a virus.


From: Kim Chappell


I came across a situation where the computer would not boot from the hard drive. The drive was making a horrible whining noise, and I was getting messages like "invalid media" or something similar. The user had all of her e-mail stored in a PST file on the hard drive and had never backed it up.

She was frantic. This is what I did:

·         I got another hard drive, loaded it up with Windows 95, and put it in the station.

·         I made the original drive a slave and then booted up with the new drive.

·         I then had no problem seeing the files on the old drive.

·         Apparently only the boot sector was corrupted. I was lucky (so was the user).

·         I copied the PST file, and whatever else the user needed, over to the new drive. Worked like a charm.


From: mhicks


A common problem with older hard disk drives in particular, such as those found in '486 class machines, is termed ”stiction,” a condition in which the lubricants that the manufacturer coated the drive platter surfaces with have gummed up, eventuallycausing the drive spindle motor to no longer be able to spin up the drive at power-up time. The problem may manifest itself intermittently at first, allowing the user to get started today, by switching the computer's power off and on again. But finally the day comes when no amount of power switch jiggling will help.


Here's a trick that just may allow you to get the drive started, and recover the data the user refused to back up, even after weeks of obvious notice that the drive had every imminent intention of going belly up.

·         Remove the computer case ”skin,” and dismount the hard drive mechanism from its mounting.

·         Hold the drive in your hand, still connected, and turn on the computer's power switch.

·         You will be able to hear and feel that the drive refuses to spin up. Most drives have logic that delays the spindle motor start-up about a second, in order to allow the drive electronics to stabilize, and reduce total inrush, or starting current, to the system power supply.

·         Turn the power off again, and this time, about a second after you turn the power back on again, move the drive in a quick, forceful, circular motion.

·         The object here is to impart some force to the spindle platter, as a sort of mechanical ”jump-start,” so that the force of your manual motion, added to the drive motor's normal start-up torque, will be sufficient to overcome the extra dragging stiction of the gummy lubricants, allowing the spindle to start up.


If this fails the first time, try again.

·         Use both clockwise, and counter-clockwise attempts, since you probably have no way of knowing what the actual direction of spin is.

·         You'll know immediately when you succeed by the feel of the vibration of the spindle motor starting, and the sound.

·         Now, back up that irreplaceable data, make that new drive sale, and restore. Smile modestly when acknowledging your wizardry.


From: Arve Alsvik


The procedure I suggest is absolutely a last resort thing to do.

I've would have tried to replace the hard drives controller-card. The card sitting on top of the disk. Usually it can be removed. And most likely malfunctioning controller card is the reason for the hard drive crash. But it have to be replaced with another card from the same type of hard disk. In a corporate environment this would be easy, but alas, it may be more difficult in a home situation.


Anyway: This is my only suggestion.


From: John_A_Cook


·         The first thing I would do is pull in a BIOS upgrade from the PC manufacturer and flash the system.

·         You said that the user got into the Setup and changed the settings. If an upgrade for the BIOS does not find the drive and auto detect the it, then get out the tools and open the machine up to have a look at it's guts.

·         Remove the HDD and get the info off of it and manually enter it into the settings.


From: TorA.Rysstad


The most important thing to do in this situation is to protect the data on the drive. And in my experience; the more one try to "look" for data on the disk, the more it might get destroyed.


Try to listen to the hard drive. Are there any weird sounds emitting from it? I have two "sound categories.” The first is identified by sort of "buzzing" sound or perhaps a loud "ploink" sound. The second category: no sound at all, or the drive seems to running at full speed, even if the PC is "frozen.” The first might indicate a physical damage. That might be hard to solve, but that does not imply that everything is lost. I often find almost everything on the disk like this:


·         Take the damaged hard drive out of the client’s PC.


·         Take particular care not to bump the drive. There is a chance that the heads are not parked properly. You don't need more damage to the disk than there already are!


·         Put the damaged disk in another PC.


Usually with modern disks you can auto-sense the needed specs (Heads, Cylinders, etc.), but sometimes you'll need to type this manually. And of some reason the hard drive manufactures has not considered it important enough to print this information on the label. This has puzzled me more than one time... But you can find all you need on the Internet. The Compaq that was mentioned was (I think) originally equipped with a Seagate disk. Their disk Support can be found on http://www.seagate.com/support/disc/discsupt.shtml


Remember that you will probably have to change the jumper setting. MAKE SURE THE DAMAGED DISK IS SET TO BE SLAVE!!


Copy the needed files from the damaged disk


Try to copy the files you need from the damaged disk. DO NOT try to run Scandisk or Norton Disk Doctor etc!! These programs might make things worse! Do every thing to get the files you need first! Afterwards you might consider attempts to revive the disk. Then Scandisk will be very helpful.

But remember, if the disk has crashed once, then you should not trust the disk.


If you cannot find anything on the disk, then I have found that Norton Utilities is amazingly effective. But there are alternatives available at http://hotfiles.zdnet.com/


Revive is a simple small program. Try it! I've tried it a couple of times, and it really works!! BTW: The Prolinea should not be thrown away just yet! If there is a network card in it, then it can be used as a intranet server. Install Linux and Apache Web server on it, maybe even FrontPage extensions, and voila, you'll have a splendid intranet server, or a test bench for testing Web-ideas! Just remember that:


·         A computer this old might not be able to support very large disks (> 1.2 GB)

·         Update the BIOS. The Prolinea has Flashable BIOS. So updating the BIOS is very simple. Take a look here:


Install Linux without graphical interface. The 486 processor will not offer the power needed to run KDE or GNOME in a satisfying way. You will also save allot of disk space. If you can find a old 540Mb disk then that can be more than enough!


If you install NT 3.51 Server, then this computer might be used as a separate printer server. It should be able to serve approx. 30-40 people without any trouble. But you should have 32_MB RAM and approx. 500-MB free space if the users are printing large files, like PowerPoint presentations, etc.


This document is provided for informational purposes only and MindPride makes no warranties, either expressed or implied, in this document. Information in this document is subject to change without notice. The entire risk of the use or the results of the use of this document remains with the user. The example companies, organizations, products, people and events depicted herein are fictitious.  association with any real company, organization, product, person or event is intended or should be inferred. Complying with all applicable copyright laws is the responsibility of the user. Without limiting the rights under copyright, no part of this document may be reproduced, stored in or introduced into a retrieval system, or transmitted in any form or by any means (electronic, mechanical, photocopying, recording, or otherwise), or for any purpose, without the express written permission of MindPride.

The names of actual companies and products mentioned herein may be the trademarks of their respective owners.

  Services What We Offer Areas Covered Rates & Discounts
Estimates Maintenance Plans Links Phone Tech Support
About Us Refer A Friend Why Us? Reference Dictionaries Tutorials
Privacy Policy Service Protocol Disclaimer Contact Us

Web Page Designed By  ADAM
Copyright © 1981 - 2008
MINDPRIDE CONSULTING All rights reserved.
Revised: November 21, 2007