Ever since IconX was split off of DesktopX, many people have complained of startup related issues with these two programs: DX could be set to start automatically with windows boot, but IX could not; IX would no longer automatically when DX was loaded; starting IX after DX was already running caused DX to reset, causing all objects and scripts to reinitialize along with a perhaps considerable delay.

Although it's been a year, I haven't seen a solution from Stardock or anyone else, and the reinitialization of DX was irritating me enough that I finally put forth a concerted effort to do something about it. After some investigation and experimentation, I have a solution. VBscripts, batch files, and registry entries couldn't solve the problem for me because even if DX isn't set to start with Windows, it WILL set itself to autostart if Windows is shutdown while DX is running (even if the MCP is disabled). I've found the solution lies with the Stardock MCP.

Whenever you tell a ObjectDesktop app to automatically start itself, it puts itself on a list in the registry that is used by the MCP. Now the first problem is that IconX no longer has this option in its interface. The second problem is the way the MCP uses the registry list.

The ideal result is that IX must load before DX, and that the order of other apps such as RightClick or ObjectBar doesn't really matter. However, the MCP doesn't seem to know or care that IX needs to start before DX. At boot time, the MCP launches the programs it finds on the list in the order they are returned by RegEnumValue(), which under XP is in the order of the respective registry key's creation.

With this in mind, a simple procedure can ensure that IX reliably starts before DX at boot time, and no re-installations are necessary:

1. Ensure that the MCP is activated. In StardockCentral, select Tools->Settings->General and make sure that both "Enable MCP SmartStartup" and "Enable MCP noticication area support" are checked. Click OK and exit StardockCentral.

2. Launch RegEdit (via Start->Run) and navigate to HKEY_CURRENT_USER\Software\Stardock\Common\StartupManager

3. Right-click on the StartupManager folder and select New->StringValue

4a. In the Name field enter: IconX
4b. In the Data field enter the full path to the IconX executable using 8.3 filenames, surrounded by quotes. For example:
"C:\Progra~1\Object~1\IconX\IconX.exe"

Make sure the quotes are there, and that you get the path correct (you can check with DIR /X from a command prompt.

5. Exit out of Regedit

6. Right-click on the DX icon in the systray and select Configure DesktopX. Now select preferences.

7. You'll see an option "Run automatically when Windows starts". If it is already checked, UNcheck it and click Apply. If it is unchecked, do nothing.

8. Regardless of whether you did anything in step 7, now you should make sure the "Run automatically" box is CHECKED and click OK.

9. Now make sure you remove any shortcuts to DX or IX you have in your startup folders (either current user or all users), and also remove any "Run" registry entries you may have made for DX and IX. (If you didn't do this or don't know what it means, that's fine.)

You're done! At the next boot, you'll see the MCP screen, and you'll see it load IX before it loads DX. There may be other Stardock apps mixed in there, it doesn't matter, as long as IX loads before DX.

I hope this helps if you've been having problems. It works for me...

Cheers,

Will

Comments
on Jun 02, 2006
Thanks Will, maybe I'll give IX a go again.

Posted via WinCustomize Browser/Stardock Central
on Jun 02, 2006




on Jun 02, 2006
Is that a good surprised or a bad surprised, Bichur?
on Jun 02, 2006
A noble solution. It would be better if SD would actually fix the issue though so the end user does not have to resort to regedits.
on Jun 02, 2006
Good surprise.

Haven't tried to run both at start up in a while - keep remembering FireDogs thread.