Boot process for windows 2000

If I could edit this to match my system presumably it might then work, but I don't know how to do this safely. If anyone can help with this I would be very grateful, as the slow start-up of Windows has always annoyed me, although I very much like everything else about the OS, and want to keep using it! I would also like to know how to get W2K to boot as fast as XP Can someone help me do this? I'm having a hard time here believing that a workstation OS can map the memory better than a server OS, even if it's newer.

XP's kernel is based on Indeed it is, but I do remember reading somewhere that MS had changed the startup routine in XP to make it start up faster, which is why the ntldr from XP could be used on to get at least some of the benefits of this. This is something I've never been able to try out, for the reasons given in my OP, so I've no idea if it works, and how much effect it actually has if it does work!

One of the design principles for XP was "get the user to the desktop quicker", so a lot of the startup routines were made to run in parallel in order to get to the point where winlogon. In Windows all those routines ran serially, so the logon prompt doesn't appear until it's completed all the previous startup steps. As the changes are in the 5. And for Vista the boot process is not so much of a big deal as you're encouraged to use suspend-to-RAM instead of shutdown - "restart" time is under 2 seconds then.

If that really is what MS recommend instead of shutting down properly, that doesn't sound very environmentally friendly. So much for Microsoft's "green" credentials! It's the next step up from hibernation dumping memory contents to a file on disk that is read on resume and is much quicker both in suspending and resuming. Beats having to mess about speeding up the boot process - I only reboot once a month patch Tuesday unless I need to physically move the PC or turn the mains off.

Very handy being able to tap a key and have the logon prompt up in 2 seconds, check email and then put the machine back to sleep before heading to work in the morning. Doing so does make the start of the boot sequence faster,. You assumed incorrectly. Also, having Win 2k setup as you described cannot be called non standard. It's not even unusual. HTH and please report back if my proposed "fix" works for you if it doesn't I'm sure you'll be reporting anyway The other problem with "speeding up" the Windows boot process is that it runs everything during boot serially, whereas Vista and to a much lesser extent XP will load only the most critical subsystems and drivers serially, and then load anything and everything that can load in an asynchronous fashion as such, and postpone services and drivers that don't actually need to be started during boot like Automatic Updates, BITS, the kernel transaction manager, and the Security Center, for instance.

Automatic Updates, BITS : better set to disabled or manual and enable only when needed windows updates. Delete the the users profile and recreate it. I would do this first as this would solve both problems. It is obvious you have a network problem with one particular user so it points to a profile problem. Please see my response in answer 1 above. This is the weirdest thing I have ever seen.

The machine was apparently trying to do something with the chkdsk files that it created. Thanks for your help and suggestions. If you're asking for technical help, please be sure to include all your system info, including operating system, model number, and any other specifics related to the problem. Also please exercise your best judgment when posting in the forums--revealing personal information such as your e-mail address, telephone number, and address is not recommended. Please note: Do not post advertisements, offensive material, profanity, or personal attacks.

Please remember to be considerate of other members. All submitted content is subject to our Terms Of Use. General discussion. Hi, I have a client who has a Windows machine that started having problems about a month ago. It does eventually boot up and connect to the network. This is where Windows takes over the startup process.

What comes next? Here's what happens: The MBR reads the boot sector which is the first sector of the active partition. This sector contains the code that starts Ntldr which is the boot strap loader for Windows XP.

The first role of Ntldr is to allow full memory addressing, start the file system, read boot. Ntldr then uses the ARC path specified in the boot. The one where Windows XP is installed. It might look like this: Ntldr, then, loads the two files that make up the core of XP: Ntoskrnl.

Ntldr reads the registry files, selects a hardware profile, control set and loads device drivers, in that order. Then, Ntoskrnl. You don't. A machine will not boot without that file. Boot from the XP CD use the recovery tool within the disk.

Four 4 startup disks are needed to boot Windows from floppy disks. Windows Boot Manager bootmgr File,Windows boot loader winload. Dual Booting, using a program called a 'Boot Loader'. Note: If you want boot both opreting system win xp and win at a time then you use VM ware software. Since the early days of MSDOS, a standard has existed on x86 systems for the way physical hard disks are divided into volumes. Microsoft operating systems split hard disks into discrete areas known as partitions and use file systems such as FAT and NTFS to format each partition into a volume.

A hard disk can contain up to four primary partitions. Because this apportioning scheme would limit a disk to four volumes, a special partition type, called an extended partition, further allocates up to four additional partitions within each primary partition.

Extended partitions can contain extended partitions, which can contain extended partitions, and so on, making the number of volumes an operating system can place on a disk effectively infinite. Figure shows an example of a hard disk layout. You can learn more about Windows partitioning in Chapter 10, which covers storage management.

Physical disks are addressed in units known as sectors. Utilities that prepare hard disks for the definition of logical drives, including the MS-DOS Fdisk utility or the Windows Setup program, write a sector of data called a master boot record MBR to the first sector on a hard disk.

The MBR includes a fixed amount of space that contains executable instructions called boot code and a table called a partition table with four entries that define the locations of the primary partitions on the disk.

The MBRs written by Microsoft partitioning tools, such as the one integrated into Windows Setup and the Disk Management MMC snap-in, go through a similar process of reading and transferring control. First, an MBR's code scans the primary partition table until it locates a partition containing a flag that signals the partition is bootable. When the MBR finds at least one such flag, it reads the first sector from the flagged partition into memory and transfers control to code within the partition.

This type of partition is called a boot partition, and the first sector of such a partition is called a boot sector. Operating systems generally write boot sectors to disk without a user's involvement. For example, when Windows Setup writes the MBR to a hard disk, it also writes a boot sector to the first bootable partition of the disk. Windows Setup checks to see whether the boot sector it will overwrite with a Windows boot sector is a valid MS-DOS boot sector.

If it is, Windows Setup copies the boot sector's contents to a file named Bootsect. Before writing to a partition's boot sector, Windows Setup ensures that the partition is formatted with a file system that Windows supports FAT, FAT32, or NTFS by formatting the boot partition and any other partition with a file system type you specify.

If partitions are already formatted, you can instruct Setup to skip this step. After Setup formats the boot partition, Setup copies the files Windows uses to the logical disk drive, including two files that are part of the boot sequence, Ntldr and Ntdetect. Another of Setup's roles is to create a boot menu file, Boot.

This file contains options for starting the version of Windows that Setup installs and any preexisting Windows installations. If Bootsect. The following output shows an example Boot. Setup must know the partition format before it writes a boot sector because the contents of the boot sector vary depending on the format. For example, if the boot partition is a FAT partition, Windows writes code to the boot sector that understands the FAT file system. The role of the boot-sector code is to give Windows information about the structure and format of a logical disk drive and to read in the Ntldr file from the root directory of the logical disk drive.

Thus, the boot-sector code contains just enough read-only file system code to accomplish this task. After the boot-sector code loads Ntldr into memory, it transfers control to Ntldr's entry point. Ntldr begins its existence while a system is executing in an x86 operating mode called real mode.

In real mode, no virtual-to-physical translation of memory addresses occurs, which means that programs that use the memory addresses interpret them as physical addresses and that only the first 1 MB of the computer's physical memory is accessible.

However, the first action Ntldr takes is to switch the system to protected mode. Still no virtual-to-physical translation occurs at this point in the boot process, but a full 32 bits of memory becomes accessible. After the system is in protected mode, Ntldr can access all of physical memory. After creating enough page tables to make memory below 16 MB accessible with paging turned on, Ntldr enables paging.

Protected mode with paging enabled is the mode in which Windows executes in normal operation. After Ntldr enables paging, it is fully operational. However, it still relies on functions supplied by the boot code to access IDE-based system and boot disks as well as the display. The boot-code functions briefly switch off paging and switch the processor back to a mode in which services provided by the BIOS can be executed.

Ntldr next reads the Boot. Ntldr clears the screen and if there is more than one boot-selection entry in Boot. If there is only one entry, Ntldr bypasses the menu and proceeds to displaying the startup progress bar.

Selection entries in Boot. This partition might be the same as the boot partition, or it might be another primary partition. If the Boot. This action causes the Bootsect. Code in Bootsect. Entries in Boot. Table contains a complete list of these options and their effects. Giving virtual-memory-intensive applications such as database servers a larger address space can improve their performance. For an application to take advantage of this feature, however, two additional conditions must be met: the system must be running Windows Advanced Server or Datacenter Server and the application.

See the section "Address Space Layout" in Chapter 7 for more information. The first thing the Windows kernel does when it initializes is to initialize the HAL, so this breakpoint is the earliest one possible. The HAL will wait indefinitely at the breakpoint until a kernel-debugger connection is made.

The value is specified in megabytes. Level-sensitive and edge-triggered are terms used to describe hardware interrupt types. This allows the serial port that the kernel debugger would use to be available for use by the system until the system crashes vs. The reason the qualifier exists vs.