2010 mid-year link clearance


Another round of the semi-annual link clearance.

And, as always, the obligatory plug for my column in TechNet Magazine:

Starting in June 2010, TechNet Magazine publishes each issue in two stages, and my column appears in the second half of the month, so don't freak out when you don't see it when a new issue first comes out.

Comments (19)
  1. Marquess says:

    Please, for the love of all that's good and holy, do not link to eBaum's World!

  2. Medinoc says:

    Speaking of the file associations, do you have anything planned about those weird file associations that put themselves in HKCU SofwareMicrosoftWindowsCurrentVersion ExplorerFileExts ?

    [No. I leave file associations to Zeke. -Raymond]
  3. Emmanuel says:

    Thanks for letting us know about your TechNet column. I was quite disappointed earlier this month when I looked at the June 2010 issue and didn't see your column listed. It's nice to know that they will still be there eventually!

  4. AC says:

    From the Programming Language History:

    "1983 – Bjarne Stroustrup bolts everything he's ever heard of onto C to create C++. The resulting language is so complex that programs must be sent to the future to be compiled by the Skynet artificial intelligence. Build times suffer."

    That's the most apt quip about C++ I've ever read!

  5. Joshua says:

    Too bad about the file associations really.

    Most of the programs for which I would have wanted to change the open action *to* expect to have new instances spawned rather than using DDE *and* have no code to register file extensions.

  6. Anonymous Coward says:

    The main problem with the file types dialogue is that it takes half an eternity to open because it's busy filling its list box.

    But just dropping it was a bad decision. It would have been better to be able to select a file (or other item) and then something like "edit file type" from the menu. Such a dialogue would know exactly where all menu items come from, could edit those that are user-editable, de-register shell extensions in case of trouble, and so on.

  7. cfgauss says:

    I noticed the new TechNet article has a picture of you in it!  I didn't recognize it, though, is there a way you could get it replaced with a more recognizable picture of you, say e.g., one of your withered hand?

    Also, I noticed part of the picture's name is "en-us" is there a non-English version of you I am unaware of?

  8. Nick says:

    Uh oh, what did I do now…

    *Reads long-forgotten comment*

    Okay, that was pretty rantish, must have been in a bad mood that day. I will say, however, that I do still miss being able to easily edit file verbs in Vista/Win7.  Your column was interesting and makes its point well, but given the nature of the problems faced it seems like the dialog could have been reworked so that it didn't pretend to be a "context-menu editor" for a file type, but still allowed for editing and adding custom verbs.

    Couldn't the issues with permissions have been handled by using the HKCU part of the file association mappings?  I thought that was a big reason behind the keys at HKEY_CURRENT_USERSoftwareClasses. For kicks I created a new verb under HKCUSoftwareClassestxtfileshellFoocommand and it appeared for me.  Is there a reason this wouldn't work, or is a bad idea?

    Of course, if you have a shell extensions that mucks around with the context menu it's impossible to know what the real end result will be, but it seems like anyone advanced enough to dig through the dialogs to get to the editor should understand that (sadly this is probably a bad assumption).

    I'm aware that at some point you have to stop trying to shoehorn something into place and realize it just doesn't fit — but it seems like it would be nicer to go buy new shoes instead of going around barefoot.  Don't take this the wrong way; I'm not criticizing or telling anyone how to do their job. I realize I'm not terribly knowledgeable on the subject and don't have any idea what goes on behind the scenes when features are considered being cut. I just miss them when they are :(

    [There are reasons why HKCU doesn't work (although it may seem to in specific cases), which I may get around to explaining someday. -Raymond]
  9. Marquess says:

    @Anonymous Coward:

    You mean something like the dialog you get when you click on “Change …” in a files Properties window?

  10. asdbsd says:

    If you think like a geek, the Power Options control panel is the logical place for configuring the Power button on the Start menu, because that’s where you control the computer’s power management decisions.

    To me it seems like, ironically, Power Options was NOT the logical place. After all, how the button on the start menu works has nothing to do with power configuration. The setting was probably placed there exactly because somebody tried NOT to think like a geek: "who cares that power management and power button user interface are unrelated? They both got "power" in them, so user would expect them to be in one place". Moving the start menu setting onto start menu settings page was exactly what a geek would do, so I guess everybody benefits from this change.

  11. anonymuos says:

    Pls fix file types dialog in 7 SP1.

    [You appear to have me confused with somebody who has control over what changes go into SP1. -Raymond]
  12. Jules says:

    "Teller (of Penn and Teller)  co-authors a paper on the neuroscience of magic."

    Not to mention James Randi ( en.wikipedia.org/…/James_Randi ), which is possibly even more cool.

  13. Anonymous says:

    Let me tell you that Microsoft also removed parts of the dialog that were NOT broken. Like manually defining a new file extension and *associated file type* without doing it programmatically, defining/editing custom secondary verbs by the user who knows nothing about programming, showing extensions only for specific file types, customizing the file icon and IE related settings like "Confirm open after download". This is a part of Vista/7 that remains broken by design. A powertoy with all of the functionality of the old dialog/clone of it and the same UI (which no can't replicate frustratingly) would make millions happier. The whole dumbing down essentially takes away *user* control over command line associated with file types. NOT HAPPY MICROSOFT.

  14. Gabe says:

    asdbsd: In the Power Options (Advanced tab) is where you specify things like what happens when you close the lid on your laptop, press the sleep button, or press your computer's power button. Since that's where you configure what happens when you press the hardware power button, it's logical that you would put the configuration for the software power button as well.

  15. asdbsd says:

    Gabe, it's logical if you think from a non-geek standpoint. But to a geek how a button in user interface of some random program works (explorer is just another program, after all) has nothing to do with how operating system manages computer's power. They're like clouds and stars in the skies: seemingly close for layman, but very unrelated in fact.

  16. anonymuos says:

    Pls fix file types dialog in windows 8.

    [You appear to have me confused with somebody who has control over what changes go into Windows 8. (You also appear to have missed the point of this Web site, which is to discuss old things, not new things.) -Raymond]
  17. someone says:

    Was it in the design goals of Windows 7 to not support and break compatibility with all 32 bit shell extensions? This is something I feel should change between the majority of the industry has migrated to 64-bit and 32-bit system is too rare to find.

  18. someone says:

    I mean 64-bit Windows 7 obviously. Why is it not possible any more to run 32-bit Explorer in the RC/RTM when the betas allowed that?

  19. Brian Tkatch says:

    You appear to have me confused with a real commenter.

    the point of this Web site, which is to discuss old things, not new things.) -Raymond]

    Raymond, you're the greatest. :)

Comments are closed.