Anyone else seen this?
Published on September 21, 2007 By Asmodean_dk In

First of all a disclaimer: I am not at all sure that the following problem is related to WB - nor do I blame Stardock in any way, should it be. I am aware that this is a beta version, and as such cannot be guaranteed to function 100% in all areas.

Then to my problem:

Yesterday afternoon, I updated WB to 5.92.090. SDC prompted me to restart my computer, and I did. Upon restarting, Windows Data Execution Prevention (nice name for a service, eh?) closed Windows Explorer. I went huh??? But then Windows Explorer started again the next second, and all was fine.

Since then, though, about 50% of the times I reboot my computer I get the exact same thing. Windows Explorer gets closed by Windows Data Execution Prevention, but starts again right after.

Anyone else seen this?

Asmodean
Comments (Page 2)
6 Pages1 2 3 4  Last
on Sep 22, 2007
on Sep 23, 2007

Hmm - it seems I inadvertently started a whole new bug reports thread. Truly sorry for that, Neil...was not my intention.

As for my problem, it has since corrected itself. I have no idea what was wrong.

Asmodean
on Sep 23, 2007
Up, Up

Mayday, Mayday, Mayday


I just wanted to add that this problem just came with the last beta version of WB6 (the one which move WB skins ...)
on Sep 23, 2007

@ Neophil, #3:
I have the same problem, Neophil. This is the first post I've seen that mentions the prob. I upgraded to WB6 and Start Meneu and Taskbar were skinned 'til I rebooted, then both were rendered in Windows Classic only. When I opened WBconfig, the skin did not show a taskbar in the preview! If there was a substyle to the skin, it still had the taskbar visible in the preview pane, and a skinned taskbar and Start Menu...until reboot, then also that substyle had no taskbar in the preview pane. Any skin I chose, same behavior. Diamond ran until I rebooted, then no taskbar skinned and none visible in the preview pane. Only way I fixed it was to delete the theme and reinstall it, then fine 'til next boot! Weird, yes. Have since gone back to WB5.51. Hope it gets fixed so I can use WB6...   


I have the same problum help


WindowBlinds version : WindowBlinds 6 (6.0 (beta build 25 x86))

WindowBlinds is installed correctly on this PC

WindowBlinds appears to be activated on this PC

Your machine supports per pixel borders on WindowBlinds skins.

(Plug and Play Monitor) 1 is attached to NVIDIA GeForce FX 5500

Wblind.dll 2007/09/18 15:20:20
Wbsrv.dll 2007/09/18 15:20:43
Wbconfig.exe 2007/09/18 15:20:55
Wbload.exe 2007/09/17 14:34:51
Wbhelp.dll 2007/08/27 11:54:07
Wbui.dll 2007/08/27 11:54:06
Tray.dll 2007/09/12 17:58:21


mine did not go away help!

beta 1s all worked
on Sep 23, 2007
bump
on Sep 24, 2007
on Sep 24, 2007
started a whole new bug reports thread

No pearls of wisdom to be found here...
Guess I'll save all the parts of WB5 I want, replace it with WB6, and attain Zen or samadhi or whatever, waiting to see if my system's scrambled.
"WB Roulette"   
on Sep 27, 2007
Hey guys, are you on the way to solve the trouble ???

here what i get:

Free Image Hosting at www.ImageShack.us

until i edit it in Skinstudio 5.01.049 and just apply the skin which is displayed correctly until the next boot, and back to the same way ...

It's begining to be very boaring ...
on Sep 27, 2007
Not sure if I have a solution or not. I went back to the original post and in fact all the replies and realised that I had the similar problem, except it was happening before the last update. It only happened with a couple of skins, wish I could remember which ones.

I have Object Desktop, I use WindowBlinds to change Blinds. Once I select a blind I go to setting and make sure they point to the blind I'm using, than hit apply changes. Usually everthing works okay. For the frist time it didn't, like must folks I made a sad face and tried another blind, everything worked fine. Went back to the one I was having a problem and guess what it didn't work. Taskbar and Start menue were Windows Classic.

Then I decided to try right clicking on the desktop bringing up display propreties, hit appearence than advanced and under XP Overrides it wasn't pointing to the blind that I was trying to use. Guess what it was pointed at? Changed it to the blind, closed the window hit apply and everything was find. Again I wish I could remember the blind that had the problem.

Hope this helps someone. By the way this is on an XP system.  
on Sep 27, 2007
Found the way to get rid off this ...
In fact when ugrading to WB6 (and probably during all skins are moved from C:\Program Files\Stardock\Object Desktop\WindowBlinds to C:\Documents and Settings\All Users\Documents\Stardock\WindowBlinds all .wb4 files are deleted.
If you still have Skinstudio V5 as .uis editor, when editing any .uis file and saving it, it seems to not create all the .wb4 files needed by WB6 version.

Though the solution if you have those kind of troubles with a skin (at least under XP) is to edit the .uis file no more with Skinstudio V5, but with Skinstudio beta 6 and save it this way, and as a magical fairy coming on your PC, everything's go back the right way ...


... and thanks Stardock for your kind effort in resolving this problem ...   
on Sep 27, 2007
Damned, i was wrong, it still doesn't work this way ...   
on Sep 27, 2007
Thanks, everyone, for your input. At least this thread is still ative so maybe we'll get a fix soon. Using WIN XP SP2, WB5.51
on Sep 27, 2007
After each of the last 2 updates, the WBConfig preview & settings went weird (no StartPanel in the Preview at all, transparency settings changed without my input). I don't know why the updates are borking things up, but my display issues went away after deleting the skin's cache files (*.wb4, ~*.*, *.*~) and re-applying the skin, combined with altering & resetting to defaults all the transparency/blur settings in WBConfig to "wake them up" or whatever. Had to do it at least twice to get everything displaying correctly.

WB &/or SKS need a better way of handling/updating these cache files - I suspect they are a culprit (not necessarily the culprit) in a lot of the problems people have been reporting with the betas.

FWIW, I'm still developing & modifying skins with SKS5, which may or may not be a factor - I'm waiting for the SKS6 bugs to get sorted out a bit more before moving over.
on Sep 28, 2007
I was wrong to say i was wrong IT WORKS, i just omit to delete previously the lefted .wb4 made when applying skin through SKS V5 (BTW, it would be interisting to understand why SKS v5 is now obsolete ... )

Seldomseen, i also continue to use SKS V5, but for resolving the trouble for WB6, i just installed the SKS V6 beta (both version can be installed), just edit the .uis file of the skin which have a trouble, save it through SKS V6 and thing's are OK (well i hope, i did 3 reboot to see, if the skin is correctly applying ... and it is)
on Sep 28, 2007
Aaaaaaaaaaarrrrrrrrrggggggggggggggg, it doesn't work anymore

I've updated to latest WB6 build, reboot and then * BUMP *
6 Pages1 2 3 4  Last