Unfortunately problems and incompatibilities can arise, and there will be a section at the end to address these.

The Taskbar

If you're like me you would prefer to have all of your notification area icons visible.  However you may find yourself with less than sufficient room on the taskbar for the tasks themselves.  This is especially true if you have a rather wide quick launch area - which can be very valuable, as you'll see in a moment.  Some attempt to alleviate this issue by expanding their taskbar to two separate rows, but the additional bulk at the edge of your screen isn't very pleasing, nor will your pointer movement be as precise now that you've introduced a soft edge instead of the single hard edge of your monitor.

Likewise XP/Vista's similar task grouping feature has always struck me as a rather primitive and ineffective solution since you lose quick access to all of your tasks.

A very neat way of opening up space on your taskbar is to move minimized windows to an auto-hidden dock using RocketDock: a minimally intrusive, adequately configurable, speedy little Apple-esque application dock.

Configuring RocketDock version 1.3.5 as a Minimized Window Dock 

Although RocketDock is primarily an application launcher, it can be configured to only display minimized windows, as well as be out of your way.  Windows minimized to the dock are not displayed on the main taskbar.

I went to the trouble of exporting my RocketDock registry settings and comparing them to the defaults.  What remains is a Windows Registry file of only the relevant settings for the particular transformation you see pictured above.  I have annotated each of the settings in the file, and you may download it here: RocketDock v1.3.5 minimized window configuration.reg (3.07 kb)

I strongly advise that registry files from every source be previewed in a text-editor before being imported to the registry, due to the awesome and unchecked power that registry modifications can have on your system.  Previewing the above file you should be able to note that the only registry key affected is RocketDock's current user settings at HKEY_CURRENT_USER\Software\RocketDock.

Be advised: Holding the Ctrl key when minimizing a window is designed to bypass minimizing to the dock.  Holding Ctrl+Alt+Shift will toggle whether or not to minimize that window to the dock normally (these are stored in the registry as the process and window class names I believe).

2-16-08 On Windows Vista systems RocketDock utilizes Desktop Window Manager (DWM)'s public API for reliable live window thumbnails. However, rather unfortunately, in this mode the application's icon is no longer overlayed on the thumbnail. If you can stomach semi-frequent inaccurate thumbnails, then adjust RocketDock.exe's properties and enable Windows XP compatibility for the old (and in my opinion, more useful) behavior seen in the updated screenshot. Or, as I will be doing, you could register with RocketDock's bugtracker and gently persuade PolyVector to add the icon overlay to Vista DWM thumbnails as well.

Your taskbar is on the wrong edge

This may be a subject of contention, and you should of course use whatever you prefer, but in my opinion the taskbar is on the wrong side of the screen.  It should be on the top, not the bottom.  Although perhaps jaded from all of the separate versions of Windows happily placing the taskbar at the bottom, I had a moment of clarity in which I questioned the traditional, and I moved beyond.  Why is the top edge the better edge?  The reason is fairly simple: that's where everything else is.  Application menus and buttons have a long history of residence near the top, as well as address bars.  I find it preferable that my eyes and pointer need no longer unnecessarily traverse back and forth between edges.

Now it's true that this will place a buffer between the top edge and maximized windows - potentially slowing down the time it takes to target the titlebar (for double-click restoring) or the window buttons, but I find those too slow anyways, and don't use them (subject of a future post).  (Also, maximized windows aren't quite as useful as they once were.)

Use a persistent stand-alone OS toolbar for mouse application launching

The Quick Launch toolbar is underrated.  What appears to be a small space for launching a few specific applications in an unorganized manner need not be any of these things.  It is rather apparent that the quickest application launching possible with the mouse alone would require the least input and thought from the user.  The start menu is not in the least suitable, requiring far too much scrolling, clicking, and searching for company branded folders, all with the same generic folder icon.  Quick Launch is always immediatly present and visible (unless you use autohide) and it's a one click solution.  Once we've learned to associate an icon with its respective purpose they are much faster to process and far more compact than text.

Unlock your taskkbar if it's locked (context menu).  On XP you could simply grab the Quick Launch toolbar by its border and drag it anywhere you would like - leaving it as a floating toolbar, docking it against an edge, or adding it to an existing toolbar.  On Vista you can't drag around toolbars like this - but you can drag the folder itself to an edge to create a toolbar, and then as in XP, add additional folders to this toolbar with Toolbars in the context menu.

So to give Quick Launch its own stand-alone toolbar in Vista it may be fastest to right click the current Quick Launch toolbar, select Open Folder, navigate up to its parent, and then go ahead and drag "Quick Launch" to an absolute edge of your desktop.  Be careful not to drop the folder on your desktop itself.  Note that there is no cursor change or other indication for this, which is a bit bizarre.

On my 22" widescreen monitor at 1680 x 1050 resolution I can fit a maximum of about 70 icons across the bottom (the natural place for the toolbar, since my taskbar is at the top).

"Now wait a minute Chris.  70?  You said organized."

70 maximum.  Use as many program shortcuts as you find agreeable, and would like to launch in a single click.  For everything else there's a two click solution:

Never navigate your start menu again: Quick Launch pop up menus

You can view a little video of my full configuration for organizational ideas.

I know of two beautiful universal pop-up menu applications.  ShortPopUp and menuApp.  They both operate the same: they show a pop-up menu of the contents of the folder in which they are run.  Therefore creating a shortcut to either of these programs and specifying a folder full of shortcuts (or files) as the folder to "Start in" yields a fantastic menu for your toolbar.  There are essential differences between the two.

Middle click close and rearrange tasks with Taskbar Shuffle

Taskbar Shuffle is a fantastic lightweight tool which enables you to rearrange tasks with drag and drop, and most importantly, middle click close.  (If you don't already use the middle mouse button to open and close tabs in your web browser, you may want to start.)  Taskbar Shuffle also provides the means to rearrange notification area icons via holding down Ctrl.

A small issue or two, which may or may not apply to you

Unfortunately there are some minor problems with these recommendations.

1. Upper edge taskbar: Many programs attempt to be helpful by positioning themselves at the very top of your screen in an unintelligent manner.  If your taskkbar is at the top edge then these windows will be obscured and you'll have to resort to using the keyboard to reposition them (or temporarily repositioning the taskbar).  Right click their task in the taskbar, select Move, and press a directional arrow key on your keyboard.  The window will now be attached to your mouse and free to reposition.  (As Alt+Spacebar opens the same menu for the focused window, I tend to use Alt+Spacebar+M+directional arrow.)
   
   I'm sure this can in fact be automatically worked around with an AutoHotkey script for instance.  Since I have a bit of a love affair with AutoHotkey I don't find this too inconvenient of a solution, and will likely whip up a script when I have time.
   
   
2. RocketDock and UltraMon: Unfortunately the extremely helpful Move window to next monitor hotkey feature of UltraMon (which isn't discussed in this entry) has a very annoying issue with RocketDock, where windows, while technically moved, are minimized to the dock.  Neither program is really to blame for this problem.
   
   I indeed crafted an AutoHotkey script to fix this, but then realized a much simpler solution was to include Ctrl (but not Ctrl+Alt+Shift, see above) in the hotkey, since minimizing a window with Ctrl bypasses RocketDock.  So that's an easy fix.  However, since this means Ctrl must be held down until the window is minimized, you can't make a mouse binding (or some other automation) which rapidly sends the hotkey and expect it to work.  Since I use a mouse binding I may be resurrecting an extremely simplified AutoHotkey script which merely waits for the minimization before releasing Ctrl.  3-25-08 Fix available here.  Requires AutoHotkey.  Modify the opening lines for your (true) hotkey and UltraMon's, respectfully.  It even refocuses window controls beyond UltraMon's ability.

So the Thursday before last I set out to configure Vista's file indexing to only index file extensions of type lnk and exe, as I already had it configured to only index the locations on my computer which contained program shortcuts, but I wanted to extend these locations to include a folder of standalone executables and launch them from my start menu as well.

 But lo, I encountered this:

Just where exactly did all of my file types go?  You can see from the screenshot that the list stopped at .ado.

Well, like any good Windows troubleshooter, I turned to Sysinternal's essential Process Monitor.  I re-opened the file type dialog, this time with monitoring enabled, and performed a search for the last file type on the list, .ado.

As you can see from the lines I highlighted in the screenshot above, Vista was failing to read the next file extension in the list, .adobebridge, and presenting an Access Denied error.

Using Process Monitor's oh so useful Jump To... context menu feature, I jumped straight to the registry key having difficulty, and sure enough:

How interesting.  Using the key's context menu to view and modify its permissions presented me with this amusing (but accurate, I suppose) little message box before presenting the actual Permissions dialog.

Using the Ownership tab under Advanced to take ownership of the key allowed me to see the permission settings:

As you can see, there are no permissions set at all.  Adding the Users group and granting them Read privileges was enough to fix the dialog, but it takes write privileges to be able to actually toggle indexing on and off for the file type, so I made sure to add the Administrators group and grant them Full Control.  (UAC prompts you to allow the Advanced settings dialog to be launched with administrative rights when you first enter it, as denoted by the icon on the button: )  As it turned out that there were a dozen or so other keys the dialog choked on which required the same modification.  They didn't all have blank permissions, but none of them had read access for my account.

I'm not sure what's broken here, perhaps the software or installers which added these file extensions did so improperly, or maybe it was intentional and they didn't realize the entire file type indexing dialog would break when it was denied access.  Either way I would gander that the dialog behavior is most certainly a bug.

Unfortunately I'm not an expert when it comes to Windows Permissions setting, as I've never interacted with them on more than a casual basis, and I've done very little in the way of inheriting and propogating permissions, so I'm curious about the most appropriate and efficient solution to a scenario like this.   Include inheritable permissions from this object's parent was enabled for the registry keys with the problem, and other working keys claimed to be inheriting permissions from their parent, but I looked at the permissions on HKEY_CLASSES_ROOT and there appeared to be none to propogate.  So perhaps that is not their parent?  Any revealing information would be welcome.

(Note: Mark Russinovich of Sysinternals does an ever enlightening job of educating us on Windows internals, making copious use of Process Monitor in the process.)

It will be some time before the rest of my projects can showcase themselves, but at least now they will have a home.

And it will also be some time before this blog is precisely how I'd like it, but at least I have the power to shape it, and having already delved into BlogEngine's source code once, I should be in good shape myself.

Now let's look forward to the coming attractions. ;)