Current location - Education and Training Encyclopedia - Graduation thesis - Computer maintenance paper
Computer maintenance paper
/news_list.asp? id= 17954

Computer maintenance paper

First of all, explain the basic configuration of my own computer: inter (r) on (r) CPU1.81GHz; Memory 260,580 KB RAM; ; Hard disk 60GB;; Graphics card ASUS v 7100pro/si 416v29.80.

Sometimes, my computer has a blue screen. Personally, I think my computer is ok, but I don't know much about it. Driven by curiosity, I often disassemble my computer. I know my personal computer very well, and I am bold. I'll buy a new one if it's a big deal During this period, I also learned a lot about computer maintenance, which is why I like this course very much. Below I will list some problems I have encountered:

Hard disk not found.

For the hard disk with the error message "HDD not detected", first check whether the interface of the external data signal line of the hard disk is deformed and whether there is virtual welding on the interface solder joint. After eliminating the above possibilities, remove the hard disk back cover to expose the circuit control board. Unscrew the fixing screw of the control board and remove the control board from the hard disk body. At this time, you can see two rows of spring plates on the hard disk body. One row is used as the power supply of the main motor, and the other row is used as the power supply of the drive coil of the head manipulator of the hard disk body and the data transmission interface between the hard disk body and the circuit control board. For hard disks without special packaging, dust can often be seen in the corresponding parts of the spring leaf and the control circuit board. Cleaning with absorbent cotton dipped in anhydrous alcohol, correcting the shape of the deformed part of the spring piece and removing the oxide layer can generally return to normal.

If the above processing fails, you have to open the hard disk body. Choose an environment with little dust and unscrew the screws on the front cover of the hard disk (some of them are stuck firmly). Remove the front cover of the hard disk and you can see the disk clearly. Firstly, the digital multimeter is used to detect whether the drive coil of the head manipulator is open. The normal resistance of the coil is about 20ω. Secondly, check whether the connecting wire on the magnetic head is disconnected. There is a magnetic head on both sides of the surface of each disk, and each magnetic head has two wires connected to the integrated chip on the head manipulator. The common model of this chip is H 17 10Q, which is used to convert magnetic signals into electrical signals and then send them to the circuit control board for processing. The head resistance should be between 23ω and 26ω. If the head resistance is large, the head is damaged. Wire the chip H 17 10Q, and the corresponding pin resistance of H 17 10Q should be around1.7kΩ. If it is lower than1.2kΩ, the chip has been broken down and can be replaced together with the cable.

If the connecting wire on the magnetic head is broken, it can be replaced with a high-quality enameled wire with a diameter of 0.2 mm, one end of which is pressed on the metal shrapnel of the magnetic head, and the other end is welded on the corresponding foot of H 17 10Q. Pay attention to clamp the enameled wire in the corresponding groove of the mechanical arm and fix it with a little 502 glue to prevent the enameled wire from rubbing when the hard disk rotates. After all parts of the hard disk are restored, finally seal the periphery of the hard disk with 702 silica gel to prevent dust from entering. Because the magnetic head is very small, it is not easy to clamp the enameled wire on it, so it is best to operate it under a magnifying glass. Don't push too hard at this time, or you will damage your head. Be careful. After this repair, the hard disk can return to normal after booting.

Prompt hard disk error condition

For the hard disk with "HDD Controller Error" error, most files on the master boot record (MBR) of the hard disk are damaged for some reason. MBR is located at 0 head /0 cylinder/1 sector, which was generated when Fdisk.exe partitioned the hard disk. If the MBR is damaged, the microcomputer will prompt the HDD controller to make an error. In fact, the file on track zero is corrupted. At this time, formatting can't solve the problem, and it must be handled by special software. First, use the system disk to check the C disk after the A disk is started.

If the zero track is not damaged, just use Norton8.0 to repair the files on the track. The specific method is: find a computer with Norton8.0 software, with a hard disk with the same model and specification as the hard disk to be repaired, and connect the hard disk to the hard disk power cord. The hard disk signal cord is not connected, and the jumper remains unchanged. (1) Run the disk editing command after startup, and click the configuration item from the menu tool to cancel the read-only item; ② Select the driver from the drop-down menu O-biect, set the hard disk type as physical disk, and click OK to confirm; ③ Select the partition table item from the object menu, unplug the signal line of the well-connected hard disk, connect it to the hard disk to be repaired, and click OK to confirm; ④ Select the hard disk 1, click OK to confirm, and then set the cylinder, side and sector to 0, 0 and 1 respectively in the Write Object to Physical Sector dialog box, and click OK to confirm. When the warning dialog box appears, select Yes. Quit Norton software to restore the master boot information of the hard disk. After restarting, the hard disk will return to normal, and the files in the original hard disk will not be lost.

If the zero track hard disk is damaged, Norton8.0 software will still be used to handle it according to the above steps, but in the third step, set the cylinder, side and sector to 1, 0, 1 respectively, and click OK. When the warning dialog box appears, select Yes. Quit Norton software and restart your computer. As you can see in the column of BIOS setting hard disk automatic detection, the CYLS value is reduced by 1. If the original CYLS is 2 1 12, it will become 211. Explain that the original hard disk partition table started from the 0 cylinder of drive C, and now it starts from 1 cylinder. Save BIOS settings and exit. After repartition and formatting, the hard disk returned to normal. There are also some hard disks that prompt "HDD controller error" during self-test. The above methods are invalid and can only be scrapped.

The most exquisite part of the computer should be the hard disk. Although this situation has changed with the continuous progress of manufacturing technology, some hard disk manufacturers, such as Quantum, have also released related new technologies, such as SPS anti-vibration system developed by Quantum VII, to reduce the impact on hard disks, so as to make them "firm". However, the shortcoming that hard disks are easy to break has not been fundamentally changed. For personal computer users who like to catch up with the new, the update frequency of hard disk is generally not as fast as that of CPU or graphics card-even if they want to buy a new hard disk, they have to hang the old hard disk in the chassis to give full play to the residual heat, so people especially don't want to see the hard disk break, especially the precious data stored in the hard disk. It doesn't matter if the hard disk logic is damaged. What if you reinstall the software and physically damage it? In fact, as long as the situation is not particularly serious, some methods can generally solve the problem.

First of all, let's look at the physical damage of the hard disk, that is, what will happen after the bad track.

1. When reading files or running software, errors often occur, or it takes a long time to operate successfully, during which the hard disk keeps reading disks and makes harsh noise. This phenomenon means that some sectors with data on the hard disk are broken.

2. The system can't boot through the hard disk when it is turned on. After the floppy disk is started, you can go to the hard disk drive letter, but you can't enter it, and the system with SYS command can't succeed. This situation is more serious, because it is likely that there is something wrong with the boot sector of the hard disk.

3. When using the computer normally, the blue screen often appears for no reason.

For the first three cases, we generally have more or less ways to remedy them. The following is the method to repair the bad track of the hard disk. It should be noted that the first method should be given priority.

1. Start with the simplest method. Select the hard drive letter in Windows98 Explorer, right-click and select Properties from the shortcut menu. In the "Tools" item, the hard disk surface is completely scanned, and possible bad clusters are automatically corrected. For the second case above, that is, you can't enter Windows98, you can start the machine with the startup disk of Windows98, and then click "A: >" after the prompt and type "scand isk X:" to scan the hard disk, where "X" is the specific hard disk drive letter. For bad clusters, the program will mark "B" in red on a black background.

2. In fact, the method of 1 often doesn't work, because Windows98 automatically repairs "bad tracks" mainly for logical bad tracks, but can't automatically repair physical bad tracks, so it is necessary to consider "cold processing" these bad tracks. The so-called "cold treatment" is to mark these bad roads and avoid them if they are not used or provoked. Remember the location of the bad track in the 1 method, then divide the high-level format of the hard disk into an area with bad tracks, and don't access the files in this area in the future. To be clear, don't divide this area too "economically" in order to save hard disk space, but leave appropriate space, because it is unwise to read "good tracks" around bad tracks-bad tracks are spreading. If the "good track" you use is too close to the bad track, it won't be long before new bad tracks appear on the hard disk.

3. Use some software to deal with the hard disk, the most typical of which is PartitionMagic. Take version 4.0 as an example: scanning the hard disk can be completed directly with the "check" command in PartitionMagic4, but this command has no automatic repair function, so it is best to call the relevant programs of Windows98 in Pa rtitionMagic4 to complete this task. After marking the bad cluster, you can try to retest it by selecting "Advanced/Bad Sector Retest" under the operation menu; After dividing the bad cluster into one (or more) areas, we can consider hiding the area in Windows98 to avoid misoperation. This function is realized by hiding some items. It is important to note that if the partition of the bad cluster is directly hidden without formatting, some programs related to the drive letter will not run normally in the subsequent partitions because of the change of the drive letter. For example, some software shortcuts on the desktop can't find the host program. The solution is to use the DriveMapper menu item under the Tools menu, which will automatically collect shortcuts and related information in the registry, and correct them. Especially in the newer version of PartitionMagic5.0 Pro, DriveMapp er has also been upgraded to version 3.0, which makes the work more efficient and concise. In addition, the software DiskManager can also do this work. After hiding the partition, don't try to merge the front and back partitions of the partition where the bad track is located-this is futile because the two partitions are physically discontinuous.

4. It seems difficult for the hard disk sector 0 to be damaged, but it is not hopeless-just shield the scrapped sector 0 and replace it with 1 sector. The ideal software for this job is Pctools9.0, specifically the DE tool in Pctools9.0. It should be noted that after the sector modification is completed, the information in the partition table will only be formatted for the hard disk.

Unless absolutely necessary, it is best not to use this trick: write down the hard disk. Because the low-level hard disk has at least two shortcomings: one is to wear the disk, and the other is that for the hard disk with bad tracks, the low-level hard disk will accelerate the spread of bad tracks.

6. Finally, the relevant contents of the motherboard BIOS should be set well, especially for some motherboards before TX chipset level. Because they do not have the ability to automatically identify the specifications of hard disks, the use of hard disks is often affected by improper settings, and the hard disks are not fully utilized and will be damaged.

The above is the solution when the hard disk is physically damaged. However, most of these methods are passive, at the expense of hard disk capacity. Hard disk has bad tracks. If it is not due to aging, it means that there are some improper places in normal use, such as defragmenting the hard disk too frequently and having too little memory, so that application software frequently accesses the hard disk. Ignoring the dustproof treatment of hard disk will also lead to mechanical failure of hard disk head because of difficult positioning. In addition, the overclocking of CPU leads to the increase of external frequency, which forces the hard disk to work at too high voltage for a long time, and also leads to failure. Therefore, the best way to use hard disk at ordinary times should be to operate carefully.

Detailed explanation of hard disk logical lock

I don't know if you have ever encountered a situation where the hard disk can be detected in the bios, but the computer can't be started from the floppy disk and the hard disk? Maybe you will feel that your hard disk is broken at this time, but it is very likely that your hard disk has a logical lock.

There are three kinds of hard disk logical locks, the essence of which is to modify the hard disk partition table. Previously, it was only used by some hacker programs, and it began to cause widespread harm to computers when the notorious KV3000 anti-piracy incident occurred, when Jiang Min Company was * *. A hacker program has been implanted in the new upgrade program of KV3000. When it is detected that users use pirated KV3000, the hard disk partition table is locked. It is called "active logical lock" and is actually a logical lock of hard disk. At that time, countless innocent people were victimized and Jiang Min Company was found guilty. This is an old story. Here are three situations and solutions.

First, let's take a look at the partition table of the hard disk. The hard disk partition table is located in the 1 sector of the first cylinder of disk 0, and the 64 bytes of this sector starting from 0 1BEH are the partition table. Partition table ***64 bytes, divided into 4 columns, each column 16 bytes describes a partition. If you partition with FDISK program, you only need two columns at most. The first column describes the main boot partition and the second column describes the extended partition. The structure of partition table and the meaning of each byte are as follows:

00H— Mark valid bytes. The active DOS partition is 80H, and others are 00H.

01h-the number of heads of logical sector 0 in this partition.

02h-the sector number of the cylinder where the logical 0 sector is located.

03h-the cylinder number where the logical 0 sector is located.

04H— Partition type flag.

05H— The header number of the last sector in this partition.

06H— The sector number of the last sector.

07h-cylinder number of the last cylinder.

08H———— The total number of sectors on the hard disk before this partition, expressed in double bytes.

0CH— The total number of sectors in this partition, counting from logical 0 sectors, excluding hidden sectors, expressed in double bytes.

The last two bytes of the partition table are its valid flags, and you will not be able to boot from the hard disk after the change. This is the first simple way to lock the hard disk. However, it is relatively easy to solve it. As long as you start with the floppy disk, everything will be fine. After startup, use software such as Debug or Diskedit to restore the marks in the hard disk partition table. The second method is to modify the partition parameters. If all partition parameters are changed to 0, because the partition parameters cannot be found, you can't boot from the hard disk after starting, and you can't identify the hard disk after starting from the floppy disk with the startup disk. However, the machine can be started after all. We can repair the changed partition table parameters in the floppy disk with tools such as debug after startup, and there will be no problem after restart.

We will focus on the third type, that is, the "active logical lock" mentioned above, because the partition table parameters have been modified into infinite loops. During normal startup, DOS takes over the hard disk and looks for the partition table. The main boot partition is defined as drive C, then the logical disk is defined as drive D, and then E, F, G. This active logical lock is to point the next partition of the first logical disk (usually drive D) to itself and keep reading the next one. In fact, it is reading itself, and the result is infinite loop. Because DOS startup must contain the basic input and output file io.sys (we can also see it under windows, which is located in the root directory of drive C). And a little stubborn. After starting, we have to read the hard disk partition table and take over, so no matter what we start with, it will cycle as soon as it finds the logical disk, and we will see that the hard disk light is always on and the system hangs.

So how do we untie it? Basically, it only works by invalidating io.sys or modifying partition table parameters.

1, debugging method.

In this way, we must be able to start the machine first We can modify the io.sys file in the startup floppy disk on a common computer, find the first "55aa" string, and modify it to any other value after finding it. With this boot floppy disk, you can successfully boot from the locked hard disk. But at this time, the partition table of the hard disk is not normal, so we can't use FDISK to delete and modify the partition, and we still can't start the system with the normal startup disk. At this point, we can use DEBUG to restore manually. Specific commands are as follows: