Severe Problems with Window Blinds on a Win7 64-bit system

from WinCustomize Forums

Hello there,

well, I know this is another win7 64-bit post ... but I've encountered severe problems with window blinds on my brand new (got it yesterday) win 7 professional 64-bit system.  Install via Impulse worked just fine, but after applying a blind ("Frosted WB", I chose the win7 style) some explorer file couldn't be read anymore and the system froze. After rebooting all I got was a grey screen and a cursor. No access to anything. I managed to restore my system using the "starting/start up assistance" (I shut down the system while booting to get access to the screen asking you how to start windows, offering the options "start windows normally" or using the "starting assistance" - sorry for my bad english, I don't know the correct english terms). But now I'm reluctant to even try using Icon Packager or any other Object Desktop application. Objekt Dock Plus seems to work, Cursor FX does work. My Virus-Scanner and Firewall are the same as on my XP-Notebook (32-bit) and neither has ever caused problems with any Object Desktop application before and are running fine on my new system.

Is there a way to make WB etc. run on my sytem???? Will there be native 64-bit support in the near future?

Thanks for any suggestions!

2,659 views 4 replies
Reply #1 from WinCustomize Forums Top

The description of the error message does not sound like a problem that WindowBlinds would normally cause.  The error sounds more like a hard drive related problem.

WindowBlinds has native 64 bit support already and it does not replace any of the OS files on disk and does not start skinning until after the user has logged in.

Did you also install LogonStudio?  That could have an impact before login.

Reply #2 from WinCustomize Forums Top

Hello Neil,

thanks for your reply.

Yes, I did install LogonStudio but haven't used it yet. The Problem didn't occur while booting or logging in (though when logging in I already received the error message). Only after Login I experienced the blank screen, which was strange enough.

I used to run WB/Object Desktop on my 32-Bit-XP-Notebook before and never experienced any Problems at all (all Stardock Apps worked fine).

What also happened after System Recovery is that my entire Adobe Installation (CS4) was messed up and now I can't either uninstall or install it correctly anymore (already contacted Adobe support) - which doesn't have anything to do with Stardock, of course, but might help to describe the problem.

One Question though: All my Stardock/OD-stuff was automatically installed in the "Programs (x86)" Folder, as all other 32-Bit Programs such as Firefox etc. were installed into. Is that correct? I'm new to the 64-bit-world...

Anyway, I will contact my vendor today >:( . 

Multiplicity - Control multiple PCs using one keyboard and mouse
Reply #3 from WinCustomize Forums Top

That location is correct for the SD apps.

We make use of a mixture of 32 and 64 bit components when on a 64 bit OS based on actual need (there is no need for the config UI to be 64 bit for example)

Reply #4 from WinCustomize Forums Top

I tried to apply a skin again and encountered the same problems - but now I noted down the error message (I've translated it as best as I could):

"the command in 0x002c000 is pointing to memory/repository 0xffffffff. Operation read couldn't be operated in memory/repository. Klick ok to exit the program."

This Message appears while the skin is being applied. At the same time all desktop icons and the windows taskbar disappear. I can exit WB by just normally clicking the exit button. Object Dock is still working but nothing else. And after reboot I get that blank screen.

System recovery fixed that. By the way Icon Packager is running without problems. So this really seems to be a WB-related problem...

Any suggestions appreciated, thanks :) !