Picture 1 of 1

Stock photo

Windows 2000 Kernel Debugging (Prentice Hall Ptr Microsoft Technologies Series), - Picture 1 of 1

Windows 2000 Kernel Debugging by Steven McDowell (Paperback, 2001)

Buchpark (78328)

98.2% positive Feedback

Price:

£11.69

Free postage

Estimated delivery Wed, 7 May - Wed, 14 May

Returns:

30 days return. Buyer pays for return postage. If you use an eBay delivery label, it will be deducted from your refund amount.

Condition:

Very Good

(Rebinding, adhesive, covers, or similar). In rare cases, a book may differ from the stated edition. Still suitable for personal use. CDs/DVDs/Vinyls may have scratches, but functionality should not be impaired.

About this product

Product Information

This is the first comprehensive guide to Windows 2000 kernel debugging: an invaluable resource for everyone who needs to analyze and prevent Windows 2000 system crashes -- especially device driver authors and debuggers. Understand exactly what debugging means in a Windows 2000 environment, and what Microsoft's WinDbg debugger can (and cannot) do for you; and how to configure both local and remote kernel debugging environments. Learn how to analyze blue screens and utilize Windows 2000's crash dump feature; then walk through debugging a sample device driver, step-by-step. Discover how to start and stop errant drivers, pause a target system, retrieve system and driver state, and step through source code using breakpoints and source-level debugging. Master advanced techniques for taking control of target systems, including finding lost memory blocks; setting process and thread contexts; reviewing I/O system error logs; and more. Explore your target computer's hardware through the WinDbg interface, reading and writing hardware ports, the BIOS, the SCSI bus, and the PCI bus; even learn how to use Microsoft's Debugger Extensions to run virtually any command you choose. Finally, master Microsoft's powerful Driver Verifier utility, which can unobtrusively detect many of the most common mistakes made by device driver writers -- errors that might not have been discovered until long after software release.