• The Old New Thing

    Lighting organic material and sucking it into your lungs


    Last year, The Philip Morris Companies renamed itself to the warm-and-fuzzy sounding Altria Group. Gotta love the colorful abstract logo they've got. (Psst, editors of the Altria home page: It's "Whom We Fund". "Whom" with an "m".)

    They claim the name comes from the Latin altus ("high") but that doesn't explain where the "r" comes from. Any similarity to "altruism" is purely unintentional, I am certain. Would a tobacco company lie to me? Or, As Business 2.0 put it, "[The renamed company] does not, however, stop producing tobacco, which does not stop causing cancer."

    Plus of course there's the matter that there is already a company called Altria Healthcare, which was none too pleased that a cigarette company decided to choose a name that matched theirs. But a Philip Morris spokesperson said that there is no conflict, pointing out that it is okay for companies to share the same name as long as they are in different fields of business, and "In our case that's not an issue. We're in very different lines of business."

    Because Altria Healthcare's job is to help people improve their health.

    Anyway, I was reminded of their 1995 recall of 8 billion cigarettes out of concern that their customers may become sick because the cigarettes allegedly contained the chemical methyl isothiocyanate (MITC). The Centers for Disease Control and Prevention investigated this problem and concluded that while it was true that the recalled cigarettes contained MITC, so too did cigarettes manufactured both before and after the recall, as well as cigarettes by other manufacturers. In other words, there was nothing wrong with those cigarettes.

    Well, aside from the fact that they are cigarettes.

    Michael Eriksen, chairman of the CDC's Office on Smoking and Health noted that the real problem is "lighting organic material and sucking it into your lungs". Somehow this way of describing smoking struck me as elegantly dry.

  • The Old New Thing

    Obtaining a window's size and position while it is minimized


    If you have a minimized window and want to know where it will go when you restore it, the GetWindowPlacement function will tell you. In particular, the rcNormalPosition tells you where the window would go if it were restored (as opposed to minimized or maximized).

    One perhaps-non-obvious flag is WPF_RESTORETOMAXIMIZED. This flag indicates that the window is currently minimized, but if the user selects "Restore", it will restore to its maximized instead of restored state. (This may seem strange, but you see it every day without even realizing. Take a window and maximize it. Now minimize it. Now click the taskbar button to re-open the window. Notice that it returns to its maximized state, not to its restored state. Imagine how frustrated you would be if it returned to its restored state instead. You'd have to keep re-maximizing the window.)

    The GetWindowPlacement and SetWindowPlacement functions are typically used by programs that wish to save/restore window positioning information across runs.

    You should also be aware that the coordinate system for window placement is not screen coordinates, but rather workspace coordinates. The consequence of getting this wrong is that your window creeps up (or to the left) over time, eventually getting itself stuck underneath the taskbar.
  • The Old New Thing

    Differences between managers and programmers, part 2


    If you are attending a presentation, you can tell whether the person at the lectern is a manager or a programmer by looking at their PowerPoint presentation.

    If it's black-and-white, all-text, multimedia-free, and rarely has more than ten bullet points on a page, then the presenter is probably a programmer.

    If it's colorful, with graphics, animation, and pages crammed with information bordering on illegibility, then the presenter is probably a manager.

    It's fun watching a manager try to rewind their presentation to a particular page. As you step over pages, you still have to sit through the animations, which means that instead of "hit space five times" to go forward five pages, you have to "hit space fifteen times, waiting three seconds between each press of the spacebar" because each page has three animations which you must sit through and experience again.

  • The Old New Thing

    Diagnosing a problem with calling conventions


    A commenter asks for help with an unresolved external. One of my goals is to give you more insight into how things work so you can solve problems yourself. This particular problem - resolving the error "Undefined symbol: '__stdcall(0) pl_pvcam_init (_pl_pvcam_init@0)' referenced from '_main' in Acquisition.c:15" is one example of something you can solve with the tips you've already learned.

    First, let's look at the unresolved external itself. "_pl_pvcam_init@0". From the article this comment was posted to, you can see that the leading underscore and trailing @0 indicate that the function uses the __stdcall calling convention. (This is confirmed by the linker's undeciration of the name.)

    So your function "_main" wants the function pl_pvcam_init with the __stdcall calling convention. But it's not found in the library even though you linked to it.

    If you look inside the library itself, you'll find the desired symbols with some decoration. Decode that decoration. (My psychic powers tell me that when you do, you'll find that the decoration is "_pl_pvcam_init", which is the __cdecl calling convention.)

    So now you see the problem. Your code is calling with the __stdcall calling convention, but the function actually uses the __cdecl calling convention. The calling conventions don't match up, so the linkage fails.

    The solution, of course, is to fix the declaration of the pl_pvcam_init function in the header file to specify the correct calling convention. My psychic powers tell me that the header file doesn't specify any calling convention at all, which puts it at the mercy of the ambient calling convention for your project, which appears to be __stdcall. But the author of the header file expected __cdecl to be the default calling convention.

    Put explicit calling conventions on the functions and you should be all set.

  • The Old New Thing

    Differences between managers and programmers


    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

    Another chance to see Elvis take on a mummy


    For those in the Seattle area who missed it last year, The Fremont Outdoor Cinema is screening Bubba Ho-Tep on Friday, July 9th.

    Go see it. You won't be disappointed. Assuming what you were expecting to see was Elvis fighting a mummy. With the help of JFK. In a wheelchair.

    If you were expecting something else, then okay maybe you'll be disappointed after all.

  • The Old New Thing

    What's the difference between SHGetMalloc, SHAlloc, CoGetMalloc, and CoTaskMemAlloc


    Let's get the easy ones out of the way.

    First, CoTaskMemAlloc is exactly the same as CoGetMalloc(MEMCTX_TASK) + IMalloc::Alloc, and CoTaskMemFree is the same as CoGetMalloc(MEMCTX_TASK) + IMalloc::Free. CoTaskMemAlloc and CoTaskMemFree (and the less-used CoTaskMemRealloc) are just convenience functions that save you the trouble of having to mess with CoGetMalloc yourself. Consequently, you can safely allocate memory via CoGetMalloc(MEMCTX_TASK) + IMalloc::Alloc, and then free it with CoTaskMemFree, and vice versa. It's all the same allocator.

    Similarly, SHAlloc and SHFree are just wrappers around SHGetMalloc which allocate/free the memory via the shell task allocator. Memory you allocated via SHGetMalloc + IMalloc::Alloc can be freed with SHFree.

    So far, we have this diagram.

    Shell task allocator
    OLE task allocator
    = SHGetMalloc  ??  CoGetMalloc = CoTaskMemAlloc/

    Now what about those question marks?

    If you read the comments in shlobj.h, you may get a bit of a hint:

    // Task allocator API
    //  All the shell extensions MUST use the task allocator (see OLE 2.0
    // programming guild for its definition) when they allocate or free
    // memory objects (mostly ITEMIDLIST) that are returned across any
    // shell interfaces. There are two ways to access the task allocator
    // from a shell extension depending on whether or not it is linked with
    // OLE32.DLL or not (purely for efficiency).
    // (1) A shell extension which calls any OLE API (i.e., linked with
    //  OLE32.DLL) should call OLE's task allocator (by retrieving
    //  the task allocator by calling CoGetMalloc API).
    // (2) A shell extension which does not call any OLE API (i.e., not linked
    //  with OLE32.DLL) should call the shell task allocator API (defined
    //  below), so that the shell can quickly loads it when OLE32.DLL is not
    //  loaded by any application at that point.
    // Notes:
    //  In next version of Windowso release, SHGetMalloc will be replaced by
    // the following macro.
    // #define SHGetMalloc(ppmem)   CoGetMalloc(MEMCTX_TASK, ppmem)

    (Yes, those typos "guild" and "Windowso" have been there since 1995.)

    This discussion strongly hints at what's going on.

    When Windows 95 was being developed, computers typically had just 4MB of memory. (The cool people got 8MB.) But Explorer was also heavily reliant upon COM for its shell extension architecture, and loading OLE32.DLL into memory was a significant kick in the teeth. Under such tight memory conditions, even the loss of 4K of memory was noticeable.

    The solution: Play "OLE Chicken".

    The shell, it turns out, didn't use very much of COM: The only objects it supported were in-process apartment-threaded objects with no marshalling. So the shell team wrote a "mini-COM" that supported only those operations and use it instead of the real thing. (It helped that one of the high-ranking members of the shell team was a COM super-expert.) The shell had its own miniature task allocator, its own miniature binder, its own miniature drag-drop loop, everything it needed provided you didn't run any other programs that used OLE32.

    Once some other program that used OLE32 started running, you had a problem: There were now two separate versions of OLE in the system: the real thing and the fake version inside the shell. Unless something was done, you wouldn't be able to interoperate between real-COM and fake-shell-COM. For example, you wouldn't be able to drag/drop data between Explorer (using fake-shell-COM) and a window that was using real-COM.

    The solution: With the help of other parts of the system, the shell detected that "COM is now in the building" once anybody loaded OLE32.DLL, and it and transferred all the information it had been managing on its own into the world of real COM. Once it did this, all the shell pseudo-COM functions switched to real-COM as well. For example, once OLE32.DLL got loaded, calls to the shell's fake-task-allocator just went to the real task allocator.

    But what is "OLE Chicken"? This is another variation of the various "chicken"-type games, perhaps the most famous of which is Schedule Chicken. In "OLE Chicken", each program would avoid loading OLE32.DLL as long as possible, so that it wouldn't be the one blamed for the long pause as OLE32.DLL got itself off the ground and ready for action. (Remember, we're talking 1995-era machines where allocating 32K would bring the wrath of the performance team upon your head.) [Typo fixed, 12:04pm]

    Okay, so let's look at that comment block again.

    The opening paragraph mentions the possibility that a shell extension does not itself link with OLE32.DLL. Option (1) discusses a shell extension that does use OLE32, in which case it should use the official OLE functions like CoGetMalloc. But Option (2) discusses a shell extension that does not use OLE32. Those shell extensions are directed to use the shell's fake-COM functions like SHGetMalloc, instead of the real-COM functions, so that no new dependency on OLE32 is created. Therefore, if OLE32 is not yet loaded, loading these shell extensions will also not cause OLE32 to be loaded, thereby saving the cost of loading and initializing OLE32.DLL.

    So the completion of our diagram for 1995-era programs would be something like this:

    Before OLE32.DLL is loaded:

    Shell task allocator
    OLE task allocator
    = SHGetMalloc    CoGetMalloc = CoTaskMemAlloc/

    After OLE32.DLL is loaded:

    Shell task allocator
    OLE task allocator
    = SHGetMalloc  =  CoGetMalloc = CoTaskMemAlloc/

    The final "Note" hints at the direction the shell intended to go. Eventually, loading OLE32.DLL would not be as painful as it was in Windows 95, and the shell can abandon its fake-COM and just use the real thing. At this point, asking for the shell task allocator would become the same as asking for the COM task allocator.

    That time actually arrived a long time ago. The days of 4MB machines are now the stuff of legend. The shell has ditched its fake-COM and now just uses real-COM everywhere.

    Therefore, the diagram today is the one with the equals-sign. All four functions are interchangeable in Windows XP and beyond.

    What if you want to run on older systems? Well, it is always acceptable to use CoTaskMemAlloc/CoTaskMemFree. Why? You can puzzle this out logically. Since those functions are exported from OLE32.DLL, the fact that you are using them means that OLE32.DLL is loaded, at which point the "After" diagram above with the equals sign kicks in, and everything is all one big happy family.

    The case where you need to be careful is if your DLL does not link to OLE32.DLL. In that case, you don't know whether you are in the "Before" or "After" case, and you have to play it safe and use the shell task allocator for the things that are documented as using the shell task allocator.

    I hope this discussion also provides the historical background of the function SHLoadOLE, which today doesn't do anything because OLE is already always loaded. But in the old days, this signalled to the shell, "Okay, now is the time to brain-dump your fake-COM into the real-COM."

  • The Old New Thing

    Don't name your DLL "Security.dll"


    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.)

  • The Old New Thing

    Being in upper management must damage certain portions of your brain


    The air must be thinner the higher up the management chain you go, or maybe it just gives you more opportunities to look stupid. Like this message:

    From: <some upper manager>
    Subject: <some subject>

    I will try to keep this relatively brief as I know how busy everyone is.

    <... 4-page message follows...>

    If this is brief, I'd hate to see a "somewhat lengthy" message.

  • The Old New Thing

    Why can't I use the same tree item multiple times?


    It's the continuing balance between ease-of-use and generality.

    At a literal level, you can't use the same tree items in multiple places in the tree, because then various properties would become ambiguous, properties like TVGN_PARENT or TVIS_EXPANDED. (If a tree could be in two places, then it would have two parents, for example.)

    Of course, this problem could have been solved by separating the item content from the item presence. So instead of just having an HTREEITEM, there would be, say, HTREENODE and HTREENODECONTENTS. The node would represent a physical location in the tree, and the item contents would represent the contents of that node: its name, icon, etc.

    Sure, that could have been done, but remember the balance. You're making the common case hard in order to benefit the rare case. Now everybody who is manipulating treeviews has to worry about twice as many objects (what used to be one item is now a node plus contents). This is generally not the balance you want to strike when designing an interface.

    When you design an interface, you want to make the common case easier than the rare case.

    A program that wants this separation can, of course, do the separation manually. Put all the contents in a separate shareable structure and have your HTREEITEMs refer to that shared structure in their lParams. This is more work for the program, but now the cost is being shouldered by the one who wants the extra functionality.

Page 385 of 430 (4,293 items) «383384385386387»