July, 2004

  • The Old New Thing

    How does Add/Remove Programs get the size and other information?

    • 120 Comments

    If the program doesn't provide this information itself, Add/Remove Programs is forced to guess.

    The problem is that there is no "obvious" way to map an entry in the Add/Remove Programs list to an actual program. Each entry in the list, for those who care about such things, comes from the HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Uninstall registry key. The only mandatory properties for an uninstallable program are the DisplayName and the UninstallPath. Everything else is optional.

    Let's suppose Add/Remove Programs is given a program registration like this:

    HKEY_LOCAL_MACHINE\
     Software\
      Microsoft\
       Windows\
        CurrentVersion\
         Uninstall\
          SomeProgram
           DisplayName=REG_SZ:"Awesome Program for Windows"
           UninstallPath=REG_SZ:"C:\WINDOWS\uninstall.exe -SomeParameters"
    

    In order to get the "Last Used" and "Frequency" values, Add/Remove Programs needs to know the name of the EXE so it can ask the Start menu "Hey, how often did the user run this program, and when was the last time it happened?"

    Notice that there are no clues in the registration above as to the identity of this EXE file.

    So Add/Remove Programs starts guessing. It goes through all the programs on your Start menu and compares their names with the display name of the uninstallable item. It looks for Start menu items which share at least two words with the words in the DisplayName.

    For example, if there were a Start menu item called "Pretty Decent Windows Program", this would count as a two-word match ("Windows" and "Program").

    It then takes the one with the most matches and decides, "Okay, I guess this is it." Suppose for the sake of illustration that the best match is indeed "Pretty Decent Windows Program.lnk", which is a shortcut to "C:\Program Files\LitWare\Decent Program\Decent.exe". Add/Remove Programs would decide that "Awesome Program for Windows" should get the icon for "Pretty Decent Windows Program.lnk", that the frequency of use and most-recently-used information for "C:\Program Files\LitWare\Decent Program\Decent.exe" will be displayed for "Awesome Program for Windows".

    But wait, there's more. There's also the program size. Add/Remove Programs looks in your "Program Files" directory for directories whose names share at least two words in common with the DisplayName. The best match is assumed to be the directory that the program files are installed into. The sizes are added together and reported as the size of "Awesome Program for Windows".

    A program can add some properties to its registration to avoid a lot of this guessing. It can set an EstimatedSize property to avoid making Add/Remove Programs guess how big the program is. It can also set a DisplayIcon property to specify which icon to show for the program in the list.

    But if a program omits all of these hints, the guess that Add/Remove Programs ends up making can often be ridiculously wide of the mark due to coincidental word matches. In my experience, Spanish suffers particularly badly from this algorithm, due to that language's heavy use of prepositions and articles (which result in a lot of false matches).

    Yes, this is all lame, but when you are forced to operate with inadequate information, lame is the best you can do.

    [July 15 2004: Emphasizing that this is done only if the program fails to provide the information itself. For some reason, a lot of people who link to this page fail to notice that little detail.]

  • The Old New Thing

    The evolution of mascara in Windows UI

    • 86 Comments

    The "look" of the Windows user interface has gone through fashion cycles.

    In the beginning, there was Windows 1.0, which looked very flat because screen resolutions were rather low in those days and color depth was practically nonexistent. If you had 16 colors, you were doing pretty good. You couldn't afford to spend very many pixels on fluff like borders, and shadows were out of the question due to lack of color depth.

    The "flat look" continued in Windows 2.0, but Windows 3.0 added a hint of 3D (notice the beveling in the minimize/maximize buttons and in the toolbar buttons on the help window).

    Other people decided that the 3D look was the hot new thing, and libraries sprung up to add 3D shadow and outlining effects to nearly everything. The library CTL3D.DLL started out as just an Excel thing, but it grew in popularity until it became the "standard" way to make your dialog boxes "even more 3D".

    Come Windows 95, even more of the system had a 3D look. Notice the beveling along the inside edge of the panes in the Explorer window. Furthermore, 3D-ness was turned on by default for all programs that marked themselves as "4.0"; i.e., programs that were designed for Windows 95. For programs that wanted to run on older versions of Windows as well, a new dialog style DS_3DLOOK was added, so that they could indicate that they wanted 3D-ization if available.

    And if the 3D provided by Windows 95 by default wasn't enough, you could use CTL3D32.DLL to make your controls even more 3D. By this point, things started getting really ugly. Buttons on dialog boxes had so many heavy black outlines that it started to look like a really bad mascara job.

    Fortunately, like many fashions that get out of hand, people realized that too much 3D is not a good thing. User interfaces got flatter. Instead of using 3D effects and bold outlines to separate items, subtler dividers were used. Divider lines became more subdued and sometimes disappeared entirely.

    Microsoft Office and Microsoft Money were two programs that embraced the "less is more" approach. In this screenshot from Microsoft Money, observe that the beveling is gone. There are no 3D effects. Buttons are flat and unobtrusive. The task pane separates itself from the content pane by a simple gray line and a change in background shade. Even the toolbar has gone flat. Office 2000 also went largely flat, though some 3D effects linger, in the grooves and in the scrollbars (not visible in picture).

    Windows XP jumped on the "flat is good" bandwagon and even got rid of the separator line between the tasks pane and the contents pane. The division is merely implied by the change in color. "Separation through juxtaposition."

    Office XP and Outlook 2003 continue the trend and flatten nearly everything aside from the scrollbar elements. Blocks of color are used to separate elements onscreen, sometimes with the help of simple outlines.

    So now the pendulum of fashion has swung away from 3D back towards flatness. Who knows how long this school of visual expression will hold the upper hand. Will 3D return with a vengeance when people tire of the starkness of the flat look?

  • The Old New Thing

    How do you detect "Large Fonts"?

    • 58 Comments

    When people ask, "How do I detect Large Fonts", they aren't really asking how to detect Large Fonts specifically. Rather, Large Fonts is just the most common manifestation of "unusual DPI".

    Windows uses a nominal DPI of 96 pixels per inch. In other words, if Windows wants to draw a line that is one inch long, it draws 96 pixels. Of course, the physical length of this line depends on your screen resolution and the size of your monitor. The value of 96 is merely nominal.

    You can change this DPI setting from the Display control panel, either by choosing Large Fonts, or by choosing a custom font size. Standard size is 96DPI. Large is 120DPI. Custom is, well, custom.

    DPI higher than 96 will become more and more prevalent as LCD technology improves.

    Programs can query the DPI setting by asking GetDeviceCaps for the LOGPIXELSX of the screen DC.

    int GetScreenDPI()
    {
      HDC hdcScreen = GetDC(NULL);
      int iDPI = -1; // assume failure
      if (hdcScreen) {
        iDPI = GetDeviceCaps(hdcScreen, LOGPIXELSX);
        ReleaseDC(NULL, hdcScreen);
      }
      return iDPI;
    }
    

    The code above assumes that pixels are square, which is true of most modern devices. (You can choose an odd screen resolution and get non-square pixels, but most people avoid such resolutions.) Back in the old days, there were many devices with non-square pixels. For example, the EGA video adapter had pixels which were 1.33 times as tall as they were wide.

    For nonsquare-pixel devices, the values of the LOGPIXELSX and LOGPIXELSY metrics will be different. On an EGA, if the value of the LOGPIXELSX metric were 96, then the LOGPIXELSY metric would be 72, since there are only 72 vertical pixels per inch. Similarly, the ASPECTX, ASPECTY and ASPECTXY values for nonsquare-pixel devices will be somewhat interesting as well, as this diagram demonstrates:

    36 27 45

    The ASPECTX is 27 and the ASPECTY is 36, representing the 4:3 ratio of vertical to horizontal, and the ASPECTXY is 45, representing the hypotenuse.

  • The Old New Thing

    Differences between managers and programmers

    • 50 Comments

    If you find yourself in a meeting with a mix of managers and programmers, here's one way to tell the difference between them: Look at what they brough to the meeting.

    Did they bring a laptop computer? Score bonus points if the laptop computer is actually turned on during the meeting or if the laptop is special in some way (e.g., it has a wireless card or it's a Tablet PC). If so, then that person is probably a manager.

    Did they come to the meeting empty-handed or with a spiral-bound notebook? If so, then that person is probably a programmer.

    It's not an infallible test, but it works with surprisingly high accuracy.

  • The Old New Thing

    Why does icon text get a solid background if drop shadows are disabled?

    • 49 Comments

    A commenter asks why icon label have "those ugly color boxes" when there is a background image.

    The answer: Because the alternative would be worse.

    Imagine if there were no solid background between the text and the background image. You would end up with text against an unpredictable background, which doesn't help readability.

    Take the default background for Windows XP: There are some places that are very light and other places that are very dark. No matter what color you pick for the icon text, it will look bad in one or the other place. If you decide to use white, then the text becomes unreadable in the clouds. If you decide to use black, then the text becomes unreadable in the shadows.

    You lose either way.

    The solution is to intercede a contrasting color to ensure that the text is readable. If your video card is powerful enough, the contrasting color is used only just around the strokes of text themselves, which lends a shadow-effect. If shadows are not enabled, then a solid block of contrast is used.

    (And for those of you who say, "Use white in the dark places and black in the light places," what if there is a section of the wallpaper that has a dark area right next to a light area, and the text covers both?)

  • The Old New Thing

    Disabling the program crash dialog

    • 48 Comments

    If you don't want your program to display the standard crash dialog, you can disable it by setting the SEM_NOGPFAULTERRORBOX flag in the process error mode.

    The simple-minded way is just to do

    SetErrorMode(SEM_NOGPFAULTERRORBOX);
    

    but this overwrites the previous error mode rather than augmenting it. In other words, you inadvertently turned off the other error modes!

    Unfortunately, there is no GetErrorMode function, so you have to do a double-shuffle.

    DWORD dwMode = SetErrorMode(SEM_NOGPFAULTERRORBOX);
    SetErrorMode(dwMode | SEM_NOGPFAULTERRORBOX);
    

    This sets the new error mode (possibly disabling some other error modes that had been set) and saves the previous mode. Then it sets the error mode the right way, adding the SEM_NOGPFAULTERRORBOX flag to the existing error modes.

    Merging with existing error modes is important. For example, the previous error mode may have included SEM_NOALIGNMENTFAULTEXCEPT. If you casually turned that off, then the program would not longer receive automatic alignment fault fixups and will start crashing.

    (But if you read the documentation, you'll see that SEM_NOALIGNMENTFAULTEXCEPT is special: The system won't let you turn it off once it's been turned on. Why? Because too many people were already making this mistake. I remember before this special rule was introduced. Programs were crashing left and right because they didn't do the double-set shuffle above; as a result, they started crashing on alignment faults. So the special rule had to be added. Welcome to the world of compatibility, where it is the operating system's duty to cover for other people's mistakes. Mind you, the design of the SetErrorMode function makes this mistake a very easy one to commit.)

    Note that the error mode is a process-wide setting, not a per-thread setting. This means that manipulating the process error mode is not something you should do lightly, since it may have unintended consequences for other threads (which you might not have control over). For safety's sake, a program should set its error mode when it starts up and not mess with it thereafter.

    Of course, if you disable the crash dialog, then you also miss out on the opportunity to retrieve crash reports collected by Windows Error Reporting so you can see where your program is crashing in the real world.

  • The Old New Thing

    Why was nine the maximum number of monitors in Windows 98?

    • 44 Comments

    Windows 98 was the first version of Windows to support multiple monitors. And the limit was nine.

    Why nine?

    Because that allowed you to arrange your monitors like this. You have early seventies television to thank.

    [Raymond is currently on vacation; this message was pre-recorded.]

  • The Old New Thing

    Querying information from an Explorer window

    • 37 Comments

    Sometimes software development is inventing new stuff. But often, it's just putting together the stuff you already have. Today's puzzle is one of the latter type of problem.

    Given a window handle, you can you determine (1) whether it is an Explorer window, and if so (2) what folder it is viewing, and (3) what item is currently focused.

    This is not an inherently difficult task. You just have to put together lots of small pieces.

    Start with the ShellWindows object which represents all the open shell windows. You can enumerate through them all with the Item property. This is rather clumsy from C++ because the ShellWindows object was designed for use by a scripting language like JScript or Visual Basic.

     IShellWindows *psw;
     if (SUCCEEDED(CoCreateInstance(CLSID_ShellWindows, NULL, CLSCTX_ALL,
                                    IID_IShellWindows, (void**)&psw))) {
      VARIANT v;
      V_VT(&v) = VT_I4;
      IDispatch  *pdisp;
      BOOL fFound = FALSE;
      for (V_I4(&v) = 0; !fFound && psw->Item(v, &pdisp) == S_OK;
           V_I4(&v)++) {
        ...
        pdisp->Release();
      }
      psw->Release();
     }
    

    From each item, we can ask it for its window handle and see if it's the one we want.

       IWebBrowserApp *pwba;
       if (SUCCEEDED(pdisp->QueryInterface(IID_IWebBrowserApp, (void**)&pwba))) {
         HWND hwndWBA;
         if (SUCCEEDED(pwba->get_HWND((LONG_PTR*)&hwndWBA)) &&
           hwndWBA == hwndFind) {
           fFound = TRUE;
           ...
         }
         pwba->Release();
       }
    

    Okay, now that we have found the folder via its IWebBrowserApp, we need to get to the top shell browser. This is done by querying for the SID_STopLevelBrowser service and asking for the IShellBrowser interface.

           IServiceProvider *psp;
           if (SUCCEEDED(pwba->QueryInterface(IID_IServiceProvider, (void**)&psp))) {
             IShellBrowser *psb;
             if (SUCCEEDED(psp->QueryService(SID_STopLevelBrowser,
                                  IID_IShellBrowser, (void**)&psb))) {
               ...
               psb->Release();
             }
             psp->Release();
           }
    

    From the IShellBrowser, we can ask for the current shell view via the QueryActiveShellView method.

               IShellView *psv;
               if (SUCCEEDED(psb->QueryActiveShellView(&psv))) {
                 ...
                 psv->Release();
               }
    

    Of course, what we really want is the IFolderView interface, which is the automation object that contains all the real goodies.

                 IFolderView *pfv;
                 if (SUCCEEDED(psv->QueryInterface(IID_IFolderView,
                                                   (void**)&pfv))) {
                   ...
                   pfv->Release();
                 }
    

    Okay, now we're golden. What do you want to get from the view? How about the location of the IShellFolder being viewed. To do that, we need to use IPersistFolder2::GetCurFolder. The GetFolder method will give us access to the shell folder, from which we ask for IPersistFolder2. (Most of the time you want the IShellFolder interface, since that's where most of the cool stuff hangs out.)

                   IPersistFolder2 *ppf2;
                   if (SUCCEEDED(pfv->GetFolder(IID_IPersistFolder2,
                                                (void**)&ppf2))) {
                     LPITEMIDLIST pidlFolder;
                     if (SUCCEEDED(ppf2->GetCurFolder(&pidlFolder))) {
                       ...
                       CoTaskMemFree(pidlFolder);
                     }
                     ppf2->Release();
                   }
    

    Let's convert that pidl into a path, for display purposes.

                       if (!SHGetPathFromIDList(pidlFolder, g_szPath)) {
                         lstrcpyn(g_szPath, TEXT("<not a directory>"), MAX_PATH);
                       }
                       ...
    

    What else can we do with what we've got? Oh right, let's see what the currently-focused object is.

                       int iFocus;
                       if (SUCCEEDED(pfv->GetFocusedItem(&iFocus))) {
                         ...
                       }
    

    Let's display the name of the focused item. To do that we need the item's pidl and the IShellFolder. (See, I told you the IShellFolder is where the cool stuff is.) The item comes from the Item method (surprisingly enough).

                         LPITEMIDLIST pidlItem;
                         if (SUCCEEDED(pfv->Item(iFocus, &pidlItem))) {
                           ...
                           CoTaskMemFree(pidlItem);
                         }
    

    (If we had wanted a list of selected items we could have used the Items method, passing SVGIO_SELECTION.)

    After we get the item's pidl, we also need the IShellFolder:

                           IShellFolder *psf;
                           if (SUCCEEDED(ppf2->QueryInterface(IID_IShellFolder,
                                                              (void**)&psf))) {
                             ...
                             psf->Release();
                           }
    

    Then we put the two together to get the item's display name, with the help of the GetDisplayNameOf method.

                             STRRET str;
                             if (SUCCEEDED(psf->GetDisplayNameOf(pidlItem,
                                                       SHGDN_INFOLDER,
                                                       &str))) {
                               ...
                             }
    

    We can use the helper function StrRetToBuf to convert the kooky STRRET structure into a boring string buffer. (The history of the kooky STRRET structure will have to wait for another day.)

                               StrRetToBuf(&str, pidlItem, g_szItem, MAX_PATH);
    

    Okay, let's put this all together. It looks rather ugly because I put everything into one huge function instead of breaking them out into subfunctions. In "real life" I would have broken things up into little helper functions to make things more manageable.

    Start with the scratch program and add this new function:

    #include <shlobj.h>
    #include <exdisp.h>
    
    TCHAR g_szPath[MAX_PATH];
    TCHAR g_szItem[MAX_PATH];
    
    void CALLBACK RecalcText(HWND hwnd, UINT, UINT_PTR, DWORD)
    {
     HWND hwndFind = GetForegroundWindow();
     g_szPath[0] = TEXT('\0');
     g_szItem[0] = TEXT('\0');
    
     IShellWindows *psw;
     if (SUCCEEDED(CoCreateInstance(CLSID_ShellWindows, NULL, CLSCTX_ALL,
                                    IID_IShellWindows, (void**)&psw))) {
      VARIANT v;
      V_VT(&v) = VT_I4;
      IDispatch  *pdisp;
      BOOL fFound = FALSE;
      for (V_I4(&v) = 0; !fFound && psw->Item(v, &pdisp) == S_OK;
           V_I4(&v)++) {
       IWebBrowserApp *pwba;
       if (SUCCEEDED(pdisp->QueryInterface(IID_IWebBrowserApp, (void**)&pwba))) {
         HWND hwndWBA;
         if (SUCCEEDED(pwba->get_HWND((LONG_PTR*)&hwndWBA)) &&
           hwndWBA == hwndFind) {
           fFound = TRUE;
           IServiceProvider *psp;
           if (SUCCEEDED(pwba->QueryInterface(IID_IServiceProvider, (void**)&psp))) {
             IShellBrowser *psb;
             if (SUCCEEDED(psp->QueryService(SID_STopLevelBrowser,
                                  IID_IShellBrowser, (void**)&psb))) {
               IShellView *psv;
               if (SUCCEEDED(psb->QueryActiveShellView(&psv))) {
                 IFolderView *pfv;
                 if (SUCCEEDED(psv->QueryInterface(IID_IFolderView,
                                                   (void**)&pfv))) {
                   IPersistFolder2 *ppf2;
                   if (SUCCEEDED(pfv->GetFolder(IID_IPersistFolder2,
                                                (void**)&ppf2))) {
                     LPITEMIDLIST pidlFolder;
                     if (SUCCEEDED(ppf2->GetCurFolder(&pidlFolder))) {
                       if (!SHGetPathFromIDList(pidlFolder, g_szPath)) {
                         lstrcpyn(g_szPath, TEXT("<not a directory>"), MAX_PATH);
                       }
                       int iFocus;
                       if (SUCCEEDED(pfv->GetFocusedItem(&iFocus))) {
                         LPITEMIDLIST pidlItem;
                         if (SUCCEEDED(pfv->Item(iFocus, &pidlItem))) {
                           IShellFolder *psf;
                           if (SUCCEEDED(ppf2->QueryInterface(IID_IShellFolder,
                                                              (void**)&psf))) {
                             STRRET str;
                             if (SUCCEEDED(psf->GetDisplayNameOf(pidlItem,
                                                       SHGDN_INFOLDER,
                                                       &str))) {
                               StrRetToBuf(&str, pidlItem, g_szItem, MAX_PATH);
                             }
                             psf->Release();
                           }
                           CoTaskMemFree(pidlItem);
                         }
                       }
                       CoTaskMemFree(pidlFolder);
                     }
                     ppf2->Release();
                   }
                   pfv->Release();
                 }
                 psv->Release();
               }
               psb->Release();
             }
             psp->Release();
           }
         }
         pwba->Release();
       }
        pdisp->Release();
      }
      psw->Release();
     }
     InvalidateRect(hwnd, NULL, TRUE);
    }
    

    Now all we have to do is call this function periodically and print the results.

    BOOL
    OnCreate(HWND hwnd, LPCREATESTRUCT lpcs)
    {
        SetTimer(hwnd, 1, 1000, RecalcText);
        return TRUE;
    }
    
    void
    PaintContent(HWND hwnd, PAINTSTRUCT *pps)
    {
      TextOut(pps->hdc, 0, 0, g_szPath, lstrlen(g_szPath));
      TextOut(pps->hdc, 0, 20, g_szItem, lstrlen(g_szItem));
    }
    

    We're ready to roll. Run this program and set it to the side. Then launch an Explorer window and watch the program track the folder you're in and what item you have focused.

    Okay, so I hope I made my point: Often, the pieces you need are already there; you just have to figure out how to put them together. Notice that each of the pieces is in itself not very big. You just had to recognize that they could be put together in an interesting way.

    Exercise: Change this program so it takes the folder and switches it to details view.

    [Raymond is currently on vacation; this message was pre-recorded.]

  • The Old New Thing

    Why do some process stay in Task Manager after they've been killed?

    • 35 Comments

    When a process ends (either of natural causes or due to something harsher like TerminateProcess), the user-mode part of the process is thrown away. But the kernel-mode part can't go away until all drivers are finished with the thread, too.

    For example, if a thread was in the middle of an I/O operation, the kernel signals to the driver responsible for the I/O that the operation should be cancelled. If the driver is well-behaved, it cleans up the bookkeeping for the incomplete I/O and releases the thread.

    If the driver is not as well-behaved (or if the hardware that the driver is managing is acting up), it may take a long time for it to clean up the incomplete I/O. During that time, the driver holds that thread (and therefore the process that the thread belongs to) hostage.

    (This is a simplification of what actually goes on. Commenter Skywing gave a more precise explanation, for those who like more precise explanations.)

    If you think your problem is a wedged driver, you can drop into the kernel debugger, find the process that is stuck and look at its threads to see why they aren't exiting. You can use the !irp debugger command to view any pending IRPs to see what device is not completing.

    After all the drivers have acknowledged the death of the process, the "meat" of the process finally goes away. All that remains is the "process object", which lingers until all handles to the process and all the threads in the process have been closed. (You did remember to CloseHandle the handles returned in the PROCESS_INFORMATION structure that you passed to the CreateProcess function, didn't you?)

    In other words, if a process hangs around after you've terminated it, it's really dead, but its remnants will remain in the system until all drivers have cleaned up their process bookkeeping, and all open handles to the process have been closed.

  • The Old New Thing

    Don't name your DLL "Security.dll"

    • 32 Comments

    Reaching back into the history bucket...

    Some people have discovered that strange things happen if you name your DLL "security.dll".

    The reason is that there is already a system DLL called "security.dll"; it's the Security Support Provider Interface DLL, and it used to go by the name "security.dll", though nowadays the name "secur32.dll" is preferred. If you look into your system32 directory, you'll see both "security.dll" and "secur32.dll" in there. And if you're handy with an export dumper, you'll see that "security.dll" is just a bunch of forwarders to "secur32.dll". If you browse through the MSDN documentation, you'll see that everybody talks about "secur32.dll" and hardly any mention is made of its doppelgänger "security.dll".

    Okay, here's where the history comes in. Wind back to Windows 95.

    Back in those days, the Security Support Provider Interface was implemented in two different DLLs. The one you wanted depended on whether you are running Windows NT or Windows 95. On Windows 95, it was called "secur32.dll", but on Windows NT, it was called "security.dll".

    This was obviously a messed-up state of affairs, so the Windows NT folks decided to "go with the flow" and rename their security DLL to "secur32.dll". This was probably for application compatibility reasons: Applications that were written to run on Windows 95 and were never tested on Windows NT just went straight for "secur32.dll" instead of loading the correct DLL based on the operating system.

    Okay, so now pop back to the present day. When you put a DLL called "Security.dll" in your application directory, what happens?

    Recall that the rules for the order in which DLLs are searched for checks the application directory before it checks the system directory. As a result, anybody in your application who wants "Security.dll" will get your version instead of the system version.

    Even if the system version is the one they really wanted.

    That's why overriding the system's Security.dll with your own results in a bunch of SSPI errors. Components you are using in your program are trying to talk to SPPI by loading "security.dll" and instead of getting the system one, they get yours. But yours was never meant to be a replacement for "security.dll"; it's just some random DLL that happens to have the same name.

    You would have had the same problem if you happened to name your DLL something like "DDRAW.DLL" and some component in your program tried to create a DirectDraw surface. "Security.dll" has the disadvantage that it has a simple name (which people are likely to want to name their own DLL), and its importance to proper system functionality is not well-known. (Whereas it would be more obvious that creating a DLL called "kernel32.dll" and putting it in your application directory is going to cause nothing but trouble.)

Page 1 of 4 (33 items) 1234