Derell Licht

O...M...G... [e digicons]:(O[/e] I didn't even know that setting existed!!!!!!!!!!!!! How in the hells did that get set ?!?! Thank you... nevermind...

Update: Actually, I've just realized that *many* programs are doing this, including Mozilla Thunderbird, Pale Moon browser, and a couple of others... this is not good...

I've been using WindowBlinds on Windows 10 for awhile now, on two other machines. The first machine was a Surface laptop, the second was a desktop machine which had been upgraded from Windows 7 Pro previously. Neither of them exhibited the issue that I'm seeing here... Details on my system: WindowsBlinds 10.84 (059 - Windows 10 Edition) Windows 10 Build 19042 A couple of days ago, I replaced motherboard/cpu/memory/cpu_cooler on my desktop machine, a

[quote who="JimBurd" reply="19" id="3776938"] My biggest problem has been that I'm running Win10 on several VM test machines, and certain skins consume *huge* amounts of CPU or GPU time. The Diamond skin looks (visually) the best to me (and plays well with Open-Shell), but it makes the VM almost unusable due to GPU loading. (This is on 3-year-old hardware, so maybe not an issue on newer machines?) Corporate runs just fine on all the machines, but I really want the look

[quote who="stardock725" reply="17" id="3776915"] I've been using Open-Shell with WindowBlinds on several Windows 10 machines. The only problem I've had so far is that some skins use a *ton* of CPU or GPU resources. None of the skins (Acrylic 7, Corporate, Diamond) have resulted in the Taskbar problems that you've described. [/quote] Really ?!?! That's interesting... Are those all skins which came with WB? Or are some of them user-dev

Is it 5 activations, like WindowBlinds ?? This seems like something I should be able to answer for myself, but I can't find the answer anywhere (product page, Start10 FAQ, nor on these forums).

Yeah, I know... but Classic Shell was free, and highly configurable, and I've loved it for *years* ... Trust Microsoft to break anything that we users actually value...

Okay, this be resolved... dang it... I was using a start-menu replacement program called Open Shell, which is a fork of the older Classic Shell (including Classic Start Menu). I didn't think it was involved with this issue, because it does not affect the taskbar. However, I went ahead and removed it, restarted Windows, and now WindowBlinds is working just fine. New skins load fine, and are remembered across restarts. Damn... I *love* Classic Start Menu, I hate

Well... that was interesting... @almonty - I did that last reboot... no affect on the symptoms. @basj - Okay, I did the cleanboot routine... and got a different result. First, when I logged out after creating the Admin account, then logged back in with that account... Windows came up with the 'Acrylic 7' theme properly loaded !! So far so good... However, once I try to load any other theme, even one of the default themes, then I get a variant of my

Okay, after following all those instructions, I loaded the 'Acrylic 7' theme, and it still behaves the same. Here is a screen capture of the taskbar. hmmm... I don't see any 'attach image' option here, and drag-and-drop does not work... I'll try uploading to Flickr and linking... https://www.flickr.com/photos/derelllicht/49464670752

Interesting point... on 'My Downloads' page, the WB10 installer is listed as "WindowsBlinds 10 Upgrade" ... I wonder if I should first install WB 8, then upgrade to WB 10 ?? For now, though, I will proceed as if the WB10 install is okay.

Okay, running the WBPurge batch file as admin... Got an error message: 'the module ...\WBCore.exe was loaded but the entry-point DLLUnregisterServer was not found' and 'make sure ...\WBCore.exe is a valid DLL or OCX file and then try again.' I got the same errors for another file, but didn't catch the name. It has now completed, and I'm back to normal Windows. Will continue with the instructions!

Hi all; first, I'm not using Object Desktop at all, I'm only using Windowblinds second, you are correct, @basj ! It is XPWood, not WoodXP... oops !! I love *both* of the XPWood skins. Okay, I just loaded another theme, Radio, which is a paid theme and is quite recent. It shows the same problem with taskbar as the others do. In fact, I can provide more details about what is going on at this point: 1. The only element which i

I just installed WB on my new Windows 10 laptop. WB version: 10.8.4 Windows version: build 18362 The machine is a Microsoft Surface Laptop (Core i5) At first installation, it was "sort of" working... some things didn't display correctly, but it was mostly usable. I also copied all my .wba files over from my Windows 7 machine, and tried installing some of my favorite skins, starting with SetiGreen and WoodXP. When I installed SetiGreen, it caus

I don't have ObjectDesktop, only Windowblinds and Groupy. However, I *did* find the page that I was looking for, eventually. It was at: Account -> Images -> Stardock Account -> Downloads, Orders & Billing -> My Downloads -> View Product Keys -> (Manage) and that, finally, gave me the list of registered products!! And I only have 1 current activation, so I'm good to go now!!!

I have a new laptop machine that I'd like to add WB to. I know I can activate on several machines, either 3, or 5??, don't exactly recall... Anyway, I'm still using it on my Win7 machine, and so much love it!! I'm pretty sure I installed it previously on at least one, possibly 2 other machines, both of which were laptops. I uninstalled it on one of the old machines, but did not actually de-activate it... I simply forgot. The machine itself has been recycled.<b

One of the reasons that I'm pursuing this, is that I would like to modify this skin (and some of the others) to support later Windows versions; don't know how much work that's going to be, but there are several that I really like, and would be cool to have updated.

Admittedly, that's an easy answer, which requires no thought. (BTW, I'm on Windows 7, not Windows 10) However, what I'm actually looking for is a fix for the theme, since it is a standard wba file. What could Windowblinds be doing with the theme, that would disable explorer.exe ?? Later: BTW, I loaded the theme into SkinStudio 10, then saved it under a different name, and it *still* prevents explorer.exe from running. &nbsp

Nope, same issue(s) without Classic Shell. BTW, I've tried other early non-taskbar themes, and they *don't* have the Explorer issue; this is only with Alibaba.

I've discussed this concept (using older themes) before, but I'm having a problem now that I haven't had before; I'm hoping someone can help me with it. I'll confess that there are many older themes (pre-WinXP) that I really like. Some beautiful, creative things were done in the early days, which unfortunately were never ported into the modern taskbar world. With most of these themes, the main problem is simply that the taskbar/notification_area don&#39

hmmm... well, in the various other forums where I've used it, over the past decade, it has presented no problems. Anyway, I first tried dropping the image into my post, but it displayed as garbage text instead of an image. I'm glad you were able to make it work.

Okay, I'll try that out, though it doesn't seem to offer the level of control that I enjoy with Windows... I want to set the following (using Windows names): icon - used for desktop icons and labels <span st

While trying other ideas to address my title-bar issues with ConEmu, I added the ConEmu executable to "Per Application" settings. Then, instead of just saying "ignore this application", I selected a different style for it, under "Style to use for this application". It is really beautiful, and seems to solve the title-bar conflicts that I discussed in a previous message. However, this setting seems to cause other problems with certain dialog boxes, including both ConEmu:Setti

Thanks for the response, Neil; I know that you'd prefer that I use Skin Studio to change fonts, rather than the Windows font properties... but the truth is, Skin Studio is a *very* difficult tool to use for this purpose!! The Windows tool is far easier, more intuitive, and I've been using it for years for this purpose (though I know I won't have the option any more, if I'm ever forced to move to Win8 or Win10); that is why I continue to use it. I es

BTW, this issue had previously been discussed by someone else, on the ConEmu support forum: https://github.com/Maximus5/ConEmu/issues/291 The ConEmu author said: "I consider this is a bug of Windowblinds or exact theme. Contact their authors. Weird arguments come into WM_NCCALCSIZE while using that t