Iconpacker download through Stardock Central Issue

Iconpacker program download issue

from Stardock Forums
I had to reinstall icon packer again after a harddrive wipe. While downloading iconpacker through the stardock central I got an error message near the end. At the point where it was applying install actions. The error was "Application path not found. Please run the application setup again to correct this problem". I clicked ok and it finishes, activates the product & then says successfully installed?
It then says, do you want to run the application?
I assumed from the error message it wanted me to uninstall & try reinstalling. I did this three times with the same error message each time & then it successfully finishes. IT seems to me a kind of contradiction. Please run the application setup again/ Sucessfully installed? Was it successful & if so, why the error in to run the application again?
I am afraid to just leave it in my computer like that. I do not want to have to reinstall windows again down the road because of it.

There is also a couple of icon packs below the iconpacker program in Stardock Central. When I download them, they go to progams/stardock/object desktop, while others go to documents & settings/all users/shared documents/stardock. The ones in program folder do not show up in icon packer.

Rick
iconpackager
5,307 views 4 replies
Reply #1 from WinCustomize Forums Top
I can't really give you solid answers but I think I can turn the wheel a little bit, someone else can quite likely come along and elaborate. It also might matter which version of XP or Vista you're using.

On XP I just updated Iconpackager from version 3.20.128 to 3.20a[rc].033 which is what's out there today and what you likely installed. During that update it moved my icon packs from the Programs directory into the All Users directory - I suspect that since you were installing the new version from scratch the "Application path not found" error was the result of the installation looking for the icon packs in the Programs directory to move them and not finding any.

Also, quite likely that the additional icon packs still assume they need to go into the Programs directory and go there. I already had them installed and didn't delete them / re-install them to check, but that's what it sounds like. I would imagine that you can just move them up with the others and they'll show in Icon Packager and be fine.

Your comfort level with the installation is of course up to you. Knowing that the installation might very well have been trying to move icon packages that didn't exist might give you a little additional insight into the error messages though. Given all that, if it were me and Icon Packager appeared to be working fine while applying and changing themes, I'd move the misplaced themes up with the others, and carry on. Admittedly though I'm not the safest guy around.
Reply #2 from Stardock Forums Top
Thank you DaveRI, I really appreciate your insight on this & you are probably correct.

Mike from Stardock sent me an email on this & wanted the the ip.log file located within the C:\Program Files\Stardock\SDCentral\Installed directory

There was no folder called Installed directory in this SDCentral Folder. Nor was there an ip.log anywhere in the Stardock/SDCentral Folder.

I also noticed in start/all programs then highlighting Stardock/ObjectDesktop I could access & open windowblinds, iconpacker. Cursor xp was in start/programs/stardock & not in Object desktop. Iconpacker & Cursor XP Plus were also listed individually in the start/programs menu, further down? Why would Stardock Central put Iconpacker & cursor xp in two different places in the start menu? Windowblinds was only listed the one time in stardock/ObjectDesktop.

Should I download a earlier version of stardock central? Should I turn off show pre-releases?
Thank you

Rick
CursorFX - Customize your Windows cursor
Reply #3 from WinCustomize Forums Top
If you have a dialogue going with Mike, by all means pursue that direction. I'll be exiting soon as I don't want to confuse the issue.


Mike from Stardock sent me an email on this & wanted the the ip.log file located within the C:\Program Files\Stardock\SDCentral\Installed directory

There was no folder called Installed directory in this SDCentral Folder. Nor was there an ip.log anywhere in the Stardock/SDCentral Folder.
End of quote


A little clarification on this - I believe the file Mike asking you for is

C:\Program Files\Stardock\SDCentral\Installed\ip.log

Reading your post I'm not sure if you thought you were looking for a directory called "Installed Directory", which it is not, it is simply "Installed" as I've indicated above.

Regarding the locations within the Start Menu - I've moved my stuff around so much I can't even tell you where it went originally. By the way, I don't particularly recommend moving them around, especially for you right now, as moving them around only adds to the confusion later when updating or installing new programs. I do recall however that not everything gets put under the same catagory and I'm pretty sure that at least CurserXP was one that strayed.

I'm sure Mike will get you sorted out. For that matter you might not REALLY even have any issue, particularly if the "Installed" vs "Installed Directory" turns out to just be a communication issue. At this point I wouldn't download an earlier version of Stardock Central, or turn off pre-releases, or for that matter change anything within it at all. It will likely be much easier for both you and Mike if you don't change things right now while you're working on it unless he asks you to, and you might end up breaking something that isn't already broken or otherwise making matters worse. Again, it seems like you may already be fine.

And with that I'll leave it to the pro's.  :) 

Reply #4 from Stardock Forums Top
just wanted to mention that i'm experiencing the same "Application path not found. Please run the application setup again to correct this problem" problem. iconpackager though seems to be running without any problems, so no big problem here.

but nevertheless, i'd prefer an installation without receiving error messages ;)