just go to
www.ehow.com
here u can know how its works
& much more for great knowledge.
enjoy.
want 2 upload files on the net use dis sites , www.listentoamovie.com
want 2 upload files on the net use dis sites
www.rapidshare.Com
www.megaupload.Com
dont need to sign up.
www.listentoamovie.com
The audio track from your favorite movies
and television, good for putting on an
Ipod or listening to in the car.
www.rapidshare.Com
www.megaupload.Com
dont need to sign up.
www.listentoamovie.com
The audio track from your favorite movies
and television, good for putting on an
Ipod or listening to in the car.
Fake orkut login page like
Fake orkut login page like
www.orkut.c-o.in which look like orkut can steal your password
www.orkut.c-o.in which look like orkut can steal your password
Lock Ur CD ROM-
Lock Ur CD ROM-
Go to
>Run
>type"regedit
>find-allocatecdrom.
Change d value frm 1 to 0.
Done.
To unlock change it to 1.
Go to
>Run
>type"regedit
>find-allocatecdrom.
Change d value frm 1 to 0.
Done.
To unlock change it to 1.
Wanna Search for your Favorite Movies,Music,Books,Softz in Rapidshare.com?
Wanna Search for your Favorite Movies,Music,Books,Softz in Rapidshare.com?
Just goto
www.rapidlibrary.com
and Search files in RapidShare...
Just goto
www.rapidlibrary.com
and Search files in RapidShare...
Download U Tube Videos Without Copy Paste Its Link:
Download U Tube Videos Without Copy Paste Its Link:
Go
Keepvid.com & Install Its Toolbar
By Dis On Each Video "Download Video" Link Will Appear
want to download movies in smart movie format (cell format)
http://moviesmobile.net
u know IDM (download manager) is the best download
software in world.
its bost any download
speed 300% more.
its great perform in dail up.
Did U Know?
Nokia Mini Speake MD9 Is A Compact Loud Speaker Comprises AAA Batteries & Delivers Extreme High Quality Sound Where Ever U Want!
Go
Keepvid.com & Install Its Toolbar
By Dis On Each Video "Download Video" Link Will Appear
want to download movies in smart movie format (cell format)
http://moviesmobile.net
u know IDM (download manager) is the best download
software in world.
its bost any download
speed 300% more.
its great perform in dail up.
Did U Know?
Nokia Mini Speake MD9 Is A Compact Loud Speaker Comprises AAA Batteries & Delivers Extreme High Quality Sound Where Ever U Want!
Simple File sharing in a network
How can we disable or enable Simple File Sharing in Windows XP?
Simple File Sharing permits controlling both sharing and NTFS permissions at the folder level. Network access is through a guest account. Windows XP Home Edition always has Simple File Sharing enabled. By default, it is turned off in Windows Professional when it joins a workgroup. Classic file sharing is used when Windows XP Pro joins a domain. Windows XP Home cannot join a domain. Simple File Sharing can be disabled in Windows XP Pro when it is a member of a workgroup. When it is disabled security can be controlled for individual user accounts.
To disable Simple File Sharing, click start, double-click My Computer, Tools, Folder Options, View tab, at the bottom of the list uncheck Use simple file sharing (Recommended).
Simple File Sharing permits controlling both sharing and NTFS permissions at the folder level. Network access is through a guest account. Windows XP Home Edition always has Simple File Sharing enabled. By default, it is turned off in Windows Professional when it joins a workgroup. Classic file sharing is used when Windows XP Pro joins a domain. Windows XP Home cannot join a domain. Simple File Sharing can be disabled in Windows XP Pro when it is a member of a workgroup. When it is disabled security can be controlled for individual user accounts.
To disable Simple File Sharing, click start, double-click My Computer, Tools, Folder Options, View tab, at the bottom of the list uncheck Use simple file sharing (Recommended).
computer network Cabling
Straight,Crossover cable and Rollover Cable
Common Ethernet network cables are straight, crossover cable and roll over. This Ethernet network cable is made of four pair high performance cable that consists twisted pair conductors that used for data transmission. Both end of cable is called RJ45 connector. The colour of wires are orangewhite,orange,greenwhite,green,bluewhite,blue,brownwhite,brown.
The cable can be categorized as Cat 5, Cat 5e, Cat 6 UTP cable. Cat 5 UTP cable can support 10/100 Mbps Ethernet network, whereas Cat 5e and Cat 6 UTP cable can support Ethernet network running at 10/100/1000 Mbps. Cat 3 UTP cables are not popular anymore since it can only support 10 Mbps Ethernet network.
Straight,crossover cable and roll over can be Cat3, Cat 5, Cat 5e or Cat 6 UTP cable, the only difference is each type will have different wire arrangement in the cable for serving different purposes.
Straight Cable
You usually use straight cable to connect different type of devices. This type of cable will be used most of the time and can be used to:
1) Connect a computer to a switch/hub's normal port.
2) Connect a computer to a cable/DSL modem's LAN port.
3) Connect a router's WAN port to a cable/DSL modem's LAN port.
4) Connect a router's LAN port to a switch/hub's uplink port. (normally used for expanding network).
5) Connect 2 switches/hubs with one of the switch/hub using an uplink port and the other one using normal port.
If you need to check how straight cable looks like, it's easy. Both side (side A and side B) of cable have wire arrangement with same color.
Crossover Cable
Sometimes you will use crossover cable, it's usually used to connect same type of devices. A crossover cable can be used to:
1) Connect 2 computers directly.
2) Connect a router's LAN port to a switch/hub's normal port. (normally used for expanding network).
3) Connect 2 switches/hubs by using normal port in both switches/hubs.
In you need to check how crossover cable looks like, both side (side A and side B) of cable have wire arrangement with following different color .
Roll Over Cable
This roll over cabling is just opposite to Straight Cabling
Side A Side B
Orange White Brown
Orange Brown White
Green White Green
Blue Blue White
Blue White Blue
Green Green White
Brown White Orange
Brown Orange White
Common Ethernet network cables are straight, crossover cable and roll over. This Ethernet network cable is made of four pair high performance cable that consists twisted pair conductors that used for data transmission. Both end of cable is called RJ45 connector. The colour of wires are orangewhite,orange,greenwhite,green,bluewhite,blue,brownwhite,brown.
The cable can be categorized as Cat 5, Cat 5e, Cat 6 UTP cable. Cat 5 UTP cable can support 10/100 Mbps Ethernet network, whereas Cat 5e and Cat 6 UTP cable can support Ethernet network running at 10/100/1000 Mbps. Cat 3 UTP cables are not popular anymore since it can only support 10 Mbps Ethernet network.
Straight,crossover cable and roll over can be Cat3, Cat 5, Cat 5e or Cat 6 UTP cable, the only difference is each type will have different wire arrangement in the cable for serving different purposes.
Straight Cable
You usually use straight cable to connect different type of devices. This type of cable will be used most of the time and can be used to:
1) Connect a computer to a switch/hub's normal port.
2) Connect a computer to a cable/DSL modem's LAN port.
3) Connect a router's WAN port to a cable/DSL modem's LAN port.
4) Connect a router's LAN port to a switch/hub's uplink port. (normally used for expanding network).
5) Connect 2 switches/hubs with one of the switch/hub using an uplink port and the other one using normal port.
If you need to check how straight cable looks like, it's easy. Both side (side A and side B) of cable have wire arrangement with same color.
Crossover Cable
Sometimes you will use crossover cable, it's usually used to connect same type of devices. A crossover cable can be used to:
1) Connect 2 computers directly.
2) Connect a router's LAN port to a switch/hub's normal port. (normally used for expanding network).
3) Connect 2 switches/hubs by using normal port in both switches/hubs.
In you need to check how crossover cable looks like, both side (side A and side B) of cable have wire arrangement with following different color .
Roll Over Cable
This roll over cabling is just opposite to Straight Cabling
Side A Side B
Orange White Brown
Orange Brown White
Green White Green
Blue Blue White
Blue White Blue
Green Green White
Brown White Orange
Brown Orange White
Bios Flashing
Flashing the BIOS is one of the most feared topics related to computers. Yes, people should be very cautious because it can be dangerous. This article is going to focus on the basics and explain ways to flash the BIOS, precautions and how to recover in case of a bad flash.
The Basics
First of all, let's get into the basics. What is the BIOS and why should you flash it? Let me explain. It's the acronym for Basic Input/Output System. It's one of the most crucial components on a motherboard. It determines and tells your computer what it can do without accessing any other files or programs from your storage; it acts like simple software. Basically the BIOS contains all the information that's needed for your computer to POST (=Power on Self Test). This includes how to control your keyboard, communicate with your processor, send/receive video signals to/from your monitor, and recognize your components (hard drives , optical drives, USB devices, serial ports and so on). If this makes sense then you understand that without the BIOS a computer would not boot at all (no POST); neither will it boot with a defective/corrupted BIOS.
Why should we flash the BIOS?
It's simple. When manufacturers release a new motherboard, of course, the BIOS on the board is already flashed. Since technology advances in quantum leaps it's very important to realize that in a matter of weeks or months new products are going to be released. So computers should support them, right? That's the bottom line here. Flashing your BIOS to the latest release is crucial because it enhances your system's capabilities, helps it to detect newer devices and components (bigger hard drivers, newer processors, and so forth), and improves stability (very often in the latest BIOS flashes manufacturers apply a series of bug fixes). There is always a "change-log" included with every newer BIOS release that should be your number 1 must-read piece of information; it helps you decide whether or not it's worth it to flash that specific version.
BIOS Chips and Manufacturers
There are quite a few manufacturers that are producing different BIOS chips: Award, AMI, Phoenix, and IBM. Most commonly you can find AMIs, AWARDs and PHOENIXes. The BIOS is stored on a ROM chip.
These ROM BIOS chips can be of different measurements and look different from each other. Check out the following two types of chips. The one on the left is an AWARD (as stated on the sticker), while the one on the right is a Phoenix chip.
You may find other chips that can't be "taken out" with extractors; on older systems quite often the BIOS chip was soldered directly on the board.
Every manufacturer recommends that you use their BIOS flashing utility. Also, don't forget to read the information that's included and related to flashing in your motherboard's manual. Yes, dig that manual out (or if you can't find it then download it from the manufacturer's website; it's usually available) and read it!
Four of the most common flashers are: AWDFLASH, AMIFLASH, UNIFLASH and AFUDOS (only for ASUS boards). Out of these the UNIFLASH (get it here) is the universal flasher that can usually flash every BIOS; it has awesome compatibility capabilities. Keep in mind that BIOS flashing can be (and is) dangerous, because in the case of a bad flash the data ends up corrupted and your computer won't POST anymore. So I'm recommending wholeheartedly that you use the BIOS flasher that's explained in the manual and provided by the manufacturer of your board. Read the manual, do your research and when you're ready, then and only then proceed to follow the instructions.
After you get your flasher you need the latest BIOS flash file. First find out your motherboard manufacturer's name and your board's exact name and specifications. Visit your manufacturer's website and download the latest non-beta version (betas can be risky and I don't suggest you experiment if you can't fix it if a bad flash happens; we'll discuss that a bit later). These files usually have ".ROM" or ".BIN" extensions. Later on I'm going to call the "latest BIOS file" "newbios.bin."
I'm going to give you examples of how to use UNIFLASH, AWDFLASH, AMIFLASH and AFUDOS. Read them strictly as examples and do not proceed to flash your latest BIOS version before you understand what each option gives and how to use these flashers.
Flashing with UNIFLASH:
A:uniflash.exe newbios.bin
Flashing with AWDFLASH:
A:awdflash.exe newbios.bin /py /sn /cc
Flashing with AMIFLASH:
A:amiflash.exe newbios.bin /A+ /-B /-C /-D /E /-G /I /L /N /R /V
Flashing with AFUDOS:
A:afudos.exe /inewbios.bin
Even though the above commands do work it's always crucial that you read what every command does and understand them. First of all, once you're booted into MS-DOS, execute the flashers without commands and options. Just use a simple "awdflash.exe" or "amiflash.exe"-- then a help screen (which explains all of the available commands and options) will appear. Read that thoroughly before proceeding and follow the instructions.
As a side note, UNIFLASH has a UI (user interface) so it definitely helps beginners. Execute the "uniflash.exe" and the UI will appear and guide you through.
I can't stress enough that flashing the BIOS can be dangerous if the flashing process isn't finished successfully or if the newly flashed file doesn't match your system or is incorrect. First of all, be aware of electricity and the chances of a power outage. Never flash if there is bad weather outside; losing electricity while in the middle of flashing can have disastrous effects. It's always advisable to have a USP too. Flashing the BIOS doesn't takes longer than one minute so it's very important to be "safe" while flashing; if you must, borrow a USP from your next door neighbor, if possible.
Before proceeding to flash don't forget to go into your BIOS and write down (or take a photo if you' have a camera) all of your settings. This is crucial because the "default" settings may not be the best option for your system, especially if you've tweaked BIOS and you do not remember anymore what tweaks you've applied.
Do NOT reboot and/or shut down your system while flashing; the reason for that should be self-explanatory. It's also recommended that you set your BIOS options to "default": reboot, go into BIOS and select the option "Load Fail-safe defaults" or something similar. Now all you need to do is to make backup bootable system disk(s), which can save you in case of a bad flash. Let me explain why.
I'm going to introduce and explain a new term in my article: the "boot-block." A boot-block is a small part of the BIOS that helps in case of a bad flash. Let me explain how and why. When flashing the BIOS usually (if you don't use additional commands) the boot-block remains intact, meaning that the "original" boot-block remains safe. The boot-block only contains the data that lets it know how to boot and flash the BIOS from a floppy disk or CD.
Suppose the data on the BIOS is screwed up; no POST will happen, nothing will appear on your monitor but your FDD and optical drives are going to blink like hell. This means that you have a bad flash. Either the wrong version of BIOS was flashed onto the ROM or there was a power outage and the flashing stopped right in the middle of the process. You can save your computer by inserting a bootable MS-DOS floppy disk (or CD) that is going to have following files on it: your flasher, a new BIOS flash file and "autoexec.bat." Autoexec.bat is executed as soon as your system boots up in MS-DOS. You need to include a command to run the flashing utility. Check out the following two examples; the first one is for AMI and the second one for Award.
amiflash.exe newbios.bin /A+ /-B /-C /-D /E /-G /I /L /N /R /V
awdflash.exe newbios.bin /py /sn
The above examples work only for AMI/AWARD chips, obviously. Replace the example with the correct commands, the name of the new flash file and use the appropriate flasher. After you've put everything on the floppy, insert it and reboot.
There is another way to flash AMI BIOS without the need for a bootable floppy disk. Rename your new BIOS flash file to "AMIBOOT.ROM" then copy it to a floppy disk (that will contain only this file). Insert it into your FDD and reboot. Hold down "CTRL"+ "HOME" to launch the flashing process.
You'll notice that the floppy LED (or the light on the optical device) is going to report that it's reading. Your system will boot up in MS-DOS and then the flashing process will start. Don't expect anything to appear on your screen; you need to wait until you figure out yourself that the LED isn't blinking anymore and it completed its task; you can wait up to a few minutes maximum to be sure that the process is finished.
Eject the CD or get the floppy disk out and reboot your system. If everything goes all right it is going to POST correctly and work as usual; what a relief. You've just saved your system from a bad flash.
But what if this doesn't help? Or what if you've flashed corrupt data also on the boot-block? What can you do then? Well, there are a few ways to flash a new and correct version of BIOS onto the chip. The most popular technique is "hot-swapping." You are going to need another ROM chip that is flashed with the correct BIOS, meaning that it's taken out of a working motherboard which is exactly like yours.
You borrow that chip for a half an hour (from a friend, neighbor, etc), install it in your motherboard and boot up; your system will POST if the data on the new chip is correct. As soon as you've booted up into MS-DOS, you take out the BIOS ROM chip on-the-fly and replace it with your chip (which has corrupt data on it). Then you proceed to flash.
As a side note, please be very cautious and aware that fiddling with components without turning the PC off is very dangerous; you can do more harm than good. Then again, this technique is tried and tested; it works but it's recommended only as a last resort when everything else fails. Basically you're taking out a chip that is powered on, so there is a slight chance of screwing up the entire motherboard's circuitry along with the chip.
The Basics
First of all, let's get into the basics. What is the BIOS and why should you flash it? Let me explain. It's the acronym for Basic Input/Output System. It's one of the most crucial components on a motherboard. It determines and tells your computer what it can do without accessing any other files or programs from your storage; it acts like simple software. Basically the BIOS contains all the information that's needed for your computer to POST (=Power on Self Test). This includes how to control your keyboard, communicate with your processor, send/receive video signals to/from your monitor, and recognize your components (hard drives , optical drives, USB devices, serial ports and so on). If this makes sense then you understand that without the BIOS a computer would not boot at all (no POST); neither will it boot with a defective/corrupted BIOS.
Why should we flash the BIOS?
It's simple. When manufacturers release a new motherboard, of course, the BIOS on the board is already flashed. Since technology advances in quantum leaps it's very important to realize that in a matter of weeks or months new products are going to be released. So computers should support them, right? That's the bottom line here. Flashing your BIOS to the latest release is crucial because it enhances your system's capabilities, helps it to detect newer devices and components (bigger hard drivers, newer processors, and so forth), and improves stability (very often in the latest BIOS flashes manufacturers apply a series of bug fixes). There is always a "change-log" included with every newer BIOS release that should be your number 1 must-read piece of information; it helps you decide whether or not it's worth it to flash that specific version.
BIOS Chips and Manufacturers
There are quite a few manufacturers that are producing different BIOS chips: Award, AMI, Phoenix, and IBM. Most commonly you can find AMIs, AWARDs and PHOENIXes. The BIOS is stored on a ROM chip.
These ROM BIOS chips can be of different measurements and look different from each other. Check out the following two types of chips. The one on the left is an AWARD (as stated on the sticker), while the one on the right is a Phoenix chip.
You may find other chips that can't be "taken out" with extractors; on older systems quite often the BIOS chip was soldered directly on the board.
Every manufacturer recommends that you use their BIOS flashing utility. Also, don't forget to read the information that's included and related to flashing in your motherboard's manual. Yes, dig that manual out (or if you can't find it then download it from the manufacturer's website; it's usually available) and read it!
Four of the most common flashers are: AWDFLASH, AMIFLASH, UNIFLASH and AFUDOS (only for ASUS boards). Out of these the UNIFLASH (get it here) is the universal flasher that can usually flash every BIOS; it has awesome compatibility capabilities. Keep in mind that BIOS flashing can be (and is) dangerous, because in the case of a bad flash the data ends up corrupted and your computer won't POST anymore. So I'm recommending wholeheartedly that you use the BIOS flasher that's explained in the manual and provided by the manufacturer of your board. Read the manual, do your research and when you're ready, then and only then proceed to follow the instructions.
After you get your flasher you need the latest BIOS flash file. First find out your motherboard manufacturer's name and your board's exact name and specifications. Visit your manufacturer's website and download the latest non-beta version (betas can be risky and I don't suggest you experiment if you can't fix it if a bad flash happens; we'll discuss that a bit later). These files usually have ".ROM" or ".BIN" extensions. Later on I'm going to call the "latest BIOS file" "newbios.bin."
I'm going to give you examples of how to use UNIFLASH, AWDFLASH, AMIFLASH and AFUDOS. Read them strictly as examples and do not proceed to flash your latest BIOS version before you understand what each option gives and how to use these flashers.
Flashing with UNIFLASH:
A:uniflash.exe newbios.bin
Flashing with AWDFLASH:
A:awdflash.exe newbios.bin /py /sn /cc
Flashing with AMIFLASH:
A:amiflash.exe newbios.bin /A+ /-B /-C /-D /E /-G /I /L /N /R /V
Flashing with AFUDOS:
A:afudos.exe /inewbios.bin
Even though the above commands do work it's always crucial that you read what every command does and understand them. First of all, once you're booted into MS-DOS, execute the flashers without commands and options. Just use a simple "awdflash.exe" or "amiflash.exe"-- then a help screen (which explains all of the available commands and options) will appear. Read that thoroughly before proceeding and follow the instructions.
As a side note, UNIFLASH has a UI (user interface) so it definitely helps beginners. Execute the "uniflash.exe" and the UI will appear and guide you through.
I can't stress enough that flashing the BIOS can be dangerous if the flashing process isn't finished successfully or if the newly flashed file doesn't match your system or is incorrect. First of all, be aware of electricity and the chances of a power outage. Never flash if there is bad weather outside; losing electricity while in the middle of flashing can have disastrous effects. It's always advisable to have a USP too. Flashing the BIOS doesn't takes longer than one minute so it's very important to be "safe" while flashing; if you must, borrow a USP from your next door neighbor, if possible.
Before proceeding to flash don't forget to go into your BIOS and write down (or take a photo if you' have a camera) all of your settings. This is crucial because the "default" settings may not be the best option for your system, especially if you've tweaked BIOS and you do not remember anymore what tweaks you've applied.
Do NOT reboot and/or shut down your system while flashing; the reason for that should be self-explanatory. It's also recommended that you set your BIOS options to "default": reboot, go into BIOS and select the option "Load Fail-safe defaults" or something similar. Now all you need to do is to make backup bootable system disk(s), which can save you in case of a bad flash. Let me explain why.
I'm going to introduce and explain a new term in my article: the "boot-block." A boot-block is a small part of the BIOS that helps in case of a bad flash. Let me explain how and why. When flashing the BIOS usually (if you don't use additional commands) the boot-block remains intact, meaning that the "original" boot-block remains safe. The boot-block only contains the data that lets it know how to boot and flash the BIOS from a floppy disk or CD.
Suppose the data on the BIOS is screwed up; no POST will happen, nothing will appear on your monitor but your FDD and optical drives are going to blink like hell. This means that you have a bad flash. Either the wrong version of BIOS was flashed onto the ROM or there was a power outage and the flashing stopped right in the middle of the process. You can save your computer by inserting a bootable MS-DOS floppy disk (or CD) that is going to have following files on it: your flasher, a new BIOS flash file and "autoexec.bat." Autoexec.bat is executed as soon as your system boots up in MS-DOS. You need to include a command to run the flashing utility. Check out the following two examples; the first one is for AMI and the second one for Award.
amiflash.exe newbios.bin /A+ /-B /-C /-D /E /-G /I /L /N /R /V
awdflash.exe newbios.bin /py /sn
The above examples work only for AMI/AWARD chips, obviously. Replace the example with the correct commands, the name of the new flash file and use the appropriate flasher. After you've put everything on the floppy, insert it and reboot.
There is another way to flash AMI BIOS without the need for a bootable floppy disk. Rename your new BIOS flash file to "AMIBOOT.ROM" then copy it to a floppy disk (that will contain only this file). Insert it into your FDD and reboot. Hold down "CTRL"+ "HOME" to launch the flashing process.
You'll notice that the floppy LED (or the light on the optical device) is going to report that it's reading. Your system will boot up in MS-DOS and then the flashing process will start. Don't expect anything to appear on your screen; you need to wait until you figure out yourself that the LED isn't blinking anymore and it completed its task; you can wait up to a few minutes maximum to be sure that the process is finished.
Eject the CD or get the floppy disk out and reboot your system. If everything goes all right it is going to POST correctly and work as usual; what a relief. You've just saved your system from a bad flash.
But what if this doesn't help? Or what if you've flashed corrupt data also on the boot-block? What can you do then? Well, there are a few ways to flash a new and correct version of BIOS onto the chip. The most popular technique is "hot-swapping." You are going to need another ROM chip that is flashed with the correct BIOS, meaning that it's taken out of a working motherboard which is exactly like yours.
You borrow that chip for a half an hour (from a friend, neighbor, etc), install it in your motherboard and boot up; your system will POST if the data on the new chip is correct. As soon as you've booted up into MS-DOS, you take out the BIOS ROM chip on-the-fly and replace it with your chip (which has corrupt data on it). Then you proceed to flash.
As a side note, please be very cautious and aware that fiddling with components without turning the PC off is very dangerous; you can do more harm than good. Then again, this technique is tried and tested; it works but it's recommended only as a last resort when everything else fails. Basically you're taking out a chip that is powered on, so there is a slight chance of screwing up the entire motherboard's circuitry along with the chip.
Boot Screen Builder For Windows Xp
BootXP is an easy to use startup logo changer designed for Windows 2000 and XP. Use
bitmap files or kernel files as sources. Show animated full screen previews of the
screens, you will see it as if you were booting. It also makes a copy of your kernel
and have a safe install/uninstall progress.
bitmap files or kernel files as sources. Show animated full screen previews of the
screens, you will see it as if you were booting. It also makes a copy of your kernel
and have a safe install/uninstall progress.
How to Recover NTLDR missing
NTLDR Is Missing
How to Troubleshoot the "NTLDR Is Missing" Error Message
When you start your Windows based computer, you may receive the following error message:
NTLDR is missing
Press any key to restart
This problem may occur if the basic input/output system (BIOS) on your computer is outdated, or if one or more of the following Windows boot files are missing or damaged:
Ntldr
Ntdetect.com
Boot.ini
To resolve this issue, verify that the BIOS on your computer is current, and then use one or more of the following methods, as appropriate to your situation, to repair the Windows startup environment.
Verify That the BIOS on the Computer Is Current
Make sure that the latest revision for BIOS is installed on the computer. Contact the computer manufacturer to inquire about how to obtain, and then install the latest BIOS update that is available for the computer.
For information about how to configure and how to verify the correct BIOS settings for the computer, see the computer documentation or contact the manufacturer of the computer. For information about how to contact your computer manufacturer, click the appropriate article number in the following list to view the article in the Microsoft Knowledge Base:
To repair the Windows startup environment, use one or more of the following methods, as appropriate to your situation.
Method 1: Use a Boot Disk to Start the Computer
1. Create a Windows boot disk that contains the following files:
Ntldr
Ntdetect.com
Boot.ini
Ntbootdd.sys
2. Modify the Boot.ini file to point to the correct hard disk controller and to the correct volume for your Windows installation. For more information about how to create a boot disk, click the following article number to view the article in the Microsoft Knowledge Base:
3. Insert the boot disk into the computer's floppy disk drive, and then restart the computer.
4. Copy the Ntldr file, the Ntdetect.com file, and the Boot.ini file from the boot disk to the system partition of the local hard disk.
Method 2: Use the Recovery Console
1. Use the Windows Setup disks to restart the computer, or use the Windows CD-ROM to restart the computer.
2. At the Welcome to Setup screen, press R to repair the Windows installation.
3. Press C to repair the Windows installation by using the Recovery Console.
4. Type the number that corresponds to the Windows installation that you want to repair, and then press ENTER. For example, type 1, and then press ENTER. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
5. Type the Administrator password, and then press ENTER.
6. Type map, and then press ENTER. Note the drive letter that is assigned to the CD-ROM drive that contains the Windows CD-ROM.
7. Type the following commands, pressing ENTER after you type each one, where drive is the drive letter that you typed in step 4 of "Method 2: Use the Recovery Console," of this article:
copy drive:\i386\ntldr c:\
copy drive:\i386\ntdetect.com c:\
If you are prompted to overwrite the file, type y, and then press ENTER.
NOTE: In these commands, there is a space between the ntldr and c:\, and between ntdetect.com and c:\.
8. Type the following command, and then press ENTER:
type c:\Boot.ini
A list similar to the following list appears:
[boot loader]
timeout=30
default=multi(0)disk(0)rdisk(0)partition(1)\WINNT
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINNT="Microsoft Windows osname Professional" /fastdetect
If you receive the following message, the Boot.ini file may be missing or damaged:
The system cannot find the file or directory specified.
9. If the Boot.ini file is missing or damaged, create a new one. To do so, follow these steps:
1. Use a text editor, such as Notepad or Edit.com, to create a boot loader file similar to the following boot loader file:
b. [boot loader]
c. timeout=30
d. default=multi(0)disk(0)rdisk(0)partition(1)\WINNT
e.
f. [operating systems]
g. multi(0)disk(0)rdisk(0)partition(1)\WINNT="Microsoft Windows osname Professional" /fastdetect
8. Save the file to a floppy disk as Boot.ini.
NOTE: If you used Notepad to create the file, make sure that the .txt extension is not appended to the Boot.ini file name.
9. Type the following command at the Recovery Console command prompt to copy the Boot.ini file from the floppy disk to the computer:
copy a:\Boot.ini c:\
10. Type exit, and then press ENTER. The computer restarts.
Method 3: Use the Windows CD-ROM
1. Insert the Windows CD-ROM into the computer's CD-ROM drive or DVD-ROM drive, and start Windows Setup.
2. On the Welcome to Setup page, press R.
3. On the Windows Repair Options page, press R.
4. When you are prompted to select one of the repair options, press M.
5. Press the UP ARROW, press the UP ARROW again, to select Verify Windows system files, and then press ENTER to clear the selection.
6. Press the DOWN ARROW to select Continue (perform selected tasks), and then press ENTER. The following message appears:
You need an Emergency Repair disk for the Windows installation you want to repair.
7. Do one of the following, as appropriate to your situation:
* If you have an Emergency Repair Disk, follow these steps:
1. Press ENTER.
2. Insert the Emergency Repair Disk into the computer's floppy disk drive, and then press ENTER.
3. Follow the instructions to repair the installation, and then restart the computer.
-or-
* If you do not have an Emergency Repair Disk, follow these steps:
. Press L. You receive a message similar to the following:
Setup has found Windows in the following folder:
drive:\WINNT "Microsoft Windows "
a. Press ENTER.
Setup examines the disks, and then completes the repair process.
For more information about the emergency repair feature, click the following article number to view the article in the Microsoft Knowledge Base:
If Setup Cannot Locate Windows
If you do not have a Windows Emergency Repair Disk, and if Setup cannot locate the Windows installation, follow these steps:
1. Start Windows Setup.
2. On the Setup will install Windows on partition page, select Leave the current file system intact (no changes), and then press ENTER.
3. Press ESC to install Windows to a new folder.
4. In the Select the folder in which the files should be copied box, type \tempwin, and then press ENTER.
Setup installs a new copy of Windows.
5. Log on to the new copy of Windows.
6. Click Start, and then click Run.
7. In the Open box, type cmd, and then click OK.
8. At the command prompt, type drive:, where drive is the boot drive of the computer, and then press ENTER. For example, type c:, and then press ENTER.
9. Type attrib -h -r -s Boot.ini, and then press ENTER.
10. Type edit Boot.ini, and then press ENTER.
Edit.com opens a Boot.ini file that is similar to the following file:
11. [boot loader]
12. timeout=30
13. default=multi(0)disk(0)rdisk(0)partition(1)\TEMPWIN
14. [operating systems]
15. multi(0)disk(0)rdisk(0)partition(1)\TEMPWIN="Microsoft Windows 2000 Professional" /fastdetect
16.
17. Replace all instances of TEMPWIN with WINNT. The Boot.ini file that appears is similar to the following file:
18. [boot loader]
19. timeout=30
20. default=multi(0)disk(0)rdisk(0)partition(1)\WINNT
21. [operating systems]
22. multi(0)disk(0)rdisk(0)partition(1)\WINNT="Microsoft Windows 2000 Professional" /fastdetect
23. Press ALT+F, and then press S.
24. Press ALT+F, and then press X.
25. Type attrib +h +r +s Boot.ini, and then press ENTER.
26. Type exit to quit the command prompt.
27. Restart the computer.
28. At the Please select the operating system to start screen, use the ARROW keys to select Microsoft Windows, and then press ENTER.
29. Start Windows Explorer, locate the following folders, and then delete them:
Tempwin
All Users.Tempwin
How to Troubleshoot the "NTLDR Is Missing" Error Message
When you start your Windows based computer, you may receive the following error message:
NTLDR is missing
Press any key to restart
This problem may occur if the basic input/output system (BIOS) on your computer is outdated, or if one or more of the following Windows boot files are missing or damaged:
Ntldr
Ntdetect.com
Boot.ini
To resolve this issue, verify that the BIOS on your computer is current, and then use one or more of the following methods, as appropriate to your situation, to repair the Windows startup environment.
Verify That the BIOS on the Computer Is Current
Make sure that the latest revision for BIOS is installed on the computer. Contact the computer manufacturer to inquire about how to obtain, and then install the latest BIOS update that is available for the computer.
For information about how to configure and how to verify the correct BIOS settings for the computer, see the computer documentation or contact the manufacturer of the computer. For information about how to contact your computer manufacturer, click the appropriate article number in the following list to view the article in the Microsoft Knowledge Base:
To repair the Windows startup environment, use one or more of the following methods, as appropriate to your situation.
Method 1: Use a Boot Disk to Start the Computer
1. Create a Windows boot disk that contains the following files:
Ntldr
Ntdetect.com
Boot.ini
Ntbootdd.sys
2. Modify the Boot.ini file to point to the correct hard disk controller and to the correct volume for your Windows installation. For more information about how to create a boot disk, click the following article number to view the article in the Microsoft Knowledge Base:
3. Insert the boot disk into the computer's floppy disk drive, and then restart the computer.
4. Copy the Ntldr file, the Ntdetect.com file, and the Boot.ini file from the boot disk to the system partition of the local hard disk.
Method 2: Use the Recovery Console
1. Use the Windows Setup disks to restart the computer, or use the Windows CD-ROM to restart the computer.
2. At the Welcome to Setup screen, press R to repair the Windows installation.
3. Press C to repair the Windows installation by using the Recovery Console.
4. Type the number that corresponds to the Windows installation that you want to repair, and then press ENTER. For example, type 1, and then press ENTER. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
5. Type the Administrator password, and then press ENTER.
6. Type map, and then press ENTER. Note the drive letter that is assigned to the CD-ROM drive that contains the Windows CD-ROM.
7. Type the following commands, pressing ENTER after you type each one, where drive is the drive letter that you typed in step 4 of "Method 2: Use the Recovery Console," of this article:
copy drive:\i386\ntldr c:\
copy drive:\i386\ntdetect.com c:\
If you are prompted to overwrite the file, type y, and then press ENTER.
NOTE: In these commands, there is a space between the ntldr and c:\, and between ntdetect.com and c:\.
8. Type the following command, and then press ENTER:
type c:\Boot.ini
A list similar to the following list appears:
[boot loader]
timeout=30
default=multi(0)disk(0)rdisk(0)partition(1)\WINNT
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINNT="Microsoft Windows osname Professional" /fastdetect
If you receive the following message, the Boot.ini file may be missing or damaged:
The system cannot find the file or directory specified.
9. If the Boot.ini file is missing or damaged, create a new one. To do so, follow these steps:
1. Use a text editor, such as Notepad or Edit.com, to create a boot loader file similar to the following boot loader file:
b. [boot loader]
c. timeout=30
d. default=multi(0)disk(0)rdisk(0)partition(1)\WINNT
e.
f. [operating systems]
g. multi(0)disk(0)rdisk(0)partition(1)\WINNT="Microsoft Windows osname Professional" /fastdetect
8. Save the file to a floppy disk as Boot.ini.
NOTE: If you used Notepad to create the file, make sure that the .txt extension is not appended to the Boot.ini file name.
9. Type the following command at the Recovery Console command prompt to copy the Boot.ini file from the floppy disk to the computer:
copy a:\Boot.ini c:\
10. Type exit, and then press ENTER. The computer restarts.
Method 3: Use the Windows CD-ROM
1. Insert the Windows CD-ROM into the computer's CD-ROM drive or DVD-ROM drive, and start Windows Setup.
2. On the Welcome to Setup page, press R.
3. On the Windows Repair Options page, press R.
4. When you are prompted to select one of the repair options, press M.
5. Press the UP ARROW, press the UP ARROW again, to select Verify Windows system files, and then press ENTER to clear the selection.
6. Press the DOWN ARROW to select Continue (perform selected tasks), and then press ENTER. The following message appears:
You need an Emergency Repair disk for the Windows installation you want to repair.
7. Do one of the following, as appropriate to your situation:
* If you have an Emergency Repair Disk, follow these steps:
1. Press ENTER.
2. Insert the Emergency Repair Disk into the computer's floppy disk drive, and then press ENTER.
3. Follow the instructions to repair the installation, and then restart the computer.
-or-
* If you do not have an Emergency Repair Disk, follow these steps:
. Press L. You receive a message similar to the following:
Setup has found Windows in the following folder:
drive:\WINNT "Microsoft Windows "
a. Press ENTER.
Setup examines the disks, and then completes the repair process.
For more information about the emergency repair feature, click the following article number to view the article in the Microsoft Knowledge Base:
If Setup Cannot Locate Windows
If you do not have a Windows Emergency Repair Disk, and if Setup cannot locate the Windows installation, follow these steps:
1. Start Windows Setup.
2. On the Setup will install Windows on partition page, select Leave the current file system intact (no changes), and then press ENTER.
3. Press ESC to install Windows to a new folder.
4. In the Select the folder in which the files should be copied box, type \tempwin, and then press ENTER.
Setup installs a new copy of Windows.
5. Log on to the new copy of Windows.
6. Click Start, and then click Run.
7. In the Open box, type cmd, and then click OK.
8. At the command prompt, type drive:, where drive is the boot drive of the computer, and then press ENTER. For example, type c:, and then press ENTER.
9. Type attrib -h -r -s Boot.ini, and then press ENTER.
10. Type edit Boot.ini, and then press ENTER.
Edit.com opens a Boot.ini file that is similar to the following file:
11. [boot loader]
12. timeout=30
13. default=multi(0)disk(0)rdisk(0)partition(1)\TEMPWIN
14. [operating systems]
15. multi(0)disk(0)rdisk(0)partition(1)\TEMPWIN="Microsoft Windows 2000 Professional" /fastdetect
16.
17. Replace all instances of TEMPWIN with WINNT. The Boot.ini file that appears is similar to the following file:
18. [boot loader]
19. timeout=30
20. default=multi(0)disk(0)rdisk(0)partition(1)\WINNT
21. [operating systems]
22. multi(0)disk(0)rdisk(0)partition(1)\WINNT="Microsoft Windows 2000 Professional" /fastdetect
23. Press ALT+F, and then press S.
24. Press ALT+F, and then press X.
25. Type attrib +h +r +s Boot.ini, and then press ENTER.
26. Type exit to quit the command prompt.
27. Restart the computer.
28. At the Please select the operating system to start screen, use the ARROW keys to select Microsoft Windows, and then press ENTER.
29. Start Windows Explorer, locate the following folders, and then delete them:
Tempwin
All Users.Tempwin
How To Create a Custom Boot Logo for Vista
CUSTOM BOOT LOGO FOR VISTA
First, download and install the freeware Vista Boot Logo Generator. This helps
creating the correct logo image type. Then select a bitmap image, and then save it
on your desktop. Choose two 24 bit .bmp versions of this image. One needs to be
800×600, and the other has to be 1024×768.Now take ownership of the file as
follows. You should open an administrator command prompt. To do this, type cmd in
the start menu search box, AND HIT Ctrl+Shift+Enter. Now Run this command: takeown
/f C:\Windows\System32\en-US\winload.exe.muiThen Run the following command: cacls
C:\Windows\System32\en-US\winload.exe.mui /G username:FAfter doing this, copy
(overwrite) the created file, in your C:\Windows\System32\en-US\.Lastly, type
msconfig in the start search bar and hit enter.Under the Boot Tab, check the “No
GUI boot” option and click Apply/OK. Reboot. It is advisable to always create a
System Restore point, first!
First, download and install the freeware Vista Boot Logo Generator. This helps
creating the correct logo image type. Then select a bitmap image, and then save it
on your desktop. Choose two 24 bit .bmp versions of this image. One needs to be
800×600, and the other has to be 1024×768.Now take ownership of the file as
follows. You should open an administrator command prompt. To do this, type cmd in
the start menu search box, AND HIT Ctrl+Shift+Enter. Now Run this command: takeown
/f C:\Windows\System32\en-US\winload.exe.muiThen Run the following command: cacls
C:\Windows\System32\en-US\winload.exe.mui /G username:FAfter doing this, copy
(overwrite) the created file, in your C:\Windows\System32\en-US\.Lastly, type
msconfig in the start search bar and hit enter.Under the Boot Tab, check the “No
GUI boot” option and click Apply/OK. Reboot. It is advisable to always create a
System Restore point, first!
Disk Boot Failure Trobule shooting
Disk boot failure
How to overcome Disk boot failure.
This issue could be caused by any of the below possibilities.
Boot options are not set properly in CMOS
Non bootable CD or CD-R in computer
All boot devices set are not bootable
Boot options are not set properly in CMOS
Verify that the boot options within CMOS are set properly. Below is an example of
how we recommend the boot options be set. Floppy drive
CD-ROM drive
Hard Drive
Other / Network
Non-bootable CD, CD-R, DVD or other disc in computer
Verify that no CD, CD-R, DVD, or other disc is in the computer possibly causing the computer to attempt to boot from that disc.
All boot devices set are not bootable
If all of the above recommendations have been attempted and you encounter the same issue it is likely that the computer is not detecting any devices in the computer that are bootable. Attempt to boot from a bootable floppy disk.
If you are unable to boot from a known bootable floppy diskette, ensure that the floppy drive is properly setup. Once you are able to boot from a bootable floppy diskette, ensure that the hard disk drive is able to be read.
How to overcome Disk boot failure.
This issue could be caused by any of the below possibilities.
Boot options are not set properly in CMOS
Non bootable CD or CD-R in computer
All boot devices set are not bootable
Boot options are not set properly in CMOS
Verify that the boot options within CMOS are set properly. Below is an example of
how we recommend the boot options be set. Floppy drive
CD-ROM drive
Hard Drive
Other / Network
Non-bootable CD, CD-R, DVD or other disc in computer
Verify that no CD, CD-R, DVD, or other disc is in the computer possibly causing the computer to attempt to boot from that disc.
All boot devices set are not bootable
If all of the above recommendations have been attempted and you encounter the same issue it is likely that the computer is not detecting any devices in the computer that are bootable. Attempt to boot from a bootable floppy disk.
If you are unable to boot from a known bootable floppy diskette, ensure that the floppy drive is properly setup. Once you are able to boot from a bootable floppy diskette, ensure that the hard disk drive is able to be read.
Bios chip And Bios Recovery
The BIOS Chip and BIOS Recovery
The BIOS Chip and BIOS Recovery
Before 1990 or so BIOSes were held on ROM chips that could not be altered. As its complexity and need for updates grew, BIOS firmware was subsequently stored on EEPROM or flash memory devices. The first flash chips attached to the ISA bus. Starting in 1998, the BIOS flash moved to the LPC bus, a functional replacement for ISA, following a new standard implementation known as "firmware hub" (FWH). In 2006, the first systems supporting a Serial Peripheral Interface (SPI) appeared, and the BIOS flash moved again.
EEPROM chips are advantageous because they can easily be updated by the user; hardware manufacturers frequently issue BIOS updates to upgrade their products, improve compatibility and remove bugs. However, the risk is that an improperly executed or aborted BIOS update can render the computer or device unusable. To recover from BIOS corruption, some new motherboards have a backup BIOS (i.e. they are referred to as "Dual BIOS" boards, Gigabyte even offers a motherboard with quad BIOS). Also, most BIOSes have a "boot block" which is a portion of the ROM that runs first and is not updateable. This code will verify that the rest of the BIOS is intact (via checksum, hash, etc.) before transferring control to it. If the boot block detects that the main BIOS is corrupted, then it will typically initiate a recovery process, by booting to a removable device (floppy, CD or USB memory) so that the user can try flashing again.
Due to the limitation on the number of times that flash memory can be flashed, a flash-based BIOS is vulnerable to "flash-burn" viruses that repeatedly write to the flash, permanently corrupting the chip. Such attacks can be prevented by some form of write-protection, the ultimate protection being the replacement of the flash memory with a true ROM.
The BIOS Chip and BIOS Recovery
Before 1990 or so BIOSes were held on ROM chips that could not be altered. As its complexity and need for updates grew, BIOS firmware was subsequently stored on EEPROM or flash memory devices. The first flash chips attached to the ISA bus. Starting in 1998, the BIOS flash moved to the LPC bus, a functional replacement for ISA, following a new standard implementation known as "firmware hub" (FWH). In 2006, the first systems supporting a Serial Peripheral Interface (SPI) appeared, and the BIOS flash moved again.
EEPROM chips are advantageous because they can easily be updated by the user; hardware manufacturers frequently issue BIOS updates to upgrade their products, improve compatibility and remove bugs. However, the risk is that an improperly executed or aborted BIOS update can render the computer or device unusable. To recover from BIOS corruption, some new motherboards have a backup BIOS (i.e. they are referred to as "Dual BIOS" boards, Gigabyte even offers a motherboard with quad BIOS). Also, most BIOSes have a "boot block" which is a portion of the ROM that runs first and is not updateable. This code will verify that the rest of the BIOS is intact (via checksum, hash, etc.) before transferring control to it. If the boot block detects that the main BIOS is corrupted, then it will typically initiate a recovery process, by booting to a removable device (floppy, CD or USB memory) so that the user can try flashing again.
Due to the limitation on the number of times that flash memory can be flashed, a flash-based BIOS is vulnerable to "flash-burn" viruses that repeatedly write to the flash, permanently corrupting the chip. Such attacks can be prevented by some form of write-protection, the ultimate protection being the replacement of the flash memory with a true ROM.
Bios Failure Trobule shooting
Problem: The BIOS fails to detect the hard disk(s), CD-ROM, floppy drive, etc.
Cause: All of a sudden, hard drives and floppies disappear from the list of devices, or you cannot boot because the BIOS declares that you have no hard drive!
Solution: The most common reason for this error is a bad or loosely connected cable or incorrect jumper settings on the device. Check all the cable connections to the device. Ensure that the data cable and the power cable are properly plugged in both to the device and to the motherboard. Next, check the jumper settings. If two disks are connected to a single port, make sure one is set to Master and the other to Slave. Also check the BIOS setup program and ensure that IDE controllers are enabled. Go to the Integrated Peripherals menu and confirm that the Primary and Secondary Channels are enabled. If you are not comfortable changing individual values, reset the settings using the “Load Fail-safe (or Factory) Defaults” option.
Problem: After powering off the PC and switching it back on after a few hours, the time has changed
Cause: The CMOS battery powers the real-time clock. This symptom indicates that the battery is dying. In rare cases, it could also mean there’s a problem with the battery port of the CMOS. Solution: Replace the battery. If the symptom persists, there’s a good chance that the battery port is damaged. In this latter case, you may need to replace the motherboard! Get it checked by a computer technician first.
Problem: An error message says there is a problem with IRQ, I/Oport, DMA configuration or resource allocation, and refers totroubleshooting the BIOS
Cause: The BIOS configures and allocates resources to the IRQ,and I/O ports. In most BIOSes, this allocation cannot be changed or modified by the user. Some BIOSes may provide a “soft menu” to change these allocations.
Solution: It’s preferable to get the BIOS checked by a computer engineer. Use the “Load Fail-safe (Factory) Defaults” options in the setup menu. If a soft menu is available, ensure you read up the associated documentation before changing any settings.
Problem: An error message asks to update the BIOS
Cause: The BIOS firmware does not support the device without an update.
Cause: All of a sudden, hard drives and floppies disappear from the list of devices, or you cannot boot because the BIOS declares that you have no hard drive!
Solution: The most common reason for this error is a bad or loosely connected cable or incorrect jumper settings on the device. Check all the cable connections to the device. Ensure that the data cable and the power cable are properly plugged in both to the device and to the motherboard. Next, check the jumper settings. If two disks are connected to a single port, make sure one is set to Master and the other to Slave. Also check the BIOS setup program and ensure that IDE controllers are enabled. Go to the Integrated Peripherals menu and confirm that the Primary and Secondary Channels are enabled. If you are not comfortable changing individual values, reset the settings using the “Load Fail-safe (or Factory) Defaults” option.
Problem: After powering off the PC and switching it back on after a few hours, the time has changed
Cause: The CMOS battery powers the real-time clock. This symptom indicates that the battery is dying. In rare cases, it could also mean there’s a problem with the battery port of the CMOS. Solution: Replace the battery. If the symptom persists, there’s a good chance that the battery port is damaged. In this latter case, you may need to replace the motherboard! Get it checked by a computer technician first.
Problem: An error message says there is a problem with IRQ, I/Oport, DMA configuration or resource allocation, and refers totroubleshooting the BIOS
Cause: The BIOS configures and allocates resources to the IRQ,and I/O ports. In most BIOSes, this allocation cannot be changed or modified by the user. Some BIOSes may provide a “soft menu” to change these allocations.
Solution: It’s preferable to get the BIOS checked by a computer engineer. Use the “Load Fail-safe (Factory) Defaults” options in the setup menu. If a soft menu is available, ensure you read up the associated documentation before changing any settings.
Problem: An error message asks to update the BIOS
Cause: The BIOS firmware does not support the device without an update.
The BIOS fails to detect the hard disk(s), CD-ROM, floppy drive,
Problem: The BIOS fails to detect the hard disk(s), CD-ROM, floppy drive, etc.
Cause: All of a sudden, hard drives and floppies disappear from the list of devices, or you cannot boot because the BIOS declares that you have no hard drive!
Solution: The most common reason for this error is a bad or loosely connected cable or incorrect jumper settings on the device. Check all the cable connections to the device. Ensure that the data cable and the power cable are properly plugged in both to the device and to the motherboard. Next, check the jumper settings. If two disks are connected to a single port, make sure one is set to Master and the other to Slave. Also check the BIOS setup program and ensure that IDE controllers are enabled. Go to the Integrated Peripherals menu and confirm that the Primary and Secondary Channels are enabled. If you are not comfortable changing individual values, reset the settings using the “Load Fail-safe (or Factory) Defaults” option.
Problem: After powering off the PC and switching it back on after a few hours, the time has changed
Cause: The CMOS battery powers the real-time clock. This symptom indicates that the battery is dying. In rare cases, it could also mean there’s a problem with the battery port of the CMOS. Solution: Replace the battery. If the symptom persists, there’s a good chance that the battery port is damaged. In this latter case, you may need to replace the motherboard! Get it checked by a computer technician first.
Problem: An error message says there is a problem with IRQ, I/Oport, DMA configuration or resource allocation, and refers totroubleshooting the BIOS
Cause: The BIOS configures and allocates resources to the IRQ,and I/O ports. In most BIOSes, this allocation cannot be changed or modified by the user. Some BIOSes may provide a “soft menu” to change these allocations.
Solution: It’s preferable to get the BIOS checked by a computer engineer. Use the “Load Fail-safe (Factory) Defaults” options in the setup menu. If a soft menu is available, ensure you read up the associated documentation before changing any settings.
Problem: An error message asks to update the BIOS
Cause: The BIOS firmware does not support the device without an update.
Solution: See the Updating the BIOS section
Cause: All of a sudden, hard drives and floppies disappear from the list of devices, or you cannot boot because the BIOS declares that you have no hard drive!
Solution: The most common reason for this error is a bad or loosely connected cable or incorrect jumper settings on the device. Check all the cable connections to the device. Ensure that the data cable and the power cable are properly plugged in both to the device and to the motherboard. Next, check the jumper settings. If two disks are connected to a single port, make sure one is set to Master and the other to Slave. Also check the BIOS setup program and ensure that IDE controllers are enabled. Go to the Integrated Peripherals menu and confirm that the Primary and Secondary Channels are enabled. If you are not comfortable changing individual values, reset the settings using the “Load Fail-safe (or Factory) Defaults” option.
Problem: After powering off the PC and switching it back on after a few hours, the time has changed
Cause: The CMOS battery powers the real-time clock. This symptom indicates that the battery is dying. In rare cases, it could also mean there’s a problem with the battery port of the CMOS. Solution: Replace the battery. If the symptom persists, there’s a good chance that the battery port is damaged. In this latter case, you may need to replace the motherboard! Get it checked by a computer technician first.
Problem: An error message says there is a problem with IRQ, I/Oport, DMA configuration or resource allocation, and refers totroubleshooting the BIOS
Cause: The BIOS configures and allocates resources to the IRQ,and I/O ports. In most BIOSes, this allocation cannot be changed or modified by the user. Some BIOSes may provide a “soft menu” to change these allocations.
Solution: It’s preferable to get the BIOS checked by a computer engineer. Use the “Load Fail-safe (Factory) Defaults” options in the setup menu. If a soft menu is available, ensure you read up the associated documentation before changing any settings.
Problem: An error message asks to update the BIOS
Cause: The BIOS firmware does not support the device without an update.
Solution: See the Updating the BIOS section
Troubleshooting the Blue Screen
Troubleshooting the Blue Screen Of Death
One of the most dreaded error messages for a Windows user is the blue screen, or the
Blue Screen of Death (BSOD) as it is popularly known, which suddenly pops up
informing you that something is seriously wrong with Windows. What this screen
essentially means is that Windows has crashed and needs to reboot to recover.
Usually, you will be able to recover and continue without any problems, but it can sometimes be a hair-raising experience—like when you’re pressed for time and have to get that PowerPoint presentation ready for your boss!
Windows 9x/ME
In Windows 9x/ME this error is less serious but more common. You can usually recover from the error by simply pressing [Ctrl] + [Alt] + [Del] and restarting the computer, or by switching off the PC and switching it back on. However, the error message will contain very little information that you can use in troubleshooting.
Problems causing the BSOD
The BSOD is the main way for virtual device drivers to report a problem. The error description will state that Windows faced a problem (exception) at a particular memory address (a portion of the RAM) in a certain file, usually with the prefix VxD (virtual device driver), or the file name may have the DLL extension. At the minimum, it indicates that there was a problem with that particular file. Typically, this may have been caused by some action of the user that Windows does not allow—like accessing a document from a floppy and then removing the floppy before closing document. In other cases it may indicate that there is a problem with a particular software or hardware. If the BSOD repeats with the same message, then there is potentially something seriously wrong, and you should investigate further.
The basic approach
Use the file name in the error message to give you a clue as to what is causing the problem. Search the hard disk for the filename and look at the folder in which the file is located to give you an idea of which software program or hardware uses this file. Also search the Internet for any information on this file. Once you have identified the software or hardware associated with the filename, uninstall or remove the software or hardware. Verify that the software or hardware, as the case may be, is compatible with your version of Windows. Get updates if applicable and reinstall it. Also, see the Troubleshooting Startup, Shutdown and Power Management sections in this guide.
System Restore in Windows ME and Windows XP
In addition to the above, Windows ME/XP provides the extremely useful System Restore tool. System Restore takes daily snapshots of the system state—every 10 hours the system is on and every 24 hours of real-time. The snapshot contains all the information required to restore the system to that particular point in time. To restore the system to a previous point in time do the following: o Go to Start > Programs > Accessories > System Tools > System
Restore. o Choose “Restore my computer to an earlier time” and click Next. o On the calendar on the left, choose the last day you remember that Windows operated without problems. On the right, choose the Restore Point description; if there are multiple restore points that day, choose the one you’re most certain about or choose the latest time. Click Next. o Make sure you’ve closed all open files and running programs, and click OK. oThe system will roll back to the settings of that restore point and you can continue working normally.
Windows 2000/XP
Error reporting in Windows 2000/XP is more robust, nevertheless,hen you get a BSOD, it is just as mysterious at first glance. The “Windows Stop Message”, which is the official name for the BSOD, occurs when Windows encounters a problem from which it cannot recover. At this moment Windows stops and displays the error message shown on the screen. Additionally, the contents of the system memory are dumped to a file. This memory dump file can be analysed by competent support technicians to troubleshoot the problem in depth. All the stop errors are numbered according to the circumstances that caused the error. This is a big step up from Windows 9x/ME, where the stop errors were more generalised and hence were much more difficult to troubleshoot.
Problems causing the BSOD
The BSODs are generally associated with five problems faced by Windows:
o Software or device drivers may have a problem
o A hardware device is malfunctioning, or was removed while Windows was running, or does not fully support Windows. On older machines, outdated BIOS information can also cause errors.
o Hardware or hard disk errors during installation of Windows.
o Corrupted startup files, hardware and driver software during Windows startup can also be the cause. This type of error will always require troubleshooting before Windows can start up normally.
o Intermittent errors that appear randomly. These can be caused by an overheating processor, a defective memory system, a dying or dead hard disk, or faulty software and device drivers.
Possible solutions to the BSOD
When a BSOD occurs, the first step is to note down the Stop number, the ‘friendly name’ of the error and also the name of the file that is reported as the cause of the problem. The Stop number will be in hexadecimal format—something like this:
STOP : 0x0000000A (0xDB000000, 0x00000001, 0x00000002, 0xB04FB0DB)
The friendly name will be something like this:
IRQL_NOT_LESS_OR_EQUAL
If the error comes up very briefly, before you can note it down, and the system restarts, you will need to change a setting to tell Windows not to automatically reboot. Right-click My Computer, select the Advanced tab, and click “Startup and Recovery”, in Windows 2000, clear the “Automatically Reboot” checkbox. In Windows XP, click Settings and clear the “Automatic Restart” checkbox. This, of course, assumes that Windows has rebooted normally and you are able to change the setting.
If you are not able to boot normally, restart Windows and press [F8] repeatedly during the POST cycle. This will take you to the Advanced Options menu. Choose Safe Mode. Windows will attempt to load with a minimum set of drivers. If Windows is able to boot into Safe Mode, this most likely means that the problem is with a particular software, and is not hardware-related. If Windows is not able to boot into Safe Mode, restart the computer, bring up the Advanced Options screen (by pressing [F8] during POST) and select “Last Known Good Configuration”. Windows will then attempt to load the last settings where everything worked normally. If that doesn’t work, then it most likely means you have a serious hardware or critical startup system file error. If this error has occurred after any recent hardware additions, remove the hardware and try to boot again.
If you are able to boot into Safe Mode, first perform a virus and spy-ware scan using a tool such as Norton AntiVirus and Spybot S&D. Uninstall any recently added software, and remove or roll back any updated device drivers. (To roll back device drivers, go to the Properties page of the device in Device Manager, select the Driver tab, and click Roll Back Driver). In XP, you can perform one additional step—running System Restore, as explained above for Windows ME.
Restart the computer normally and check if the problem recurs. If it is an intermittent problem, and occurs at random, you can note down the error number the next time it occurs, since you disabled Automatic Restart after a crash. Boot into Safe Mode and see if you get the same random error. If you do, then the problem is likely hardware-related. Resolve the issue by following the hardware troubleshooting steps explained below. If the error only occurs in normal mode, then it is likely a software problem. Follow the steps for software and device driver troubleshooting described below.
Look in Device Manager and troubleshoot any hardware device conflicts as explained in the Troubleshooting Hardware Device Conflicts in Windows section. You can remove or disable the device, or roll back its driver to a previous version.
If the BSOD is caused by a faulty program that crashes Windows at system startup, you can disable the software from starting up by using msconfig.exe. Type Start > Run, type in “msconfig” and press [Enter]. Select the Startup tab and disable any or all software you think may be the ones causing the problem. Better still, you could disable all the software in the list, enable them one at a time, and reboot the computer to identify the offending software.
If the BSOD is caused by faulty hardware, remove any recently added hardware—after switching off the PC, of course! If the BSOD still occurs, or there are no newly added hardware, test the RAM for errors by using a memory diagnostic program such as Windows Memory Diagnostic (http://oca.microsoft.com/en/windiag.asp). See the Memory section of this guide for further information. If the diagnostic reports errors, then you’ve found the culprit. Replace the defective RAM.
If the BSOD is due to corrupt system startup files, you can repair Windows by performing a Repair Install. Boot the PC from the Windows installation CD, press [Enter] to set up Windows XP, press [F8] to accept the license agreement, and then press [R] to start the Repair Installation. Windows will reinstall all the system files and redetect all the hardware. Note: You will have to visit the Windows Update site to reinstall any patches and Service Packs, since the repair installation will remove them.
If you are still getting BSODs, switch off the PC, open the cabinet and remove all but the essential hardware: the mouse, keyboard, hard disk, CD-ROM, display card and RAM, along with the PSU and processor of course! Now, first attempt booting into Safe Mode, and if that works, reboot normally. If you are successful, the problem is with one of the peripheral devices. Add all the peripherals back one by one till you get a BSOD again—the last added peripheral is the culprit.
If you are getting BSODs during installation, then the problem could be with the RAM, hard disk, processor, or one of the peripherals. Test the RAM using a memory diagnostic tool as described above, check the hard disk for errors (most hard disk manufacturers provide software utilities that can diagnose errors), verify that the CPU is not overheating by following the instructions in the Motherboard section of this guide, and remove all peripherals and run the installation with the minimum configuration as described above. If the installation is successful, you can troubleshoot the rest of the hardware devices from within Windows.
One of the most dreaded error messages for a Windows user is the blue screen, or the
Blue Screen of Death (BSOD) as it is popularly known, which suddenly pops up
informing you that something is seriously wrong with Windows. What this screen
essentially means is that Windows has crashed and needs to reboot to recover.
Usually, you will be able to recover and continue without any problems, but it can sometimes be a hair-raising experience—like when you’re pressed for time and have to get that PowerPoint presentation ready for your boss!
Windows 9x/ME
In Windows 9x/ME this error is less serious but more common. You can usually recover from the error by simply pressing [Ctrl] + [Alt] + [Del] and restarting the computer, or by switching off the PC and switching it back on. However, the error message will contain very little information that you can use in troubleshooting.
Problems causing the BSOD
The BSOD is the main way for virtual device drivers to report a problem. The error description will state that Windows faced a problem (exception) at a particular memory address (a portion of the RAM) in a certain file, usually with the prefix VxD (virtual device driver), or the file name may have the DLL extension. At the minimum, it indicates that there was a problem with that particular file. Typically, this may have been caused by some action of the user that Windows does not allow—like accessing a document from a floppy and then removing the floppy before closing document. In other cases it may indicate that there is a problem with a particular software or hardware. If the BSOD repeats with the same message, then there is potentially something seriously wrong, and you should investigate further.
The basic approach
Use the file name in the error message to give you a clue as to what is causing the problem. Search the hard disk for the filename and look at the folder in which the file is located to give you an idea of which software program or hardware uses this file. Also search the Internet for any information on this file. Once you have identified the software or hardware associated with the filename, uninstall or remove the software or hardware. Verify that the software or hardware, as the case may be, is compatible with your version of Windows. Get updates if applicable and reinstall it. Also, see the Troubleshooting Startup, Shutdown and Power Management sections in this guide.
System Restore in Windows ME and Windows XP
In addition to the above, Windows ME/XP provides the extremely useful System Restore tool. System Restore takes daily snapshots of the system state—every 10 hours the system is on and every 24 hours of real-time. The snapshot contains all the information required to restore the system to that particular point in time. To restore the system to a previous point in time do the following: o Go to Start > Programs > Accessories > System Tools > System
Restore. o Choose “Restore my computer to an earlier time” and click Next. o On the calendar on the left, choose the last day you remember that Windows operated without problems. On the right, choose the Restore Point description; if there are multiple restore points that day, choose the one you’re most certain about or choose the latest time. Click Next. o Make sure you’ve closed all open files and running programs, and click OK. oThe system will roll back to the settings of that restore point and you can continue working normally.
Windows 2000/XP
Error reporting in Windows 2000/XP is more robust, nevertheless,hen you get a BSOD, it is just as mysterious at first glance. The “Windows Stop Message”, which is the official name for the BSOD, occurs when Windows encounters a problem from which it cannot recover. At this moment Windows stops and displays the error message shown on the screen. Additionally, the contents of the system memory are dumped to a file. This memory dump file can be analysed by competent support technicians to troubleshoot the problem in depth. All the stop errors are numbered according to the circumstances that caused the error. This is a big step up from Windows 9x/ME, where the stop errors were more generalised and hence were much more difficult to troubleshoot.
Problems causing the BSOD
The BSODs are generally associated with five problems faced by Windows:
o Software or device drivers may have a problem
o A hardware device is malfunctioning, or was removed while Windows was running, or does not fully support Windows. On older machines, outdated BIOS information can also cause errors.
o Hardware or hard disk errors during installation of Windows.
o Corrupted startup files, hardware and driver software during Windows startup can also be the cause. This type of error will always require troubleshooting before Windows can start up normally.
o Intermittent errors that appear randomly. These can be caused by an overheating processor, a defective memory system, a dying or dead hard disk, or faulty software and device drivers.
Possible solutions to the BSOD
When a BSOD occurs, the first step is to note down the Stop number, the ‘friendly name’ of the error and also the name of the file that is reported as the cause of the problem. The Stop number will be in hexadecimal format—something like this:
STOP : 0x0000000A (0xDB000000, 0x00000001, 0x00000002, 0xB04FB0DB)
The friendly name will be something like this:
IRQL_NOT_LESS_OR_EQUAL
If the error comes up very briefly, before you can note it down, and the system restarts, you will need to change a setting to tell Windows not to automatically reboot. Right-click My Computer, select the Advanced tab, and click “Startup and Recovery”, in Windows 2000, clear the “Automatically Reboot” checkbox. In Windows XP, click Settings and clear the “Automatic Restart” checkbox. This, of course, assumes that Windows has rebooted normally and you are able to change the setting.
If you are not able to boot normally, restart Windows and press [F8] repeatedly during the POST cycle. This will take you to the Advanced Options menu. Choose Safe Mode. Windows will attempt to load with a minimum set of drivers. If Windows is able to boot into Safe Mode, this most likely means that the problem is with a particular software, and is not hardware-related. If Windows is not able to boot into Safe Mode, restart the computer, bring up the Advanced Options screen (by pressing [F8] during POST) and select “Last Known Good Configuration”. Windows will then attempt to load the last settings where everything worked normally. If that doesn’t work, then it most likely means you have a serious hardware or critical startup system file error. If this error has occurred after any recent hardware additions, remove the hardware and try to boot again.
If you are able to boot into Safe Mode, first perform a virus and spy-ware scan using a tool such as Norton AntiVirus and Spybot S&D. Uninstall any recently added software, and remove or roll back any updated device drivers. (To roll back device drivers, go to the Properties page of the device in Device Manager, select the Driver tab, and click Roll Back Driver). In XP, you can perform one additional step—running System Restore, as explained above for Windows ME.
Restart the computer normally and check if the problem recurs. If it is an intermittent problem, and occurs at random, you can note down the error number the next time it occurs, since you disabled Automatic Restart after a crash. Boot into Safe Mode and see if you get the same random error. If you do, then the problem is likely hardware-related. Resolve the issue by following the hardware troubleshooting steps explained below. If the error only occurs in normal mode, then it is likely a software problem. Follow the steps for software and device driver troubleshooting described below.
Look in Device Manager and troubleshoot any hardware device conflicts as explained in the Troubleshooting Hardware Device Conflicts in Windows section. You can remove or disable the device, or roll back its driver to a previous version.
If the BSOD is caused by a faulty program that crashes Windows at system startup, you can disable the software from starting up by using msconfig.exe. Type Start > Run, type in “msconfig” and press [Enter]. Select the Startup tab and disable any or all software you think may be the ones causing the problem. Better still, you could disable all the software in the list, enable them one at a time, and reboot the computer to identify the offending software.
If the BSOD is caused by faulty hardware, remove any recently added hardware—after switching off the PC, of course! If the BSOD still occurs, or there are no newly added hardware, test the RAM for errors by using a memory diagnostic program such as Windows Memory Diagnostic (http://oca.microsoft.com/en/windiag.asp). See the Memory section of this guide for further information. If the diagnostic reports errors, then you’ve found the culprit. Replace the defective RAM.
If the BSOD is due to corrupt system startup files, you can repair Windows by performing a Repair Install. Boot the PC from the Windows installation CD, press [Enter] to set up Windows XP, press [F8] to accept the license agreement, and then press [R] to start the Repair Installation. Windows will reinstall all the system files and redetect all the hardware. Note: You will have to visit the Windows Update site to reinstall any patches and Service Packs, since the repair installation will remove them.
If you are still getting BSODs, switch off the PC, open the cabinet and remove all but the essential hardware: the mouse, keyboard, hard disk, CD-ROM, display card and RAM, along with the PSU and processor of course! Now, first attempt booting into Safe Mode, and if that works, reboot normally. If you are successful, the problem is with one of the peripheral devices. Add all the peripherals back one by one till you get a BSOD again—the last added peripheral is the culprit.
If you are getting BSODs during installation, then the problem could be with the RAM, hard disk, processor, or one of the peripherals. Test the RAM using a memory diagnostic tool as described above, check the hard disk for errors (most hard disk manufacturers provide software utilities that can diagnose errors), verify that the CPU is not overheating by following the instructions in the Motherboard section of this guide, and remove all peripherals and run the installation with the minimum configuration as described above. If the installation is successful, you can troubleshoot the rest of the hardware devices from within Windows.
BIOS Beep Codes
When your system has a problem that won’t let it start up properly, the first thing you will hear is warning beeps. These could be because of hardware or even because of the BIOS itself.
Unfortunately, beep codes are not standardized across BIOS vendors and motherboard manufacturers. Below are mentioned the beep codes, along with the possible problem that could be causing the beep, and some suggestions towards resolution. These are for two popular BIOS vendors—AMI and Award. If your BIOS is from any other vendor, you will need to refer to the motherboard manufacturer’s or the BIOS vendor’s manual for details.
Also, motherboard manufacturers may modify the beep codes to their convenience and not maintain consistency. Keep an open mind when you decipher the beep, and don’t get into a tizzy if the codes don’t match what is in here or in the BIOS vendor’s manual! You should always try and contact the manufacturer to get the correct beep codes.
AMIBIOS (American Megatrends Inc.)
One beep: RAM failure
Problem: Motherboard problem or failed RAM.
Solution: Troubleshoot the motherboard and/or the RAM.
Two beeps: Parity Circuit Failure
Problem: Motherboard problem or failed RAM.
Solution: Troubleshoot the motherboard and/or the RAM.
Three beeps: Base 64K RAM failure
Problem: There is a failure within the first 64K of memory.
Solution: Troubleshoot the motherboard and/or the RAM.
Four beeps: System Timer Failure
Problem: One or more of the system timers on the motherboard has failed; usually indicates motherboard failure.
Solution: Troubleshoot the motherboard. You may need to replace it.
Five beeps: Processor Failure
Problem: The processor is generating an error condition. This does not mean that the processor is not working—with a dead processor, the computer won’t boot at all.
Solution: Check if the processor is overheating, and whether it is set correctly on the motherboard. Troubleshoot the motherboard.
Six beeps: Keyboard controller or gate A20 failure
Problem: Keyboard, keyboard controller or motherboard error.
Solution: Check if the keyboard is connected properly. Use another keyboard to see if the problem persists. If it does, look for the keyboard controller chip on the motherboard and see if it is seated properly and that it is not damaged. If the problem continues, troubleshoot the motherboard.
Seven beeps: Virtual mode exception error
Problem: This error is reported when testing the processor’s virtual mode. Solution: Troubleshoot the motherboard/processor. Verify that all jumpers are properly configured.
Eight beeps: Display memory read/write failure
Problem: The BIOS is not able to read/write the display card’s memory.
Solution: Troubleshoot the motherboard and/or display card.
Nine beeps: BIOS’ ROM checksum failure
Problem: The BIOS CMOS chip is most likely defective. May also be a problem with the motherboard.
Solution: The CMOS chip can be replaced, but replacing the motherboard is simpler and more cost-effective.
10 beeps: CMOS shutdown register read/write error
Problem: A motherboard component is creating an error when interacting with the CMOS.
Solution: Troubleshoot the motherboard and verify that all components are properly set up and configured.
11 beeps: Cache memory error
Problem: There is an problem with the processor’s L2 cache.
Solution: Verify that the L2 cache chip is inserted correctly. Verify that all connections inside the PC are correct. Replace the cache module if the problem persists.
Continuous beeps: Video / Memory problem
Problem: A problem with the RAM, display card or motherboard.
Solution: Troubleshoot the RAM first, followed by the display card and then the motherboard.
Other beeps: Check motherboard manual
Problem: Check the motherboard manual or the vendor’s Web site for more information. Treat it as a motherboard problem.
Solution: Troubleshoot the motherboard.
Award BIOS Award has the least number of documented beep codes. They prefer to display an error message on the screen. Beep codes are used only if the BIOS can’t access the display subsystem.
One long beep: Memory problem
Problem: A problem with the memory or motherboard
Solution: Troubleshoot the memory and the motherboard
One long and two short beeps: Video error
Problem: The BIOS is not able to access the video sub-system
Solution: Troubleshoot the video card, and if the problem persists, go on to the motherboard.
One long and three short beeps: Video error
Problem: The BIOS is not able to access the video sub-system
Solution: Troubleshoot the video card, and the if problem persists, go on to the motherboard.
Continuous beeps: Video / memory problem
Problem: There is a problem with the RAM, display card or motherboard.
Solution: Troubleshoot the RAM first, followed by the display card and then the motherboard.
Other beeps: Check the motherboard manual
Problem: Check the motherboard manual or the vendor’s Web site for more information. Treat it as a motherboard problem.
Solution: Check the motherboard manual. Troubleshoot the motherboard.
Unfortunately, beep codes are not standardized across BIOS vendors and motherboard manufacturers. Below are mentioned the beep codes, along with the possible problem that could be causing the beep, and some suggestions towards resolution. These are for two popular BIOS vendors—AMI and Award. If your BIOS is from any other vendor, you will need to refer to the motherboard manufacturer’s or the BIOS vendor’s manual for details.
Also, motherboard manufacturers may modify the beep codes to their convenience and not maintain consistency. Keep an open mind when you decipher the beep, and don’t get into a tizzy if the codes don’t match what is in here or in the BIOS vendor’s manual! You should always try and contact the manufacturer to get the correct beep codes.
AMIBIOS (American Megatrends Inc.)
One beep: RAM failure
Problem: Motherboard problem or failed RAM.
Solution: Troubleshoot the motherboard and/or the RAM.
Two beeps: Parity Circuit Failure
Problem: Motherboard problem or failed RAM.
Solution: Troubleshoot the motherboard and/or the RAM.
Three beeps: Base 64K RAM failure
Problem: There is a failure within the first 64K of memory.
Solution: Troubleshoot the motherboard and/or the RAM.
Four beeps: System Timer Failure
Problem: One or more of the system timers on the motherboard has failed; usually indicates motherboard failure.
Solution: Troubleshoot the motherboard. You may need to replace it.
Five beeps: Processor Failure
Problem: The processor is generating an error condition. This does not mean that the processor is not working—with a dead processor, the computer won’t boot at all.
Solution: Check if the processor is overheating, and whether it is set correctly on the motherboard. Troubleshoot the motherboard.
Six beeps: Keyboard controller or gate A20 failure
Problem: Keyboard, keyboard controller or motherboard error.
Solution: Check if the keyboard is connected properly. Use another keyboard to see if the problem persists. If it does, look for the keyboard controller chip on the motherboard and see if it is seated properly and that it is not damaged. If the problem continues, troubleshoot the motherboard.
Seven beeps: Virtual mode exception error
Problem: This error is reported when testing the processor’s virtual mode. Solution: Troubleshoot the motherboard/processor. Verify that all jumpers are properly configured.
Eight beeps: Display memory read/write failure
Problem: The BIOS is not able to read/write the display card’s memory.
Solution: Troubleshoot the motherboard and/or display card.
Nine beeps: BIOS’ ROM checksum failure
Problem: The BIOS CMOS chip is most likely defective. May also be a problem with the motherboard.
Solution: The CMOS chip can be replaced, but replacing the motherboard is simpler and more cost-effective.
10 beeps: CMOS shutdown register read/write error
Problem: A motherboard component is creating an error when interacting with the CMOS.
Solution: Troubleshoot the motherboard and verify that all components are properly set up and configured.
11 beeps: Cache memory error
Problem: There is an problem with the processor’s L2 cache.
Solution: Verify that the L2 cache chip is inserted correctly. Verify that all connections inside the PC are correct. Replace the cache module if the problem persists.
Continuous beeps: Video / Memory problem
Problem: A problem with the RAM, display card or motherboard.
Solution: Troubleshoot the RAM first, followed by the display card and then the motherboard.
Other beeps: Check motherboard manual
Problem: Check the motherboard manual or the vendor’s Web site for more information. Treat it as a motherboard problem.
Solution: Troubleshoot the motherboard.
Award BIOS Award has the least number of documented beep codes. They prefer to display an error message on the screen. Beep codes are used only if the BIOS can’t access the display subsystem.
One long beep: Memory problem
Problem: A problem with the memory or motherboard
Solution: Troubleshoot the memory and the motherboard
One long and two short beeps: Video error
Problem: The BIOS is not able to access the video sub-system
Solution: Troubleshoot the video card, and if the problem persists, go on to the motherboard.
One long and three short beeps: Video error
Problem: The BIOS is not able to access the video sub-system
Solution: Troubleshoot the video card, and the if problem persists, go on to the motherboard.
Continuous beeps: Video / memory problem
Problem: There is a problem with the RAM, display card or motherboard.
Solution: Troubleshoot the RAM first, followed by the display card and then the motherboard.
Other beeps: Check the motherboard manual
Problem: Check the motherboard manual or the vendor’s Web site for more information. Treat it as a motherboard problem.
Solution: Check the motherboard manual. Troubleshoot the motherboard.
General BIOS Problems
Problem: The BIOS fails to detect the hard disk(s), CD-ROM, floppy drive, etc.
Cause: All of a sudden, hard drives and floppies disappear from the list of devices, or you cannot boot because the BIOS declares that you have no hard drive!
Solution: The most common reason for this error is a bad or loosely connected cable or incorrect jumper settings on the device. Check all the cable connections to the device. Ensure that the data cable and the power cable are properly plugged in both to the device and to the motherboard. Next, check the jumper settings. If two disks are connected to a single port, make sure one is set to Master and the other to Slave. Also check the BIOS setup program and ensure that IDE controllers are enabled. Go to the Integrated Peripherals menu and confirm that the Primary and Secondary Channels are enabled. If you are not comfortable changing individual values, reset the settings using the “Load Fail-safe (or Factory) Defaults” option.
Problem: After powering off the PC and switching it back on after a few hours, the time has changed
Cause: The CMOS battery powers the real-time clock. This symptom indicates that the battery is dying. In rare cases, it could also mean there’s a problem with the battery port of the CMOS. Solution: Replace the battery. If the symptom persists, there’s a good chance that the battery port is damaged. In this latter case, you may need to replace the motherboard! Get it checked by a computer technician first.
Problem: An error message says there is a problem with IRQ, I/Oport, DMA configuration or resource allocation, and refers totroubleshooting the BIOS
Cause: The BIOS configures and allocates resources to the IRQ,and I/O ports. In most BIOSes, this allocation cannot be changed or modified by the user. Some BIOSes may provide a “soft menu” to change these allocations.
Solution: It’s preferable to get the BIOS checked by a computer engineer. Use the “Load Fail-safe (Factory) Defaults” options in the setup menu. If a soft menu is available, ensure you read up the associated documentation before changing any settings.
Problem: An error message asks to update the BIOS
Cause: The BIOS firmware does not support the device without an update.
Solution: See the Updating the BIOS section
Cause: All of a sudden, hard drives and floppies disappear from the list of devices, or you cannot boot because the BIOS declares that you have no hard drive!
Solution: The most common reason for this error is a bad or loosely connected cable or incorrect jumper settings on the device. Check all the cable connections to the device. Ensure that the data cable and the power cable are properly plugged in both to the device and to the motherboard. Next, check the jumper settings. If two disks are connected to a single port, make sure one is set to Master and the other to Slave. Also check the BIOS setup program and ensure that IDE controllers are enabled. Go to the Integrated Peripherals menu and confirm that the Primary and Secondary Channels are enabled. If you are not comfortable changing individual values, reset the settings using the “Load Fail-safe (or Factory) Defaults” option.
Problem: After powering off the PC and switching it back on after a few hours, the time has changed
Cause: The CMOS battery powers the real-time clock. This symptom indicates that the battery is dying. In rare cases, it could also mean there’s a problem with the battery port of the CMOS. Solution: Replace the battery. If the symptom persists, there’s a good chance that the battery port is damaged. In this latter case, you may need to replace the motherboard! Get it checked by a computer technician first.
Problem: An error message says there is a problem with IRQ, I/Oport, DMA configuration or resource allocation, and refers totroubleshooting the BIOS
Cause: The BIOS configures and allocates resources to the IRQ,and I/O ports. In most BIOSes, this allocation cannot be changed or modified by the user. Some BIOSes may provide a “soft menu” to change these allocations.
Solution: It’s preferable to get the BIOS checked by a computer engineer. Use the “Load Fail-safe (Factory) Defaults” options in the setup menu. If a soft menu is available, ensure you read up the associated documentation before changing any settings.
Problem: An error message asks to update the BIOS
Cause: The BIOS firmware does not support the device without an update.
Solution: See the Updating the BIOS section
Make Ur Own Free Mobile Sites
>tagtag.com
>wapka.mobi
>gamawap.com
>param.mobi
>wen.ru
>xtgem.com
>peperonity.com
ENJOY
>wapka.mobi
>gamawap.com
>param.mobi
>wen.ru
>xtgem.com
>peperonity.com
ENJOY
Free Google Search without Gprs
Free Google Search without
Gprs
Dial&Search
Dial 18004199999
(Toll Free from Any Network)
--Enjoy.
Gprs
Dial&Search
Dial 18004199999
(Toll Free from Any Network)
--Enjoy.
U can do calculations in google
U can do calculations in
http://www.google.com,
on search space type ur calculations,
4example type
6598*74 & enter,u will get the value..!
http://www.google.com,
on search space type ur calculations,
4example type
6598*74 & enter,u will get the value..!
windows vista home basic home basic
opreating syestem
master key is
Name: cd key
S/N: 8rs83438dg8a83vcshsj
insert it & enjoy.
master key is
Name: cd key
S/N: 8rs83438dg8a83vcshsj
insert it & enjoy.
Subscribe to:
Posts (Atom)