What is it?
--------------------
This docklet is intended for XP64 only. It addresses the issue that on XP64, 64-bit tasks are not shown with the running tasks on the dock. This docklet allows a 64-bit system to use objectdock as a taskbar replacement.

When using objectdock as a taskbar replacement, it is necessary to see all running tasks on the objectdock in order to still have a usable means to switch tasks. However, due to the fact that objectdock is running in 32bit address space, some of the task information is unavailable. This results in objectdock not showing 64bit windows.  It will show them if the tasks are running before objectdock starts, but they will all be grouped together under one icon and new tasks will not be shown. It's basically useless for a 64-bit system.

While this docklet has some caveats, it solves the problem for the most part. The docklet polls for 64-bit tasks and creates a 32-bit task to host it. This task will show up in the taskbar with the original app's icon allowing you to use that icon to bring the task window to front or close the 64-bit task.  

Some points of interested are:

* The docklet will create a 32-bit task and run it for every 64bit task with a parent window that is launched. The 32-bit task has no visible window, but it may show up in alt-tab if anyone uses this. 
* The 64bit tasks will not support minimize window contents to objectdock feature.
* The min/max buttons currently do not work when used from the right menu on the objectdock icon (may fix in an update).
* When objectdock loads, it already enumerates all 64bit tasks running. The docklet will, therefore, only listen for additional 64bit tasks that are launched after the docklet is loaded. This prevents duplicates on the taskbar.
* If objectdock crashes or is closed, the 32-bit tasks are left running and will show up in the taskbar when it is visible again.
* The docklet creates a folder called launcherstore in its Task64Fix dir which it copies a 64kb executable for each unique task launched.  This is needed because objectdock groups tasks together based on .exe name. If a unique name isnt used for each app, they all get grouped together. (Objectdock cannot get the .exe name of 64bit tasks so that field is empty. This is why when you launch objectdock the first time and there are 64bit windows open, it groups them all together. They share the .exe name of "").
* The icon i borrowed from my objectdock installation. You can change it by changing Task64Fix.png with whatever you want to replace it with or by using the default method of changing images in objectdock.

Installation
---------------
Extract this archive to your Dockelets dir. The directory *must* be Task64Fix. This is where the docklet looks for launcher.exe. If the directory structure is changed, this docklet will not work. 

The only configuration is launcherskip.ini. This is a list of "classes" to skip. Sometimes bringing up the run or start menu might enumerate as a 64-bit window. This might result in a dead task with an ugly icon sitting on the objectdock running tasks section. If this happens, you can kill the task in task manager. You can find the class of the task using the properties menu of objectdock by right clicking on the icon. Then you can enter that class in launcherskip.ini and it will ignore that class preventing the problem. I have entered already all the common ones that occurred on my system. 

Bug reports
-------------
I use this myself and use it as a taskbar replacement. I fix bugs I find on the spot. If you find a serious issue, there's a good chance that I have already fixed it. However, if you want to report a bug you may do so by  posting in one of the objectdock forums. I may or may not read it. I'm sorry, but due to spam I will not provide my email address.

