michaeljennings2 michaeljennings2

ObjectDock Settings won't open in Windows 7

▼

ObjectDock Settings won't open in Windows 7

Can't access settings - right click dock/ settings

from Stardock Forums

I just purchased ObjectDock Plus and I can't access the settings menu to configure the product.

I'm running Windows 7 Professional. I disabled Virus scanner. I ran as administrator. Neither worked.

anyone know how to fix this?

26,145 views 37 replies
Reply #26 from WinCustomize Forums Top

How did you run a log on Object Dock?I went in to event vieweer and set up a number of logs but did not see anything.

 

Reply #27 from WinCustomize Forums Top

Quoting CFJ90210, reply 25
If you haven't found a solution to this problem yet, I figured out a way that worked for me. I forgot where I found it, but I opened a log for Objectdock that reported errors and found that my Arial font was apparently messing up the settings menu because it was corrupted for some reason. This seems to happen a lot because as soon as I searched generically for the Arial font being corrupted, I saw that tons of different programs don't work.

 

Try to find a non-corrupted Arial font on the web and copy into your fonts folder in the Windows filesystem. I used this one to overwrite my Arial font: http://sourceforge.net/projects/corefonts/files/the%20fonts/final/arial32.exe/download?use_mirror=voxel

 

I found this out with literally no help from Objectdock support, I might add.
End of CFJ90210's quote

 

I ran the exe to install the Arial font. Still no luck in opening the Object Dock Config/Settings window.

I've emaied StarDock 3 times last week - not one reply!

Groupy 2 - Organize multiple applications into grouped tabs on your Windows desktop
Reply #28 from WinCustomize Forums Top

And each one sent pushed your request to the back of the cue. Its like stepping out of line and losing your place. Bummer.

Reply #29 from WinCustomize Forums Top

^ Uvah is correct. You need to wait after sending in a problem....don't worry your place in the queue will be there unless you email again, in which case you go to the back of the line.

Reply #30 from WinCustomize Forums Top

I had a Zubaz moment. Cue instead of queue. hehe

Reply #31 from Stardock Forums Top

ljhite

had some problem, Stardock Support could not resolve.

Window 7 64 bit

Got refund

Reply #32 from Stardock Forums Top

   Just bought upgrade, same problem,  Win7 Ent 64-bit , no settings access whatsoever, opened a case and now ....

-rob

 

 

Reply #33 from Stardock Forums Top

Ill be damned if that isn't it... I installed that Ariel font thinking that wasn't gonna do anything.. and it friggen worked....

 

problem solved...

Reply #34 from Stardock Forums Top

here's how I did it... I uninstalled object dock , restarted, then installed the ariel font, and then reinstalled object dock... done that was it...

Reply #35 from WinCustomize Forums Top

OK. I uninstalled using Impulse. That reset the PC. I rant he .exe to install the font. I reset again and then had Impulse re-install Object Dock. Still no Configuration/ Settings!

Anyone know where I can access the log so I can figure out what issues this thing is having?

Reply #36 from WinCustomize Forums Top

Michael for what it is worth, you are not the only one who has had problems with Object Dock Plus 2.0. I am running Windows 7 Pro 64 bit. I have never been able to get ODP 2.0 to run correctly. One of my main issues is that I can only get the default themes to show, no matter how many I add, and no matter where I place new themes (correct folders). After getting a few patronizing answers in the Impulse chat room(s), I gave up. Since then I have been using ODP 1.90. At least I can add and change themes with it. Good luck! :)

Reply #37 from WinCustomize Forums Top

Success! It turns out it was the Arial font. The issue was, I had to select 'Run as Administrator'! The Stardock support team sent over a logging program, logged in and saw it couldn't find the font. When I installed before by selecting run, it said t installed but something ovviosuly didn't take. So I figured I'd try Run as Administrator, and it worked!

Thanks to all of you for helping out. Much appreciated!