Computer Hardware Installation and Maintenance Lab Manual

Government Girls’ Polytechnic, Bilaspur
Name of the Lab: Hardware & Maintenance Lab
Practical : Computer Hardware Installation and

Maintenance Lab
Class: 3rd Semester ( ET&T )
Teachers Assessment: 40 End Semester Examination: 100
EXPERIMENT NO:-1
1. OBJECTIVE :- Troubleshooting symptom failures in motherboard.
2. HARDWARE & SYSTEM SOFTWARE REQUIRED :- Motherboard of computer

system.
3. SOFTWARE REQUIRED :- NA
4. THEORY :- The Five Basic Elements Of Computer System Are

Storage
Arithmetic and Logical Unit
Control Unit
Input device
Output device
And The Basic Element Of Your Computer System is Us -
Elements Computer System.
Because we are the five basic elements of your computer system.
Storage
We have the most suitable storage solution for your organization to store one of the
most valuable resources - data. You can have a hassle free server in your office, or you
can store your data at the secure server which you can access the data any time and
every where.
Arithmetic and Logical Unit
Computer Hardware Installation and Maintenance Lab Manual: 3rd sem (ET&T) 1
With a logical goal, we provide the most cost effective, practical and feasible solution to
smooth your corporate process and make your resources perform more effectively.
Control Unit
By using our cost effective mistake proofing solution to control your user data access or
internet traffic will the most easiest task that you ever perform. By monitoring and
auditing, you will be able to gain more control on the computer system in your
organization.
Input device
We help you to automate your data entry process so that you can relocate your resource
to other task that can't be automated. Beside that our hassle free solution come with web
based GUI which allow you to update or modify data from any device at any time and
every where. We also provide a channel for your customer to input their valuable
feedback, enquiry and even their purchasing order into your system.
Output device
We provide data mining application that help you to generate sales report, customer
behaviour analytic report and even your corporate web site monthly traffic report. doc is
not the only extension for your document, you can have your document output as pdf,
png and other popular file format.
5. FLOW CHART (IF REQUIRED) :- NA
6. PROGRAM INPUTS & OUTPUT :- NA
7. OBSERVATIONS :- Different elements of computer system are studied.
EXPERIMENT NO:-2
1. OBJECTIVE :- Identify different beep codes and error codes.
2. HARDWARE & SYSTEM SOFTWARE REQUIRED :- Computer System
4. THEORY :- POST ABCs
The computer power-on self-test (POST) tests the computer to make sure it meets the
necessary system requirements and that all hardware is working properly before starting
the remainder of the boot process. If the computer passes the POST the computer will
have a single beep (with some computer BIOS manufacturers it may beep twice) as the
computer starts and the computer will continue to start normally. However, if the
computer fails the POST, the computer will either not beep at all or will generate a beep
code, which tells the user the source of the problem.
If you're receiving an irregular POST or a beep code not mentioned below follow the
POST troubleshooting steps to determine the failing hardware component.
AMI BIOS beep codes
Below are the AMI BIOS Beep codes that can occur. However, because of the wide
variety of different computer manufacturers with this BIOS, the beep codes may vary.
Beep Code Descriptions

1 short DRAM refresh failure
2 short Parity circuit failure
3 short Base 64K RAM failure
4 short System timer failure
5 short Process failure
6 short Keyboard controller Gate A20 error
7 short Virtual mode exception error
8 short Display memory Read/Write test failure
9 short ROM BIOS checksum failure
10 short CMOS shutdown Read/Write error
11 short Cache Memory error
1 long, 3 short Conventional/Extended memory failure
1 long, 8 short Display/Retrace test failed
AWARD BIOS beep codes
Below are Award BIOS Beep codes that can occur. However, because of the wide variety
of different computer manufacturers with this BIOS, the beep codes may vary.
Beep Code Description

1 long, 2 Indicates a video error has occurred and the BIOS cannot initialize the
short video screen to display any additional information
Any other
RAM problem.
beep(s)
If any other correctable hardware issues, the BIOS will display a message.
IBM BIOS beep codes
Below are general IBM BIOS Beep codes that can occur. However, because of the wide
variety of models shipping with this BIOS, the beep codes may vary.
Beep Code Description

No Beeps No Power, Loose Card, or Short.
1 Short Beep Normal POST, computer is ok.
2 Short Beep POST error, review screen for error code.
Continuous Beep No Power, Loose Card, or Short.
Repeating Short Beep No Power, Loose Card, or Short.
One Long and one Short Beep Motherboard issue.
One Long and Two Short Beeps Video (Mono/CGA Display Circuitry) issue.
One Long and Three Short Beeps. Video (EGA) Display Circuitry.
Three Long Beeps Keyboard / Keyboard card error.
One Beep, Blank or Incorrect Display Video Display Circuitry.
7. OBSERVATIONS :- Different beep codes of computer system listened
carefully and identified.
EXPERIMENT NO:-3
1. OBJECTIVE :- Identification of different motherboards & CPU’s.
2. HARDWARE & SYSTEM SOFTWARE REQUIRED :- different motherboards &

CPU’s.
4. THEORY :- PC Mainboard Identification

Every now and then, we see questions in the PC911 Forum regarding identification of
the mainboard installed in a PC. Many users simply don’t know the make and model of
the mainboard (motherboard or mobo) that their systems are built around. Does this
really matter? No … not unless and until something goes wrong where you need that
info to effect a repair. Or, until you decide to perform some DIY system upgrade and
suddenly you need to know something specific about the board.If all was done according
to Hoyle when you purchased your system, you received some sort of documentation
with it. Many times, that documentation will include at least a spec sheet itemizing the
individual components, and at best it will include a User’s Guide or manual for the mobo.
Several types of system upgrades might require the user to have this documentation.
Sometimes, you will need to change jumper or DIP switch settings when installing a
processor of a different type or speed. Some memory changes will also require such
changes. Then there are such tasks as enabling or disabling integrated sound, modem,
and video features. Or, maybe you’re just plain curious! If you find yourself in the
position of needing to identify an unknown mainboard, fret not – there are several
workable alternatives to throwing darts at a list of mobo makers.
In this article, I will concentrate on the American Megatrends and Award BIOS’es, as
they are by far the ones most commonly used by modern desktop systems. I will
address three basic methods for use in determining your mainboard manufacturer.
The ―Lookatit‖ Method…

The first thing to do, and probably the last thing that many folks think of, is to simply
―look at it‖. Many mobo makers will screen-print their ID right on the board. Ideally this ID
will be on the upper (visible) surface of the board, but this is often not the case with
―generic‖ mobo’s. With some of these boards, if they are ID’ed at all, it is on the lower
surface, which is normally not visible on an installed board.
Look carefully at the entire surface of the board, including those areas that may be
hidden behind drives, cables, or the power supply. Many boards are labeled between
their expansion slots. Another common location on newer boards is in the area of the
CPU slot or socket. Also, be aware that while the board may not have its maker’s name
showing, it just may have its model name or number printed there for all the world to
see.
While you are searching the board for make and model info, take a minute to note the
location of any jumpers or DIP switches on the board. If you are doing an upgrade
requiring resetting any of these devices, it will help to know where they are located.
Figures 1A through 1E illustrate the mainboard identification schemes used on four
different mainboards.
Figure 1A – Two model numbers on same board, on side of ISA slot
In Figure 1A, we can see the markings applied to a generic model. The markings here
are somewhat unusual in that it would appear that there are two different model numbers
identified – 8500TVX and MBD-5VX2. This is sometimes the case when a basic board
from one manufacturer is sold under another brand name. There are several mainboards
on the market, under widely varying names, all made by one company. This situation is
a real problem when the manufacturing company is just that – an operation that builds
and sells generic boards for other (marketing) firms without providing any real end-user
support. The support responsibilities fall on the seller, and often there is little or no
support to be had as a result. A web search for these models via www.google.com
returned enough hits on the 8500-TVX to make it obvious that the board is a Biostar
board. A similar search for the MBD-5VX2 designation returned no hits. A quick hop to
Biostar’s website www.biostar-usa.com and a little bit of detective-type browsing through
their museum showed the board to be a model MB8500TVX-A version 1 board. For the
record, this board is also screened with that information on its surface, as shown in
Figure 1B below.
Figure 1B – MB8500TVX-A surface marking
7. OBSERVATIONS :- Different elements of computer system are studied.
Figure 1C – Board ID between ISA slots
Figure 1C – Board ID between ISA slots
In Figure 1C, we can see the markings on an older 386 mainboard. Here, the model
number and revision level are clearly evident, but the manufacturer is again not shown.
Get used to that. As a general rule, the top name-brand boards will usually headline their
brand name, but the lesser-known boards are going require some digging. This
particular board can be identified as a product of Edom International, but not with a
simple web search. Once identified via an advanced search, using MA013 and 386DX
as the search strings, it becomes evident that the board was an Edom product.
Figure 1D – Board ID on edge of board, near cache slot
In Figure 1D, we see another model number, AP5C/P. This time, a simple web search on
that string returned numerous (102) hits. Among the top ten hits, six were for pages on
Acer or AOpen sites. A couple of clicks later and we’re at http://english.aopen.com.tw,
the English-language home page for this manufacturer. Pretty sweet, huh? Let’s take a
look at the last picture, Figure 1E.
Figure 1E – Board ID between PCI slots
Here again we can see a model number and revision level only. First step, which by now
should pretty apparent, is a web search. In this case, the web search leads us to
www.dcscomputer.com.tw, the home page for the board maker DCS Computer Systems.
So what does all of this mean – why did I go through all of this if it is so obvious? Well
… because it is only obvious once you’ve done it a time or two. Sometimes the most
obvious alternative gets overlooked simply because we think that it can’t be that easy!
Moral of this story – start out with what you can see – “Lookatit”.
7. OBSERVATIONS :- Different motherboards of computer system are studied

carefully and identified.
EXPERIMENT NO:-4
1. OBJECTIVE :- Troubleshooting symptom failures in motherboard.
2.HARDWARE & SYSTEM SOFTWARE REQUIRED :- Motherboard of

Computer System
4. THEORY :- A computer motherboard is one of the most hardest pieces

of hardware to troubleshoot, because the symptoms are too similar to other
pieces, the best way to make sure the motherboard or mobo is failing is to
boot your computer with just crucial components connected (CPU, RAM,
and motherboard), and see what happens, if it displays the same
symptoms, then you have 3 suspects.
If the problem is when booting Windows, then you will have to include the hard drive, but
the hard drive troubleshooting symptoms are much different from that of a
motherboard, so don't worry about this, just install it if your computer seems to pass the
initial boot.
Remember that troubleshooting your computer it's just like playing the game "Clue" you
need to eliminate the suspects in order to find the culprit. Keep in mind that it's very rare
for a motherboard to fail especially if it's a good motherboard, so try every
troubleshooting available.
Reasons a motherboard fails
A Motherboard can fail for a number of reasons:
Electricity and voltage spikes

Dust, smoke
Age
Fan failure or heating issues
Force or pressure
If you live in a place with a lot of voltage spikes, I suggest you get a voltage regulator
outlet or a backup (this usually comes with this feature) and will prolong your
motherboard life over time. Clean your fans at least once a year even if you live in a
clean place, dust can play a significant part in hardware failures, from fans not working
to hardware connectors not working well because of dust.
Failure symptoms
Motherboard failures can be similar to the ones the power supply has,
Everything powers on but you can't see a live screen
Computer turns on for just a few seconds then turns off
Some peripherals work others don't
System shuts off randomly
If peripherals don't work, don't look if it's connected right, take the peripherals out clean
their connectors and reattach them again, see if there's any change, try connecting
something else to that same connector and see if it works.
Because the motherboard failure symptoms can be confused with those of the power
supply, always keep a spare power supply so you can replace it and see if the problem
persists, for example when a computer powers on but fails to give you a live screen,
there's a possibility the power supply and motherboard may be damaged so you need to
be sure you have the correct piece of hardware.
How to troubleshoot a Windows PC Motherboard.
If your system keeps crashing after a recovery then it is probably the

motherboard.
Operating System will not load? Reseat RAM - if multiple SIMMS (single inline
memory modules) or DIMMS (dual inline memory modules) then remove them all
and replace and test individually. Did you install after market RAM? Is it
compatible? Is it sequenced correctly - must be in pairs? Is it the correct amount
of RAM?
POST Codes (Power On Self Test) - Computer Beeps at start up - Reseat the
PCI cards. For notebooks then reseat the mini-PCI bus. Reseat the RAM.
For Notebooks - perform a hard reset.
Perform Diagnostics test.
Perform an MSCONFIG if your computer has it.
Shut down all other applications to avoid conflicts. Remove all other hardware
devices.
Perform a recovery. Ensure that you backup your data prior to doing a recovery.
If the problem persists then send in for service.
Check error messages in Event Viewer. Start / Settings / Control Panel /

Administrative Tools / Computer Management (or Event Viewer)
CPU Heat - check to ensure that there is proper ventilation and the fan is
working. Diagostics will test the fan for you. For notebook heat issues - use
SPEEDSTEP (Intel) to the lower the cycle speed (megahertz). Enable Battery
Optimized Performance. Was your CPU replaced? Was the thermal barrier
replaced correctly. The CPU must be sealed correctly with a thermal barrier
(adhesive between CPU and motherboard) or it could cause heat problems.
Conflicts in system devices - check the IRQ (Interrupt Requests 0-15) in the
BIOS and reset the BIOS.
7. OBSERVATIONS :- Different methods of troubleshooting motherboard

performed.
EXPERIMENT NO:-5
1. OBJECTIVE :- Troubleshooting symptom failures in FDDI.
2. HARDWARE & SYSTEM SOFTWARE REQUIRED :- FDDI network
4. THEORY :- The Fiber Distributed Data Interface (FDDI) standard was

produced by the ANSI X3T9.5 standards committee in the mid-1980s.
During this period, high-speed engineering workstations were beginning to
tax the capabilities of existing local-area networks (LANs)—primarily
Ethernet and Token Ring. A new LAN was needed that could easily support
these workstations and their new distributed applications. At the same time,
network reliability was becoming an increasingly important issue as system
managers began to migrate mission-critical applications from large
computers to networks. FDDI was developed to fill these needs.
After completing the FDDI specification, ANSI submitted FDDI to the International
Organization for Standardization (ISO). ISO has created an international version
of FDDI that is completely compatible with the ANSI standard version.
Although FDDI implementations are not as common as Ethernet or Token Ring,

FDDI has gained a substantial following that continues to increase as the cost of
FDDI interfaces diminishes. FDDI is frequently used as a backbone technology
as well as a means to connect high-speed computers in a local area.
Troubleshooting FDDI
This section provides troubleshooting procedures for common FDDI media problems.
Table 5-1 outlines problems commonly encountered on FDDI networks and offers
general guidelines for solving those problems.
Table 5-1 Media Problems: FDDI

Media Problem Suggested Actions
Nonfunctional 1. Use the show interfaces fddi exec
FDDI ring command to determine the status of the router's
FDDI interfaces.
2. If the show interfaces fddi command

indicates that the interface and line protocol are
up, use the ping command between routers to
test connectivity.
3. If the interface and line protocol are up, make

sure the MAC addresses of upstream and
downstream neighbors are as expected.
4. If all zeros appear in either of the address

fields for these neighbors, there is probably a
physical connection problem.
In this case (or if the status line does not indicate

that the interface and line protocol are up), check
patch-panel connections or use an OTDR1 or light
meter to check connectivity between neighbors.
Ensure that signal strength is within
specifications.
Upstream neighbor Bypass switches can cause signal degradation
has failed and because they do not repeat signals as a normal
bypass switch is transceiver does.
installed
1. Check upstream neighbor to determine
whether it is operational.
2. If the node is down and a bypass switch is in

place, resolve any problems found in the
upstream neighbor.
1
OTDR = optical time-domain reflectometer
When you're troubleshooting FDDI media in a Cisco router environment, the show
interfaces fddi command provides several key fields of information that can assist in
isolating problems. The following section provides detailed description of the show
interfaces fddi command and the information it provides.
show interfaces fddi
To display information about the FDDI interface, use the show interfaces fddi exec
command:
show interfaces fddi number [accounting]

show interfaces fddi [slot | port] [accounting] (Cisco 7000 series and Cisco 7200
series)
show interfaces fddi [slot | port-adapter | port] [accounting] (Cisco 7500 series
routers)
Syntax Description
• number—Port number on the selected interface.
• accounting—(Optional) Displays the number of packets of each protocol type that

have been sent through the interface.
• slot—Refers to the appropriate hardware manual for slot and port information.
• port—Refers to the appropriate hardware manual for slot and port information.
• port-adapter—Refers to the appropriate hardware manual for information about port

adapter compatibility.
Command Mode
exec
5. CODING (IF REQUIRED) :- NA
7. OBSERVATIONS :- Preformed troubleshooting of FDDi successfully.
EXPERIMENT NO:-6
1. OBJECTIVE :- Installation of operating system
2. HARDWARE & SYSTEM SOFTWARE REQUIRED :-Windows 98 CD.
3. SOFTWARE REQUIRED :- Windows 98 CD
4. THEORY :- Windows 98 Installation

This is what you will need before installing windows 98.
1.Windows 98 CD.
2. Computer with CD-ROM Access.
Configuring your BIOS for the Install:
To find out how to access the BIOS please refer to your motherboard manual or
the manufacturer of
your computer. (The system bios can usually be entered on boot, usually by
pressing the F1, F2, F8,
F10 or DEL key. Make sure you save the settings before exiting. If you are
unsure or don’t want to
enter the BIOS then just test the computer by putting the CD-ROM in the drive
and rebooting the
computer. This is the recommended way to install windows 98.
5. STEPS (IF REQUIRED) :- Starting The Setup:

1.Insert CD and restart PC.
2. Once the Windows 98 Setup Menu comes up choose option 2 (Boot fromCD-
ROM)
3. Then the Windows 98 Startup Menu will come up. Select Option 1. (Start
Windows 98
Setup from CD-ROM)
4. Now your computer will install some drivers so please wait a few moments.
5. Now a blue setup screen will come up. Press enter.
6. Setup then wants to do some system tests. Just press enter.
7. Scandisk will now run, please wait.
8. After ScanDisk completes Windows will copy a few important files for setup.
9. Now the graphical Windows 98 Setup Screen will come up.
10. Click continues and wait for the setup wizard to complete.
11. Now it will ask you in which directory to install Windows to. The default
directory is just fine so click
next.
12. Setup will now prepare the directory, please wait.
13. Setup will now check for installed components and disk space, pleasewait.
14. Setup will now prompt you what type of install. Choose typical if you have a
desktop computer or
portable if it is a laptop.
15. Windows will prompt you to install components, just choose continue.
16. If a network card is detected a network information screen will appear. Type
in the required
information and click next
17. Select your country settings, United States should be chosen by default.
18. Now finally the main part of Setup is here. Setup will start copying files. This
will take a pretty long
time, be patient.
19. Once setup is done copying files Windows will restart automatically.
20. The Windows 98 Startup Menu will appear. Select option 1 (Boot from Hard
Disk)
21. The Windows 98 booting screen will appear!
22. Now Windows will prompt you for user information, enter it and click continue.
23. Now the License Agreement. Read and if you agree click on ―I accept the
Agreement‖ and click
next. If you select ―‖I don’t accept the Agreement‖ then setup will end.
24. Now input your product key computer. Click next to continue.
25. Next click on Finish.
26. Setup will now finalize the hardware and install settings.
27. Setup will now install plug and play devices.
28. Your computer will restart automatically.
Disk)
30. Windows will start booting for the second time.
31. Setup will continue installing hardware.
32. Now setup will prompt you to enter in your time, date, and time zone. Once
selected click on apply
and then ok.
33. Windows will continue to setup Windows items.
34. The computer will restart automatically once again.
Disk)
36. Windows will boot for the third time.
37. Windows will update system settings.
38. Now finally you have reached the Windows Desktop!
39. You also may need to install your hardware drivers. If everything is working
properly then you
shouldn’t worry about them.
Enjoy your new freshly installed Windows
7. OBSERVATIONS :- Windows 98 operating system successfully

installed.
EXPERIMENT NO:-7
1. OBJECTIVE :- Installation of application software like MS-Office 2000/2003 .
2. HARDWARE & SYSTEM SOFTWARE REQUIRED :- Windows Xp.
3. SOFTWARE REQUIRED :- Office 2003 CD.
4. THEORY :- MS OFFICE 2003 INSTALLATION

In order to install Microsoft Office 2003, simply begin by putting the Office CD in
the CD or DVD drive. The XP operating system will begin the loading process
and the software will ask if you want to install Office. Click Yes as usual. And
then assent to the license agreement. You will then be asked for the 25 digit
security code which we have made available to you. Type this in exactly as it
has been given to you (Figure 1).
You will then be asked what type of installation you wish to perform. Please
choose ―Complete Installation‖ as indicated in Figure 2. The Complete
Installation assures you that you have all the file converters necessary to read
these documentsAfter you have chosen the Complete Installation, click next. You
will get a review screen which should look like Figure 3. After you click the Install
box the software should begin to install from the CD.
5. STEPS (IF REQUIRED) :-
Figure 1 - Enter the MS Office security code
Figure 3 - MS Office software review prior to installation
After MS Office installs, you will get a screen which will allow you to Check the web for
updates and Delete installation files (Figure 4). You will certainly want to Check the web
for updates (so check this box) and you may want to Delete the installation files to save
disk space (this is up to you). Click the appropriate boxes and click on the Finish box.
You will be directed to the Microsoft Office Update website.
Figure 4 - MS Office installation last step
You certainly want to Check the web for MS Office updates now because you have the
CD. Microsoft Office updates often require a CD and the CDs are only available through
the Library and Computer Services. So save yourself the hassle and check for updates
now.
Figure 5 - The MS Office update website
The Microsoft Office update website currently looks like Figure 5. Because you have not
previously checked for Office updates, you will be asked to install the Office updated
installation engine (Figure 6). Click Yes and install this on your computer (when you go
back to the Office Update site, you will not be asked about nor do you need to reinstall
this update engine). The update engine is a small piece of software which works with
this website and will check Office on your computer to determine what components need
updating.
The update list (Figure 7) will depend on exactly what release of Office 2003 you have
installed and what updates are available subsequent to that release. Some of these
updates need to be installed independently of the others. Often then can be bundled
together so you can download a number of updates together and install them together.
Click the updates you wish to install (we recommend installing all the security related
updates and all the updates that are appropriate for your computer. If you don’t have a
tablet PC and there are updates
Specifically for this type of computer, you don’t have to install them.) You can’t go wrong
by installing all the updates for MS Office. After you have checked the boxes of the
updates you wish to install, click the Start Installation box. The updates will begin to
download and install.
Figure 7 - The Office update installation engine
Figure 8 - Choose the updates you wish to install
After you have installed the updates successfully, the MS Office update site will provide
you with a screen which tells you which updates have been successfully installed (Figure
8).
Figure 9 - Successful MS Office update installation
This finishes the process of installing MS Office
7. OBSERVATIONS :- Office 2003 installed successfully.
EXPERIMENT NO:-8
1. OBJECTIVE :- Installation of antivirus software.
2. HARDWARE & SYSTEM SOFTWARE REQUIRED :- Windows Xp as

O.S.
3. SOFTWARE REQUIRED :- Antivirus software.
4. THEORY :- computer virus can severely hamper the performance of your

computer. They are structured to damage the stored data on your computer.
Unlike other malicious software, they do not replicate, but still could do
irreparable damage by taking full control of your PC. To assure complete
protection of your computer, installing anti-virus is a must. An anti-virus
protects your computer against viruses and Trojans, which can be deadly for
your computer. AVG anti-virus is an effective anti-virus, which detects and
removes viruses without hampering your PC performance.
5. STEPS (IF REQUIRED) :- Step 1: Click the "Install Now" button

This should be located in the lower left hand corner of the web site. Clicking this button
begins the process.
Step 2: Download the required files

After you
click the
"Install
Now"
button, the
required
files will
automaticall
y download
to your
computer.
This may
take a
while.
Step 3: The Installation
When the
Welcome to
the
InstallShiel
d Wizard
window
opens, click
the "Next"
button.
The next
step in the
installer is
the license
agreement
. Choose
the radio
button that
says that
you agree
with the
license
terms, and
then click
the "Next"
button.
For the Mail
Snap-In
Selection,
remove the
check from the
Microsoft
Exchange/Outlo
ok option, and
then click the
"Next" button.
The
default
location
for the
Destinatio
n Folder
Selection
is correct,
so click the
"Next"
button.
Click the
"Install"
button.
The
installatio
n may take
a few
minutes.
The next
step in the
installer is
the
Technical
Support
information
. Click the
"Next"
button.
The
installation
is
complete.
Click the
"Finish"
button.
Step 4: Restart
You may be asked to restart your machine when the process is complete. Do so if
prompted. When your computer restarts, Norton AntiVirus will begin a system scan of
your machine.
6. PROGRAM INPUTS & OUTPUT :- Input is the antivirus software and output is
installed antivirus software .
7. OBSERVATIONS :- Antivirus software installed and working properly.
EXPERIMENT NO:-9
1. OBJECTIVE :- Preventive maintenance of the computer system.
2. HARDWARE & SYSTEM SOFTWARE REQUIRED :- Computer system .
3. SOFTWARE REQUIRED :- System tools.
4. THEORY :- Preventive Maintenance
Preventive maintenance is a schedule of planned maintenance actions aimed at

the prevention of breakdowns and failures. The primary goal of preventive
maintenance is to prevent the failure of equipment before it actually occurs. It is
designed to preserve and enhance equipment reliability by replacing worn
components before they actually fail. Preventive maintenance activities include
equipment checks, partial or complete overhauls at specified periods, oil
changes, lubrication and so on. In addition, workers can record equipment
deterioration so they know to replace or repair worn parts before they cause
system failure. Recent technological advances in tools for inspection and
diagnosis have enabled even more accurate and effective equipment
maintenance. The ideal preventive maintenance program would prevent all
equipment failure before it occurs
5. CODING (IF REQUIRED) :- Operations for PC preventive chechs:-
Your PC's two mortal enemies are heat and moisture. Excess heat accelerates the
deterioration of the delicate circuits in your system. The most common causes of
overheating are dust and dirt: Clogged vents and CPU cooling fans can keep heat-
dissipating air from moving through the case, and even a thin coating of dust or dirt can
raise the temperature of your machine's components.
Any grime, but especially the residue of cigarette smoke, can corrode exposed metal
contacts. That's why it pays to keep your system clean, inside and out.
If your PC resides in a relatively clean, climate-controlled environment, an annual

cleaning should be sufficient. But in most real-world locations, such as dusty offices or
shop floors, your system may need a cleaning every few months.
All you need are lint-free wipes, a can of compressed air, a few drops of a mild cleaning
solution such as Formula 409 or Simple Green in a bowl of water, and an antistatic wrist
strap to protect your system when you clean inside the case.
Think Outside the Box
Before you get started cleaning, check around your PC for anything nearby that could
raise its temperature (such as a heating duct or sunshine coming through a window).
Also clear away anything that might fall on it or make it dirty, such as a bookcase or
houseplants.
Always turn off and unplug the system before you clean any of its components. Never
apply any liquid directly to a component. Spray or pour the liquid on a lint-free cloth, and
wipe the PC with the cloth.
Clean the case: Wipe the case and clear its ventilation ports of any obstructions.
Compressed air is great for this, but don't blow dust into the PC or its optical and floppy
drives. Keep all cables firmly attached to their connectors on the case.
Maintain your mechanical mouse: When a nonoptical mouse gets dirty, the pointer
moves erratically. Unscrew the ring on the bottom of the unit and remove the ball. Then
scrape the accumulated gunk off the two plastic rollers that are set 90 degrees apart
inside the ball's housing.
Keep a neat keyboard: Turn the keyboard upside down and shake it to clear the
crumbs from between the keys. If that doesn't suffice, blast it (briefly) with compressed
air. If your keys stick or your keyboard is really dirty, pry the keys off for easier cleaning.
Computer shops have special tools for removing keys, but you can also pop them off by
using two pencils with broken tips as jumbo tweezers--just be sure to use a soft touch.
Make your monitor sparkle: Wipe the monitor case and clear its vents of obstructions,
without pushing dust into the unit. Clean the screen with a standard glass cleaner and a
lint-free cloth. If your monitor has a degauss button (look for a small magnet icon), push
it to clear magnetic interference. Many LCDs can be cleaned with isopropyl alcohol;
check with your LCD manufacturer. Wipe your LCD lightly: The underlying glass is
fragile.
Check your power protection: Reseat the cables plugged into your surge protector.
Check the unit's warning indicator, if it has one. Surge protectors may power your PC
even after being compromised by a voltage spike (making your system susceptible to a
second spike). If your power protector doesn't have a warning indicator and your area
suffers frequent power outages, replace it with one that has such an indicator and is UL
1449 certified.
Swipe your CD and DVD media: Gently wipe each disc with a moistened, soft cloth.
Use a motion that starts at the center of the disc and then moves outward toward the
edge. Never wipe a disc in a circular motion.
Inside the Box
Before cracking open the case, turn off the power and unplug your PC. Ground yourself
before you touch anything inside to avoid destroying your circuitry with a static charge. If
you don't have a grounding wrist strap, you can ground yourself by touching any of
various household objects, such as a water pipe, a lamp, or another grounded electrical
device. Be sure to unplug the power cord before you open the case.
Use antistatic wipes to remove dust from inside the case. Avoid touching any circuit-
board surfaces. Pay close attention to the power-supply fan, as well as to the case and
to CPU fans, if you have them. Spray these components with a blast of compressed air
to loosen dust; but to remove the dust rather than rearrange it, you should use a small
vacuum like the $12 Belkin MiniVak.
If your PC is more than four years old, or if the expansion cards plugged into its
motherboard are exceptionally dirty, remove each card, clean its contacts with isopropyl
alcohol, and reseat it. If your system is less than a couple years old, however, just make
sure each card is firmly seated by pressing gently downward on its top edge while not
touching its face. Likewise, check your power connectors, EIDE connectors, and other
internal cables for a snug fit.
While you have the case open, familiarize yourself with the CMOS battery on the
motherboard (see FIGURE 1
FIGURE 1: The CMOS battery on your motherboard may need to be replaced after four
or five years.
). For its location, check the motherboard manual. If your PC is more than four or five
years old, the CMOS battery may need to be replaced. (A system clock that loses time is
one indicator of a dying CMOS battery.)
Look for Trouble
Give your PC a periodic checkup with a good hardware diagnostic utility. Two excellent
choices are Sandra Standard from SiSoftware and #1-TuffTest-Lite from #1-PC
Diagnostics.
Adding and removing system components leaves orphaned entries in the Windows
Registry. This can increase the time your PC takes to boot and can slow system
performance. Many shareware utilities are designed to clean the Registry, but my
favorite is Registry Drill from Easy Desk Software..
Windows stores files on a hard drive in rows of contiguous segments, but over time the
disk fills and segments become scattered, so they take longer to access. To keep your
drive shipshape, run Windows' Disk Defragmenter utility. Click Start, Programs (All
Programs in XP), Accessories, System Tools, Disk Defragmenter. If your drive is heavily
fragmented, you could boost performance (see FIGURE 2
FIGURE 2: Run Windows' disk defragmenter regularly to speed up hard-disk
performance.
). Defragging may take hours, however. Disable your screen saver and other automatic
programs beforehand to keep the defrag from restarting every few minutes.
Disk Defragmenter won't defragment the file on your hard drive that holds overflow data
from system memory (also known as the swap file). Since the swap file is frequently
accessed, defragmenting it can give your PC more pep. You can defragment your swap
file by using a utility such as the SpeedDisk program included with Norton SystemWorks
2004, but there's a way to reset it in Windows.
In Windows XP, right-click My Computer and choose Properties. Click Advanced, and
then choose the Settings button under Performance. Click Advanced again and the
Change button under Virtual Memory. Select another drive or partition, set your swap file
size, and click OK. Visit "Hardware Tips: Jog Your Memory for Faster PC Performance"
for instructions on moving your swap file in other versions of Windows. If you have only
one partition and no way to create a second one, and you have at least 256MB of RAM,
disable the swap file rather than moving it: Select No paging file in the Virtual Memory
settings (see FIGURE 3
FIGURE 3: Reset your swap file by temporarily disabling its Windows setting.
). If you have trouble booting, start Windows in Safe Mode and re-enable this option.
Hard-Drive Checkup
Windows XP offers a rudimentary evaluation of your hard disk's health with its error-
checking utility: Right-click the drive's icon in Windows Explorer and select Properties,
Tools, Check Now. (Windows can fix errors and recover bad sectors automatically if you
wish.) If the check discovers a few file errors, don't worry, but if it comes up with
hundreds of errors, the drive could be in trouble.
FIGURE 4: HDD Health alerts you to impending trouble using your drive's built-in
S.M.A.R.T technology.
The program works only with drives that support S.M.A.R.T technology, but nearly all
drives released since 2000 are S.M.A.R.T.-compliant.
Many hardware and software designers humbly assume you want their program running
on your PC all the time, so they tell Windows to load the application at startup (hence,
the ever-growing string of icons in your system tray). These programs eat up system
resources and make hardware conflicts and compatibility problems more likely. To
prevent them from launching, just click Start, Run, type msconfig, and press Enter. The
programs listed under the Startup tab are set to start along with Windows. Uncheck the
box at the left of each undesirable program to prevent it from starting automatically.
PC Maintenance: Four Tips for Longer PC Life
1. Keep your PC in a smoke-free environment. Tobacco smoke can damage delicate

contacts and circuits.
2. Leave your PC running. Powering up from a cold state is one of the most stressful
things you can do to your system's components. If you don't want to leave your PC
running all the time, use Windows' Power Management settings to put your machine into
hibernation rather than completely shutting down. In Windows XP, right-click the desktop
and select Properties. Click the Screen Saver tab and select the Power button. Choose
the Hibernate tab to ensure that hibernation is enabled, and then select a time beneath
'System hibernates' under the Power Schemes tab. (Note that this option is not available
on all PCs.) Computers running older versions of Windows may or may not provide
similar power-management features. Look under the Power Management icon (Power
Options in Windows 2000) in Control Panel to evaluate your machine's capabilities.
3. Don't leave your monitor running. The best way to extend your display's life is to
shut it off when it's not in use.
4. Avoid jostling the PC. Whenever you move your system, even if it's just across the
desktop, make sure the machine is shut down and unplugged.
7. OBSERVATIONS :- Studied how preventive maintenance of Computer system

is done.
EXPERIMENT NO:-10
1. OBJECTIVE :- Debugging the computer system.
2. HARDWARE & SYSTEM SOFTWARE REQUIRED :- Operating system.
3. SOFTWARE REQUIRED :- Debugging software tools.
4. THEORY :- A debugger or debugging tool is a computer program that is

used to test and debug other programs (the "target" program). The code to be
examined might alternatively be running on an instruction set simulator (ISS), a
technique that allows great power in its ability to halt when specific conditions are
encountered but which will typically be somewhat slower than executing the code
directly on the appropriate (or the same) processor. Some debuggers offer two
modes of operation - full or partial simulation, to limit this impact.
5. CODING /STEPS(IF REQUIRED) :-1. Identify the Bug
Debugging means removing bugs from programs. A bug is unexpected and undesirable
behaviour by a program.
Occasionally there is a formal specification that the program is required to follow, in

which case a bug is a failure to follow the spec. More frequently the program
specification is informal, in which case people may disagree as to whether a particular
program behaviour is in fact a bug or not.
Once you have a bug report, the first step in removing the bug is identifying it. This is of
particular importance when working with a bug report produced by somebody else, such
as the testing team or a user. Some bugs are relatively obvious, as when the program
crashes unexpectedly. Others are obscure, as when the program generates output
which is slightly incorrect.
Once the bug has been identified, the easiest and fastest way to fix it is to determine that
it is not a bug at all. If there is a formal specification for the program, you may have to
modify the specification. In other cases, you may have to modify the expectations of the
user. This rapid fix is often known as declaring the behaviour to be an "undocumented
feature." Despite the obvious potential for abuse, this is in fact sometimes the correct
way to handle the problem.
2. Replicate the Bug
The first step in fixing a bug is to replicate it. This means to recreate the undesirable
behaviour under controlled conditions. The goal is to find a precisely specified set of
steps which demonstrate the bug.
In many cases this is straightforward. You run the program on a particular input, or you
press a particular button on a particular dialog, and the bug occurs. In other cases,
replication can be very difficult. It may require a lengthy series of steps, or, in an
interactive program such as a game, it may require precise timing. In the worst cases,
replication may be nearly impossible.
3. Don't skip this step
Programmers are sometimes tempted to skip the replication step, and to go straight from
the bug report to the fix. However, failing to replicate the bug means that it is impossible
to verify the fix. The fix may turn out to be for a different bug, or it may have no
significant effect at all. If the bug has not been replicated, there is no way to tell.
Failure to replicate the bug is a real problem which I've seen happen many times. In a
complex program, it's often quite easy to find something to fix--perhaps a real problem,
perhaps merely something which looks like a problem. It's human nature to assume that
any particular fix solves the problem at hand. Without a means of verification, any
plausible fix will be accepted, whether it is right or wrong. An incorrect fix leads to future
problems. On average, skipping the replication step wastes more time than it saves.
4.Understand the Bug
Once you are able to replicate the bug, you must figure out what causes it. This is
generally the most time-consuming step.
5.Understand the program
In order to understand a bug in a program, you must have some understanding of the
program.
If you wrote the program, then you presumably understand it. If not, then you have more
serious problems.
If you didn't write the program, you need to grasp its general structure. Most programs
are organized in a fairly sensible fashion, once you know the general approach. If you
are lucky, the general approach is documented, or you can ask the original designer.
6.Locate the bug
The next step is to locate the bug in the program source code.
There are two source code locations which you need to consider: the code which causes
the visible incorrect behaviour, and the code which is actually incorrect. It's fairly
common for these to be the same pieces of code. However, it's also fairly common for
these to be in different parts of the program. A typical example of this is when an error in
one part of the program causes memory corruption which leads to visible bad behaviour
in a completely different part of the program. Do not let your eagerness to fix the bug
mislead you into thinking that the code which directly causes the bad behaviour is
actually incorrect.
7.Locate the error
Now that you have found the code which causes the bad behaviour, you need to identify
the actual coding error. Often they are the same code--that is, the coding error directly
causes the bad behaviour. However, you should always consider the possibility that the
actual error is elsewhere.
For example, the routine which causes the bad behaviour may be behaving correctly,
but be called with bad input, or at the wrong time. A coding error elsewhere may cause a
data structure to hold unreasonable values. Another possibility is bad user input.
The fix in such cases may be two-fold. You should, of course, fix the code which called
the routine incorrectly or otherwise created the bad input data. In the case of bad user
input, you should validate the input. In addition, however, you may want to add checks to
the code which used the values. It should check for unreasonable input, and report an
error or otherwise handle the error without causing invalid behaviour.
8.Fix the bug
The final step in the debugging process is, of course, to fix the bug. I won't discuss this
step in detail, as fixing a bug is where you leave the debugging phase and return to
programming. I'll just mention a couple of points.
If you want a program which can be maintained in the future, then make sure you fix the
bug in the right way. This means making a fix which fits in with the rest of the program,
and which fixes all aspects of the problem, without introducing any new problems. Don't
forget to update any relevant documentation.
In some cases you may need a quick patch to fix an immediate problem. There is
nothing wrong with doing that, as long as you take the time afterward to go back and
make the right fix.
Obviously, always test any fix you make by ensuring that you can no longer replicate the
bad behaviour. Don't forget to make sure that the program continues to pass its test
suites. Consider extending the test suites to detect the case which you just fixed, to
make sure it doesn't reappear.
9.Learn From the Bug
After you fix the bug, consider whether there is anything you can learn from it. Here are
some things to think about:
Does the same programming error occur anywhere else in the program?
What new problems might be introduced by the bug fix?
How could this error have been prevented? What could you have done differently
such that the bug was not created in the first place? Even some excellent
programmers repeatedly make characteristic errors; are there types of
programming where you need to exercise particular care?
If you didn't find the bug yourself, could it have been detected sooner? Do your
testing procedures need improvement? If you have not already done so, can you
automate the testing? Would it have been possible to use automated code
inspection tools to find the error?
7. OBSERVATIONS :- Studied how to debug computer system carefully and

performed it.

Computer Hardware Installation and Maintenance Lab Manual

Diunggah oleh

Informasi Dokumen

Deskripsi Asli:

Hak Cipta

Format Tersedia

Bagikan dokumen Ini

Bagikan atau Tanam Dokumen

Opsi Berbagi

Apakah menurut Anda dokumen ini bermanfaat?

Apakah konten ini tidak pantas?

Hak Cipta:

Format Tersedia

Computer Hardware Installation and Maintenance Lab Manual

Diunggah oleh

Hak Cipta:

Format Tersedia

Government Girls’ Polytechnic, Bilaspur

Name of the Lab: Hardware & Maintenance Lab

Practical : Computer Hardware Installation and

Class: 3rd Semester ( ET&T )

Teachers Assessment: 40 End Semester Examination: 100

1. OBJECTIVE :- Troubleshooting symptom failures in motherboard.

2. HARDWARE & SYSTEM SOFTWARE REQUIRED :- Motherboard of computer

4. THEORY :- The Five Basic Elements Of Computer System Are

And The Basic Element Of Your Computer System is Us -

Elements Computer System.

Because we are the five basic elements of your computer system.

Arithmetic and Logical Unit

5. FLOW CHART (IF REQUIRED) :- NA

6. PROGRAM INPUTS & OUTPUT :- NA

7. OBSERVATIONS :- Different elements of computer system are studied.

1. OBJECTIVE :- Identify different beep codes and error codes.

2. HARDWARE & SYSTEM SOFTWARE REQUIRED :- Computer System

4. THEORY :- POST ABCs

AMI BIOS beep codes

Beep Code Descriptions

AWARD BIOS beep codes

Beep Code Description

IBM BIOS beep codes

Beep Code Description

5. FLOW CHART (IF REQUIRED) :- NA

6. PROGRAM INPUTS & OUTPUT :- NA

1. OBJECTIVE :- Identification of different motherboards & CPU’s.

2. HARDWARE & SYSTEM SOFTWARE REQUIRED :- different motherboards &

4. THEORY :- PC Mainboard Identification

The ―Lookatit‖ Method…

Figure 1A – Two model numbers on same board, on side of ISA slot

Figure 1B – MB8500TVX-A surface marking

6. PROGRAM INPUTS & OUTPUT :- NA

7. OBSERVATIONS :- Different elements of computer system are studied.

Figure 1C – Board ID between ISA slots

Figure 1C – Board ID between ISA slots

Figure 1D – Board ID on edge of board, near cache slot

5. FLOW CHART (IF REQUIRED) :- NA

6. PROGRAM INPUTS & OUTPUT :- NA

7. OBSERVATIONS :- Different motherboards of computer system are studied

1. OBJECTIVE :- Troubleshooting symptom failures in motherboard.

2.HARDWARE & SYSTEM SOFTWARE REQUIRED :- Motherboard of

4. THEORY :- A computer motherboard is one of the most hardest pieces

Reasons a motherboard fails

A Motherboard can fail for a number of reasons:

Electricity and voltage spikes

How to troubleshoot a Windows PC Motherboard.

If your system keeps crashing after a recovery then it is probably the

For Notebooks - perform a hard reset.

Perform Diagnostics test.

Perform an MSCONFIG if your computer has it.

If the problem persists then send in for service.

Check error messages in Event Viewer. Start / Settings / Control Panel /

5. FLOW CHART (IF REQUIRED) :- NA

6. PROGRAM INPUTS & OUTPUT :- NA

7. OBSERVATIONS :- Different methods of troubleshooting motherboard

1. OBJECTIVE :- Troubleshooting symptom failures in FDDI.

2. HARDWARE & SYSTEM SOFTWARE REQUIRED :- FDDI network

4. THEORY :- The Fiber Distributed Data Interface (FDDI) standard was

Although FDDI implementations are not as common as Ethernet or Token Ring,

Table 5-1 Media Problems: FDDI

2. If the show interfaces fddi command

3. If the interface and line protocol are up, make