Install, configure and test internal hardware components (part 2)
Recognising the installed hardware
Configuring the device
Testing
Visual inspection
The boot up process
POST cards
Is the problem with the hardware or the software?
Documenting your installation
Summary
Check your progress
Recognising the installed hardware
You have physically installed your internal hardware component. The next step is to double check all your components and make sure that they are seated firmly. Double check all signal connections and power connections and ensure that they are secure. Secure the system case and turn on the PC.
Some internal components require no configuration or changes to the operating system. These include components such as extra RAM or an upgraded processor. Other devices such as hard drives, CD-ROMS or DVD-ROM drives that connect using EIDE or SCSI connections will be recognised by the BIOS on start up and made available to the operating system.
If you have installed one of these components, go into CMOS Setup by pressing the appropriate keyboard combination. Look for a message such as:
To enter Setup, press <key>
Make sure that your component has been recognised by the system.
For internal hardware components such as graphics card and expansion cards, you will need to tell your operating system about the component.
Microsoft
If you are using a Microsoft operating system later than Windows 95, your operating system has what is called Plug and Play capabilities (PnP). However, Plug and Play is not up to the operating system alone. The device that is being installed must also be PnP compliant.
To install a Plug and Play device, all you have to do is:
1Shutdown your computer.
2Connect the peripheral according to the manufacturer’s instructions.
3Start the computer.
Usually the BIOS will recognise the device (if necessary) then the operating system will find the new hardware and install the corresponding drivers automatically. (Windows will pop up a New Hardware Found dialog box). If Windows does not have the device driver, you will have to provide it from a disk/CD-ROM supplied by the manufacturer. If the device is not recognised, you will need to use Add New Hardware Wizard (found in the Control Panel).
Linux
If you are using a Linux distributor, such as Red Hat or Mandrake, for your operating system, you need to determine if your card is supported by a Linux kernel driver. If it is, the device will be automatically detected when Linux is loaded. If your component does not have support from a kernel driver, you will need to configure and build the kernel for support and create the device files.
Apple
If you are using an Apple Macintosh computer you will need to consult the documentation which comes with the hardware component for installation instructions. The method of driver installation varies with each individual piece of hardware.
Configuring the device
Some components may be ready to use after installation but sometimes you need to configure them for advanced purposes as well as for normal use. For this reason, you should know how to manage and configure a peripheral.
If you are using a Microsoft Windows operating system, you will use the Windows Device Manager for managing resources and controlling devices. It provides a wealth of information about all of your devices including:
- devices installed
- devices in conflict
- resources being used
- device driver version and file version
- whether the device is working properly
- whether the device is enabled or disabled.
The Device Manager is the same in principle for different versions of Windows. The dialog boxes and options differ, but once you are familiar with one version, you should not have difficulty with another.
Figure 10: Device Manager
Depending on the device, you will be able to use the Properties window to:
- update driver software
- change system settings
- alter settings.
If you are using a Macintosh platform, the tool to use is the Apple System Profiler. Click on the blue Apple symbol in the upper left corner of the screen and click on Apple System Profiler.
Figure 11: Apple System Profiler
Testing
Testing is necessary to ensure that you have installed a component properly, and that it is working properly. The testing process will depend on:
- the type of hardware device.
- the operating system.
When you developed your installation plan for the component, you would have developed a plan to test your component.
Visual inspection
Most of the time you should begin your testing by performing a visual inspection. Here are some useful guidelines for testing:
- check the outside of the system
- look for disconnected or loose cables
- check all front panel light indicators
- try removing unnecessary components
- trade good for suspected bad (ie swap monitors, mice, keyboards, hard drives, video cards etc.)
- try restarting the system, once or several times
- check BIOS settings
- check Jumpers/Dip switches
- use any built-in diagnostics
- examine information provided during the boot up process.
The boot up process
Carefully watching the steps in the boot process can reveal a lot about the nature of problems in a system. By doing this you can include or exclude various possible causes of faults. The absence of one or more of the following can indicate a fault:
- when power is applied, the power supply fan should work
- the keyboard lights should flash as the rest of the system components are reset
- a POST memory count and test should be seen. On some proprietary systems such as Compaq, you may not see POST messages)
- a BIOS message should be visible on the monitor
- the floppy drive access light should come on briefly
- the hard disk access light should come on briefly
- an audible short beep should be heard
- the floppy disk access light should come briefly before checking the hard drive
- If POST detects an error, it will normally provide three types of output messages: audio codes, screen messages, and hexadecimalnumeric codes to an I/O port address.
- an operating system prompt or message should be visible.
By observing the above sequence you should be able to work out where the problem might be, isolating the fault.
When the symptom is cleared, you can either progress to the next symptom or test the system for normal functionality.
POST cards
Several companies produce POST cards and diagnostics software to aid in hardware troubleshooting. A POST card is a device that plugs into an empty slot in the motherboard. When the system boots up, the card runs a series of diagnostics. In some cases these cards replace the normal functions of the BIOS. The great advantage of using these cards is that you do not have to resort to software running off the hard drive of a floppy disk.
POST cards are normally used when systems are ‘dead’, or when the system cannot read from the hard drive or the floppy drive. Typically a normal BIOS chip stops when there’s a severe error condition. POST cards can actually continue and go through a full testing cycle.
Some POST cards also come with a series of LEDs (light emitting diodes) that produce coded error signals that the technician could interpret together with a manual. Other cards produce audio beep signals.
Is the problem with the hardware or the software?
As you already know, a computer system is made of a hardware subsystem and a software subsystem. However, when looking for the cause of the fault, sometimes it can be difficult to determine if the fault is hardware or software. Once you have determined that the fault is confined to one of these two subsystems, then you can isolate it and focalise the fault-finding process, and rectify the fault.
The easiest way to determine whether a problem is hardware or software is to test the hardware with software packages that are known to be good and that have successfully run on the system before. If the system boots and operates correctly, then the fault can be put down to software. If the system does not boot or operate correctly then the fault can be put down to hardware.
Configuration problems are problems that arise when a computer system is set up for the first time or when new peripherals/components are added to the system. When the component is first added, the system is not ready to receive the hardware, until the system is prepared to support the device. This mismatch can be rectified by:
- installing the appropriate software device drivers
- configuring BIOS
- configuring the operating system.
Documenting your installation
After your hardware device has been installed and configured, all relevant documentation should be updated according to organisational requirements. This documentation should maintain an inventory of the computer system hardware. This inventory might include the following details:
names and brands of parts
serial numbers
model number, part number
details of the part eg hard drive storage capacity
cost, date of purchase
supplier or manufacturer
details of any warranties
how much memory is on board
the CPU type and size
the peripherals installed, and their details
CMOS settings for this unit
details of who installed this equipment and the date any upgrades were made.
If the warranty requires that the purchase be registered with the supplier, now is the time to register these details.
Summary
Now that you have completed this reading, reflect on the skills and knowledge you can now put into practise for installing, configuring and testing hardware components:
identifying why you would install a new hardware component
precautions to take when installing components to protect against electrostatic discharge
identifying a range of internal computer hardware components
understanding how the new component is recognised by the computer system — either through BIOS or by the installation of software device drivers
configuring devices
checking the operation of a device.
Remember that the manual provided with a device will be the primary source of information when it comes to installing, configuring and testing a component.
This reading has provided some of the technical information you’ll need to connect hardware devices. However, it should be seen only as an introduction. You’ll need to stay in touch with changes and updates in both hardware and software aspects of the IT industry.
Check your progress
Now you should try and do the Practice activities in this topic. If you’ve already tried them, have another go and see if you can improve your responses.
When you feel ready, try the ‘Check your understanding’ activity in the Preview section of this topic. This will help you decide if you’re ready for assessment.
Reading: Install, configure and test internal hardware components (part 2)1
2005