WB 5.5 Beta w/Vista Basic cycles dwm.exe

This is interesting. My Mobile Intel(R) 915GM/GMS,910GML Express Chipset Family based Tablet PC only supports Vista Basic. While running WB 5.5 beta, I've noticed that the Microsoft Desktop Window Manager (dwe.exe) is in an in-finite loop of starting, using CPU, ending. The process ID changes just about every other second.

Without WindowBlinds, dwm.exe runs steady (same PID) using little to no CPU.

I will be curious to find out if there's a cause/effect relationship here due to the fact that my hardware does not support aero.

Thanks for your insights!

- Jim Wilt
5,467 views 11 replies
Reply #1 Top
do you have the option checked to never use per pixel?
Reply #2 Top
what happens if you add dwe.exe to the per application to not be skinned?
Reply #3 Top
Two excellent debugging suggestions:

(1) Yes, I do you have the option checked to never use per pixel

(2) After setting dwm.exe to not be skinned, it still cycles (not surprising to me because I believe it to be a background process, but well worth trying)

Please share any further epiphanies as they come

- Jim
Reply #4 Top
are we talking dwe.exe or dwm.exe? if there's one of each did you try both?
Reply #5 Top
Good catch of my mistyping, it's dwm.exe, only.
Reply #6 Top
ummmm.... put XP back?


Reply #7 Top
He he, unfortunately Vista w/o WindowBlinds > XP w/WindowBlinds (from a tablet experience perspective)

It's worth waiting for WB to get another version out
Reply #8 Top
Reply #9 Top

As clearly stated in the history (and possibly readme), this build of WindowBlinds for Vista requires you to have DWM capable hardware which is why WB is very upset on your machine currently.

Reply #10 Top
-You must have WDDM drivers for your video card on Vista for this build to work.

Yes, it is clearly stated, but was missed by Me. Touché
Reply #11 Top