MCITP MCSE Exam, free Real Exam Test, Guide, Prepare MCITP MCSE

 

MCITP MCSE Guide Free MCITP MCSE Free MCITP MCSE Training MCITP MCSE MCITP MCSE 2003 MCITP MCSE Books MCITP MCSE Boot Camp MCITP MCSE Brain dumps MCITP MCSE Certification MCITP MCSE Exam MCITP MCSE Free MCITP MCSE Jobs MCITP MCSE Logo MCITP MCSE Online MCITP MCSE Online Training MCITP MCSE Practice MCITP MCSE Practice Exams MCITP MCSE Practice Tests MCITP MCSE Requirements MCITP MCSE Resume MCITP MCSE Salary MCITP MCSE Self Paced Training Kit MCITP MCSE Study MCITP MCSE Study Guide MCITP MCSE Study Guides MCITP MCSE Test MCITP MCSE Testing MCITP MCSE Training MCITP MCSE Training Kit MCITP MCSE Training Video MCITP MCSE Windows 2003 Microsoft MCITP MCSE Training Training MCITP MCSE Windows 2003 MCITP MCSE

 

MCITP MCSE : Security Specialist Installing Windows 2000 Minimum hardware requirements 133 MHz Pentium or higher microprocessor (or equivalent). 64 megabytes of RAM recommended minimum 32 MB of RAM is the minimum supported. 4 gigabytes (GB) of RAM is the maximum. 2 GB hard disk with 650 MB of free space. VGA or higher resolution monitor. Clean Install Using the Setup startup disks Insert Setup startup Disk 1. Start your computer. Setup starts automatically. Follow on screen instructions. Using the CD If Windows automatically detects the CD, click Install Windows 2000. If Windows doesn't automatically detect the CD, start Setup from the Run command if you are in windows 9x. Type cd drive:\i386\winnt32.exe If you're using Windows 3.1 or the command prompt, type cd drive:\i386\winnt.exe Follow on screen instructions. Dual-Boot Configuration Windows 2000 supports dual booting with the following operating systems Windows NT 3.51, Windows NT 4.0 Windows 95, Windows 98 Windows 3.1, Windows for Workgroups 3.11 MS-DOS OS/2 Start Up Windows 9x Start Up Process 1) The ROM BIOS Bootstrap Process Power On Self-Test (POST) occurs The master boot record and partition table are read 2) The Master Boot Record and Boot Sector The master boot record determines the location of the boot partition by reading the partition table located at the end of the master boot record. Once the location of the boot partition is determined, the master boot record passes control to the boot sector in that partition. The boot sector contains the disk boot program and a table of disk characteristics. The boot sector checks the BIOS Parameter Block (BPB) to find the location of the root directory, and then copies the Io.sys file from the root directory into memory. 3) The Io.sys File A minimal file allocation table (FAT) file system is loaded The MSDOS.SYS file is read The Starting Windows message is displayed The Logo.sys file is loaded and displays a startup image on the screen If the Drvspace.ini or Dblspace.ini file exists, the Drvspace.bin or Dblspace.bin file is loaded into memory The Io.sys file opens the System.dat file The Dblbuff.sys file is loaded if the "DoubleBuffer=1" is in the Msdos.sys file If you have multiple hardware profiles , the hardware profile you chose is loaded from the registry The Io.sys file processes the Config.sys file 4) Real-Mode Configuration Some hardware devices and programs require that drivers or files be loaded in real-mode in order for them to work properly. To ensure backwards compatibility with these types of hardware devices or programs, Windows 95 processes the Config.sys and Autoexec.bat files if they exist. The Config.sys file loads drivers into memory. If the Config.sys file does not exist, the Io.sys file loads the following required drivers Ifshlp.sys, Himem.sys, and Setver.exe Windows reserves all global upper memory blocks (UMBs) for Windows 9x operating system use or for expanded memory support (EMS). The Autoexec.bat file loads files and terminate and stay resident (TSR) programs into memory The Win.com File and the Windows 95 Environment After the Autoexec.bat file is processed, the Win.com file is run The Win.com file accesses the Vmm32.vxd file. If there is enough available RAM, the Vmm32.vxd file loads into memory, otherwise, it is accessed from the hard disk. This may result in a slower startup time. The Vmm32.vxd file is similar to the Win386.exe file used in earlier versions of Windows The real-mode virtual device driver loader checks for duplicate virtual device drivers (VxDs) in the Windows\System\Vmm32 folder and the Vmm32.vxd file. If a VxD exists in both the Windows\System\Vmm32 folder and the Vmm32.vxd file, the duplicate VxD is "marked" in the Vmm32.vxd file so that it is not loaded. The real-mode virtual device driver loader checks that all required VxDs loaded successfully. If not, it attempts to load the drivers again Once the real-mode virtual device driver loading is logged, driver initialization occurs. If there are any VxDs that require real-mode initialization, they begin their process in real-mode. Vmm32 switches the computer's processor from real-mode to protected- mode After all the static VxDs are loaded, the Krnl32.dll, Gdi.exe, User.exe, and Explorer.exe (the default Windows 95 shell) files are loaded. Network Environment and Multi-User Profiles The next step in the startup process is to load the network environment. Once this occurs, the user is prompted to log on to the network that is installed. Windows 95 allows multiple users to save their custom desktop settings. When a user logs on to Windows 95, their desktop settings are loaded from the registry. If the user does not log on, the desktop configuration uses a default desktop.