Afrikaans
Akan
Albanian
Amharic
Armenian
Azerbaijani
Basque
Belarusian
Bemba
Bengali
Bihari
Bosnian
Breton
Bulgarian
Cambodian
Catalan
Cebuano
Cherokee
Chichewa
Chinese (Simplified)
Chinese (Traditional)
Corsican
Croatian
Czech
Danish
Dutch
English
Esperanto
Estonian
Ewe
Faroese
Filipino
Finnish
French
Frisian
Ga
Galician
Georgian
German
Greek
Guarani
Gujarati
Haitian Creole
Hausa
Hawaiian
Hebrew
Hindi
Hmong
Hungarian
Icelandic
Igbo
Indonesian
Interlingua
Irish
Italian
Japanese
Javanese
Kannada
Kazakh
Kinyarwanda
Kirundi
Kongo
Korean
Krio (Sierra Leone)
Kurdish
Kurdish (Soranî)
Kyrgyz
Laothian
Latin
Latvian
Lingala
Lithuanian
Lozi
Luganda
Luo
Luxembourgish
Macedonian
Malagasy
Malay
Malayalam
Maltese
Maori
Marathi
Mauritian Creole
Moldavian
Mongolian
Myanmar (Burmese)
Montenegrin
Nepali
Nigerian Pidgin
Northern Sotho
Norwegian
Norwegian (Nynorsk)
Occitan
Oriya
Oromo
Pashto
Persian
Polish
Portuguese (Brazil)
Portuguese (Portugal)
Punjabi
Quechua
Romanian
Romansh
Runyakitara
Russian
Samoan
Scots Gaelic
Serbian
Serbo-Croatian
Sesotho
Setswana
Seychellois Creole
Shona
Sindhi
Sinhalese
Slovak
Slovenian
Somali
Spanish
Spanish (Latin American)
Sundanese
Swahili
Swedish
Tajik
Tamil
Tatar
Telugu
Thai
Tigrinya
Tonga
Tshiluba
Tumbuka
Turkish
Turkmen
Twi
Uighur
Ukrainian
Urdu
Uzbek
Vietnamese
Welsh
Wolof
Xhosa
Yiddish
Yoruba
Zulu
Now we've seen all the key components
to get our computer running.
The last thing we'll go over is
how our devices talk to each other.
We know how programs execute
from our hard drive to our CPU,
but how do other things like a mouse click or
a keyboard press gets sent to our CPU for processing?
These are fairly basic devices.
They don't contain any instructions that
our CPU knows how to read.
If you just clicked on a key from your keyboard,
you'd only be sending a bite to the CPU.
The CPU doesn't know what this is
because it doesn't have
instructions on how to deal with it.
Turns out our devices also use
programs to tell the CPU how to run them.
These programs are called services or drivers.
The drivers contain the instructions
our CPU needs to understand
external devices like keyboards, webcams, printers.
Our CPU doesn't know that
there is a device that it can talk to.
It has to connect to something called
the BIOS or basic input output services.
The BIOS is software that helps initialize
the hardware in our computer and
gets our operating system up and running.
Unlike the programs, you're probably used to
running a web browser or operating system.
The bios isn't stored on a hard drive.
Our motherboard stores the bios in a special type of
memory called the read only memory chip or ROM chip.
Unlike RAM, ROM is non-volatile,
meaning it won't erase
the data if the computer is turned off.
Once the operating system loads,
we're able to load drivers from
non-essential devices directly from the hard drive.
In today's system there's
another player for bios called UEFI,
which stands for Unified Extensible Firmware Interface.
UEFI performs the same function
of starting your computer as a traditional BIOS,
but it's more modern and has
better compatibility and support for new hardware.
Most hardware out there today comes with UEFI built in.
Eventually, UEFI will become the predominant BIOS.
When you turn on a computer,
you might notice a beeping from time-to-time.
Our computers run a test to make
sure all the hardware is working correctly.
This is called a power-on self-test or POST.
The bios runs it when you boot up your computer.
The POST figures out what hardware is on the computer.
It happens before the BIOS initializes
any hardware or loads up essential drivers.
If there's an issue with anything at that point,
there's no way to display it on the screen
since things like the video driver haven't been loaded.
Instead, the computer can
usually produce a series of beeps,
almost like Morse code,
which will help identify the problem.
Different manufacturers have different beep codes.
If you computer successfully boots up,
you may hear a single beep.
If you hear two beeps,
it could mean a POST error.
It's best to refer to your motherboard manual
to find out what each code means.
Also, you should know that
not all machines have built-in speakers.
Don't worry if your computer boots without a beep.
If it does have a built-in speaker,
being able to distinguish what the beep codes mean is
an extremely helpful tool
when troubleshooting boot issues.
One last thing, we will discuss our BIOS settings.
There's a special chip on
our motherboard called the CMOS chip.
It stores basic data about boosting your computer,
like the date, time,
and how you want it to start up.
You can change these settings by booting
into CMOS or BIOS settings menu.
It varies on different computers,
but usually when you boot the computer,
there will be a quick screen that tells you
what button to push to get into the settings.
From there, you can change
the basic BIOS settings of your machine.
In an IT support role,
you might interact with the BIOS
more often than you think.
BIOS settings control which devices to boot to.
In an IT role, you might need to
change the settings more often than not.
A frequently performed IT task
is the reimaging of a computer.
The term refers to a disk image,
which is a copy of an operating system.
The process of reimaging involves
wiping and installing an operating system.
This procedure is typically performed using
a program that stored on some external device,
like a USB memory stick or a CD ROM,
or even a server accessible through the network.
To access these programs and perform the re-image,
you will need to use the bios to tell the computer to
boot up from that external device.
Can't find what you're looking for?
Get subtitles in any language from opensubtitles.com, and translate them here.