Mastering Windows XP Registry
-
Author:
-
Subject:
-
Published by:John Wiley & Sons Inc (US)
-
Published:15/05/2002
-
Price:$74.99
- < Buy this book >
Created for Windows power users and anyone who aspires to be one, Mastering Windows XP Registry provides focused, practical coverage of Windows' most important--and most challenging--element: the registry. Inside, you'll learn to customize Windows XP, optimize the network, and avoid scores of potential disasters, all by working with registry settings. If you're a power user, a system administrator, programmer, or consultant, this guide is absolutely essential.
Coverage includes:
* Understanding registry keys and data types
* Applying the secrets of the most important registry keys
* Adjusting the Windows GUI through registry settings
* Using the registry in networking
* Optimizing performance by editing registry settings
* Working with registry tools
* Recovering from disasters
* Eliminating unwanted keys, entries, applications, and files
* Taking advantage of the registry in your own programs
* Tracking registry changes made by applications
* Navigating registry entries
Biography
Table of Contents
Part I: Registry Basics.
Chapter 1: What Is a Registry and Why?
Chapter 2: Readme.1st: Preventing Disaster!
Chapter 3: Anatomy of the Registry: The Blood, Gore, and Guts.
Chapter 4: Registry Tools and Tips: Getting the Work Done.
Chapter 5: Policies: Good for One, Good for All.
Part II: Advanced Registry Stuff.
Chapter 6: Associations, Linkages, and OLE: How Confusing Can This Get?
Chapter 7: Why, Oh Why, Are There system.ini and win.ini Files?
Chapter 8: Getting Rid of the Unwanted.
Chapter 9: Recovering from Disaster, or Making the Best of a Bad Situation.
Chapter 10: Programming and the Registry: A Developer’s Paradise?
Chapter 11: The Performance Monitor Meets the Registry.
Part III: Windows and Office Registry Entries.
Chapter 12: The Windows XP User Interface: Changing How It Looks.
Chapter 13: Networking and Registry System Entries.
Chapter 14: Microsoft Office Entries.
Part IV: The Registry Reference.
Chapter 15: Introduction to HKEY_CLASSES_ROOT.
Chapter 16: Introduction to HKEY_CURRENT_USER and HKEY_USERS.
Chapter 17: Introduction to HKEY_LOCAL_MACHINE.
Chapter 18: Introduction to HKEY_LOCAL_MACHINESoftware.
Chapter 19: Introduction to HKEY_LOCAL_MACHINESystem and HKEY_CURRENT_CONFIG.
Part V: Appendices.
Appendix A: Common Hives and Keys.
Appendix B: Registry Data Types.
Appendix C: Where Can I Get More Help?
Appendix D: Performance Counters.
Appendix E: Plug and Play Identifiers.
Appendix F: Microsoft Office CLSIDs.
Index.
- FTMobile Portal Architect - .Net TechnologiesNSW
- FTSenior .Net Developer - Mobility/Portal SolutionsNSW
- CCDB2 / DBA Technical Consultant - Finance company - Melbourne CBD - DB2VIC
- FTAccount Manager - Strategic Enterprise DevelopmentNSW
- FTTechnical Operations ManagerNSW
- CCDigital Business Analyst - Agile/ScrumNSW
- FTDigital Account ManagerNSW
- FTSupport Consultant - Global Vendor - $55-75,000NSW
- FTDigital Account ManagerNSW
iAsset is a channel management ecosystem that automates all major aspects of the entire sales,marketing and service process, including data tracking, integrated learning, knowledge management and product lifecycle management.
What is Wireless 2.0
The challenges and the Practical Approach to a ‘Wi-Fi that works’ Creating “Wi-Fi that works”, even with minimal requirements, is a tall order given the breadth of client and application types that must perform well over the wireless infrastructure, but when adding in the speed and complexity of 802.11n, a variety of demanding applications, high-density environments, and tricky deployment scenarios, controller-based vendors cannot live up to their promises of Ethernet-like determinism. This whitepaper defines what a Wireless 2.0 network is, and the importance of a controller-less architecture for performance, reliability, scalability, security, and flexibility. Download this now
HiveManager Online: Less Dollars, More Sense
Today’s de facto standard controller-based Wi-Fi infrastructure model is just too complicated, too expensive, and too unreliable. It’s common for enterprise and mid-market network operators alike to get caught in a crossroads of compromises involving costs, complexity, features, and reliability.








