Why do the new versions of IP crash on my computer?
Tuesday, June 7, 2005 by Brock Beesley | Discussion: IconPackager
I'm a little frustrated. The last 4 versions of IP to be released (we're now on 3.00a[b].003) have all crashed on my comp. I open up the program and it immediately crashes. I've ended up having to uncheck the "show pre-release versions", uninstall Icon Packager and then re-install the old 2.50h.087 version. Does anyone else have this problem and how can it be fixed? For the split second that the new betas are open, the changes in the program look SWEEET! I just want to be able to use it.
 |
|
Page 3 of 3 | |
|
|---|
vascoma
Reply #42 Thursday, June 30, 2005 5:40 AM
Reply #42 Thursday, June 30, 2005 5:40 AM
Same problem here: IP breaks help&support and some other system applications. Took me about two days of testing and a complete reinstall of windows before I found out which program was responsible for this... 
Chasbo
Reply #43 Thursday, June 30, 2005 9:38 AM
Reply #43 Thursday, June 30, 2005 9:38 AM
Citizen Casalla - Just so I understand, are you saying that after two days of testing you found out that it was IP messsing up the system or you know what other program is messing with IP. If it is the later would you be willing to share your knowledge? What program is messing up IP3? All I have gotten from Stardock help & support so far is uninstall - reboot - reinstall. This was done before I even contacted them. In the real world if I bought a product that didn't work I could go back to the store and exchange it or get my money back. This doesn't seem to be going down like that. I realize that this is software and there are other issues involved, it's not like returning a flashlight but at the same time when you purchase something you expect it to work. There is nothing on the IP page that mentions that there will problems if you are running McAfee or whatever. According to the requirements listed on the IP page my system should be fine for IP but right now it isn't and so far I'm not getting satisfaction as far as getting this fixed. It is rather disapointing because I have been very happy with WB-DX3 etc. I've been very happy with Stardock. I hope they can come up with a solution, soon.
Corky_O
Reply #44 Thursday, June 30, 2005 10:24 AM
Reply #44 Thursday, June 30, 2005 10:24 AM
One way to troubleshoot IconPackager program conflicts is to:
Deselect any options to run at start-up in Stardock programs (including widgets) > unload all Stardock programs > return Windows to the default theme including all icons > uninstall all Stardock programs > reboot computer > delete the IconPackager sub-directory in "\Program Files\Stardock" (or "\Program Files\Stardock\Object Desktop") folder > then install IconPackager only, and reboot computer.
Download a recent package from WC by right-clicking the download link > Save target as.. > select "All files" in the "Save as Type:" drop-down list > save to My Documents > double-click the downloaded file to invoke IconPackager > click "Apply".
Start any programs that displayed problems with IconPackager previously installed to test functionality.
If all is well, reboot computer and repeat tests.
If all is still well, install the other Stardock programs one at a time, testing between each install.
Here is a link to the zapper utility which is designed to uninstall many of the Stardock programs by double-clicking after download and using the "uninstall" tab to select programs you want to remove Link
Note - you may want to save any downloaded "skin/theme/image" files to a temporary folder which will allow you to replace them after re-installing the programs.
BTW - I run IconPackager, WindowBlinds, and ObjectDock Plus all the time without issue on XP Pro (SP2), including Norton Internet Security Pro 2003.
I hope this helps you narrow the issue down.
Deselect any options to run at start-up in Stardock programs (including widgets) > unload all Stardock programs > return Windows to the default theme including all icons > uninstall all Stardock programs > reboot computer > delete the IconPackager sub-directory in "\Program Files\Stardock" (or "\Program Files\Stardock\Object Desktop") folder > then install IconPackager only, and reboot computer.
Download a recent package from WC by right-clicking the download link > Save target as.. > select "All files" in the "Save as Type:" drop-down list > save to My Documents > double-click the downloaded file to invoke IconPackager > click "Apply".
Start any programs that displayed problems with IconPackager previously installed to test functionality.
If all is well, reboot computer and repeat tests.
If all is still well, install the other Stardock programs one at a time, testing between each install.
Here is a link to the zapper utility which is designed to uninstall many of the Stardock programs by double-clicking after download and using the "uninstall" tab to select programs you want to remove Link
Note - you may want to save any downloaded "skin/theme/image" files to a temporary folder which will allow you to replace them after re-installing the programs.
BTW - I run IconPackager, WindowBlinds, and ObjectDock Plus all the time without issue on XP Pro (SP2), including Norton Internet Security Pro 2003.
I hope this helps you narrow the issue down.
vascoma
Reply #45 Thursday, June 30, 2005 10:33 AM
Reply #45 Thursday, June 30, 2005 10:33 AM
Chasbo,
what I meant was that Icon Packager was messing up the system. I only found out in the end by manually creating restore points before installing each program on the new system. The problems appeared only after installing IP over Stardock Central and was gone again after switching back to the last restore point. So unfortunately I don't have any solution but I do hope that they will fix it soon because it seems to be quite a severe "low-level" problem...
what I meant was that Icon Packager was messing up the system. I only found out in the end by manually creating restore points before installing each program on the new system. The problems appeared only after installing IP over Stardock Central and was gone again after switching back to the last restore point. So unfortunately I don't have any solution but I do hope that they will fix it soon because it seems to be quite a severe "low-level" problem...
lynnyf
Reply #46 Thursday, June 30, 2005 10:41 AM
Reply #46 Thursday, June 30, 2005 10:41 AM
I have also been having problems with MaAfee since I installed IP3. I upgraded my McAfee (it was due to expire in a month anyway) and I am still having problems. For example, I can't open the McAfee Security Center using the icon in the lower left of the task bar. In fact I can't open any of my Mcafee programs.
Anyone have any suggestions (besides using a different security system)?
Anyone have any suggestions (besides using a different security system)?
Chasbo
Reply #47 Thursday, June 30, 2005 10:45 AM
Reply #47 Thursday, June 30, 2005 10:45 AM
Thank you Corky O and Casalla.
Corky O - I will do as you say when I get the time. On one hand it seems like a lot to go through but on the other.....ya gotta do what ya gotta do. I hope it works.
Casalla - Thank the Lord for restore points!
Corky O - I will do as you say when I get the time. On one hand it seems like a lot to go through but on the other.....ya gotta do what ya gotta do. I hope it works.
Casalla - Thank the Lord for restore points!
dScans
Reply #48 Thursday, June 30, 2005 11:26 AM
Reply #48 Thursday, June 30, 2005 11:26 AM
My system is an AMD64 3500+ running WinXp Pro SP2 with 1 GB of memory. I'm running Kerio Personal Firewall and using Avast antivirus. I was running Windowblinds downloaded via Stardock with no problems. Only when I install Iconpackager the problem starts. Like many others in the forums, it took me some time to figure this out. The first time I went whole hog and downloaded everything in Objectdesk 
Luckily I did a Ghost backup before I installed Stardock because I learnt the hard way that restore points in XP does not always work, especially for complicated installs
Luckily I did a Ghost backup before I installed Stardock because I learnt the hard way that restore points in XP does not always work, especially for complicated installs
Katrinakat
Reply #49 Thursday, June 30, 2005 4:58 PM
Reply #49 Thursday, June 30, 2005 4:58 PM
Is someone still working on a fix for this issue? I've followed most of the advice I was given previously, and eventually have been able to use IP partially, but I've had many of the problems mentioned here, including losing Windows Help and one of my graphics programs. This was solved for me by using System Restore, but though I can now change icons in most cases, the program still seems to shut down prematurely. I downloaded the "Smart Exception" program and have sent several logs to Stardock. I hope this can be fixed, because it (IP) is really an excellent program.
dScans
Reply #50 Thursday, June 30, 2005 8:04 PM
Amen to that! IconPackager and Windowblinds go together!
Reply #50 Thursday, June 30, 2005 8:04 PM
| I hope this can be fixed, because it (IP) is really an excellent program. |
Amen to that! IconPackager and Windowblinds go together!
dScans
Reply #51 Monday, July 4, 2005 3:03 AM
Reply #51 Monday, July 4, 2005 3:03 AM
Hi all,
For those who tried to uninstall IconPackager and their system still do not work properly, I found this tip in the Object Desktop forum. Apparently, you have to remove this service before uninstallation. Access the command prompt, and type in the following "regsvr32 /u iprepair.dll" (do not type in the quotes
)
This should save some time from restoring from a backup
For those who tried to uninstall IconPackager and their system still do not work properly, I found this tip in the Object Desktop forum. Apparently, you have to remove this service before uninstallation. Access the command prompt, and type in the following "regsvr32 /u iprepair.dll" (do not type in the quotes
)This should save some time from restoring from a backup
Scarborough
Reply #52 Monday, July 4, 2005 3:51 AM
Reply #52 Monday, July 4, 2005 3:51 AM
Thanks for the post Mr Beesley. Deleting Bluecurve worked - Way to go Cafeend. It raises questions about quality control. This issue had been bugging me for some time. I sent an email to Stardock Support on 05/06/05 exactly describing the problem as stated here. Recieved an automated reply immediately but nothing since. Raises questions about...
Carl Sawyer
Reply #53 Tuesday, July 12, 2005 8:15 PM
Reply #53 Tuesday, July 12, 2005 8:15 PM
I had similar problems with IP and e-mailed Stardock on 6/28/2005 and still have not received a reply (other than the automated reply). I have seen numerous posts about this issue and nothing from Stardock.
Please login to comment and/or vote for this skin.
Welcome Guest! Please take the time to register with us.
There are many great features available to you once you register, including:
- Richer content, access to many features that are disabled for guests like commenting on the forums and downloading skins.
- Access to a great community, with a massive database of many, many areas of interest.
- Access to contests & subscription offers like exclusive emails.
- It's simple, and FREE!
|
|
Page 3 of 3 | |
|
|---|
Reply #41 Wednesday, June 29, 2005 2:43 PM