Just playin'
Incompatible with WB
Published on May 14, 2005 By enoch In WindowBlinds
Yahoo! Music Engine Won't launch (at least in XP) when WB is enabled. I found this out the hard way when I fist installed it. It freezes my system and I have to do a hard re-boot. After turning off WB, then launching YME it loaded. It's a Beta program granted. I would tell Yahoo! about this but they don't have a submit link for it (unless you are a beta tester I presume). Just a heads up in hopes someone might include a WB workaround in the next release. Link
Comments
on May 14, 2005
Sheeesh!..Must be real important to have posted 3 threads about it!
If it were my decision I would have probably just deleted YME and gotten that junk out of my system ..
without posting..LoL

Lets face it..Windowblinds are waaaaay cooler!

Zero.
on May 14, 2005
I had this same problem.....unloaded both the Y! music engine and WB. Added the Y! music engine to the list of excluded programs under WB control panel and restarted both. Also if you have the enhanced dialog box program installed add the music engine to the exclusion list also.

Now they work fine. I must say that for a beta program....it is doing just fine. Understand that Yahoo can't anticapte every possible program glitch before releasing it.
on May 24, 2005
I had the same problem. I contacted Y! Music through general feedback. I received an e-mail reply that they were referring this problem to the techs responsible for this part of the program and they would be looking into it further.
on May 25, 2005
Yup, I had the same problem -- I simply added Y! music engine to the exclusion list for Windowblinds. It works fine for now. I'm sure a revision is coming that will allow WB to skin the generic interface.
on Nov 21, 2005
In case no one has responded to this yet, someone showed me the workaround for this in Windowblinds: there's an "exceptions" link somewhere in the ap on the left side. You navigate to Yahoo folder, YME and set up the exception so it doesn't try to skin YME. Problem solved.
on Nov 21, 2005
You should find this is resolved in WB 4.6 and later anyway.