WB Just just caused erros all over my pc.ARG!

from WinCustomize Forums
WindowBlinds version : WindowBlinds 5 (5.5 (build 86 x86))

I have this installed...its been working fine...I Have it set to not skin photoshop cs2. All of a sudden today, while working in PS it started skinning it...it would freeze up really bad...then flicker fast and then un skin it. Well...needless to say it was very annoying...so I opened WB to turn it off completly until my project was done...the normal splash screen came up and it just sat there...a good 3 minutes....then all of my windows error reports starting popping up. It closed Photoshop, Zone alarm, Avast anti virus and some component im not sure of..sorry...i was seeing red art the time. I lost about 10 hours of work today because of this.

Can anyone please tell me what happened or why it still skins a program when you have it set to not skin it?

Thank you very much for your time.
Steve
DP Studios

Using SOHO WB by Navigatsio https://www.wincustomize.com/skins.aspx?skinid=6038&libid=1 at the time, been using it since the day it came out and no problems till now.

WindowBlinds version : WindowBlinds 5 (5.5 (build 86 x86))

WindowBlinds is installed correctly on this PC

WindowBlinds appears to be activated on this PC

You have one monitor in total.

(Plug and Play Monitor) 1 is attached to Intel(R) 82845G/GL/GE/PE/GV Graphics Controller

Wblind.dll         2007/02/01 18:53:20
Wblind64.dll         2006/10/09 12:51:37
Wbsrv.dll         2006/11/18 14:47:19
Wbconfig.exe         2007/01/30 11:41:02
Wbload.exe         2006/03/13 17:54:14
Wbhelp.dll         2004/09/18 16:37:07
Wbui.dll         2005/12/06 22:29:06
Tray.dll         2006/04/28 19:27:49
windowblinds
1,573 views 4 replies
Reply #1 from WinCustomize Forums Top

If you exclude an app in WB you have excluded it.

When a window under XP stops responding a ghost window is created by the OS and the app window is hidden.  This ghost window (which is just a snapshot of the original) will be skinned by WB as it is part of explorer which is not excluded.

So what you are seeing is Photoshop stopping responding and a ghost window replacing it.  WB will skin this window & once the app starts to respond again the ghost window is removed & the original is reshown which will be unskinned as you excluded the app.

The same thing happens with the Windows XP Style on XP if you exclude an app from themes.

Basically the skinning is a symptom of Photoshop not responding on your PC.  The app had already stopped responding before the skinned window would show and that is not being caused by WindowBlinds.  Why the app started to not respond is something only adobe can answer.

Regarding the crashes on unload, did you get any information about the crash addresses?

Also why are you excluding that app?  It should work fine with WB and if it does not then I would be interested in knowing what does not work so we can look into it.

Reply #2 from WinCustomize Forums Top
Thank you for your response...that makes a lot of sense to me. Im glad it wasn't the WB. And im sorry I didn't get any info.I was so mad.i just started clicking don't send. When I installed it and ran PS I just found it very distracting....Im so used to using it with out it...its nothing about WB...just a personal preference. If it crashes my other programs again ill be sure to get the info for you. Thank you again.
Steve
Offworld Trading Company
Reply #3 from WinCustomize Forums Top
There may be information about the crashes in the event log.
Reply #4 from WinCustomize Forums Top

So what you are seeing is Photoshop stopping responding and a ghost window replacing it. WB will skin this window & once the app starts to respond again the ghost window is removed & the original is reshown which will be unskinned as you excluded the app.

I always wondered about that...