Is there a full Un-Installer?
Friday, June 4, 2004 by themusicguy | Discussion: Stardock Software
Is there a full un-installer for DesktopX (trial version)?
I am asking because I have run into a problem that nobody can seem to answer other than to re-install desktopX.
The problem is that whenever I try to load an object (or theme for that matter) with any type of scripting in it, the DesktopX program crashes with the infamous "send error message" window.
After un-installing, shutting down and then re-installing, when DesktopX is re-run, I get that other infamous message "desktopX did not shut down properly, would you like to continue or start from new" (thus telling me that the un-install that came with the program does a very poor job at getting rid of 'residew' from the DesktopX un-install.
So, I am asking if anybody knows of the proper procedure for complete un-install or procedures to do it manually.
I am a little weary of going into the registry and searching for "Stardock" or "DesktopX" to do a manual fix... I actually was curious enough to check that out AFTER the uninstall and there were over 300 entries in the registry.
Please, if anybody knows anything I would be so very thankful since I've been working on my theme for the past month and fell in love with the system. I was almost convinced to buy the program until this happened (and if I knew that the purchas would fix the program 100%, I would take that as a solution).
Thanks,
Bryan
I am asking because I have run into a problem that nobody can seem to answer other than to re-install desktopX.
The problem is that whenever I try to load an object (or theme for that matter) with any type of scripting in it, the DesktopX program crashes with the infamous "send error message" window.
After un-installing, shutting down and then re-installing, when DesktopX is re-run, I get that other infamous message "desktopX did not shut down properly, would you like to continue or start from new" (thus telling me that the un-install that came with the program does a very poor job at getting rid of 'residew' from the DesktopX un-install.
So, I am asking if anybody knows of the proper procedure for complete un-install or procedures to do it manually.
I am a little weary of going into the registry and searching for "Stardock" or "DesktopX" to do a manual fix... I actually was curious enough to check that out AFTER the uninstall and there were over 300 entries in the registry.
Please, if anybody knows anything I would be so very thankful since I've been working on my theme for the past month and fell in love with the system. I was almost convinced to buy the program until this happened (and if I knew that the purchas would fix the program 100%, I would take that as a solution).
Thanks,
Bryan
themusicguy
Reply #2 Friday, June 4, 2004 11:07 AM
Reply #2 Friday, June 4, 2004 11:07 AM
Yes, I actually got rid of ALL stardock folders, even windowsblinds.
I started from scratch, as they say.
Re-installed everything and still the same problem.
Thanks for such a quick reply btw!
Bryan
I started from scratch, as they say.
Re-installed everything and still the same problem.
Thanks for such a quick reply btw!
Bryan
Watson
Reply #3 Friday, June 4, 2004 11:14 AM
Reply #3 Friday, June 4, 2004 11:14 AM
It's no porblem, but if you have uninstalled everything each time, then I'm not really sure what you should do... Have you downloaded the most up to date version(trial or otherwise) of DesktopX?
Shameless Designs
Reply #4 Friday, June 4, 2004 11:50 AM
Reply #4 Friday, June 4, 2004 11:50 AM
You can try this: https://www.stardock.com/files/odnt_zapper.exe It's a small download that should clear out everything related to Stardock Object Desktop.
themusicguy
Reply #5 Friday, June 4, 2004 12:04 PM
Reply #5 Friday, June 4, 2004 12:04 PM
Thanks!
I'll try it out and let you know if it works out!
Much appreciated!
Bryan
I'll try it out and let you know if it works out!
Much appreciated!
Bryan
themusicguy
Reply #6 Saturday, June 5, 2004 7:13 AM
Reply #6 Saturday, June 5, 2004 7:13 AM
Good news!
Unfortunately the zapper didn't do the trick, but... I finally clued in enough to do a system restore of winXP to a point prior to the initial error. That fixed the problem!
Thanks tones for your help, as I said before, it was very much appreciated!
This might be a good tip for anybody who has had unanswered problems that seem unsolvable. If it does help out someone who has run into the same issue as I, then I'm glad we went through these steps so somebody else can try this as a solution if not, well... i'm sorry for troubling you (i feel a little silly for not trying this earlier lol).
Once again, thanks! You have shown great patience and support!
Well done!
Bryan
Unfortunately the zapper didn't do the trick, but... I finally clued in enough to do a system restore of winXP to a point prior to the initial error. That fixed the problem!
Thanks tones for your help, as I said before, it was very much appreciated!
This might be a good tip for anybody who has had unanswered problems that seem unsolvable. If it does help out someone who has run into the same issue as I, then I'm glad we went through these steps so somebody else can try this as a solution if not, well... i'm sorry for troubling you (i feel a little silly for not trying this earlier lol).
Once again, thanks! You have shown great patience and support!
Well done!
Bryan
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!
Reply #1 Friday, June 4, 2004 11:02 AM
Do as follows
My Computer/Local Disk (C:)/Program Files/Stardock/Object Desktop
And you should find the folder there, Uninstall and once you have done the uninstall, get rid of that folder, then reinstall and see if it works after doing all of that