WinInfo Short Takes: Week of November 23, 2009
An often irreverent look at some of the week's other news, including some post-PDC some soul searching, a Google Chrome OS announcement and a Microsoft response, Windows 7 off to a supposedly strong start, the Jonas Brothers and Xbox 360, and so much more ...
2009 Windows IT Pro Editors' Best and Community Choice Awards
Picking a favorite product from an impressive crowd of competitive offerings is never an easy task, and such was the case with our Editors' Best and Community Choice awards this year. ...
Command Prompt Tricks
One reader shares his tip for setting up the command prompt to reflect a remote path. ...
1. Power on self test (POST) routines are run
2. Master Boot Record is loaded into memory, and the program is run
3. The Boot Sector from Active Partition is Loaded into Memory
4. Ntldr is loaded and initialized from the boot sector
5. Change the processor from real mode to 32-bit flat memory mode
6. Ntldr starts the appropriate minifile system drivers. Minifile system drivers are built into Ntldr and can read FAT or NTFS
7. Ntldr reads the Boot.ini file
8. Ntldr loads the operating system selected, on of two things happen
* If Windows NT is selected, Ntldr runs Ntdetect.com
* For other operating system, Ntldr loads and runs Bootsect.dos and passes control to it. The Windows NT process ends here
9. Ntdetect.com scans the computer hardware and sends the list to Ntldr for inclusion in HKEY_LOCAL_MACHINE\HARDWARE
10. Ntldr then loads Ntoskrnl.exe, Hal.dll and the system hive
11. Ntldr scans the System hive and loads the device drivers configured to start at boot time
12. Ntldr passes control to Ntoskrnl.exe, at which point the boot process ends and the load phases begin
Thanks for any help.
Jeff November 14, 2003