Description of the Windows XP Recovery Console for advanced users. When you use the Windows Recovery Console, you can obtain limited access to the NTFS file system, FAT, and FAT32 volumes without starting the Windows graphical user interface (GUI). In the Windows Recovery Console, you can perform the following actions: Use, copy, rename, or replace operating system files and foldersEnable or disable service or device startup the next time that you start your computerRepair the file system boot sector or the master boot record (MBR)Create and format partitions on drivesNote Only an administrator can obtain access to the Windows Recovery Console. This prevents unauthorized users from using any NTFS volume. Option 1: If you have already installed the Recovery Console If you have already installed the Recovery Console, you can select it during your usual Windows Startup.
Option 2: Starting the Windows Recovery Console from the Windows XP CD-ROM Option 3: Adding the Windows Recovery Console as a startup option ( ) Notes map. WDK Windows Driver Kit | Overview for Driver Developers. Visual Studio 2013 Start by downloading Visual Studio 2013. Used together, Visual Studio 2013 and the Windows Driver Kit 8.1 Update provide an integrated development environment for creating efficient, high-quality drivers for Windows 8.1 Update, 8.1, 8, and 7. WDK 8.1 Update (for Windows 8.1, 8, and 7 drivers) Important: Before installing WDK 8.1 Update, you need to install Visual Studio 2013. Standalone Debugging Tools for Windows (WinDbg) If you just need the Debugging Tools for Windows, and not WDK 8.1 Update or Visual Studio 2013, you can install the Debugging Tools as a standalone component from the SDK for Windows 8.1.
Windows Remote Debugging Client for Windows 8.1 You can use the Windows Remote Debugging (Windows RD) client to work remotely with developers from Microsoft via the internet to debug kernel-mode failures by using the Kernel Debugger (KD). Driver samples Code samples are valuable guides whether you're writing your first driver or updating an older one. Windows symbols. Physical Address Extension. Physical Address Extension (PAE) is a processor feature that enables x86 processors to access more than 4 GB of physical memory on capable versions of Windows.
Certain 32-bit versions of Windows Server running on x86-based systems can use PAE to access up to 64 GB or 128 GB of physical memory, depending on the physical address size of the processor. For details, see Memory Limits for Windows Releases. The Intel Itanium and x64 processor architectures can access more than 4 GB of physical memory natively and therefore do not provide the equivalent of PAE.
PAE is used only by 32-bit versions of Windows running on x86-based systems. With PAE, the operating system moves from two-level linear address translation to three-level address translation. PAE does not change the amount of virtual address space available to a process. Each process running in 32-bit Windows is still limited to a 4 GB virtual address space. System Support for PAE Enabling PAE bcdedit /set [{ID}] pae ForceEnable.
Windows Deployment Services. Windows Deployment Services is a server technology from Microsoft for network-based installation of Windows operating systems. It is the successor to Remote Installation Services.[1] WDS is intended to be used for remotely deploying Windows Vista, Windows 7, Windows 8, Windows Server 2008, and Windows Server 2012, but also supports other operating systems because unlike its predecessor RIS, which was a method of automating the installation process, WDS uses disk imaging, in particular the Windows Imaging Format (WIM). WDS is included as a Server Role in all 32-bit and 64-bit versions of Windows Server 2008, and is included as an optionally installable component with Windows Server 2003 Service Pack 2.
Automated image capture and apply[edit] WDS functions in conjunction with the Preboot Execution Environment (PXE) to load a miniature version of Windows known as Windows PE for installation and maintenance tasks. Windows PE automation using WAIK[edit] Automated apply process[edit] DRBL-winroll. Windows Automated Installation Kit.
History[edit] Windows AIK Version 1.0 was released with Windows Vista. New or redesigned tools and technologies included Windows System Image Manager (Windows SIM), SysPrep, ImageX, and Windows Preinstallation Environment (WinPE) v2.0.[2] Windows AIK Version 1.1 was released with Windows Vista SP1 (and Windows Server 2008). A number of new tools were introduced, including PostReflect and VSP1Cln. The new WinPE 2.1 could be more customized.[3] Supported operating systems include Windows Server 2008, Windows Vista, Windows Vista SP1, Windows Server 2003 SP1, Windows Server 2003 SP2 and Windows XP SP2.
Windows AIK Version 2.0 was released with Windows 7 beta. Significantly, a single new tool, DISM, replaced several earlier tools including PEImg and IntlCfg, which were deprecated. Windows AIK version 3.0 is exactly the same as 2.0. The AIK has been renamed The Windows Assessment and Deployment Kit (ADK) for Windows 8 and now includes the Windows OEM Preinstallation Kit. [6] Features[edit]