Cover | Table of Contents | Colophon

Table of Contents

Chapter 1: Making the Most of Windows Me

Content preview·Buy PDF of this chapter|Buy reprint rights for this chapter

Do you get a sinking feeling in your stomach every time you are about to install new software? Does the expectation that the installer will overwrite all your settings and disable other software on your computer make you want to chuck the whole system out the window? Have you calmly accepted the fact that your new operating system will most likely contain more bugs than improvements?

Why fight it? Why not simply join the masses and slip into the mind-numbing abyss of acquiescence, feeling powerless whenever technology isn't as seamless as it is promised by software marketers? Because you know there's a better way. You know there's more to Windows Me than what's mentioned in the documentation, such as it is, and in Microsoft's press clippings.

The purpose of these rants, as well as the goal of the entire book, is not to complain or to criticize. The idea is to acknowledge the problems and shortcomings of the operating system—and the software that runs on it—in an effort to overcome them. If users had a large selection of operating systems from which to choose, the point would be almost moot; each user would simply choose the most appropriate and least annoying software available. However, the real world isn't like that, and most computer users using Microsoft Windows are doing so out of necessity, rather than choice. That puts Microsoft in a position to control what we see and how we work. Realizing you're not alone is the first step to improving your experience with Windows Me and regaining control of your machine before it assumes control of you.

While nobody's particular requirements, preferences, and annoyances will be the same, everyone can benefit when light is shed on the inner workings of an operating system. A little knowledge can be dangerous, but a lot of knowledge can keep your system running smoothly and make your Windows experience relatively aggravation free.

There are many reasons that software, and Windows Me in particular, annoys us. One of the most common excuses is that software is designed to be used by a large number of people and to be compatible with a vast array of hardware components, and that no single piece of software can be expected to satisfy everyone. That's true to some extent, but it's too often used as a scapegoat for other problems. One real reason for problems with software is that software designers often don't understand good user-interface design or simply don't understand users and, therefore, create incomplete products that don't work the way we expect or just don't work at all. And another reason is that users don't understand software designers and, therefore, often aren't able to comfortably follow the same lines of logic (or lack thereof ) that the designers used.

Additional content appearing in this section has been removed.
Purchase this book now or read it online at Safari to get the whole thing!

What's Wrong with Windows

Content preview·Buy PDF of this chapter|Buy reprint rights for this chapter

There are many reasons that software, and Windows Me in particular, annoys us. One of the most common excuses is that software is designed to be used by a large number of people and to be compatible with a vast array of hardware components, and that no single piece of software can be expected to satisfy everyone. That's true to some extent, but it's too often used as a scapegoat for other problems. One real reason for problems with software is that software designers often don't understand good user-interface design or simply don't understand users and, therefore, create incomplete products that don't work the way we expect or just don't work at all. And another reason is that users don't understand software designers and, therefore, often aren't able to comfortably follow the same lines of logic (or lack thereof ) that the designers used.

Another truth, and one that most computer companies will never admit, is that consumer computer technology, in general, is still quite infantile. It's truly amazing what some of these devices are capable of, but the sad fact is that the majority of technology hasn't caught up to most users' expectations or requirements. What's worse is that neither has our understanding of human-computer interaction.

There's also an inherent difficulty with the role of the personal computer that ends up causing all sorts of problems. We expect every computer to flawlessly manage our finances, seamlessly connect us to the Internet and allow us to communicate, run our latest 3D-accelerated games, create magazine-quality documents, and about 50,000 other things. Part of the solution to this has been the proliferation of special-function devices, most notably the Palm OS-based personal digital assistants (PDAs). Instead of trying to do everything (a mistake Microsoft, not surprisingly, has migrated to their Windows CE-based devices), the Palm OS has been kept extremely simple; it does only a few things, and it does them reliably well.

In an interview a few years ago, Bill Gates, head bigwig at Microsoft, bragged that Windows 98 had something like seven times as many lines of code as the software used in air-traffic control systems in the U.S. I was appalled. Think about the millions and millions of lines of code and the countless teams of programmers responsible for all the different elements of Windows Me—each programmer with different levels of skill, experience, and adherence to the theoretical interface standards. Instead of giving us a tighter, simpler product, Microsoft keeps making Windows more complex and cumbersome, adding more pointless wizards and market-driven features.

Additional content appearing in this section has been removed.
Purchase this book now or read it online at Safari to get the whole thing!

The Windows Family Tree

Content preview·Buy PDF of this chapter|Buy reprint rights for this chapter

As time progresses, the lineage of Windows becomes less linear. Windows 2000, despite its name, is not the successor to Windows 98 and Windows 95; Windows Me, of course, has that distinction. Windows 2000 is, instead, the latest installment to the less-consumer-oriented Windows NT line of operating systems, developed in parallel to the Windows 9x line.

Figure 1-1 shows a representative family tree and where Windows Me and Windows 2000 fit in. Note that wider boxes imply a greater installed base, and wider gray arrows imply a greater migration from one product to another. Products appearing farther to the right are perceived to have both greater complexity and more technological sophistication.

Figure 1-1: The nonlinear Windows Family Tree is hopefully heading toward a future unifying product

There were rumors that what has become Windows 2000 was supposed to be the product that unified the upscale NT line with the consumer-oriented Windows 9x line. This role has been ostensibly postponed to the Windows XP operating system (code-named "Whistler"), probably Microsoft's most confusing name choice to date.

So why the distinction between DOS-based Windows operating systems and the NT line? We peons were informed at the inception of Windows NT 3.1 that "NT" was an acronym for "New Technology," which is actually quite an accurate description. The NT kernel, or underlying code upon which the interface (Explorer) runs, was completely new and did not rely on DOS. This resulted in a (theoretically) more stable environment, much better security, and the ability to be easily ported to work on other processors (such as Compaq's Alpha chip). Over the years, this "portability" has become much less emphasized. More recently, the NT line has been marketed as a web, intranet, and network server; a challenger to Unix; and now, with Windows 2000, a viable home-office operating system.

Additional content appearing in this section has been removed.
Purchase this book now or read it online at Safari to get the whole thing!

Transition to Windows Me

Content preview·Buy PDF of this chapter|Buy reprint rights for this chapter

If Windows Me is your foray into Windows, you're lucky to have escaped the early days of changing jumpers, editing the config.sys file, running out of "system resources," and suffering with the Windows 3.x Program Manager. However, dealing with the problems of the early days of Windows is a good way to build coping skills and is the only way to appreciate some of the things now taken for granted, such as Plug-and-Play and fast Internet connections. Getting under the hood of Windows is not only a great way to take charge of the operating system and make it conform to the way you work and think, but it's also a very effective method for learning more about Windows and the technology that makes it work.

The basic "shell" interface (Explorer, the Desktop, the Start Menu, and [shiver] the Web View) is relatively unchanged from Windows 98, with the exception of newly painted desktop icons. Those migrating from Windows NT 4.0 will notice slightly more substantial changes, such as menu animation and Internet Explorer integration. Anyone who is accustomed to any recent release of Windows, though, will feel immediately comfortable with the Windows Me version, at least on the surface.

What follows are a few highlights and lowlights of Windows Me, most notably for those who have upgraded or who are thinking of upgrading from a previous version. Some may seem insignificant; others may mean the difference between upgrading to Windows Me and waiting for something better to come along. All of these, naturally, add up to the total Windows Me experience.

Drag-and-drop of EXE files finally makes sense

After five years of customer complaints, Microsoft has finally fixed the absurd way Windows handled the drag-and-drop of EXE files. As one visitor to Annoyances.org wrote several years ago, "whoever came up with the `dragging an application creates a shortcut' behavior must be shot immediately." Now, dragging an EXE file works the same as dragging any other type of file. See Chapter 2, for details, exceptions, and helpful tips.

Additional content appearing in this section has been removed.
Purchase this book now or read it online at Safari to get the whole thing!

Chapter 2: Basic Explorer Coping Skills

Content preview·Buy PDF of this chapter|Buy reprint rights for this chapter

The face of Windows Me that users see most is Windows Explorer, commonly known simply as Explorer. Explorer (Explorer.exe) is the primary shell interface, handling the desktop, the Start Menu, the Recycle Bin, Control Panel, My Computer, the Explorer window, and about a million other things.

Given the amount of time we spend starting programs, finding files, copying folders, and configuring Windows, it makes sense to invest a little time not only to find better ways to accomplish these tasks, but also to learn how to configure Windows to work more like the way we think. In addition, you can make your experience with Windows a lot more pleasurable by giving it a little personality and reducing the various headache-causing annoyances—think of all the money for codeine you'll save.

The ideal user interface should adapt to you, rather than the other way around. One of the primary goals of this book is to show you how to change the w ay Windows looks, feels, and operates so that it is more closely in tune with the way you think and work. However, there are some fundamental features of the interface that simply can't be changed, such as the way icons and folders are drag-dropped.

There are times, on the other hand, when the design of certain basic Windows functionality is so frustrating that it makes you want to tear your hair out: such as how accessing the Search tool from Explorer disables the folder tree, forcing you either to open a new Explorer window or to turn the folder tree back on (select View, Explorer Bar, and then Folders), which incidentally is the only entry in this menu without a keyboard shortcut. (See Section 2.1.8 later in this chapter for several workarounds.)

So, it is the slightly revised goal of all the solutions in this book to arrive at the best compromise between the ideal solution and what is actually possible, while maintaining the lowest practical "annoyance coefficient."

Many of the topics discussed throughout this book require knowledge of the Windows Registry, with the exception of this chapter—I figured you'd want to jump right in. In addition to the Explorer-related tips and tricks, many of the topics of this chapter document the subtle interface differences in Windows Me from previous releases—it's all good stuff. Chapter 3, covers the Registry thoroughly, and all subsequent material assumes a working knowledge of the Registry.

Additional content appearing in this section has been removed.
Purchase this book now or read it online at Safari to get the whole thing!

Coping with Explorer

Content preview·Buy PDF of this chapter|Buy reprint rights for this chapter

Explorer is the all-encompassing program that provides the basic working interface to all modern versions of Windows, allowing you to manage the files, folders, and applications on your system. The Windows desktop, the My Computer window, the single-folder windows, the Tree View window, and the Start Menu are all part of the Explorer application. However, in most Windows lore and in most of the solutions in this book, the term Explorer refers specifically to the window that has the Tree View shown in the left pane; it is opened by selecting Windows Explorer from the Start Menu or by launching Explorer.exe from the Start Menu's Run command. All other windows used to browse folders—those windows accessible from the My Computer window—are commonly referred to as folder windows or the single-folder view.

In reality, Explorer with the folder view and single-folder windows are exactly the same, except for the folder tree pane, which can be turned on or off by selecting Explorer Bar from the View menu and then selecting Folders. The distinction in this book is purely for semantics and casual conversation.

The good news is that files, folders, and most other system objects are copied, moved, opened, closed, and deleted in virtually the same way in all of these places. Interface consistency is one of the most important aspects of interface design, but, unfortunately, often contradicts other factors, such as intuition and historical consistency. For example, drag-drop in Explorer behaves differently when you're dragging from one drive to another (d: to c:) than when dragging from one folder to another on the same drive (c:\docs to c:\files). Why the inconsistency? Because that's the way it has been done in Windows for years, and fixing it would likely confuse too many users. (At least from the perspective of the company that otherwise would have to answer all the technical support calls.)

I've found that Windows Me has the best interface consistency of any Microsoft operating system I've seen. In Windows 98, for example, keystrokes that worked in one situation in Explorer didn't work in other situations, and this has been fixed in Windows Me. Surprisingly, Microsoft has also done away with the "drag an EXE file to create a shortcut" behavior that

Additional content appearing in this section has been removed.
Purchase this book now or read it online at Safari to get the whole thing!

Tweaking the Interface

Content preview·Buy PDF of this chapter|Buy reprint rights for this chapter

If you've made it this far, odds are that you already know how to change your desktop wallpaper, create shortcuts on your desktop, and rearrange the items in your Start Menu. The following solutions allow you to customize some of the more subtle aspects of the Windows interface, using methods somewhat less obvious than those found in ordinary dialog boxes.

Probably the most important customizations in this section are illustrated in Section 2.2.1 and Section 2.2.6. Both of these solutions utilize built-in features of the operating system in ways for which they weren't necessarily intended. The rest of this section should help you tame the Tray, the Control Panel, and the Start Menu—stuff you won't find in the manual.

There are several ways to open an Explorer window, but the most direct method is to use the Windows Explorer shortcut in the Start Menu. This has the same effect as selecting Run in the Start Menu and typing explorer.exe. That is, the Explorer application is run without any command-line arguments.

When Explorer is run without any arguments, it opens to its default location, the Documents shortcut on your desktop (even if you've deleted the Documents icon from your desktop). You may want to have Explorer open to a custom folder each time, saving the time required to repeatedly navigate through all the folders on your hard disk.

Section 2.2.1.1: Launch Explorer from a shortcut

The following steps show how to modify your existing Windows Explorer shortcut in your Start Menu. If you want to create a new shortcut instead, right-click on an empty portion of your desktop or the currently open folder, and select New and then Shortcut. When prompted for an application, point to explorer.exe (located in your Windows folder):

1. Right-click on the Windows Explorer shortcut, select Properties, and click on the Shortcut tab.

Additional content appearing in this section has been removed.
Purchase this book now or read it online at Safari to get the whole thing!

Regaining Control of the Desktop

Content preview·Buy PDF of this chapter|Buy reprint rights for this chapter

Microsoft has, in terms of the interface, positioned the desktop as the root of all other objects in the imaginary hierarchy depicted by Explorer's tree. This includes all drives, the Control Panel, the Network Neighborhood, and even all running applications. The following topics cover some fundamental tasks when dealing with the desktop, such as refreshing the desktop and how to make sure your desktop configuration remains intact. For details on the Active Desktop and other Web integration topics, see Chapter 8.

When Windows starts, it loads the Explorer application, which provides the desktop and the Start Menu. While it's loading, Explorer reads its settings from the Registry (see Chapter 3). If you make a change to the Registry, such as when following some of the procedures in this book, it might not take effect until you reload Explorer, which usually means restarting Windows. However, restarting Windows can take several minutes and will mean shutting down all applications and disconnecting your dial-up connection to the Internet (if applicable). In some cases you can put your changes into effect without restarting Windows, as outlined in the following solutions. Whether any of these solutions work depends on the type of setting you've changed.

Section 2.3.1.1: Solution 1

Click on any empty area of your desktop or any icon on your desktop with the left mouse button, and press the F5 key to refresh the desktop.

Section 2.3.1.2: Solution 2

In cases where Solution 1 is not sufficient to implement your changes, you can force Explorer to reload without restarting:

1. Press Ctrl-Alt-Del to display the Close Program dialog box.
2. Select Explorer from the list, and click End Task.

Additional content appearing in this section has been removed.
Purchase this book now or read it online at Safari to get the whole thing!

Chapter 3: The Registry

Content preview·Buy PDF of this chapter|Buy reprint rights for this chapter

Whenever you change your system colors, install an application, or change a setting in Control Panel, the relevant information is stored in your Registry. The Registry is a database of all the settings for Windows Me, as well as the applications installed on your system. Knowing how to use the Registry effectively is important for improving performance in Windows, troubleshooting all kinds of problems, and, most importantly, customizing Windows Me beyond what is possible with the dialog boxes scattered throughout the interface.

All of your file types (also known as associations; see Section 4.2.2 in Chapter 4) are stored in the Registry, as well as all of the network, hardware, and software settings for Windows Me and all of the particular configuration options for most of the software you've installed. The particular settings and data stored by each of your applications and by the various Windows components vary substantially, but you can use some special techniques to figure out undocumented settings and uncover hidden functionality. What's especially helpful is that most of the settings stored in the Registry are named in plain English rather than with obscure codes and acronyms. You shouldn't take this fact for granted, but it does help quite a bit in finding settings and troubleshooting problems.

Word to the wise: you can irreversibly disable certain components of Windows Me—or even prevent Windows from running—by changing some settings in the Registry. This is intended to scare you, so that you will use caution when editing the Registry and take appropriate measures to prevent catastrophe. Now, of course, the world will not come to an end if you inadvertently change a zero to a one in some obscure Registry key; most of the Registry settings are benign. The worst that will happen is that you might give yourself an enormous headache when you try to remember which setting you changed that disabled your Internet connection or caused Windows to create a folder called "Bubba" on your desktop every time you start your computer. That said, you can virtually eliminate the possibility of disaster by utilizing the systems in place for safeguarding the Registry, as described in Section 3.3 later in this chapter. Furthermore, backing up your

Additional content appearing in this section has been removed.
Purchase this book now or read it online at Safari to get the whole thing!

Getting to Know the Registry Editor

Content preview·Buy PDF of this chapter|Buy reprint rights for this chapter

Although the Registry is stored in multiple files on your hard disk, it is represented by a single logical hierarchical structure, similar to the folders on your hard disk. The Registry Editor (regedit.exe, located in your Windows folder) is included with Windows Me to enable you to view and manually edit the contents of the Registry. Most of the access to the Registry is performed behind the scenes by the applications that you run, as well as by Windows—settings and other information are read from and written to the Registry constantly.

When you open the Registry Editor, you'll see a window divided into two panes (see Figure 3-1). The left side shows a tree with folders, and the right side shows the contents of the currently selected folder. Now, these aren't really folders—it's just a convenient and familiar method of organizing and displaying the information stored in your Registry files.

Figure 3-1: The Registry Editor lets you view and change the contents of the Registry

Each branch (denoted by a folder icon in the Registry Editor) is called a key. Each key can contain other keys, as well as values. Values contain the actual information stored in the Registry, and keys are used only to organize the values. Keys are shown only in the left pane; values are shown only in the right pane (unlike Explorer, where folders are shown in both panes).

To display the contents of a key (folder), just click the desired key name on the left, and the values contained therein will be listed on the right side. To expand a certain branch to show its subkeys, click on the plus sign [+] to the left of any folder or double-click on the folder name.

Editing the Registry generally involves navigating down through branches to a particular key and then modifying an existing value or creating a new key or value. You can modify the contents of any value by double-clicking on it.

Additional content appearing in this section has been removed.
Purchase this book now or read it online at Safari to get the whole thing!

Behind the Scenes: Hives and DAT Files

Content preview·Buy PDF of this chapter|Buy reprint rights for this chapter

HKEY_USERS and HKEY_LOCAL_MACHINE can be thought of as the only true root keys, because the Registry's three other root keys are simply symbolic links, or "mirrors," of different portions of the first two (see Section 3.1 earlier in this chapter). This means that only these two branches actually need to be stored.

Like its predecessors, Windows Me stores the HKEY_USERS and HKEY_LOCAL_MACHINE branches in two files, User.dat and System.dat, respectively. On a single-user system, both files are located in your Windows folder; on a multiple-user system, the User.dat file for each configured user is stored in that user's personal folder. These files are all hidden, meaning that with Explorer's default settings, you won't be able to see or find them. To view hidden files, select Folder Options from Explorer's View menu, choose the View tab, select the Show all files option, and click OK.

Not all Registry data is stored on your hard disk, however. Some keys are dynamic, in that they are held only in memory and are forgotten when you shut down. An example of a dynamic branch is HKEY_LOCAL_MACHINE\HARDWARE, which is built up each time Windows is started (an artifact of Plug and Play). Only static (non-dynamic) branches are stored on your hard disk.

Knowing which files comprise the Registry is important only for backup and emergency recovery procedures (see Section 3.3 later) and for troubleshooting (and so you don't accidentally delete them). The storage mechanism is quite transparent to the Registry Editor and the applications that use the Registry; there's no reason to ever edit the hive files directly. If you want to migrate a key or a collection of keys from one computer to another, you should not try to copy the hive files. Instead, see Section 3.5 later in this chapter for a more convenient procedure.

Additional content appearing in this section has been removed.
Purchase this book now or read it online at Safari to get the whole thing!

Backing Up the Registry

Content preview·Buy PDF of this chapter|Buy reprint rights for this chapter

The Registry is stored in certain files (see Section 3.2 earlier in this chapter) on your hard disk, so you can create a backup by simply copying the appropriate files to another location. Although your Registry is not likely to be small enough to fit on a single floppy, it will fit easily on a removable drive (recordable CD, Zip disk, etc.). In addition, most modern backup software, such as the Backup utility that comes with Windows, includes a feature to back up the Registry. It's always a good idea to exploit this functionality.

When you start Windows, the information in the Registry is loaded into memory. While Windows is running, some changes may not be physically written to the Registry files until you shut down your computer; others, such as those made by the Registry Editor, are usually written immediately. For this reason, if you've made any substantial changes to the contents of the Registry, you may want to restart Windows before backing up the Registry to ensure that the files on the disk reflect the most recent changes.

Remember, if you have more than one user configured, you'll want to include the User.dat file for each user in your backup.

Windows Me comes with the Registry Checker (a.k.a. ScanReg ), a simple utility (introduced in Windows 98) that handles several Registry maintenance tasks, such as checking for errors, optimizing the files, and backing up the entire Registry every time Windows is started. This is especially useful, because a single application crash can crash Windows, which, in turn, can corrupt a Registry file, making it impossible to start Windows! See Section 3.3.1 later in this chapter for details.

Quite simply, you can manually make duplicates of the appropriate Registry files at any time to effect a pretty good Registry backup; see Section 2.1.4 in Chapter 2, for details.

Although it's very useful and quite easy to make backups of the Registry in another location on your hard disk (which is what the Windows Registry Checker does), it certainly can't prepare your computer for an actual disaster. If your hard disk crashes or gets infected with a virus or if your computer is stolen or is dropped out of a seven-story building, those Registry backups on your hard disk won't do you much good. The most effective Registry backup is simply a matter of making a copy of all hives on your hard disk and keeping that copy somewhere other than inside your computer. If you back up your entire system regularly, such as to a tape drive or other backup device, you should ensure that the backup software you use specifically supports safeguarding the Registry. See Chapter 6, for more information on backing up and using backup devices.

Additional content appearing in this section has been removed.
Purchase this book now or read it online at Safari to get the whole thing!

Restoring a Corrupted Registry

Content preview·Buy PDF of this chapter|Buy reprint rights for this chapter

There are several ways to restore a corrupted Registry. The appropriate method depends on how serious the problem is and how diligent you've been about keeping backups. Naturally, you'll want to consider the restoration process when deciding on a backup procedure.

Details aside, restoring a corrupted Registry essentially involves copying your backup over the Registry files in use, replacing the damaged hives with good ones. However, the more backups you restore, the more recent settings will be overwritten with old information; how old the backups are depends solely on how often you back up. Duplicating a dozen files every Thursday suddenly doesn't seem like such a waste of time.

If you can't start Windows, or if you see a warning message about a corrupted Registry every time you start Windows, you'll need to follow these steps, in order, until the problem is solved:

1. Try shutting down and starting again. Surprisingly, this often works.
2. Boot off your startup disk (see Section 6.4.5 in Chapter 6), which will take you to the command prompt. If you don't have a Windows Me startup disk, there's no way to get to the command prompt without loading Windows.
   Check your hard disk for errors by typing scandisk at the command prompt. If it finds any errors, confirm that you want to fix them, and restart.
3. Delete your swap file, Win386.swp , located in your root directory, by typing DEL \WIN386.SWP at the prompt. Then, delete all the files in your Temp folder by typing DEL \windows\temp\*.* (assuming your Temp folder is \Windows\Temp—see Section 4.2.1 in Chapter 4 for more information). You may not believe me, but this often works. Try restarting after this, too.
4. Copy your most recently backed-up Registry files to their original locations, replacing the files that are there. Type

Additional content appearing in this section has been removed.
Purchase this book now or read it online at Safari to get the whole thing!

Using Registry Patches

Content preview·Buy PDF of this chapter|Buy reprint rights for this chapter

In addition to editing the Registry with the Registry Editor (see earlier in this chapter), you can make changes by using Registry patches. A Registry patch is simply a text file with the .reg extension that contains one or more Registry keys or values. If you double-click on a .reg file, the patch is applied to the Registry, meaning that the contents of the patch are merged with the contents of the Registry. This tool is especially handy for backing up small portions of the Registry or copying Registry data to someone else's computer.

1. Open the Registry Editor, and select a branch you wish to use. The branch can be anywhere from one of the top level branches to a branch a dozen layers deep. Registry patches include not only the branch you select, but all of the values and subkeys in the branch. Don't select anything more than what you absolutely need.
2. Select Export Registry File from the Registry menu, type a filename, and press OK. All of the values and subkeys in the selected branch will then be duplicated in the patch. Make sure the filename of the new Registry patch has the .reg extension.

Creating a Registry patch is the easy part; the hard part is determining the Registry keys from which you should make patches. See Section 3.6 later in this chapter for details.

Since Registry patches are just plain text files, you can edit them with any plain-text editor, such as Notepad (notepad.exe). The contents of the Registry patch will look something like the text shown in Example 3-2.

Example 3-2. Contents of a Registry Patch Created from HKEY_CLASSES_ROOT \.txt

REGEDIT4

[HKEY_CLASSES_ROOT\.txt]
@="txtfile"
"Content Type"="text/plain"

[HKEY_CLASSES_ROOT\.txt\ShellNew]
"FileName"="template.txt"

The first line, REGEDIT4, tells Windows that this file is a valid Registry patch; don't remove this line. The rest of the Registry patch is a series of key names and values. The key names appear in brackets (

Additional content appearing in this section has been removed.
Purchase this book now or read it online at Safari to get the whole thing!

Finding the Right Registry Key

Content preview·Buy PDF of this chapter|Buy reprint rights for this chapter

The two main obstacles you'll encounter when trying to make a change to the Registry are (1) where a setting is located in the Registry and (2) what modifications are necessary to effect the desired changes. Sometimes it's obvious, such as a value called ShowSplashScreen, with its contents set to 1; changing the 1 to a 0 would most likely result in turning the option off. Other times you'll see a long, seemingly meaningless series of numbers and letters. Although there are no strict rules as to how values and keys are named or how the data therein is arranged, a little common sense and intuition will get you through most situations.

Here's a solution that will help you find the corresponding Registry key for a particular setting in Windows. For this example, we'll find the Registry setting associated with showing or hiding hidden files in Explorer, and then we'll create the appropriate Registry patch.

A Registry patch is a convenient way of automating changes to the Registry, and therefore to Windows and your applications, and is useful if you frequently change a setting or a group of settings. It's also a convenient way to propagate a group of settings to one or more other computers. This solution provides a way to come up with a Registry patch that corresponds to one or more options in the interface.

The idea is to take snapshots (make Registry patches) of your entire Registry before and after a change is made in Explorer (or another program). By comparing the two snapshots, we can easily see which Registry keys and values were affected:

1. Make sure no applications are running, because they could write to the Registry at any time, adding unexpected changes.
2. Open the Registry Editor, and highlight the HKEY_CURRENT_USER branch. Select Export Registry File from the Registry menu, and export the entire branch to a file called User1.reg (or something like that), stored somewhere convenient, such as your desktop. Then, select the

Additional content appearing in this section has been removed.
Purchase this book now or read it online at Safari to get the whole thing!

Automating the Deletion of Registry Items

Content preview·Buy PDF of this chapter|Buy reprint rights for this chapter

An important drawback to using Registry patches is that they can be used only to replace or augment information in the Registry. No provision for removing keys or values is included in Registry patches, yet some important changes can only be made by removing keys or values. For example, to remove the Bitmap Image entry from Explorer's New menu, you need to delete the key HKEY_CLASSES_ROOT\.bmp\ShellNew entirely, and no Registry patch can do that.

Here, we enlist the services of the Windows Script Host, which includes a functionality for manipulating Registry information. Chapter 9 documents writing scripts for the Windows Script Host and, in particular, Registry functions like the one used in this solution:

1. Open a plain-text editor, such as Notepad, and type the following:

   Call RegistryDelete("HKEY_CURRENT_USER\.bmp\ShellNew", "")
   
   Sub RegistryDelete(KeyName, ValueName)
     Set WshShell = WScript.CreateObject("WScript.Shell")
     WshShell.RegWrite KeyName & "\" & ValueName, ""
     WshShell.RegDelete KeyName & "\" & ValueName
   End Sub

   RegistryDelete subroutine, listed immediately after. Simply put the full path of the Registry key you wish to delete between the quotation marks, making sure not to include a trailing slash (a "\" at the end).
   To delete a single value rather than an entire key, specify the value name between the second pair of quotes, like this:

   Call RegistryDelete("HKEY_CURRENT_USER\.bmp", "Content Type")

   To remove the (default) value of a key (which can't be deleted), just use a standard Registry patch, and simply set the default value to an empty string (@="").
2. Save the file, calling it something like Delete.vbs. Double-click on the script file to execute it.

Another instance where it might be useful to delete a Registry key is removing special icons from the desktop. In this case, use the same script, but replace the Registry path with:

Additional content appearing in this section has been removed.
Purchase this book now or read it online at Safari to get the whole thing!

Search the Registry Effectively

Content preview·Buy PDF of this chapter|Buy reprint rights for this chapter

The Registry Editor has a simple search feature, allowing you to search through all the keys and values for text. Just select Find from the Registry Editor's Edit menu, type the desired text, and click Find Next. Because the Registry can become quite large and have a wide variety of settings and information, it is important to learn to search effectively, so you don't miss anything or waste a lot of time wading through irrelevant results. Additionally, the Registry Editor doesn't have a search-and-replace feature, so doing something as simple as changing every occurrence of c:\program files to d:\program files can be a monumental chor

Return to Windows Me Annoyances

© 2008, O'Reilly Media, Inc. (707) 827-7000 / (800) 998-9938 All trademarks and registered trademarks appearing on oreilly.com are the property of their respective owners.

About O'Reilly Privacy Policy Contacts Authors Press Room Jobs User Groups Academic Solutions Newsletters Writing for O'Reilly RSS Feeds

Other O'Reilly Sites O'Reilly Radar Ignite Tools of Change for Publishing Digital Media Inside iPhone O'Reilly FYI makezine.com craftzine.com hackszine.com perl.com xml.com

Sponsored Sites Inside Aperture Inside Lightroom Inside Port 25 InsideRIA