myarmor

Why isn't there a "revert to default" button somewhere? If I install and apply one skin, then does the same with a second and a third, somehow the result is a combination of the three. It is seriously annoying as currently it's almost needed to reimage the drive between skins to get rid of the garbage inbetween. For instance, the image below shows a thingy left by either the Azul3D or the Dark Knight skin which for now seems to require an image restore to remove. (ap

Bebi, cure one thing and everything activation related would appear to be fixed (and apparently is). If everything has the correct activation, no attempt to run activate.exe will happen from the shell extension, IP or IPE, so no error dialog will show.. :)

Christolia, I guess it might only be available in Impulse as it is the primary delivery vehicle for the products, although SDC isn't abandoned. As I've mentioned before this is a beta, so it should be treated as such.. If you're not familiar with the term, read http://en.wikipedia.org/wiki/Software_release_life_cycle

I asked specifically about repeatedly running each part of IP when I asked for confirmation.. (sorry for the extra post, it's not possible to edit as I'm posting from my phone with no visible edit button on the page)

@pictoratus, I was a bit hesitant myself when it was mentioned in the thread "activation keeps coming up..." that Goose40 got rid of this issue after installing the beta. After asking for confirmation and receiving it from Goose40 I decided to try (making sure I had a new backup image before continuing), and, well it seems to have squashed my problems with activation (battle of activations etc) which is somewhat well documented in these forums. As it is a beta, the only thing yo

Btw, I guess I should update this thread too.. IP4 4.09b cured all my issues with activation it seems.. :) I can run all parts of IP4 in sequence as many times as I want to without any of them nagging for activation. To be sure the beta contained activation I renamed the sig.bin and they asked for activation when they should (I only tested one or two of the parts this way).

@Seabass, yes it was very nice to have something that works :) If it stays that way there's no need bothering with locating the missing tickets, although I hope something has been done to avoid deleting active escalated tickets again. And whatever you do (and I seriously hope you currently don't), don't run antispam software on tickets that have been replied to by your own staff (you suggested this could've happened, but I hope you meant only replies sent by email only, and not

@Goose40, thank you.. I guess I'm going to try the beta then :) Hopefully without any extra issues. However, I do see some complains that the 09 in some cases may cause explorer to crash and crash (hopefully I avoid this issue, I have a backup image just in case). Hopefully I can confirm the working activations as this has been my persistent issue with IP4 since the date it was released.

@Seabass, I appreciate you taking the time to attempt to help me.. Sounds like you either found it or you found the original (pre mergeattempt ticket). Answered. I hear some rumours that the newest beta has a fix for the battle of activations that works.. Can this be confirmed by you or anyone? I'm a bit reluctant to install beta's on this computer as I prefer my own programs to be the only ones with beta status, but I will if it cures this problem without introducing too much new b

I'm looking for confirmation before even attempting installing the beta so I can save myself the eventual trouble needlessly..

Still no replies anywhere regarding the lost tickets (especially one of them regarding IP), just a single one on Aug 6 stating that the tickets I was referring to wasn't there.. which was my point exactly. Btw, the ticket number for my IP case was apparently [color="#8B0000"]CYT-199472[/color] according to [link="https://forums.stardock.com/312892/page/1/#1745512"]this post[/link]

@Goose, so you can run all three IP apps (including changing an icon via Properties->Icon tab and applying) repeatedly without any of them asking for activation at all?

@Seabass, you have a PM.. In this case both I refer to was escalated the last I saw of them, but now they're gone completely missing. By reading some of my last messages on these forums you should get an idea on when the ticket was first started.. I guess it is about 2 months 16 days ago (something along those lines, IP was at .164).. IP was about the activation issue..

@Dazzyl, now try to run IconPackager and IconExplorer.. At least one of them will demand activation, and when you do, the shell extension won't be.

Congratulations Milksama :) I hope you're happy with your new job.

Seabass, thank you for the update. However, a small update of my own.. Now, after I posted 2 tickets over 2 months (2 months, 10 days I think) ago, one for IconPackager and one for Impulse(the former is not fixed, but the latter probably is), they have apparently just deleted the tickets from esupport. My 2 very old (and unrelated) ones that are closed is displayed in the "View Tickets", but not the two I mentioned. I must say I haven't found an update that fixes the IP

Oh, for completeness.. I restored a 6.2 archive when I succeed, not direct install. Sorry for using multiple posts.. I'm writing this on my mobile, and it doesn't display the mess above the edit field correctly..

Strange.. I can't see what other programs might interfere.. The only significant nonStardock software usually running) is StorageCraft ShadowProtect Desktop 3.2, VMWare Workstation 6.0.4 and Everest Ultimate. Most of these is a h*ll to disable completely. :) I tried the complete uninstall approach (in addition to the new Impulse update), with Ccleaner and the lot. Version 6.2 is finally installed successfully! Apparently the new version isn't made for

@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.

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

@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.