DesktopX COMPLETLY dead

from WinCustomize Forums
I converted 3 DX objects (Killer Media, Email and Alarm) into widgets and they worked fine. I put shotcuts to them in my startup folder and when I restarted DXwidget.exe crashed. After that happened I can't load anything in DX without DesktopX.exe crashing.
I uninstalled EVERY Stardock program from my system, cleaned my registry with Norton to remove any old references and then re-installed everything. DesktopX.exe still crashes every time. Could it have damaged a Windows component and that's why I can't get it to run right?

HELP!!!!!
wincustomize
3,866 views 8 replies
Reply #1 from WinCustomize Forums Top
I don't know. You have done everything that I could suggest: uninstall. clean registry, restart, reinstall. I suggest you contact stardock support: [email protected]
[Message Edited]
Reply #2 from WinCustomize Forums Top
I'm waiting to hear from Stardock. I was just hoping someone here might have an idea.
Multiplicity - Control multiple PCs using one keyboard and mouse
Reply #3 from WinCustomize Forums Top
This is a dumb question but...do you have the latest version of DX installed? Some of the newer objects only work with the newest version without problems. (I personally never use the beta that is often available because of the same type of problems.) I have a year old Dell 8250, with all the bells and whistles...great graphics card, lots of memory, etc.,... but DX ALWAYS locks up my computer. I can't tell you why, either! I try it every once in awhile to see if it's just me and maybe I'll learn something new and see what I have been doing wrong but I have never used it successfully for more than a day. The only thing that I can guess is that it really sucks up the memory...maybe if I had 1G of memory it would work better?! I use ObjectDock with docklets for weather and time and other streaming media and that works great...I guess you can say that I substituted ObjectDock for DX. I still use IconPackager, LogOn Studio, WindowBlinds, and BootSkin (and wallpaper) with it, so it kind of really is like using a DX theme without using Dx! Hope you can find the answer to your problem. Like I said, my guess is either that you need to use the newest version of DX with the newest objects/themes OR plunk down some cash for more memory (wouldn't we all love to do that!) Good Luck!
Reply #4 from WinCustomize Forums Top
These problems are usually caused by the windows scripting host being corrupted or damaged in some way. Try creating a normal vbscript file and running it. Chances are if this has happened that will not work either. You may need to reinstall the script host for your operating system.

http://www.microsoft.com/downloads/details.aspx?FamilyID=c717d943-7e4b-4622-86eb-95a22b832caa&DisplayLang=en

for Win2k/XP.
Reply #5 from WinCustomize Forums Top
I had same problem...
The only way I was able to fix it was to do a system restore (back up stuff on a disk first) to a time before I had the problem. Then never leave it in edit mode for more than 3 minutes or it will crash. Whenever it crashes just cut the power and be really careful with scripts
Also never hit apply just click ok
Reply #6 from WinCustomize Forums Top
Also you dont need to put the stuff in the startup folder
If you go into the desktop X properties you can check the box labled "Run DX on startup" once you fix that you will still need to do a system restore and always cut the power when ever it crashes
Reply #7 from WinCustomize Forums Top
If I am just talking nonsense just ignore me
[Message Edited]
Reply #8 from WinCustomize Forums Top
You access system restore by going to Start/help and support then do a search in the help thing for "System restore wizard" and the option to "Run restore wizard" will appear

Also
This is a dumb question

Well it seems like an itelligent question to me... rather an unesesary comment


[Message Edited]