Weird Bug in ObjectDock Plus 1.90

By Josh Fountain Posted May 19, 2008 22:41:31

Ok I have this unexplicable error happening with my ObjectDock. Whenever I click the "My Documents" object it always opens windows search. If I right-click and hit "open" on the same object it opens My Documents folder like normal. I don't understand why this is happening. Currently I am using ObjectDock Plus v1.90 build537u Beta Release. This was the version sent to me to download when I bought it a while ago. My first question is if they ever did a full release and how can I get it as I think it's kind of silly to purchase the product and be sent a beta version (I didn't know it was beta until I just checked right now). I am also using Windows 2000 service pack 4 if that counts for anything. Any help at all would be great as I've done alot of searching and it seems that I might be the only person having this particular bug.

+1 Karma 12 Replies 5 Referrals

Not much of a useful reply but you might want to rename the topic because 1.95 hasn't been released yet

when you right click, is 'open' the 1st option?

if you just open 'my docs' normally does it 'search'

if you open my docs, the move up a folder to the desktop folder then double click my docs does it search?

if you downloaded via SDC, uncheck show pre release down at the bottom

Sorry I don't know where that "5" came from >_>

Yeah it is version 1.90 beta.

When I right click Open is the first option, yes.

When I just open My Docs from the ObjectDock normally it always opens the windows search, yes.

When I open My Docs and move up a folder then double click my docs it does NOT search, no.

I did not download via SDC. ObjectDock is the only Stardock program that I own.

Sign Up or Login and this ad disappears!
There are many great features available to you once you register. Sign Up for a free account and browse the forums without ads.

I did not download via SDC. ObjectDock is the only Stardock program that I own.

send an email to sales or support - see if they'll send you the last release version prior to the beta

don't know about the search thing, don't have plus to look at all the options.. in the freeloader version I can set it to open the folder or show in a menu - the arguments are left blank --- do your 'my documents' shortcut settings contain arguments?

Hmm that just might work. It's just support@stardock.com right? I don't have the original email as I cleared out my folders a while ago. I think I saved a copy of the purchase email receipt though somewhere on my HDD.

And all my arguments are left blank on the settings as well. This is the wierdest bug ever....

Hello there -

DId you fix the problem? Maybe it's too late. . . .

Run, "regedit" and find:

Code: php
 HKEY_CLASSES_ROOT\Directory\shell

Then, double-click on the default value and set it to "none" without the quotes.

Ok, I tried the registry edit and it didn't work either.

Now I have a new problem though (unrelated?).

http://forums.wincustomize.com/164743

I am Jamochawoke on that thread. It's an old thread but it describes how I installed ObjectDock the first time.

I am now having the same problem that I did on that thread. IE: ObjectDock now won't load up at all and gives a crash error and log. I remembered that I performed that fix with SDC and reloaded it.

Here's the entirety of it:

I installed the Plus version I got via the website and activated with code from email.
I got the error, started that old thread.
Installed SDC and installed ObjectDock Plus from SDC over my installation.
Everything worked fine.
I accidentally removed my My Documents object so I made a new one by dragging My Documents from Explorer into the dock.
The bug started happening with Search opening instead of the folder unless you rightclick->open. This happens with all folders dragged onto ObjectDock.
So I uninstalled the beta version using SDC.
Bug was still there, also all my old settings are still there.
I uninstalled it entirely using SDC and reinstalled using SDC.
Bug still there, all old settings there.
I uninstalled it entirely using SDC then uninstalled SDC using Windows.
I then restarted.
I then used a file shredder to shred the contents of the leftover Stardock folder in Program Files and any temp files I found.
I then reinstalled SDC.
I then installed ObjectDock again.
The bug was still there and my old settings were still there /boggle?
I then did the whole uninstall again.
I found a backup of my system where I had the original install file and my activation email. I installed and activated ObjectDock Plus and got the error in the first thread where it wouldn't start.
I then redownloaded SDC and installed ObjectDock over my original installation just like in the first thread that fixed it the first time. It didn't work.
I then clicked to download the ObjectDock Plus beta and it loads up now but...
The bug is still there and all of my old settings are there STILL (wtf I shredded everything >_>).

I am just totally at a loss now what to do aside from reformatting my entire computer and trying an install that way. Unfortunately I cannot do a reformat at this time without losing substantial amounts of data (no way to back it all up at this time).

EDIT:::

Using the beta version of 1.90 everything works perfectly EXCEPT the original issue.

When I click on any folder object it performs a search in that folder instead of opening the folder.

*le sigh*

FIXED

I have fixed the issue.

For some reason and some way unbeknownst to me the registry got corrupted. After a few days searching for registry fixes I found this little tidbit:

If you are also experiencing this problem when you try to click on a drive, you can run this command from the run box or command prompt:

regsvr32 /i shell32.dll

This should restore the normal behavior.

Somehow my shell32.dll file got messed up in the registry where it concerned links from other programs not in Explorer. Instead of opening a directory it would always perform a search instead.

This small run command fixed it instantly!

Since this was an on going issue were you using XP or Vista?

I am using Windows 2000 SP4.

Oh that would be a problem for several parts of the program yes. Though I am going to test that out now on one of our virtual machines. Thanks for the heads up!