Desktop X crashes 2.40c[a}.002
What should I do solve this problem
Monday, January 17, 2005 by CaPet | Discussion: DesktopX
Hallo,
since I installed the update 2.4 my desktop X does not start.
It starting process brokes with an microsoft error.
I'm using Windows XP
Icon Developper 1.11.019
Icon Packager 2.50h.087
Object Dock Plus 1.10.008
and Desktop X 2.40c[a] 002
I uninstalled DesktopX and deleted all file in dokuments and settings folder related with desktop X.
But it's allways the same problem. If I start it desktopX crashes.
What should I do to solve the problem, because I'm very disappointed. Paying 50$ and the programm
crashes during startup-process.
Greetings
Carsten
since I installed the update 2.4 my desktop X does not start.
It starting process brokes with an microsoft error.
I'm using Windows XP
Icon Developper 1.11.019
Icon Packager 2.50h.087
Object Dock Plus 1.10.008
and Desktop X 2.40c[a] 002
I uninstalled DesktopX and deleted all file in dokuments and settings folder related with desktop X.
But it's allways the same problem. If I start it desktopX crashes.
What should I do to solve the problem, because I'm very disappointed. Paying 50$ and the programm
crashes during startup-process.
Greetings
Carsten
CaPet
Reply #2 Tuesday, January 18, 2005 3:40 PM
Reply #2 Tuesday, January 18, 2005 3:40 PM
Thanks for you hint, but there is no solution and If I see the responses from helpdesk. They mean: It's problem of my user-settings. Because with an other user it works.
But I deleted all settings in local-setting folder related to stardock (from the user where desktopx doesn't start) and nothing changes.
Greetings
Carsten
But I deleted all settings in local-setting folder related to stardock (from the user where desktopx doesn't start) and nothing changes.
Greetings
Carsten
sranshaft
Reply #3 Tuesday, January 18, 2005 6:19 PM
Reply #3 Tuesday, January 18, 2005 6:19 PM
try starting up a theme without scripts. if it doesn't crash then you'll need to install the newest script engine from microsoft. i had this problem a little while back and after intalling the script engine it worked like a charm again.
CaPet
Reply #4 Wednesday, January 19, 2005 3:11 PM
Reply #4 Wednesday, January 19, 2005 3:11 PM
Hi Skinner sranshaft,
can you explain how I start a theme without scripts. Because I delete every setting and it's not possible to start desktop X. It crashes during the starting process.
Or how can I install the script engine from ms?
can you explain how I start a theme without scripts. Because I delete every setting and it's not possible to start desktop X. It crashes during the starting process.
Or how can I install the script engine from ms?
uwan
Reply #5 Wednesday, January 19, 2005 9:39 PM
Reply #5 Wednesday, January 19, 2005 9:39 PM
Hello, I have the same problem. DxDesktop chrashes in DxMain with instruction on 0x77d3b1e9. The instruction points to memory address 0x3a443d73 and crashes during a "Read".
Any idea?
Thanks. uwan
Any idea?
Thanks. uwan
Lantec
Reply #6 Wednesday, January 19, 2005 9:55 PM
Reply #6 Wednesday, January 19, 2005 9:55 PM
Just a suggestion, You might want to uncheck the "Show Pre-Release Versions" box in SDC and just install the non beta version 2.40
Uninstall DX2, reboot and then install the released version and reboot.
I'm not running the beta and I have no problems with DX2 whatsoever. Can't gaurantee that it will work but it seems all the threads mention the Beta version as the culprit.
Uninstall DX2, reboot and then install the released version and reboot.
I'm not running the beta and I have no problems with DX2 whatsoever. Can't gaurantee that it will work but it seems all the threads mention the Beta version as the culprit.
laurentfr
Reply #7 Thursday, January 20, 2005 3:18 AM
Reply #7 Thursday, January 20, 2005 3:18 AM
both 2.4 and the latest betas have their own different problems.
The latest beta has corrected many problems but still some objects/widgets do not work anymore.
The latest beta has corrected many problems but still some objects/widgets do not work anymore.
sranshaft
Reply #8 Thursday, January 20, 2005 5:54 PM
Reply #8 Thursday, January 20, 2005 5:54 PM
starting a theme without script would be just starting desktopx withan empty theme.
as for the scripting engine, go here Link and download, install the file scripten.exe. reboot your computer and try loading desktopx again. if that doesn't work trying falling back to 2.3...it's the last build of desktopx i've used that was at least some what stable. 2.4 brought nothing but headaches for me.
as for the scripting engine, go here Link and download, install the file scripten.exe. reboot your computer and try loading desktopx again. if that doesn't work trying falling back to 2.3...it's the last build of desktopx i've used that was at least some what stable. 2.4 brought nothing but headaches for me.
CaPet
Reply #9 Tuesday, January 25, 2005 5:01 PM
Reply #9 Tuesday, January 25, 2005 5:01 PM
Where I can find the 2.3 Version. Is it possible to downgrade with stardock central?
You tipp to reinstall scripten.exe unfortunatly not helped...
greeting
Carsten
You tipp to reinstall scripten.exe unfortunatly not helped...
greeting
Carsten
CaptainWin
Reply #10 Saturday, January 29, 2005 2:18 PM
Reply #10 Saturday, January 29, 2005 2:18 PM
CaPet: As far as I know you can only roll back to version 2.3 if you archived it in Stardock Central before you downloaded any updates. If you did archive it then all you have to do is click on "file" in SC and then click on "restore archive" from the drop down list. A new window will pop open with a listing of all the programs that have been archived. Just select 2.3 and restore.
Tiggz
Reply #12 Monday, January 31, 2005 12:37 PM
Reply #12 Monday, January 31, 2005 12:37 PM
Alberto - I am finding 2.40f[a].002 mostly stable and am enjoying alot of the new features
the only major problem I am encountering is that in some widgets I am making that have scripts in multiple objects, some of the scripts are not initialising properly. It is as though the Object_OnScriptEnter sub is not firing. In some cases they will initialise only after I interact with them - by clicking or dragging them for example. I imagine this is something to do with the new threading system - unfortunately I cannot run the scripts in a seperate thread because of the multiple script nature of these widgets.
Therefore I find that I can make simple widgets but my more interesting widgets are on hold at the moment. Apart from this I do like the direction you are taking dx - I especially like the new scripted context menu feature
(suggestion - if you add widget.properties to the widget namespace methods then we can safely replace the right click context menu with our own custom versions)
the only major problem I am encountering is that in some widgets I am making that have scripts in multiple objects, some of the scripts are not initialising properly. It is as though the Object_OnScriptEnter sub is not firing. In some cases they will initialise only after I interact with them - by clicking or dragging them for example. I imagine this is something to do with the new threading system - unfortunately I cannot run the scripts in a seperate thread because of the multiple script nature of these widgets.
Therefore I find that I can make simple widgets but my more interesting widgets are on hold at the moment. Apart from this I do like the direction you are taking dx - I especially like the new scripted context menu feature
(suggestion - if you add widget.properties to the widget namespace methods then we can safely replace the right click context menu with our own custom versions)
CaptainWin
Reply #13 Tuesday, February 1, 2005 4:05 PM
Reply #13 Tuesday, February 1, 2005 4:05 PM
Sadly I still have the same problem with 2.40f(a).002 
Frogboy
Reply #14 Tuesday, February 1, 2005 4:23 PM
Reply #14 Tuesday, February 1, 2005 4:23 PM
My suggestion woudl be to do this:
In your Program Files directory you have c:\program files\stardock\object desktop\desktopx
Open tha tup and delete everything in the desktopX directory. Uninstalling DesktopX only removes it. It doesn't remove your current theme and such (because people threw a fit back when we used to do that).
The problem (as you've probably already guessed) is that if your current theme is corrupted, DesktopX will crash when you load it up.
Therefore, the solution is to delete the corrupted theme. The easiest way to make everything okay again is to just delete the entire DesktopX directory and then reinstall it to make sure there's nothing floating around in there that's bad.
CaptainWin
Reply #15 Wednesday, February 2, 2005 2:55 PM
Reply #15 Wednesday, February 2, 2005 2:55 PM
Frogboy: I was going to try as you suggest but found that on my pc Object Desktop is not in the Stardock folder, it is in a folder all to itself (c:\program files\object desktop\desktopx). I only mention this in case it might be my problem i.e. that destopx 2.40 is looking for desktopx.exe in the stardock folder instead of where it is in the object desktop folder. Could this be it? If so, how do I point it to the right folder? If you do not think it is my problem I will procede as you have suggested.
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 Tuesday, January 18, 2005 3:18 PM