I've just gone through the procedure yet again.. When preparing I disabled (as I usually do when installing Stardock apps, but shouldn't be necessary) Outpost Firewall Pro and NOD32. Not only that, I stopped everything related to them, disabled all services related, and finally used msconfig to disable their gui part to start (i.e it is as disabled it is possible to achieve without uninstalling the applications themselves). The result? No dice, not even remotely pos
myarmor
@Cplair, you're correct about that.. Unless the activation itself is bad, as this one apparently is. No doubt this application has been activation hell until now at least (IP4, and it isn't possible to install the properly working 3.99 though Impulse).. I'll give this procedure yet another shot, however I'm doubtful it has any effect.
@Cplair, did you manage to get all THREE IP apps to work with that procedure (I have some doubts)? I've managed to get IP and IPE working with some assistance from travis, but the last item on the list still has the activation issue as mentioned before. IP consists of three (not two) applications, Icon Packager, Icon Explorer AND the shell extension providing the "Icon" tab on every file.
[quote]This issue is fixed!What some of you may have to do is to first uninstall Icon Packager with Impulse, and to be safe, reboot your system. After reboot relaunch Impulse and then reinstall Icon Packager. Icon Packager and Icon Explorer should now be working without having to activate it!If for some reason you can't uninstall from Impulse, then try to uninstall from SDC. But reinstall Icon Packager from Impulse!!This worked for me and all of my packages are still here.Good Luck to you all
Thankfully I'm covered until 2010.. This way I'll save the first $20. Renewals before the price increase did cost $19.95 for a 2 year subscription, so it really is a $20 (or 100%) price increase. Fair enough really.. If you don't like it, just don't renew. @Zoomba, you'll get enough to have twice as many now :)
[quote]I'm still getting the same "can't find activate.exe" errorSame here.But I didn't need to put a serial number in after the first startup after upgrade. So that's a plus.[/quote] If you can start the IP main application without activating, but you get a can't find activate.exe when trying to change a icon with the Icon tab, then you have the same as me. Shell extension tries to run activate from the wrong place, but you can copy IP's activate.* to that location. I
[quote]SDC did not get the update yet as far as I understood. Please check the last set of numbers on your version. If it is 163 then you still need to update. If you like I can send you a stand alone link that will still require activation.[/quote] @Seabass, It was on SDC, according to my first ticket reply referring to .165 (CYT-199472), earlier than 02:38 PM (I guess it's in your timezone as I got the time from the ticket in esupport.stardock.com, but I can't say for sure).
I'm not able to get activate to work yet. Apparently it is due to the three (ip, ipe, and shell extension) of them overwriting eachothers activation. Shell extension is the one trying to start a nonexisting activate.exe in all users\...\iconpackager. To those of you that had success activating IP. Did you try starting IP, IPE and the shell extension (to test the latter rightclick a file, change the icon for the filetype via the 'Icon' tab then click Apply), one by one, twice
I'm still having the issues with activation with 4.0.165 and I thought I'd give you a small update. IP and IPE overwrites eachothers activation, and the shell extension seems to belong to the IPE part of this, the reason of this assumption is below. I had the IconPackage program perfectly activated, i.e it worked without asking for activation (as long as I don't run IPE). Using the 'Icon' tab to change a icon showed a "can't execute 'C:\Documents and Settings\All Users\
[quote]What happens when you go into the Icon Packager directory, right click on Icon Explorer > Run as Admin. Then do the activation normally through that box?Edit addon: If that doesn't do the trick can you run through a manual activation process then send me the long activation string so I can try it from this end manually? You can just PM them to me here.If you haven't already seen this here are the online instructions:https://www.stardock.helpserve.com/index.php?_m=knowledgebase&_a=viewarti
[quote]If you do run into the error 6 activation error please simply contact support. A rep can then look at your account, verifiy that the serial number is not shared or compromised and reset you. It's pretty easy and we are happy to do it for you. Please let us know at [email protected] you have any further issues or questions please let me know.[/quote] This is at least good news :) I've just sent a request due to my problems activating IP4 as mentioned earlier in this
@Bichur, it is not a separate application, you're correct about that, it is one of two related applications IP installs (IconPackager and Icon Explorer). If he uses IP4, then this would be related to the activation issues with IP which I too suffer from. No form of activation of it has been successful for me other than one lasting one session (i.e until some part of IP is unloaded from memory).
milksama, jkuemel, I just wanted to let you know that I've got the issue with ID's aboutbox fixed (it only required a pure install of XP (with SP3 slipstreamed). I'm sorry I haven't mentioned it earlier (I forgot about the forums), although I tried for several days to respond to you via email without success. It always ended up in your spamfilter according to the autoreply, this happened no matter what, even when I replied to milksama's message with a quote and
[quote]How long before you get locked out for trying to activate.[/quote] Can this happen?? Then this problem is serious in more ways than making the software totally unusable.. I've just tried the procedure regarding SDC and IP 4 refered by Zubaz (quoted from Panic Button), still no dice (as expected), so I had to restore image yet again.. It gets rather tiresome. I've got lots of anger and frustration to display over this, but I'm keeping it to myself.. Use your i
[quote]This update corrects multiple bugs as well as the activation issue that many people were experiencing. If you are able to please update to this version of the software.[/quote] This seems rather funny.. It is 4.0.163 that causes the activation issues, at least in my case. I don't dare to install IP now, I guess I'll wait and see. Continously restoring disk images is too timeconsuming. I've had bad experiences with both Impulse and IconPackager today (Restored a disk
I meant confirmed to the activation issue.
[quote]May 14, 2008 21:03:09 New IP v4.00.159 not skinned drivers iconOS XP service pack3Same problem with build 4.00.160 under Windows XP SP3 32-bits > CD-rom iconEdit: Unable to reproduce this problem with build 4.00.160 under Windows Vista SP1 32-bits except for 'Network Location' icon and 'Zip drive' icon.Not fixed under Windows XP SP3 and latest build > 4.00.163.+ problematic activation process under XP.Edit: Ticket > KIW-930507[/quote] Confirmed.. How many times do I
[quote]I don't have the same problem you're having with the About box at all. I can see the app name, version number, copyright, etc. As far as the menu, the reason why it doesn't skin is because it's using a .NET Framework menu instead of a Win32 one that would be skinnable. The reason why a Win32 one isn't being used is because it caused other, more annoying graphical glitches.[/quote] This is a bit strange.. My aboutbox is completely empty except for the background and the top logo (
I ended up testing Skinstudio 6 beta (I don't like betas in general, except when they has almost zero chance of doing wrong, such as Everest Ultimate betas), and found the reason why it displayed the menubar blue. The "Menu Bar" color was the reason, I don't think it was changeable with SKS v5, and for some reason ID wanted it, but nothing else. I can't see why ID wont use the skin images for the menubar as everything else does (Use flat menus is disabled).
Oh.. Normally I use my computer with the Themes service disabled. I tried enabling it, then set the XP style. This displayed the menubar properly. XP Charcoal style displayed the blue menubar backuground in ID no matter what (ID is the only app displaying it). I then tried Dragon (Stardock Design), which displayed it properly again. I wish there was a reliable SkinStudio 6 to upgrade the skin (it was designed for v5 I think). I guess ID is incompatible wit
No change for mainmenubar or aboutbox, exept reminding more about the ugly original xp. No idea where it gets the silly blue color (#0000D3) from.
Of course.. not thar it says it needs to.. but I've rebooted several times. I also tried to clear the entire windows\prefetch folder, stop FW and AV, etc before running ID, but no luck. I also tried excluding it from Windowblinds skinning. No luck. I use Windows XP SP2 32bit, fully updated. Installed Stardock apps at the time of testing: Stardock Central 2.52.516.165 WindowBlinds 6.02.042 IconDeveloper 2.0.030 IconPackager 3.20.128 IconX 1.11.008<br/
After updating to the newest version of IconDeveloper it has taken a seriously strange look. The menubar is blue stock color, and looks seriously out of place. The aboutbox doesn't contain a single character of text (just the IconDeveloper logo), while my previous version (1.30.28) contained plenty. Anyone else experiencing this?
Hello.. Is CursorFX vista only, or is it the successor to CursorXP on both platforms? I ask because this is not shown anywhere in SD, not even Misc, whether pre-release versions is enabled or not. I use SD 2.51.513, build: 164 (the newest I guess). Btw, no updates to anything in the Misc category has been done since 12/13/2005 according to SD (i.e everything since Apogee Icons in the 'Demo' section are missing, such as Essorant 2,Utopia Icons etc). I can see Cursor
The somewhat BIG difference is that it WAS a reason or ten to upgrade to XP, with Vista there's none.. except for the DirectX10 tease. Oh, yeah, mustn't forget, you really gotta have all the DRM stuff (no need to be in charge of what happens on your computer anymore)... NOT! On top of that, there's just about 2 years until "7" should be released (apparently).. So Vista will never be as stable as XP before it's time to move on..