Magic Desktop (Clock doesn't work)

from Stardock Forums
The second hand doesn't move and the time on the clock doesn't change, except when I right click on the clock and it shows the "Close/About/Autorun" menu.
While this menu is visible, the second hand ticks happily away.
(Running Vista 32bit)

Thanks
wincustomize
8,897 views 13 replies
Reply #1 from Stardock Forums Top
Is this the MyColors version or the WindowBlinds version?
Reply #2 from WinCustomize Forums Top

Could you go to Start->Start Search and type in cmd. Then in the command window, type this: tasklist /m /fi "imagename eq Magic Clock.exe" and paste the results here or in an email to support@stardock.com

-Mike
[Stardock Support]

WindowBlinds - Free yourself of the default settings, customize your desktop.
Reply #3 from Stardock Forums Top
Didn't know there were different versions. I presume it's not the MyColours version:

Mike,
I have found what the problem is, it's a macro program called Macro Express. When this is running the clock behaves as mentioned above. When this isn't running the clock works correctly.
I have run your command with and without this program running, see below, and the difference appears to be "mexhook.dll". I don't know if thats a problem you can get around, but at least you should have a better idea where to look:


Image Name PID Modules
========================= ======== ============================================
Magic Clock.exe 2896 ntdll.dll, kernel32.dll, USER32.dll,
GDI32.dll, ADVAPI32.dll, RPCRT4.dll,
COMDLG32.dll, msvcrt.dll, SHLWAPI.dll,
COMCTL32.dll, SHELL32.dll, ole32.dll,
WINMM.dll, OLEAUT32.dll, OLEACC.dll,
WININET.dll, Normaliz.dll, iertutil.dll,
IMM32.DLL, MSCTF.dll, LPK.DLL, USP10.dll,
USERENV.dll, Secur32.dll, wbload.dll,
WBLIND.dll, UXTHEME.DLL, msimg32.dll,
wbhelp.dll, sdvdesktops.dll, gdiplus.dll,
DWMAPI.DLL, DXAxHost.dll, WS2_32.dll,
NSI.dll, CLBCatQ.DLL, msxml3.dll,
SDAnalogClock3.dll, SXS.DLL,
WindowsCodecs.dll, vbscript.dll, wshom.ocx,
MPR.dll, ScrRun.dll, VERSION.dll,
mexhook.dll

Image Name PID Modules
========================= ======== ===========================================
Magic Clock.exe 2896 ntdll.dll, kernel32.dll, USER32.dll,
GDI32.dll, ADVAPI32.dll, RPCRT4.dll,
COMDLG32.dll, msvcrt.dll, SHLWAPI.dll,
COMCTL32.dll, SHELL32.dll, ole32.dll,
WINMM.dll, OLEAUT32.dll, OLEACC.dll,
WININET.dll, Normaliz.dll, iertutil.dll,
IMM32.DLL, MSCTF.dll, LPK.DLL, USP10.dll,
USERENV.dll, Secur32.dll, wbload.dll,
WBLIND.dll, UXTHEME.DLL, msimg32.dll,
wbhelp.dll, sdvdesktops.dll, gdiplus.dll,
DWMAPI.DLL, DXAxHost.dll, WS2_32.dll,
NSI.dll, CLBCatQ.DLL, msxml3.dll,
SDAnalogClock3.dll, SXS.DLL,
WindowsCodecs.dll, vbscript.dll, wshom.ocx,
MPR.dll, ScrRun.dll, VERSION.dll


HTH
Reply #4 from Stardock Forums Top
Ah, this seems to have fallen under a S.E.P. field.
I shall log if official then, thanks.
Reply #5 from Stardock Forums Top

Does the Macro Express app have any kind of exclusion list? This might be a good instance where you can utilize that.

I will try and do some testing later today and attempt to reproduce the problem you're describing. If I am able to encounter the problem, I will see if I can get these two working together.

-Mike
[Stardock Support]

Reply #6 from Stardock Forums Top

Unfortunately I was not able to reproduce this problem using Macro Express and the Magic Clock. Would you be able to export your Macro Express program configuration and either send that here, or in a private message to me?

(Click on my name at the top of this post to access additional functions, including the private message feature).

Thanks!

-Mike
[Stardock Support]

Reply #8 from Stardock Forums Top
Apologies, I had broken the above WWW link, but it's working again now.
Reply #9 from WinCustomize Forums Top

I'm not sure whether you'd received my email, but I had loaded your configuration file, but was unfortunately not able to reproduce the problem.

Try going to File->Export->Export Macros, clicking Select All and then clicking Save File. Hopefully this file will give me something with which I can use to reproduce the issue.

Have you had any luck contacting Insight Software Solutions? (Macro Express developers)

-Mike
[Stardock Support]

Reply #10 from Stardock Forums Top
I have not received any emails.

But it doesn't have anything to do with my macros because I have uninstalled, and re-installed from scratch.
As soon as Macro Express runs for the first time, the clock gadget stops.

I have not contacted Insight Software, but I will give them a try too.

Thanks
Bryan
Reply #11 from Stardock Forums Top
Reply from Insight Software:

We looked at this problem yesterday afternoon and are getting the same results. One of the functions within the mexhook.dll file is the keyboard remapping feature in Macro Express. It looks like this is the function that is clashing with MagicClock.

Right now our thinking is to place an option in Macro Express to turn on or off the keyboard remapping option. Turning it off would allow MagicClock to work correctly, and potentially other apps as well.


I wonder what else you have running on your setup that would stop you from being able to replicate the issue. But, at least it's being dealt with.

Thanks
Bryan
Reply #12 from WinCustomize Forums Top
Hi,

I have got the same problem: the Magic Clocks hands don't move. The seconds hands used to move in 5 sec. intervals but now they don't move at all. When entering the About dialog once, the clock started to work normally, but now it doesn't work at all. I tried your command, it gave

Abbildname PID Module
========================= ======== ============================================
Magic Clock.exe 1788 ntdll.dll, wow64.dll, wow64win.dll,
wow64cpu.dll

It listed less than with the topic starter. I'm using Vista Basic 64 German.

Any idea?

Thanks, Lars