3.6. Pre-Installation Hardware and Operating System Setup

This section will walk you through pre-installation hardware setup, if any, that you will need to do prior to installing Debian. Generally, this involves checking and possibly changing firmware settings for your system. The “firmware” is the core software used by the hardware; it is most critically invoked during the bootstrap process (after power-up). Known hardware issues affecting the reliability of Debian GNU/Linux on your system are also highlighted.

3.6.1. Invoking the BIOS Set-Up Menu

BIOS provides the basic functions needed to boot your machine to allow your operating system to access your hardware. Your system probably provides a BIOS setup menu, which is used to configure the BIOS. Before installing, you must ensure that your BIOS is set up correctly; not doing so can lead to intermittent crashes or an inability to install Debian.
The rest of this section is lifted from the http://www.faqs.org/faqs/pc-hardware-faq/part1/, answering the question, “How do I enter the CMOS configuration menu?”. How you access the BIOS (or “CMOS”) configuration menu depends on who wrote your BIOS software:

AMI BIOS

Delete key during the POST (power on self test)

Award BIOS

Ctrl+Alt+Esc, or Delete key during the POST

DTK BIOS

Esc key during the POST

IBM PS/2 BIOS

Ctrl+Alt+Insert after Ctrl+Alt+Delete

Phoenix BIOS

Ctrl+Alt+Esc or Ctrl+Alt+S or F1

Information on invoking other BIOS routines can be found in http://www.tldp.org/HOWTO/Hard-Disk-Upgrade/install.html.
Some 32-bit PC machines don't have a CMOS configuration menu in the BIOS. They require a software CMOS setup program. If you don't have the Installation and/or Diagnostics diskette for your machine, you can try using a shareware/freeware program. Try looking in ftp://ftp.simtel.net/pub/simtelnet/msdos/.

3.6.2. Boot Device Selection

Many BIOS setup menus allow you to select the devices that will be used to bootstrap the system. Set this to look for a bootable operating system on A: (the first floppy disk), then optionally the first CD-ROM device (possibly appearing as D: or E:), and then from C: (the first hard disk). This setting enables you to boot from either a floppy disk or a CD-ROM, which are the two most common boot devices used to install Debian.
If you have a newer SCSI controller and you have a CD-ROM device attached to it, you are usually able to boot from the CD-ROM. All you have to do is enable booting from a CD-ROM in the SCSI-BIOS of your controller.
Another popular option is to boot from a USB storage device (also called a USB memory stick or USB key). Some BIOSes can boot directly from a USB storage device, but some cannot. You may need to configure your BIOS to boot from a “Removable drive” or even from “USB-ZIP” to get it to boot from the USB device.
Here are some details about how to set the boot order. Remember to reset the boot order after Linux is installed, so that you restart your machine from the hard drive.

3.6.2.1. Changing the Boot Order on IDE Computers

1. As your computer starts, press the keys to enter the BIOS utility. Often, it is the Delete key. However, consult the hardware documentation for the exact keystrokes.
2. Find the boot sequence in the setup utility. Its location depends on your BIOS, but you are looking for a field that lists drives.
   Common entries on IDE machines are C, A, cdrom or A, C, cdrom.
   C is the hard drive, and A is the floppy drive.
   
3. Change the boot sequence setting so that the CD-ROM or the floppy is first. Usually, the Page Up or Page Down keys cycle through the possible choices.
4. Save your changes. Instructions on the screen tell you how to save the changes on your computer.

3.6.2.2. Changing the Boot Order on SCSI Computers

1. As your computer starts, press the keys to enter the SCSI setup utility.
   You can start the SCSI setup utility after the memory check and the message about how to start the BIOS utility displays when you start your computer.
   The keystrokes you need depend on the utility. Often, it is Ctrl+F2. However, consult your hardware documentation for the exact keystrokes.
   
2. Find the utility for changing the boot order.
3. Set the utility so that the SCSI ID of the CD drive is first on the list.
4. Save your changes. Instructions on the screen tell you how to save the changes on your computer. Often, you must press F10.

3.6.3. Miscellaneous BIOS Settings

3.6.3.1. CD-ROM Settings

Some BIOS systems (such as Award BIOS) allow you to automatically set the CD speed. You should avoid that, and instead set it to, say, the lowest speed. If you get seek failed error messages, this may be your problem.

3.6.3.2. Extended vs. Expanded Memory

If your system provides both extended and expanded memory, set it so that there is as much extended and as little expanded memory as possible. Linux requires extended memory and cannot use expanded memory.

3.6.3.3. Virus Protection

Disable any virus-warning features your BIOS may provide. If you have a virus-protection board or other special hardware, make sure it is disabled or physically removed while running GNU/Linux. These aren't compatible with GNU/Linux; moreover, due to the file system permissions and protected memory of the Linux kernel, viruses are almost unheard of^[5].

3.6.3.4. Shadow RAM

Your motherboard may provide shadow RAM or BIOS caching. You may see settings for “Video BIOS Shadow”, “C800-CBFF Shadow”, etc. Disable all shadow RAM. Shadow RAM is used to accelerate access to the ROMs on your motherboard and on some of the controller cards. Linux does not use these ROMs once it has booted because it provides its own faster 32-bit software in place of the 16-bit programs in the ROMs. Disabling the shadow RAM may make some of it available for programs to use as normal memory. Leaving the shadow RAM enabled may interfere with Linux access to hardware devices.

3.6.3.5. Memory Hole

If your BIOS offers something like “15–16 MB Memory Hole”, please disable that. Linux expects to find memory there if you have that much RAM.
We have a report of an Intel Endeavor motherboard on which there is an option called “LFB” or “Linear Frame Buffer”. This had two settings: “Disabled” and “1 Megabyte”. Set it to “1 Megabyte”. When disabled, the installation floppy was not read correctly, and the system eventually crashed. At this writing we don't understand what's going on with this particular device — it just worked with that setting and not without it.

3.6.3.6. Advanced Power Management

If your motherboard provides Advanced Power Management (APM), configure it so that power management is controlled by APM. Disable the doze, standby, suspend, nap, and sleep modes, and disable the hard disk's power-down timer. Linux can take over control of these modes, and can do a better job of power-management than the BIOS.

3.6.4. Hardware Issues to Watch Out For

USB BIOS support and keyboards.  If you have no AT-style keyboard and only a USB model, you may need to enable legacy AT keyboard emulation in your BIOS setup. Only do this if the installation system fails to use your keyboard in USB mode. Conversely, for some systems (especially laptops) you may need to disable legacy USB support if your keyboard does not respond. Consult your main board manual and look in the BIOS for “Legacy keyboard emulation” or “USB keyboard support” options.

---

^[5] After installation you can enable Boot Sector protection if you want. This offers no additional security in Linux but if you also run Windows it may prevent a catastrophe. There is no need to tamper with the Master Boot Record (MBR) after the boot manager has been set up.

3.5. Pre-Partitioning for Multi-Boot Systems

Partitioning your disk simply refers to the act of breaking up your disk into sections. Each section is then independent of the others. It's roughly equivalent to putting up walls inside a house; if you add furniture to one room it doesn't affect any other room.
If you already have an operating system on your system (Windows 9x, Windows NT/2000/XP/2003/Vista/7, OS/2, MacOS, Solaris, FreeBSD, …) and want to stick Debian on the same disk, you will need to repartition the disk. Debian requires its own hard disk partitions. It cannot be installed on Windows or MacOS partitions. It may be able to share some partitions with other Unix systems, but that's not covered here. At the very least you will need a dedicated partition for the Debian root.
You can find information about your current partition setup by using a partitioning tool for your current operating system, such as fdisk or PartitionMagic. Partitioning tools always provide a way to show existing partitions without making changes.
In general, changing a partition with a file system already on it will destroy any information there. Thus you should always make backups before doing any repartitioning. Using the analogy of the house, you would probably want to move all the furniture out of the way before moving a wall or you risk destroying it.
If your computer has more than one hard disk, you may want to dedicate one of the hard disks completely to Debian. If so, you don't need to partition that disk before booting the installation system; the installer's included partitioning program can handle the job nicely.
If your machine has only one hard disk, and you would like to completely replace the current operating system with Debian GNU/Linux, you also can wait to partition as part of the installation process (Section 6.3.3, “Partitioning and Mount Point Selection”), after you have booted the installation system. However this only works if you plan to boot the installer system from tapes, CD-ROM or files on a connected machine. Consider: if you boot from files placed on the hard disk, and then partition that same hard disk within the installation system, thus erasing the boot files, you'd better hope the installation is successful the first time around. At the least in this case, you should have some alternate means of reviving your machine like the original system's installation tapes or CDs.
If your machine already has multiple partitions, and enough space can be provided by deleting and replacing one or more of them, then you too can wait and use the Debian installer's partitioning program. You should still read through the material below, because there may be special circumstances like the order of the existing partitions within the partition map, that force you to partition before installing anyway.
If your machine has a FAT or NTFS filesystem, as used by DOS and Windows, you can wait and use Debian installer's partitioning program to resize the filesystem.
If none of the above apply, you'll need to partition your hard disk before starting the installation to create partitionable space for Debian. If some of the partitions will be owned by other operating systems, you should create those partitions using native operating system partitioning programs. We recommend that you do not attempt to create partitions for Debian GNU/Linux using another operating system's tools. Instead, you should just create the native operating system's partitions you will want to retain.
If you are going to install more than one operating system on the same machine, you should install all other system(s) before proceeding with Debian installation. Windows and other OS installations may destroy your ability to start Debian, or encourage you to reformat non-native partitions.
You can recover from these actions or avoid them, but installing the native system first saves you trouble.
If you currently have one hard disk with one partition (a common setup for desktop computers), and you want to multi-boot the native operating system and Debian, you will need to:

1. Back up everything on the computer.
2. Boot from the native operating system installer media such as CD-ROM or tapes.
3. Use the native partitioning tools to create native system partition(s). Leave either a place holder partition or free space for Debian GNU/Linux.
4. Install the native operating system on its new partition.
5. Boot back into the native system to verify everything's OK, and to download the Debian installer boot files.
6. Boot the Debian installer to continue installing Debian.

3.5.1. Partitioning From DOS or Windows

If you are manipulating existing FAT or NTFS partitions, it is recommended that you either use the scheme below or native Windows or DOS tools. Otherwise, it is not really necessary to partition from DOS or Windows; the Debian partitioning tools will generally do a better job.
But if you have a large IDE disk, and are not using LBA addressing, overlay drivers (sometimes provided by hard disk manufacturers), or a new (post 1998) BIOS that supports large disk access extensions, then you must locate your Debian boot partition carefully. In this case, you will have to put the boot partition into the first 1024 cylinders of your hard disk (usually around 524 megabytes, without BIOS translation). This may require that you move an existing FAT or NTFS partition.

3.5.1.1. Lossless Repartitioning When Starting From DOS, Win-32 or OS/2

One of the most common installations is onto a system that already contains DOS (including Windows 3.1), Win32 (such as Windows 95, 98, Me, NT, 2000, XP, 2003, Vista, 7), or OS/2, and it is desired to put Debian onto the same disk without destroying the previous system. Note that the installer supports resizing of FAT and NTFS filesystems as used by DOS and Windows. Simply start the installer and when you get to the partitioning step, select the option for Manual partitioning, select the partition to resize, and specify its new size. So in most cases you should not need to use the method described below.
Before going any further, you should have decided how you will be dividing up the disk. The method in this section will only split a partition into two pieces. One will contain the original OS and the other will be used for Debian. During the installation of Debian, you will be given the opportunity to use the Debian portion of the disk as you see fit, i.e., as swap or as a file system.
The idea is to move all the data on the partition to the beginning, before changing the partition information, so that nothing will be lost. It is important that you do as little as possible between the data movement and repartitioning to minimize the chance of a file being written near the end of the partition as this will decrease the amount of space you can take from the partition.
The first thing needed is a copy of fips. Unzip the archive and copy the files RESTORRB.EXE, FIPS.EXE and ERRORS.TXT to a bootable floppy. A bootable floppy can be created using the command sys a: under DOS. fips comes with very good documentation which you may want to read. You will definitely need to read the documentation if you use a disk compression driver or a disk manager. Create the disk and read the documentation before you defragment the disk.
The next thing needed is to move all the data to the beginning of the partition. defrag, which comes standard with DOS 6.0 and later, can easily do the job. See the fips documentation for a list of other software that may do the trick. Note that if you have Windows 9x, you must run defrag from there, since DOS doesn't understand VFAT, which is used to support for long filenames, used in Windows 95 and higher.
After running the defragmenter (which can take a while on a large disk), reboot with the fips disk you created in the floppy drive. Simply type a:\fips and follow the directions.
Note that there are many other partition managers out there, in case fips doesn't do the trick for you.

3.5.1.2. Partitioning for DOS

If you are partitioning for DOS drives, or changing the size of DOS partitions, using Debian tools, many people experience problems working with the resulting FAT partitions. For instance, some have reported slow performance, consistent problems with scandisk, or other weird errors in DOS or Windows.
Apparently, whenever you create or resize a partition for DOS use, it's a good idea to fill the first few sectors with zeros. You should do this prior to running DOS's format command by executing the following command from Debian:

3.4. Meeting Minimum Hardware Requirements

Once you have gathered information about your computer's hardware, check that your hardware will let you do the type of installation that you want to do.
Depending on your needs, you might manage with less than some of the recommended hardware listed in the table below. However, most users risk being frustrated if they ignore these suggestions.
A Pentium 4, 1GHz system is the minimum recommended for a desktop system.

Table 3.2. Recommended Minimum System Requirements

Install Type	RAM (minimal)	RAM (recommended)	Hard Drive
No desktop	64 megabytes	256 megabytes	1 gigabyte
With Desktop	128 megabytes	512 megabytes	5 gigabytes

The actual minimum memory requirements are a lot less then the numbers listed in this table. Depending on the architecture, it is possible to install Debian with as little as 20MB (for s390) to 60MB (for amd64). The same goes for the disk space requirements, especially if you pick and choose which applications to install; see Section D.2, “Disk Space Needed for Tasks” for additional information on disk space requirements.
It is possible to run a graphical desktop environment on older or low-end systems, but in that case it is recommended to install a window manager that is less resource-hungry than those of the GNOME or KDE desktop environments; alternatives include xfce4, icewm and wmaker, but there are others to choose from.
It is practically impossible to give general memory or disk space requirements for server installations as those very much depend on what the server is to be used for.
Remember that these sizes don't include all the other materials which are usually to be found, such as user files, mail, and data. It is always best to be generous when considering the space for your own files and data.
Disk space required for the smooth operation of the Debian GNU/Linux system itself is taken into account in these recommended system requirements. Notably, the /var partition contains a lot of state information specific to Debian in addition to its regular contents, like logfiles. The dpkg files (with information on all installed packages) can easily consume 40MB. Also, apt-get puts downloaded packages here before they are installed. You should usually allocate at least 200MB for /var, and a lot more if you install a graphical desktop environment.

3.3. Information You Will Need

3.3.1. Documentation

3.3.1.1. Installation Manual

The document you are now reading, which is the official version of the Installation Guide for the squeeze release of Debian; available in various formats and translations.

3.3.1.2. Hardware documentation

Often contains useful information on configuring or using your hardware.

• Linux Hardware Compatibility HOWTO

3.3.2. Finding Sources of Hardware Information

In many cases, the installer will be able to automatically detect your hardware. But to be prepared, we do recommend familiarizing yourself with your hardware before the install.
Hardware information can be gathered from:

• The manuals that come with each piece of hardware.
• The BIOS setup screens of your computer. You can view these screens when you start your computer by pressing a combination of keys. Check your manual for the combination. Often, it is the Delete key.
• The cases and boxes for each piece of hardware.
• The System window in the Windows Control Panel.
• System commands or tools in another operating system, including file manager displays. This source is especially useful for information about RAM and hard drive memory.
• Your system administrator or Internet Service Provider. These sources can tell you the settings you need to set up your networking and e-mail.

Table 3.1. Hardware Information Needed for an Install

Hardware	Information You Might Need
Hard Drives	How many you have.
	Their order on the system.
	Whether IDE (also known as PATA), SATA or SCSI.
	Available free space.
	Partitions.
	Partitions where other operating systems are installed.
Monitor	Model and manufacturer.
	Resolutions supported.
	Horizontal refresh rate.
	Vertical refresh rate.
	Color depth (number of colors) supported.
	Screen size.
Mouse	Type: serial, PS/2, or USB.
	Port.
	Manufacturer.
	Number of buttons.
Network	Model and manufacturer.
	Type of adapter.
Printer	Model and manufacturer.
	Printing resolutions supported.
Video Card	Model and manufacturer.
	Video RAM available.
	Resolutions and color depths supported (these should be checked against your monitor's capabilities).

3.3.3. Hardware Compatibility

Many brand name products work without trouble on Linux. Moreover, hardware support in Linux is improving daily. However, Linux still does not run as many different types of hardware as some operating systems.
In particular, Linux usually cannot run hardware that requires a running version of Windows to work.
Although some Windows-specific hardware can be made to run on Linux, doing so usually requires extra effort. In addition, Linux drivers for Windows-specific hardware are usually specific to one Linux kernel. Therefore, they can quickly become obsolete.
So called win-modems are the most common type of this hardware. However, printers and other equipment may also be Windows-specific.
You can check hardware compatibility by:

• Checking manufacturers' web sites for new drivers.
• Looking at web sites or manuals for information about emulation. Lesser known brands can sometimes use the drivers or settings for better-known ones.
• Checking hardware compatibility lists for Linux on web sites dedicated to your architecture.
• Searching the Internet for other users' experiences.

3.3.4. Network Settings

If your computer is connected to a network 24 hours a day (i.e., an Ethernet or equivalent connection — not a PPP connection), you should ask your network's system administrator for this information.

• Your host name (you may be able to decide this on your own).
• Your domain name.
• Your computer's IP address.
• The netmask to use with your network.
• The IP address of the default gateway system you should route to, if your network has a gateway.
• The system on your network that you should use as a DNS (Domain Name Service) server.

On the other hand, if your administrator tells you that a DHCP server is available and is recommended, then you don't need this information because the DHCP server will provide it directly to your computer during the installation process.
If you use a wireless network, you should also find out:

• ESSID of your wireless network.
• WEP security key (if applicable).

3.2. Back Up Your Existing Data!

Before you start, make sure to back up every file that is now on your system. If this is the first time a non-native operating system has been installed on your computer, it's quite likely you will need to re-partition your disk to make room for Debian GNU/Linux. Anytime you partition your disk, you run a risk of losing everything on the disk, no matter what program you use to do it. The programs used in installation are quite reliable and most have seen years of use; but they are also quite powerful and a false move can cost you. Even after backing up, be careful and think about your answers and actions. Two minutes of thinking can save hours of unnecessary work.
If you are creating a multi-boot system, make sure that you have the distribution media of any other present operating systems on hand. Especially if you repartition your boot drive, you might find that you have to reinstall your operating system's boot loader, or in many cases the whole operating system itself and all files on the affected partitions.

3.1. Overview of the Installation Process

First, just a note about re-installations. With Debian, a circumstance that will require a complete re-installation of your system is very rare; perhaps mechanical failure of the hard disk would be the most common case.
Many common operating systems may require a complete installation to be performed when critical failures take place or for upgrades to new OS versions. Even if a completely new installation isn't required, often the programs you use must be re-installed to operate properly in the new OS.
Under Debian GNU/Linux, it is much more likely that your OS can be repaired rather than replaced if things go wrong. Upgrades never require a wholesale installation; you can always upgrade in-place. And the programs are almost always compatible with successive OS releases. If a new program version requires newer supporting software, the Debian packaging system ensures that all the necessary software is automatically identified and installed. The point is, much effort has been put into avoiding the need for re-installation, so think of it as your very last option. The installer is not designed to re-install over an existing system.
Here's a road map for the steps you will take during the installation process.

1. Back up any existing data or documents on the hard disk where you plan to install.
2. Gather information about your computer and any needed documentation, before starting the installation.
3. Create partitionable space for Debian on your hard disk.
4. Locate and/or download the installer software and any specialized driver files your machine requires (except Debian CD users).
5. Set up boot tapes/floppies/USB sticks, or place boot files (most Debian CD users can boot from one of the CDs).
6. Boot the installation system.
7. Select the installation language.
8. Activate the ethernet network connection, if available.
9. Create and mount the partitions on which Debian will be installed.
10. Watch the automatic download/install/setup of the base system.
11. Install a boot loader which can start up Debian GNU/Linux and/or your existing system.
12. Load the newly installed system for the first time.

For 32-bit PC you have the option of using a graphical version of the installation system. For more information about this graphical installer, see Section D.6, “The Graphical Installer”.
If you have problems during the installation, it helps to know which packages are involved in which steps. Introducing the leading software actors in this installation drama:
The installer software, debian-installer, is the primary concern of this manual. It detects hardware and loads appropriate drivers, uses dhcp-client to set up the network connection, runs debootstrap to install the base system packages, and runs tasksel to allow you to install certain additional software. Many more actors play smaller parts in this process, but debian-installer has completed its task when you load the new system for the first time.
To tune the system to your needs, tasksel allows you to choose to install various predefined bundles of software like a Web server or a Desktop environment.
One important option during the installation is whether or not to install a graphical desktop environment, consisting of the X Window System and one of the available graphical desktop environments. If you choose not to select the “Desktop environment” task, you will only have a relatively basic, command line driven system. Installing the Desktop environment task is optional because it requires a fairly large amount of disk space, and because many Debian GNU/Linux systems are servers which don't really have any need for a graphical user interface to do their job.
Just be aware that the X Window System is completely separate from debian-installer, and in fact is much more complicated. Installation and troubleshooting of the X Window System is not within the scope of this manual.

2.5. Memory and Disk Space Requirements

You must have at least 56MB of memory and 650MB of hard disk space to perform a normal installation. Note that these are fairly minimal numbers. For more realistic figures, see Section 3.4, “Meeting Minimum Hardware Requirements”.
Installation on systems with less memory^[4] or disk space available may be possible but is only advised for experienced users.

---

^[4] Installation images that support the graphical installer require more memory than images that support only the textual installer and should not be used on systems with less than 56MB of memory. If there is a choice between booting the regular and the graphical installer, the former should be selected.

2.4. Installation Media

This section will help you determine which different media types you can use to install Debian. For example, if you have a floppy disk drive on your machine, it can be used to install Debian. There is a whole chapter devoted to media, Chapter 4, Obtaining System Installation Media, which lists the advantages and disadvantages of each media type. You may want to refer back to this page once you reach that section.

2.4.1. CD-ROM/DVD-ROM

Note

Whenever you see “CD-ROM” in this manual, it applies to both CD-ROMs and DVD-ROMs, because both technologies are really the same from the operating system's point of view, except for some very old nonstandard CD-ROM drives which are neither SCSI nor IDE/ATAPI.

CD-ROM based installation is supported for some architectures. On machines which support bootable CD-ROMs, you should be able to do a completely floppy-less installation. Even if your system doesn't support booting from a CD-ROM, you can use the CD-ROM in conjunction with the other techniques to install your system, once you've booted up by other means; see Chapter 5, Booting the Installation System.
SCSI, SATA and IDE/ATAPI CD-ROMs are supported. The Linux CD-ROM HOWTO contains in-depth information on using CD-ROMs with Linux.
USB CD-ROM drives are also supported, as are FireWire devices that are supported by the ohci1394 and sbp2 drivers.

2.4.2. Hard Disk

Booting the installation system directly from a hard disk is another option for many architectures. This will require some other operating system to load the installer onto the hard disk.

2.4.3. USB Memory Stick

Many Debian boxes need their floppy and/or CD-ROM drives only for setting up the system and for rescue purposes. If you operate some servers, you will probably already have thought about omitting those drives and using an USB memory stick for installing and (when necessary) for recovering the system. This is also useful for small systems which have no room for unnecessary drives.

2.4.4. Network

The network can be used during the installation to retrieve files needed for the installation. Whether the network is used or not depends on the installation method you choose and your answers to certain questions that will be asked during the installation. The installation system supports most types of network connections (including PPPoE, but not ISDN or PPP), via either HTTP or FTP. After the installation is completed, you can also configure your system to use ISDN and PPP.
You can also boot the installation system over the network.
Diskless installation, using network booting from a local area network and NFS-mounting of all local filesystems, is another option.

2.4.5. Un*x or GNU system

If you are running another Unix-like system, you could use it to install Debian GNU/Linux without using the debian-installer described in the rest of this manual. This kind of install may be useful for users with otherwise unsupported hardware or on hosts which can't afford downtime. If you are interested in this technique, skip to the Section D.3, “Installing Debian GNU/Linux from a Unix/Linux System”.

2.4.6. Supported Storage Systems

The Debian boot disks contain a kernel which is built to maximize the number of systems it runs on. Unfortunately, this makes for a larger kernel, which includes many drivers that won't be used for your machine (see Section 8.6, “Compiling a New Kernel” to learn how to build your own kernel). Support for the widest possible range of devices is desirable in general, to ensure that Debian can be installed on the widest array of hardware.
Generally, the Debian installation system includes support for floppies, IDE (also known as PATA) drives, IDE floppies, parallel port IDE devices, SATA and SCSI controllers and drives, USB, and FireWire. The supported file systems include FAT, Win-32 FAT extensions (VFAT) and NTFS.
Disk interfaces that emulate the “AT” hard disk interface — often called MFM, RLL, IDE, or PATA — are supported. SATA and SCSI disk controllers from many different manufacturers are supported. See the Linux Hardware Compatibility HOWTO for more details.

2.3. Purchasing Hardware Specifically for GNU/Linux

There are several vendors, who ship systems with Debian or other distributions of GNU/Linux pre-installed. You might pay more for the privilege, but it does buy a level of peace of mind, since you can be sure that the hardware is well-supported by GNU/Linux.
If you do have to buy a machine with Windows bundled, carefully read the software license that comes with Windows; you may be able to reject the license and obtain a rebate from your vendor. Searching the Internet for “windows refund” may get you some useful information to help with that.
Whether or not you are purchasing a system with Linux bundled, or even a used system, it is still important to check that your hardware is supported by the Linux kernel. Check if your hardware is listed in the references found above. Let your salesperson (if any) know that you're shopping for a Linux system. Support Linux-friendly hardware vendors.

2.3.1. Avoid Proprietary or Closed Hardware

Some hardware manufacturers simply won't tell us how to write drivers for their hardware. Others won't allow us access to the documentation without a non-disclosure agreement that would prevent us from releasing the Linux source code.
Since we haven't been granted access to the documentation on these devices, they simply won't work under Linux. You can help by asking the manufacturers of such hardware to release the documentation. If enough people ask, they will realize that the free software community is an important market.

2.3.2. Windows-specific Hardware

A disturbing trend is the proliferation of Windows-specific modems and printers. In some cases these are specially designed to be operated by the Microsoft Windows operating system and bear the legend “WinModem” or “Made especially for Windows-based computers”. This is generally done by removing the embedded processors of the hardware and shifting the work they do over to a Windows driver that is run by your computer's main CPU. This strategy makes the hardware less expensive, but the savings are often not passed on to the user and this hardware may even be more expensive than equivalent devices that retain their embedded intelligence.
You should avoid Windows-specific hardware for two reasons. The first is that the manufacturers do not generally make the resources available to write a Linux driver. Generally, the hardware and software interface to the device is proprietary, and documentation is not available without a non-disclosure agreement, if it is available at all. This precludes it being used for free software, since free software writers disclose the source code of their programs. The second reason is that when devices like these have had their embedded processors removed, the operating system must perform the work of the embedded processors, often at real-time priority, and thus the CPU is not available to run your programs while it is driving these devices. Since the typical Windows user does not multi-process as intensively as a Linux user, the manufacturers hope that the Windows user simply won't notice the burden this hardware places on their CPU. However, any multi-processing operating system, even Windows 2000 or XP, suffers from degraded performance when peripheral manufacturers skimp on the embedded processing power of their hardware.
You can help improve this situation by encouraging these manufacturers to release the documentation and other resources necessary for us to program their hardware, but the best strategy is simply to avoid this sort of hardware until it is listed as working in the Linux Hardware Compatibility HOWTO.

2.2. Devices Requiring Firmware

Besides the availability of a device driver, some hardware also requires so-called firmware or microcode to be loaded into the device before it can become operational. This is most common for network interface cards (especially wireless NICs), but for example some USB devices and even some hard disk controllers also require firmware.
In most cases firmware is non-free according to the criteria used by the Debian GNU/Linux project and thus cannot be included in the main distribution or in the installation system. If the device driver itself is included in the distribution and if Debian GNU/Linux legally can distribute the firmware, it will often be available as a separate package from the non-free section of the archive.
However, this does not mean that such hardware cannot be used during an installation. Starting with Debian GNU/Linux 5.0, debian-installer supports loading firmware files or packages containing firmware from a removable medium, such as a floppy disk or USB stick. See Section 6.4, “Loading Missing Firmware” for detailed information on how to load firmware files or packages during the installation.

2.1. Supported Hardware

Debian does not impose hardware requirements beyond the requirements of the Linux or kFreeBSD kernel and the GNU tool-sets. Therefore, any architecture or platform to which the Linux or kFreeBSD kernel, libc, gcc, etc. have been ported, and for which a Debian port exists, can run Debian. Please refer to the Ports pages at http://www.debian.org/ports/i386/ for more details on 32-bit PC architecture systems which have been tested with Debian GNU/Linux.
Rather than attempting to describe all the different hardware configurations which are supported for 32-bit PC, this section contains general information and pointers to where additional information can be found.

2.1.1. Supported Architectures

Debian GNU/Linux 6.0 supports eleven major architectures and several variations of each architecture known as “flavors”.

Architecture	Debian Designation	Subarchitecture	Flavor
Intel x86-based	i386
AMD64 & Intel EM64T	amd64
ARM	armel	Intel IOP32x	iop32x
		Intel IXP4xx	ixp4xx
		Marvell Kirkwood	kirkwood
		Marvell Orion	orion5x
		Versatile	versatile
HP PA-RISC	hppa	PA-RISC 1.1	32
		PA-RISC 2.0	64
Intel IA-64	ia64
MIPS (big endian)	mips	SGI IP22 (Indy/Indigo 2)	r4k-ip22
		SGI IP32 (O2)	r5k-ip32
		MIPS Malta (32 bit)	4kc-malta
		MIPS Malta (64 bit)	5kc-malta
MIPS (little endian)	mipsel	Cobalt	cobalt
		MIPS Malta (32 bit)	4kc-malta
		MIPS Malta (64 bit)	5kc-malta
IBM/Motorola PowerPC	powerpc	PowerMac	pmac
		PReP	prep
Sun SPARC	sparc	sun4u	sparc64
		sun4v
IBM S/390	s390	IPL from VM-reader and DASD	generic
		IPL from tape	tape

Debian GNU/kFreeBSD 6.0 supports two architectures.

Architecture	Debian Designation
Intel x86-based	kfreebsd-i386
AMD64 & Intel EM64T	kfreebsd-amd64

This document covers installation for the 32-bit PC architecture using the Linux kernel. If you are looking for information on any of the other Debian-supported architectures take a look at the Debian-Ports pages.

2.1.2. CPU, Main Boards, and Video Support

Complete information concerning supported peripherals can be found at Linux Hardware Compatibility HOWTO. This section merely outlines the basics.

2.1.2.1. CPU

Nearly all x86-based (IA-32) processors still in use in personal computers are supported, including all varieties of Intel's "Pentium" series. This also includes 32-bit AMD and VIA (former Cyrix) processors, and processors like the Athlon XP and Intel P4 Xeon.
However, Debian GNU/Linux squeeze will not run on 386 or earlier processors. Despite the architecture name "i386", support for actual 80386 processors (and their clones) was dropped with the Sarge (r3.1) release of Debian^[2]. (No version of Linux has ever supported the 286 or earlier chips in the series.) All i486 and later processors are still supported^[3].

Note

If your system has a 64-bit processor from the AMD64 or Intel EM64T families, you will probably want to use the installer for the amd64 architecture instead of the installer for the (32-bit) i386 architecture.

2.1.2.2. I/O Bus

The system bus is the part of the motherboard which allows the CPU to communicate with peripherals such as storage devices. Your computer must use the ISA, EISA, PCI, PCIe, PCI-X, or VESA Local Bus (VLB, sometimes called the VL bus). Essentially all personal computers sold in recent years use one of these.

2.1.3. Laptops

Laptops are also supported and nowadays most laptops work out of the box. In case a laptop contains specialized or proprietary hardware, some specific functions may not be supported. To see if your particular laptop works well with GNU/Linux, see for example the Linux Laptop pages.

2.1.4. Multiple Processors

Multiprocessor support — also called “symmetric multiprocessing” or SMP — is available for this architecture. The standard Debian 6.0 kernel image has been compiled with SMP-alternatives support. This means that the kernel will detect the number of processors (or processor cores) and will automatically deactivate SMP on uniprocessor systems.
The 486 flavour of the Debian kernel image packages for 32-bit PC is not compiled with SMP support.

2.1.5. Graphics Card Support

You should be using a VGA-compatible display interface for the console terminal. Nearly every modern display card is compatible with VGA. Ancient standards such CGA, MDA, or HGA should also work, assuming you do not require X11 support. Note that X11 is not used during the installation process described in this document unless the graphical installer was explicitly selected.
Debian's support for graphical interfaces is determined by the underlying support found in X.Org's X11 system. Most AGP, PCI, PCIe, and PCI-X video cards work under X.Org. Details on supported graphics buses, cards, monitors, and pointing devices can be found at http://xorg.freedesktop.org/. Debian 6.0 ships with X.Org version 7.5.

2.1.6. Network Connectivity Hardware

Almost any network interface card (NIC) supported by the Linux kernel should also be supported by the installation system; modular drivers should normally be loaded automatically. This includes most PCI and PCMCIA cards. Many older ISA cards are supported as well.
ISDN is supported, but not during the installation.

2.1.6.1. Wireless Network Cards

Wireless networking is in general supported as well and a growing number of wireless adapters are supported by the official Linux kernel, although many of them do require firmware to be loaded. If firmware is needed, the installer will prompt you to load firmware. See Section 6.4, “Loading Missing Firmware” for detailed information on how to load firmware during the installation.
Wireless NICs that are not supported by the official Linux kernel can generally be made to work under Debian GNU/Linux, but are not supported during the installation.
Support for encrypted wireless during installation is currently limited to WEP. If your access point uses stronger encryption, it cannot be used during the installation process.
If there is a problem with wireless and there is no other NIC you can use during the installation, it is still possible to install Debian GNU/Linux using a full CD-ROM or DVD image. Select the option to not configure a network and install using only the packages available from the CD/DVD. You can then install the driver and firmware you need after the installation is completed (after the reboot) and configure your network manually.
In some cases the driver you need may not be available as a Debian package. You will then have to look if there is source code available in the internet and compile the driver yourself. How to do this is outside the scope of this manual. If no Linux driver is available, your last resort is to use the ndiswrapper package, which allows you to use a Windows driver.

2.1.7. Braille Displays

Support for braille displays is determined by the underlying support found in brltty. Most displays work under brltty, connected via either a serial port, USB or bluetooth. Details on supported braille devices can be found on the brltty website. Debian GNU/Linux 6.0 ships with brltty version 4.2.

2.1.8. Hardware Speech Synthesis

Support for hardware speech synthesis devices is determined by the underlying support found in speakup. speakup only supports integrated boards and external devices connected to a serial port (no USB or serial-to-USB adapters are supported). Details on supported hardware speech synthesis devices can be found on the speakup website. Debian GNU/Linux 6.0 ships with speakup version 3.1.5.

2.1.9. Peripherals and Other Hardware

Linux supports a large variety of hardware devices such as mice, printers, scanners, PCMCIA and USB devices. However, most of these devices are not required while installing the system.
USB hardware generally works fine, only some USB keyboards may require additional configuration (see Section 3.6.4, “Hardware Issues to Watch Out For”).
Again, see the Linux Hardware Compatibility HOWTO to determine whether your specific hardware is supported by Linux.

---

^[2] We have long tried to avoid this, but in the end it was necessary due a unfortunate series of issues with the compiler and the kernel, starting with an bug in the C++ ABI provided by GCC. You should still be able to run Debian GNU/Linux on actual 80386 processors if you compile your own kernel and compile all packages from source, but that is beyond the scope of this manual.

^[3] Many Debian packages will actually run slightly faster on modern computers as a positive side effect of dropping support for these old chips. The i486, introduced in 1989, has three opcodes (bswap, cmpxchg, and xadd) which the i386, introduced in 1986, did not have. Previously, these could not be easily used by most Debian packages; now they can.

1.8. About Copyrights and Software Licenses

We're sure that you've read some of the licenses that come with most commercial software — they usually say that you can only use one copy of the software on a single computer. This system's license isn't like that at all. We encourage you to put a copy of Debian GNU/Linux on every computer in your school or place of business. Lend your installation media to your friends and help them install it on their computers! You can even make thousands of copies and sell them — albeit with a few restrictions. Your freedom to install and use the system comes directly from Debian being based on free software.
Calling software free doesn't mean that the software isn't copyrighted, and it doesn't mean that CDs containing that software must be distributed at no charge. Free software, in part, means that the licenses of individual programs do not require you to pay for the privilege of distributing or using those programs. Free software also means that not only may anyone extend, adapt, and modify the software, but that they may distribute the results of their work as well.

Note

The Debian project, as a pragmatic concession to its users, does make some packages available that do not meet our criteria for being free. These packages are not part of the official distribution, however, and are only available from the contrib or non-free areas of Debian mirrors or on third-party CD-ROMs; see the Debian FAQ, under “The Debian FTP archives”, for more information about the layout and contents of the archives.

Many of the programs in the system are licensed under the GNU General Public License, often simply referred to as “the GPL”. The GPL requires you to make the source code of the programs available whenever you distribute a binary copy of the program; that provision of the license ensures that any user will be able to modify the software. Because of this provision, the source code^[1] for all such programs is available in the Debian system.
There are several other forms of copyright statements and software licenses used on the programs in Debian. You can find the copyrights and licenses for every package installed on your system by looking in the file /usr/share/doc/package-name/copyright once you've installed a package on your system.
For more information about licenses and how Debian determines whether software is free enough to be included in the main distribution, see the Debian Free Software Guidelines.
The most important legal notice is that this software comes with no warranties. The programmers who have created this software have done so for the benefit of the community. No guarantee is made as to the suitability of the software for any given purpose. However, since the software is free, you are empowered to modify that software to suit your needs — and to enjoy the benefits of the changes made by others who have extended the software in this way.

1.7. Organization of This Document

This document is meant to serve as a manual for first-time Debian users. It tries to make as few assumptions as possible about your level of expertise. However, we do assume that you have a general understanding of how the hardware in your computer works.
Expert users may also find interesting reference information in this document, including minimum installation sizes, details about the hardware supported by the Debian installation system, and so on. We encourage expert users to jump around in the document.
In general, this manual is arranged in a linear fashion, walking you through the installation process from start to finish. Here are the steps in installing Debian GNU/Linux, and the sections of this document which correlate with each step:

1. Determine whether your hardware meets the requirements for using the installation system, in Chapter 2, System Requirements.
2. Backup your system, perform any necessary planning and hardware configuration prior to installing Debian, in Chapter 3, Before Installing Debian GNU/Linux. If you are preparing a multi-boot system, you may need to create partitionable space on your hard disk for Debian to use.
3. In Chapter 4, Obtaining System Installation Media, you will obtain the necessary installation files for your method of installation.
4. Chapter 5, Booting the Installation System describes booting into the installation system. This chapter also discusses troubleshooting procedures in case you have problems with this step.
5. Perform the actual installation according to Chapter 6, Using the Debian Installer. This involves choosing your language, configuring peripheral driver modules, configuring your network connection, so that remaining installation files can be obtained directly from a Debian server (if you are not installing from a CD), partitioning your hard drives and installation of a base system, then selection and installation of tasks. (Some background about setting up the partitions for your Debian system is explained in Appendix C, Partitioning for Debian.)
6. Boot into your newly installed base system, from Chapter 7, Booting Into Your New Debian System.

Once you've got your system installed, you can read Chapter 8, Next Steps and Where to Go From Here. That chapter explains where to look to find more information about Unix and Debian, and how to replace your kernel.
Finally, information about this document and how to contribute to it may be found in Appendix E, Administrivia.

1.6. Getting the Newest Version of This Document

This document is constantly being revised. Be sure to check the Debian 6.0 pages for any last-minute information about the 6.0 release of the Debian GNU/Linux system. Updated versions of this installation manual are also available from the official Install Manual pages.

1.5. Getting Debian

For information on how to download Debian GNU/Linux from the Internet or from whom official Debian CDs can be purchased, see the distribution web page. The list of Debian mirrors contains a full set of official Debian mirrors, so you can easily find the nearest one.
Debian can be upgraded after installation very easily. The installation procedure will help set up the system so that you can make those upgrades once installation is complete, if need be.

1.4. What is Debian GNU/kFreeBSD?

Debian GNU/kFreeBSD is a Debian GNU system with the kFreeBSD kernel.
This port of Debian is currently only being developed for the i386 and amd64 architectures, although ports to other architectures is possible.
Please note that Debian GNU/kFreeBSD is not a Linux system, and thus some information on Linux system may not apply to it.
For more information, see the Debian GNU/kFreeBSD ports page and the <debian-bsd@lists.debian.org> mailing list.

1.3. What is Debian GNU/Linux?

The combination of Debian's philosophy and methodology and the GNU tools, the Linux kernel, and other important free software, form a unique software distribution called Debian GNU/Linux. This distribution is made up of a large number of software packages. Each package in the distribution contains executables, scripts, documentation, and configuration information, and has a maintainer who is primarily responsible for keeping the package up-to-date, tracking bug reports, and communicating with the upstream author(s) of the packaged software. Our extremely large user base, combined with our bug tracking system ensures that problems are found and fixed quickly.
Debian's attention to detail allows us to produce a high-quality, stable, and scalable distribution. Installations can be easily configured to serve many roles, from stripped-down firewalls to desktop scientific workstations to high-end network servers.
Debian is especially popular among advanced users because of its technical excellence and its deep commitment to the needs and expectations of the Linux community. Debian also introduced many features to Linux that are now commonplace.
For example, Debian was the first Linux distribution to include a package management system for easy installation and removal of software. It was also the first Linux distribution that could be upgraded without requiring reinstallation.
Debian continues to be a leader in Linux development. Its development process is an example of just how well the Open Source development model can work — even for very complex tasks such as building and maintaining a complete operating system.
The feature that most distinguishes Debian from other Linux distributions is its package management system. These tools give the administrator of a Debian system complete control over the packages installed on that system, including the ability to install a single package or automatically update the entire operating system. Individual packages can also be protected from being updated. You can even tell the package management system about software you have compiled yourself and what dependencies it fulfills.
To protect your system against “Trojan horses” and other malevolent software, Debian's servers verify that uploaded packages come from their registered Debian maintainers. Debian packagers also take great care to configure their packages in a secure manner. When security problems in shipped packages do appear, fixes are usually available very quickly. With Debian's simple update options, security fixes can be downloaded and installed automatically across the Internet.
The primary, and best, method of getting support for your Debian GNU/Linux system and communicating with Debian Developers is through the many mailing lists maintained by the Debian Project (there are more than 245 at this writing). The easiest way to subscribe to one or more of these lists is visit Debian's mailing list subscription page and fill out the form you'll find there.

1.2. What is GNU/Linux?

Linux is an operating system: a series of programs that let you interact with your computer and run other programs.
An operating system consists of various fundamental programs which are needed by your computer so that it can communicate and receive instructions from users; read and write data to hard disks, tapes, and printers; control the use of memory; and run other software. The most important part of an operating system is the kernel. In a GNU/Linux system, Linux is the kernel component. The rest of the system consists of other programs, many of which were written by or for the GNU Project. Because the Linux kernel alone does not form a working operating system, we prefer to use the term “GNU/Linux” to refer to systems that many people casually refer to as “Linux”.
Linux is modelled on the Unix operating system. From the start, Linux was designed to be a multi-tasking, multi-user system. These facts are enough to make Linux different from other well-known operating systems. However, Linux is even more different than you might imagine. In contrast to other operating systems, nobody owns Linux. Much of its development is done by unpaid volunteers.
Development of what later became GNU/Linux began in 1984, when the Free Software Foundation began development of a free Unix-like operating system called GNU.
The GNU Project has developed a comprehensive set of free software tools for use with Unix™ and Unix-like operating systems such as Linux. These tools enable users to perform tasks ranging from the mundane (such as copying or removing files from the system) to the arcane (such as writing and compiling programs or doing sophisticated editing in a variety of document formats).
While many groups and individuals have contributed to Linux, the largest single contributor is still the Free Software Foundation, which created not only most of the tools used in Linux, but also the philosophy and the community that made Linux possible.
The Linux kernel first appeared in 1991, when a Finnish computing science student named Linus Torvalds announced an early version of a replacement kernel for Minix to the Usenet newsgroup comp.os.minix. See Linux International's Linux History Page.
Linus Torvalds continues to coordinate the work of several hundred developers with the help of a number of subsystem maintainers. There is an official website for the Linux kernel. More information about the linux-kernel mailing list can be found on the linux-kernel mailing list FAQ.
Linux users have immense freedom of choice in their software. For example, Linux users can choose from a dozen different command line shells and several graphical desktops. This selection is often bewildering to users of other operating systems, who are not used to thinking of the command line or desktop as something that they can change.
Linux is also less likely to crash, better able to run more than one program at the same time, and more secure than many operating systems. With these advantages, Linux is the fastest growing operating system in the server market. More recently, Linux has begun to be popular among home and business users as well.

1.1. What is Debian?

Debian is an all-volunteer organization dedicated to developing free software and promoting the ideals of the Free Software community. The Debian Project began in 1993, when Ian Murdock issued an open invitation to software developers to contribute to a complete and coherent software distribution based on the relatively new Linux kernel. That relatively small band of dedicated enthusiasts, originally funded by the Free Software Foundation and influenced by the GNU philosophy, has grown over the years into an organization of around 886 Debian Developers.
Debian Developers are involved in a variety of activities, including Web and FTP site administration, graphic design, legal analysis of software licenses, writing documentation, and, of course, maintaining software packages.
In the interest of communicating our philosophy and attracting developers who believe in the principles that Debian stands for, the Debian Project has published a number of documents that outline our values and serve as guides to what it means to be a Debian Developer:

• The Debian Social Contract is a statement of Debian's commitments to the Free Software Community. Anyone who agrees to abide to the Social Contract may become a maintainer. Any maintainer can introduce new software into Debian — provided that the software meets our criteria for being free, and the package follows our quality standards.
• The Debian Free Software Guidelines are a clear and concise statement of Debian's criteria for free software. The DFSG is a very influential document in the Free Software Movement, and was the foundation of the The Open Source Definition.
• The Debian Policy Manual is an extensive specification of the Debian Project's standards of quality.

Debian developers are also involved in a number of other projects; some specific to Debian, others involving some or all of the Linux community. Some examples include:

• The Linux Standard Base (LSB) is a project aimed at standardizing the basic GNU/Linux system, which will enable third-party software and hardware developers to easily design programs and device drivers for Linux-in-general, rather than for a specific GNU/Linux distribution.
• The Filesystem Hierarchy Standard (FHS) is an effort to standardize the layout of the Linux file system. The FHS will allow software developers to concentrate their efforts on designing programs, without having to worry about how the package will be installed in different GNU/Linux distributions.
• Debian Jr. is an internal project, aimed at making sure Debian has something to offer to our youngest users.

For more general information about Debian, see the Debian FAQ.

Problems with installing Catalyst Control Center

Hey,

I own a Dell Studio 1535 with an Ati Mobility Radeon 3450 and Windows Vista 32.

I made a faulty installation of ATI's Catalyst Control Center a while back, and have been unable to use CCC since then. In addition, I've been getting a "Could not load file assembly Cli.Implementation..." error message on startup, which also pops up everytime I try to run CCC through Vista. I followed Crossfire's advice in this ,thread which reads as follows:
<

Following error message appears after installing Catalyst 7.2 and launching Catalyst Control Center
Could not load file or assembly 'CLI.Implementation, Version=2.0.2589.34531, Culture=neutral, PublicKey Token=90ba9c70f846762e' or one of its dependencies. The system cannot find the file specified


If you experience this issue, please try the following steps to resolve. If the steps do not resolve the issue, please PM me.


This can happen if you uninstall / reinstall or do an upgrade of CCC, IF certain assembly files are not properly GAC’ed during install, or removed from the GAC during uninstall (.Net “global assembly cache”).


Uninstalling CCC, and then:


1. Check that (Program Files folder )/ATI Technologies/ATI.ACE is empty
2. Check (Windows folder)/Assembly folder to see if there's any files with Public Key Token of "90ba9c70f846762e" (Sort by Public key token to get a easier view). All these tokens should be uninstalled by right clicking and uninstalling.
3. Check that (Document and Settings)/(User)/AppData/Local/ATI/ACE is empty
4. Reinstall CCC


OK I have received feedback that these steps dont work.

Please try the following and let me know. If you delete the wrong registery key, that is your problem. Please be diligent and backup your registery before completing these steps. If you are unsure, then the registery is not the place for you to be.
1. Check that registry locations are empty:
a. HKCU/Software/ATI/ACE
b. HKLM/Software/ATI/ACE
2. Check that (Program Files folder )/ATI Technologies/ATI.ACE is empty
3. Check (Windows folder)/Assembly folder to see if there's any files with Public Key Token of "90ba9c70f846762e" (Sort by Public key token to get a easier view). All these tokens should be uninstalled by right clicking and uninstalling.
4. Check that (Document and Settings)/(User)/AppData/Local/ATI/ACE is empty
5. Reinstall CCC
>

Following this, I managed to get rid of the error and I think CCC was fully removed from my computer as well. However, when I downloaded the CCC setup file, ATI Install Manager doesnt seem to see it. It only offers me the option of installing the ATI Display Driver and other stuff without allowing me to install Catalyst Command Center.

Could someone tell me what I could do? Is there any way I can manually install CCC without going through the ATI Install Manager? Or what other steps should I take short of a full system restore which I cant afford right now because of too much unsaveable data.

Macam-macam Kode Error pada Internet dan Pengertiannya

Terkadang saat sedang asik browsing di internet, entah itu saat membuka sebuah halaman website, membuka email, mendownload file dan aktivitas lainnya, tiba-tiba muncul pesan error pada halaman web yang sedang aktif. Kode error-nya pun bermacam-macam dengan kode yang berbeda. Nah, lebih baik jika sobat mengenal jenis-jenis error pada internet serta pengertiannya, sehingga tahu langkah apa yang harus diambil untuk mengatasinya.

Kode Error pada internet dan penjelasannya

Kode Error 400

400 artinya adalah kode untuk Bad Requset Error. Periksa terlebih dahulu address barpada browser sobat, mungkinsobat mengetik alamat yang salah dan server tidak dapat mengenali request yang diminta.

Kode Error 401

Error 401 biasanya terjadi jika kita membuka halaman yang unauthorized, atau membutuhkan log in terlebih dahulu sebelum menuju ke halaman tersebut. Hampir semua situs saat ini akan secara otomatis meminta username dan password terlebih dahulu tanpa menampilkan halaman error 401. Setelah sobat berhasil log in, maka halaman tersebut akan otomatis redirect ke halaman tadi. Tapi masih ada juga website yang akan langsung menampilkan halaman 401, so sobat harus mengenalinya agar tidak langsung pusing menghadapi halaman error 401.

Kode Error 402

Kode error 402 menunjukkan Payment Required Error.

Kode Error 403

Halaman 403 akan muncul jika kita membuka sebuah halaman terlarang. Itu artinya entah domain memang diblock oleh provider internet yang kita gunakan, atau bisa juga IP address kita diblock oleh pemilik website tersebut. Misalnya seperti di Indonesia, maka jika kita membuka website yang diblock oleh pemerintah, seperti situs porno dan situs judi, maka akan muncul kode error ini. Umumnya halaman ini juga berisi pesan peringatan atau pemberitahuan.

Kode Error 404

404 mungkin kode error yang sangat sering kita temui saat sedang menggunakan internet. Halaman error 404 (page not found) akan muncul jika kita membuka halaman yang tidak ada alias non-exist. Kemungkinan halaman tersebut telah terhapus sehingga tidak eksis lagi. Bisa juga jika kita salah mengetikkan alamat. Periksa terlebih dahulu address bar di browser. Jika alamat sudah benar, berarti halaman tersebut sudah dihapus dari peredaran.

Kode Error 408

Kode error 408 berarti Requset Time Out. Artinya adalah waktu request telah habis karena terlalu lama. Biasa terjadi jika koneksi internet sedang lemot, sehingga saat waktu request sudah habis, error 408 akan muncul. Kalau sobat sering mengakses internet menggunakan handphone pasti sering mengalami error seperti ini (request time out). Ulangi request atau refresh halaman tersebut untuk mengulang akses. Jika masih berlanjut, berarti jaringan internet sedang tidak bagus.


Itulah tadi sedikit penjelasan mengenai berbagai tipe error pada internet.


Cr. Edutecnolife