Sie sind auf Seite 1von 6

http://sourcedaddy.com/windows-7 http://search-ebooks.eu/f/features-win-7 The normal startup sequence for Windows 7 is: Power-on self test (POST) phase.

Initial startup phase. Windows Boot Manager phase. Windows Boot Loader phase. Kernel loading phase. Logon phase. This sequence will vary if the computer is resuming from hibernation or if a non -Windows 7 option is selected during the Windows Boot Manager phase. The followi ng sections describe the phases of a normal startup process in more detail.

Power-on Self Test Phase

As soon as you turn on a computer, its processor begins to carry out the program ming instructions contained in the BIOS or EFI. The BIOS and EFI, which are type s of firmware, contain the processor-dependent code that starts the computer reg ardless of the operating system installed. The first set of startup instructions is the POST, which is responsible for the following system and diagnostic funct ions: Performs initial hardware checks, such as determining the amount of memory prese nt Verifies that the devices needed to start an operating system, such as a hard di sk, are present Retrieves system configuration settings from nonvolatile memory, which is locate d on the motherboard The contents of the nonvolatile memory remain even after you shut down the compu ter. Examples of hardware settings stored in the nonvolatile memory include devi ce boot order and Plug and Play (PnP) information. After the motherboard POST completes, add-on adapters that have their own firmwa re (for example, video and hard drive controllers) carry out internal diagnostic tests. If startup fails before or during POST, your computer is experiencing a hardware failure. Generally, the BIOS or EFI displays an error message that indicates th e nature of the problem. If video is not functioning correctly, the BIOS or EFI usually indicates the nature of the failure with a series of beeps. To access and change system and peripheral firmware settings, consult the system documentation provided by the manufacturer. For more information, refer to your computer's documentation and see the section titled "How to Diagnose Hardware P roblems" later in this tutorial.

Initial Startup Phase

After the POST, computers must find and load the Windows Boot Manager. Older BIO S computers and newer EFI computers do this slightly differently, as the followi ng sections describe. Learn more: Initial Startup Phase for BIOS Computers, Initial Startup Phase for EFI Computers, Windows Boot Manager Phase, Windows Boot Loader Phase, Kernel Loa ding Phase, Control Sets, Values for the Start Registry Entry, Value Description s for Type Entries, Other Registry Entries in the Servicename Subkeys, Session M anager, Logon Phase, Important Startup Files, How to Configure Startup Settings, How to Use the Startup And Recovery Dialog Box, How to Use the System Configura tion Tool, How to Use BCDEdit and more.

Initial Startup Phase for BIOS Computers

After the POST, the settings that are stored in the nonvolatile memory, such as boot order, determine the devices that the computer can use to start an operatin g system. In addition to floppy disks or hard disks attached to Advanced Technol ogy Attachment (ATA), Serial ATA, and small computer system interface (SCSI) con trollers, computers can typically start an operating system from other devices, such as the following: CDs or DVDs Network adapters Universal serial bus (USB) flash drives Removable disks Secondary storage devices installed in docking stations for portable computers It is possible to specify a custom boot order, such as CDROM, Floppy, Hard Disk. When you specify CDROM, Floppy, Hard Disk as a boot order, the following events occur at startup: The computer searches the CD-ROM for bootable media. If a bootable CD or DVD is present, the computer uses the media as the startup device. Otherwise, the compu ter searches the next device in the boot order. You cannot use a non-bootable CD or DVD to start your system. The presence of a non-bootable CD or DVD in the CD -ROM drive can add to the time the system requires to start. If you do not inten d to start the computer from CD, remove all CDs from the CD-ROM drive before res tarting. The computer searches the floppy disk for bootable media. If a bootable floppy i s present, the computer uses the floppy disk as the startup device and loads the first sector (sector 0, the floppy disk boot sector) into memory. Otherwise, th e computer searches the next device in the boot order or displays an error messa ge. The computer uses the hard disk as the startup device. The computer typically us es the hard disk as the startup device only when the CD-ROM drive and the floppy disk drive are empty. There are exceptions in which code on bootable media transfers control to the ha rd disk. For example, when you start your system by using the bootable Windows D VD, Windows Setup checks the hard disk for Windows installations. If one is foun d, you have the option of bypassing DVD startup by not responding to the Press A

ny Key To Boot From CD Or DVD prompt that appears. This prompt is actually displ ayed by the startup program located on the Windows DVD, not by your computer's h ardware. If startup fails during the initial startup phase, you are experiencing a proble m with the BIOS configuration, the disk subsystem, or the file system. The follo wing error message is common during this phase. It indicates that none of the co nfigured bootable media types was available. Non-system disk or disk error Replace and press any key when ready If you changed the disk configuration recently, verify that all cables are prope rly connected and jumpers are correctly configured. If booting from the hard dis k, verify that all removable media have been removed. If booting from a CD or DV D, verify that the BIOS is configured to start from the CD or DVD and that the W indows medium is present. If the disk subsystem and BIOS are configured correctl y, the problem may be related to the file system. For instructions on repairing the Master Boot Record (MBR) and the boot sector, see the section titled "How to Run Startup Repair" later in this tutorial. For more information about configur ing the boot order, consult your computer's documentation. If you boot from the hard disk, the computer reads the boot code instructions lo cated on the MBR. The MBR is the first sector of data on the startup hard disk. The MBR contains instructions (called boot code) and a table (called a partition table) that identify primary and extended partitions. The BIOS reads the MBR in to memory and transfers control to the code in the MBR. The computer then searches the partition table for the active partition, also kn own as a bootable partition. The first sector of the active partition contains b oot code that enables the computer to do the following: Read the contents of the file system used. Locate and start a 16-bit stub program (Bootmgr) in the root directory of the bo ot volume. This stub program switches the processor into 32- or 64-bit Protected mode and loads the 32- or 64-bit Windows Boot Manager, which is stored in the s ame Bootmgr file. After the Windows Boot Manager loads, startup is identical for both BIOS and EFI computers. Note The stub program is necessary because 32-bit and 64-bit computers first sta rt in Real mode. In Real mode, the processor disables certain features to allow compatibility with software designed to run on 8-bit and 16-bit processors. The Windows Boot Manager is 32-bit or 64-bit, however, so the stub program sets up t he BIOS computer to run the 32-bit or 64-bit software properly. If an active partition does not exist or if boot sector information is missing o r corrupt, a message similar to any of the following might appear: Invalid partition table Error loading operating system Missing operating system If an active partition is successfully located, the code in the boot sector loca tes and starts Windows Boot Loader (WinLoad) and the BIOS transfers execution to it.

Initial Startup Phase for EFI Computers

Startup for EFI computers initially differs from startup for BIOS computers. EFI computers have a built-in boot manager that enables the computer's hardware to choose from multiple operating systems based on user input. When you install Win dows 7 on an EFI computer, Windows adds a single entry to the EFI boot manager w ith the title Windows Boot Manager. This entry points to the \Efi\Microsoft\Boot \Bootmgfw.efi 32-bit or 64-bit EFI executable program-the Windows Boot Manager. This is the same Windows Boot Manager that is eventually loaded on BIOS-based co mputers. Windows configures the EFI boot manager to display the EFI startup menu for only 2 seconds and then load the Windows Boot Manager by default to minimiz e complexity and startup time. If you install a different operating system or manually change the EFI boot mana ger settings, EFI might no longer load the Windows Boot Manager. To resolve this problem, use the Startup Repair tool, as described in the section titled "The P rocess of Troubleshooting Startup" later in this tutorial. Alternatively, you mi ght be able to update the EFI boot manager settings manually using your computer 's built-in EFI tools. For more information about configuring EFI, consult your computer's documentation.

Windows Boot Manager Phase

The Windows Boot Manager is capable of natively reading supported file systems, and it uses that capability to parse the BCD registry file without fully loading the file system. For computers that have a single operating system, Windows Boot Manager never di splays a user interface. It does, however, wait for a few moments to allow the u ser to press a key to display the standard boot menu or to press F8 to choose Ad vanced Boot Options. If the user does not press a key within a few seconds of PO ST completing, Windows Boot Manager starts the Windows Boot Loader, which in tur n starts Windows 7. Windows Boot Manager enables you to choose from multiple operating systems or st art Windows Memory Diagnostics. During startup, you can interrupt the default behavior of Windows Boot Manager t o view the Advanced Boot Options. For computers with multiple operating systems installed (such as both Windows 7 and Windows XP), Windows Boot Manager displays a menu of operating system choice s at startup. Depending on what you choose, Windows Boot Manager will start a di fferent process: If you choose s Boot Loader If you choose 3, Windows XP Windows Boot ion phase. If you select Windows Vista or Windows 7, Windows Boot Manager starts the Window to open Windows. Earlier Version Of Windows or another entry for Windows Server 200 Professional, Microsoft Windows 2000, or Microsoft Windows NT 4.0, Manager starts Ntldr, which then proceeds with the hardware detect another operating system, control is passed to the boot sector for

the other operating system. If you choose Windows Memory Diagnostic by pressing the Tab key, Windows Boot Ma nager starts the diagnostic tool without first opening Windows.

Windows Boot Loader Phase

The Windows Boot Manager starts the Windows Boot Loader phase when the user choo ses to load Windows Vista or Windows 7. The Windows Boot Loader does the followi ng: Loads the operating system kernel, Ntoskrnl.exe, but does not yet run it. Loads the Hardware Abstraction Layer (HAL), Hal.dll. This will not be used until the kernel is run. Loads the system registry hive (System32\Config\System) into memory. Scans the HKEY_LOCAL_MACHINE\SYSTEM\Services key for device drivers and loads al l drivers that are configured for the boot class into memory. The Windows Boot L oader does not, however, initiate the drivers. Drivers are not initiated until t he kernel loading phase. Enables paging. Passes control to the operating system kernel, which starts the next phase.

Kernel Loading Phase

The Windows Boot Loader is responsible for loading the Windows kernel (Ntoskrnl. exe) and the HAL into memory. Together, the kernel and the HAL initialize a grou p of software features that are called the Windows executive. The Windows execut ive processes the configuration information stored in the registry in HKLM\SYSTE M\CurrentControlSet and starts services and drivers. The following sections prov ide more detail about the kernel loading phase.

A master boot record (MBR) is a type of boot sector popularized by the IBM Perso nal Computer.[1] It consists of a sequence of 512 bytes located at the first sec tor of a data storage device such as a hard disk. MBRs are usually placed on sto rage devices intended for use with IBM PC-compatible systems. The MBR may be used for one or more of the following: Holding a partition table, which describes the partitions of a storage device. I n this context the boot sector may also be called a partition sector. Bootstrapping an operating system. The BIOS built into a PC-compatible computer

loads the MBR from the storage device and passes execution to machine code instr uctions at the beginning of the MBR. Uniquely identifying individual disk media, with a 32-bit disk signature, even t hough it may never be used by the operating system.[2][3][4][5] Because of the broad popularity of PC-compatible computers, the MBR format is wi dely used, to the extent of being supported by computer operating systems in add ition to other pre-existing or cross-platform standards for bootstrapping and pa rtitioning.[6]

Features of windows 7 Windows 7 is one of the successful operating system that is released after the w indows XP and is being used now. As everyone know the windows vista did not sell well in the market and it had lots of advancements to that of the windows XP bu t along with that it had lots of drawbacks also. The rectified version was the W indows 7. Windows 7 has lots of graphical components implemented and it can also be said as the most attractive operating system of the Microsoft. Even thought the windows 7 is not a open source operating system people always prefer the win dows 7 because of the reliability factor.

The Graphical User Interface (GUI) components are good in the Windows 7. The sta rt up and the shut down features are extremely fast. The operating system copies very fast to the Random access memory (RAM) during the start up. The window 7 i s proved to be great in the latest motherboard and the processors. There are als o various themes that are available along with the operating system and various themes can also be created and implemented by the user. The drivers for all the hardware comes along with the operating system. There is no necessity for the ex ternal driver components for the operating system. Difference between Windows XP and Windows 7 There are lots of difference between the windows XP and the Windows 7. Here are some of the differences listed below The shutdown and the start up is very fast in Windows 7 when compared to the Win dows XP There are not much graphical components present in the windows XP but Windows 7 provides good Graphical User Interface (GUI). In windows 7 there is no necessity for the drivers to be installed but in Window s XP it is necessary to install drivers. The Kernel of windows 7 is very good when compared to the Windows XP. User defined themes can be implemented in Windows 7 but in Windows XP themes can not be created by the user. The windows defender in Windows 7 provides maximum security to the operating sys tem but in Windows XP this feature is not available.

Das könnte Ihnen auch gefallen