@Almonty, you managed to update to WB6.2 using XP? I'm running XP Pro SP3 fully updated and somehow it forgets to add the wbsrv.dll to my installation. Has this been fixed now or? I ask because three times of reimaging the drive is enough in trying to get it to work properly.. Maybe I'll try a clean install later if I'm in the mood. However, sometimes this can create more havoc than just trying to update.
myarmor
I'm currently retrying (this means redownloading as Download & Archive doesn't exist for a installed product), this time with all security software uninstalled, ccleaned, etc. Btw, the messagebox after running 'Verify' should at least allow redownloading or whatever.. not just pointing to a update that doesn't exist (look for a update/patch said in a generic way).. I've never experienced such issues at all with WB4, 5, or 6 until this time around, come to think of it, before I
Back to 6.10.. Thankfully I had an image to go back to.. Imaging software seriously pays off..
I shut down all security software (Outpost Firewall Pro 2009, disabled NOD32 3.0.669) and tried to update from 6.10 via Impulse. Result: WB displayed a message about disable security software and reboot (which resulted in the same), eventually reinstall. Question: How much more disabled can they be? I even disabled OPF's services. And where is the option to reinstall an installed product (not on the rightclick menu, I've checked)? This is starting to remind me abou
I wouldn't mind an update myself.. Thanks
@hallv5, yes when you activate the shell extension (as you described) it will stay activated... ..until you activate IP or IPE (one or both of those will demand activation). As someone described it.. It's the battle of activations.. My support issue regarding this has a 2 month anniversary in a few days. They have tried, but so far everything has failed.
Ord3s, rightclick on a product, then select reactivate to do just that, even for IP4. The big activation issue is that activation of IP4 doesn't activate all parts of the product. In my case I use a batch file to swap two sig.bin's (one for the shell extension and one for the rest) to still be able to use the full product, although not at the same time.
This issue has existed since the release of IP4, and the thing that surprises me the most is that the issue still exists at all. In my case I reported it 20 may, still have the issue, and in 14 days it's my 2 month anniversary with it.
With wasn't touched I mean it still has the mid May as its creation date both in the downloaded Impulse archive and installed. Btw, it might be an idea to show some progress while extracting an archive.. Currently you're transferred to the download/install page which contains nothing for a while (a very long time if it's a game) until something happens and it suddenly is displayed on that page as Installing etc.
The activation issue is still present.. Initially Impulse creates a sig.bin causing IconPackager and IconExplorer to be activated... But there seems to be one difference.. With the shell extension mentioned so many times.. Copying the activate.* to the folder it expects it to be (yes it still expects activate to be another place than it is), then retry results in a sig.bin for the shell extension only, no longer creates a sig.bin activating both it and the Icon Explorer, in
Is there any news about the activation issue (i.e not able to have all three parts of IP activated at the same time, as reported in this thread and in support ticket)? 21 june is the 1 month anniversary on my computer for this one.
And it really started with .164
@Bebi, it wasn't intended to.. Seabass mentioned this when it was released. Hopefully a fix for this issue is released soon.
[quote]Serenity my friend Its not perfect software.. but its damn good and being worked on constantly.[/quote] Sorry for the tone, I'm just a bit disappointed in myself for not discovering the 'hack' earlier :) I agree with you, it is good sw.. :) However, it seems to have some issues here and there which seems strange (such as this one). I'm still a bit puzzled about how it really is intended you should do the Disabled state. So far it seems it is int
The only "extra setting" for a menuitem is "OS Menu Height", nothing related to the disabled state.
Thank you for the hints.. Apparently the only way to do the same in SKS6 is to go into the codee editor and type: FlatDisabled=1 I found that in the Molten skin, and it works. This raises the question, how is it intended that you should do this properly instead of using this hack? (I call it hack because the code editor isn't visible by default, and there's apparently no corresponding option anywhere). In addition, what is the purpose of the Disabl
Oh, and while you're in IconPackager, try to change package. All the points above will trigger a activationcheck, and if it doesn't pass it shows the activate screen (or a error referring to not being able to run activate). If this happens then you are the proud owner of the activation issue. :p
@hallv5, perhaps you didn't really have it solved in the first place. I don't know, I've struggled with this issue for a long long time. To be able to say you don't have the activation issue at all you should be able to do all points below in sequence TWICE (or more). It should NOT show any activation/error screen for any of the applications. 1. Run IconPackager, then exit 2. Run Icon Explorer, then exit 3. In windows explorer, rightclick a file, select properties,
[quote]I updated to IP 4.00.165 the other day, and am now getting the activation request too.Since I'm a OD Ultimate user I have no "standalone" registration. [/quote] In the activation box you use the mailaddress and ODU serial you were given. If you have the same issue as me you'd be able to activate IP and IPE, but the next time you use the "Icon" tab on a file you'll get either a "could not run activate.exe", or a request to activate. If/when you do this the IP
Oh, and btw, the menu with the wrong disabled color in the picture is from Windows Explorer. So far in the experiments trying to resolve this annoying behaviour it seems the Disabled state of a Menuitem isn't used for the disabled state as one would expect, but rather it is used when the WINDOW with the menu isn't focused, and therefore the menuBAR text is dimmed with the color that was set here. This is the state you would expect to be called 'Inactive menubar', not 'D
Hello.. I've noticed that no matter what colors you set Popup menus->Menu item->Text->Disabled state to it is ignored, and instead WB uses the ButtonShadow and ButtonLight system colors. Flat menus is disabled. Is this a bug or is there some hidden setting you can change to enable a skin to support the disabled state properly, including text color? The strange thing is, all the other states are displayed as they should. I've located the actual colors used
Sigh.. I just celebrated the 11 (or 12)th day of activation problems.. :( As I've mentioned before, I manage to get IP partially activated but not fully.. An example and a question.. Example: I activate IP main program, set it to use "localvista" package, then activate IPE+shell extension. What happens to the assigned icons in this case? I've not tried this because IP remains somewhat unusable except for extracting icons and changing icon for a f
Cplair, I'm just happy somebody manages to activate this program fully, although I can't see how. :) Apparently it isn't intended to do so on my computer.. I run a standard WXP Pro SP3 slipstreamed + IE7 install (not even nlited) Until IP4 came along I've never ever had any issues with activation, and I still don't, except with IP4.
@Cplair, as I mentioned in #36 I just did this (I've done this a number of times since installing Impulse, not to mention I did a similar thing when running SDC) yet again. I'm seriously frustrated with this..