Chapter 9 COE115-1L Troubleshooting

Saccuan, April Jem H. CpE/2 2012100116 Chapter 9 Discussion of Results Lab 9.1 Intellectual Property In this activity, we researched software privacy and tested if our copy of Windows is legal. From www.siia.net, how this association generate a list of potential pirated sites and what are the types of applications or protocols are monitored. From www.microsoft.com/genuine, we validated the copy of our Windows to be legal and know the advantages for using genuine Microsoft software. There are other licenses for software like the open source software (OSS) which does not restrict free distribution but rather, encourages people to copy, use, modify, and improve the software as long as they follow certain rules. We searched an OSS example for different types of programs like for Web browser (Firefox), Photo Editor (The GIMP), E-mail Client (Thunderbird), and for Media Player (VLC). Product activation ties the key to a particular computer so the same key cannot be used on multiple systems. Validation, on the other hand, check the key against known illegitimate keys when downloading updates from Microsoft. Lab 9.2 Learn about Safety Issues Part of support as the support technician includes knowing about safety and environmental issues and making users aware of these

issues. The manual provided useful tips for protecting ourselves against certain injuries. Also, there are provided tips on how to protect the PC support technicians as well as their equipment as they work. Data gathering is only in review questions. It is noted that if we use chemical solvents there should be a Material Safety Data Sheet (MSDS) that describes the solvent’s health effects, first aid, proper handling, and storage procedures. Lab 9.3 Safety Clean Computer Equipment As the technician, it is needed that we know how to clean computer peripherals like monitor, mouse, keyboard, and computer system without damaging the equipment or oneself. Like the previous lab activity, data gathering is only at the review questions that helps in further understanding of the lesson. Many components such as RAM are sensitive to ESD so it is necessary to use an ESD bracelet when working inside a computer case. It is necessary to have an MSDS on file in a computer lab because many materials such as cleaning solvents or heat-sink paste can be dangerous. It is important that computer fans not be clogged with dust because the fans are necessary for proper air flow and cooling. Restricted air flow causes heat to build up and can negatively affect a computer’s performance. Lab 9.4 Diagnose Simple Hardware Problems This lab ought to give an experience troubleshooting and repairing simple problems. We did not do this in the class. We just imagine what happens. Answering the review questions, if master boot record (MBR) cannot be found on the Hard Disk, it result in a “non-system disk” error.

POST beeps are the first indication that RAM has been removed. Likewise for a problem with drive assignments, mislabeling is the initial condition and for improper hard drive jumper assignments, hard drive is not read nor recognized by the system. Lab 9.5 Troubleshoot a Hardware Problem This activity takes us through some real-life troubleshooting situations that helped us build our troubleshooting skills that we furnished from the past chapters. Answering the troubleshooting part is a bit technical but it helps in identifying the problem and the solution to help Katie. We applied the BIOS POST audio codes that indicate and confirmed that Katie is dealing with a memory problem for her computer. In troubleshooting a boot problem, the advantage of restoring all CMOS settings to their default values is returning these settings to the most compatible ones which should eliminate configurations as a source of problem. However, doing the restoring setting to default also have a disadvantage that the user would lose any customized settings such as boot order. Lab 9.6 Troubleshoot General Computer Problems Troubleshooting a general problem is no different from troubleshooting a specific subsystem. One could simply apply the troubleshooting techniques to a wider range of possibilities. Changing the boot sequence to boot from a non-existent device switched mouse and keyboard PS/2 connectors, unplugged monitor, removed cables from the primary hard drive, charging/adding HD information in BIOS are the problems which caused the computer to halt during the boot process. The solution to the problem is not usually

obvious even we discovered it source because our exposure to these kinds of problems, count. The general steps one could take in troubleshooting the computer is as follows: Check the cables, isolate the problem, take notes about the error messages, check the POST, notice load time of OS, notice any graphics problem, perform an auditory test, and check newly installed hardware and software. Lab 9.7 Observe the Boot Process With this lab, it ought to familiarize us with the boot process and gives some practice recognizing when the boot process halts and observe the resulting information displayed on the screen. With all the problems we studies in the lab, monitor not plugged in will be the earliest to halt the boot process. When troubleshooting problems with the boot process, being familiar with all steps in the process is useful because if you are aware of what normally happens during the boot, you are more likely to be able to quickly identify where the process time boot failed and what cause the failure. The hard disk drive is the first detected during the boot process and it is vital that this device be detected early because it contains the MBR. Lab 9.8 Critical Thinking: Troubleshoot a Startup Problem Even Windows is stable, a PC support technician needs to know how to investigate problems that may occur and solve them. This lab gives a variety of experiences to help build our troubleshooting skills. We imagine the scenario with Karen and solve it step by step. For the review questions, we have just installed new software and restarted the system which now hangs before reaching the Windows desktop. Troubleshooting, we should try the last known good configuration on the Advance Boot Options menu for it would roll the

system back to a state before the software was installed. To scan the hard drive for viruses without first booting to Windows: we can boot from another device such as a live CD or USB drive, run an on-line scan, and remove the drive and scan it from another system. Lab 9.9 Critical Thinking: Troubleshoot a Startup Problem As we have learned about several tools and methods we can use to troubleshoot and repair a failed system or failed hardware devices, this lab gives us the opportunity to use these skills in a simulated troubleshooting situation. However we didn’t managed to sabotage another group’s system and repair another failed system. Thinking back on this troubleshooting experience to the problems that caused us difficulty, we recommend that we could check the internet for suggested methods. We have used third-party software utilities, specifically the diagnostic utilities SiSoftware Sandra Lite and MemTest86

Saccuan, April Jem H. CpE/2 2012100116 Chapter 9 CONCLUSION This chapter have the most number of labs included. PC Maintenance and Troubleshooting Strategies sums up and uses the skills we established for the past chapters. Knowing intellectual property we understood when software cannot be copied, identified signs that software might not be legal, and find open source alternatives to some programs. Learning about safety issues, we described safety concerns of computer users, and how to protect ourselves and the equipment as we repair a computer. We are also able to clean a computer and other computer parts without damaging ourselves nor the computer. In the fourth lab, we can start a functioning PC, introduce a problem, and remedy the problem. Also, we diagnose a problem caused by someone else, and record the troubleshooting process. After completing the fifth lab, we are able to troubleshoot boot problems caused by hardware. In troubleshooting general computer problems, we diagnosed and solved problems with various hardware devices, and document the troubleshooting process. We also observe the boot process, describe the boot process in detail, halt the boot process, and diagnose problems in the boot process. For the two critical thinking lab activities, we are able to solve startup problems with the provided OS, used windows tools to recover

data when Windows will not boot, and learned to troubleshoot a system by recovering from a sabotaged system.