Don't belittle me. The problem is not my computing methods. WindowBlinds WORKS on my system, no matter how hacked it may be. The problem is Impulse, a proprietary software installation platform designed to battle the foe known as PIRACY. One look at these forums shows just how "well" Impulse works. I'll bet money that I'm not the only one here who wishes Impulse had never been implemented...
Sorry bud, you're misreading my post. I patched (hacked) my theme files PRIOR to installing WB via Impulse, and all worked fine. The theme files were NOT the issue. The problem is the crap software called Impulse. If Stardock would just distribute proper installers like everybody else, then all would be well in the world...
Oh, suddenly the problem is moot? I really don't feel that anything has been solved here...
OK here we go! 1. Formatted my system drive. 2. Re-installed Windows. 3. Patched my theme files. 4. Installed Impulse, installed WindowBlinds, all is well. [e digicons];P[/e]
I'd like to point put that WB runs jus fine with patched theme files. As such, IF my theme files are the problem (which indoubt since Impulse still won't update after unpatchingg them), then Impulse is actively creating a problem in anticipation of an imaginary conflict which in fact does not exist, much like WB's treatment of dopus.exe to "fix" other imaginary problems...
Oh good grief. I told you, there is no hack. I manually swapped patched system files. After I reformat tonight I'll patch my theme files before I install Impulse and see how it goes :)
I'm not uninstalling Impulse! I had to reinstall Windows to install it in the first place! I'm heading for work now, no time to run chkdsk on my 4.5 TBs of hard drives. Anyway, this is obviously a software issue... I'll probably just end up formatting my system drive and starting with a fresh install of Windows. I installed a new motherboard last week so I should probably do that anyway...
Unsanctioned, but in my experience, far more reliable than the alternative [e digicons]:grin:[/e] Anyway, as I said, the original files have been replaced, but Impulse still whines...
No luck. After Impulse downloads and extracts the update, a command window pops up briefly - I can't see what it's trying to do. That's when the error comes up about Impulse updating. --- OK I just downloaded and ran the Impulse installer which worked fine, so now I have the latest version running. But I am now back to the exact same problems I had to begin with. I try to update WB, and I'm told "You must allow Impulse to run as Administrato
I restored the originals, Impulse still won't update. Not surprised, hacked theme files don't have much to do with admin rights... I'll run SFC and see what happens, but it didn't work before, so I don't have high hopes. Anyway I wouldn't call it crap. There are dozens of professional quality Visual Styles out there for Windows 7 that I enjoy, but there is only one WB skin that I have found that I like (well enough to buy WB in fact
Windows 7 Home Premium N x64. Unrestricted Admin account, UAC off. Tried with ESET Smart Security off, but results were the same. My initial problem involved not being able to install Impulse due to errors about not having admin rights. I sent in logs [#QME-952273] but they didn't help at all. As per my conversations with support [#ZQY-681319], I tried CleanImpulse.exe, I tried sfc /scannow, I tried running a repair install
I'm running the entire ESET Smart Security suite. Nothing unusual. I tried support the first time around. They were not particularly helpful. I kept getting bounced around between different agents who all told me to try things I had already tried. It wasn't much fun...
Start Impulse. Update found, logging in, downloading, extracting... ERROR! "There was a problem while Impulse was auto-updating, please try again. Updating/installing of applications will be unavailable until you restart Impulse." Click OK "Administrator privileges required for update." UAC is OFF. Can't update Fences. Can't update WindowBlinds. Can't do anything at all. I remember I had
So... Are we any closer to understanding why WB continues to target dopus.exe and what can be done about getting our favorite file manager off of WB's internal blacklist?
I don't think it has anything to do with the image size. I've used dozens of different Visual Styles, many with very slim titlebars, and none have ever presented a problem. Only select WindowBlinds skins cause the glitch. EDIT If I tell WB not to skin titlebars for dopus.exe then the toolbar displays just fine [e digicons]
[quote who="Jafo" reply="11" id="2946898"]Why on earth are you renaming notepad.exe as dopus.exe? [/quote] To prove a point. WB is intentionally and unnecessarily messing with the open dialog called by any executable named dopus.exe. Dopus doesn't skin this dialog at all, it just calls on Windows to open the default one. But for some reason WB messes with it when it does. This really has nothing to do with DOpus' ability to "replace" explorer...
DOpus doesn't skin the open dialog though. It's being actively targeted and messed with by WB! Grab notepad.exe, make a copy, rename it dopus.exe, then hit CTRL-O. Unacceptable.
I have been talking with folks over at Directory Opus about this. It seems that if you rename ANY app to dopus.exe, WindowBlinds suddenly fails to skin the Open dialog properly. Can anyone explain this?
Do you understand why it's happening? Maybe if I could approach GPSoftware with a little more information about the issue, we could get it fixed on their end. It's strange to me that certain skins display fine, but others do not...
Hi all, I'm having an issue with WindowBlinds and Directory Opus. When the Opus window is maximized, the uppermost toolbar/menu gets a little buggy. The top portion of the toolbar gets dropped to about fifty percent transparency. If the Opus window is not maximized, the top toolbar displays fine. This only happens with certain skins, like 7 Zone which I'm using now. Is there an easy fix for this issue? I tried approaching the problem through the Directory Opus