New and need help

I have the latest release of Object Desktop and all the apps are up to date. I haven't tried any other ppl's desktops, but when I make my own it repeatedly unloads/crashes when I start working with it. I really don't know where to start.

Windows XP SP3
4,127 views 9 replies
Reply #1 Top
Windows XP SP3
End of quote


Either it's SP3 or you should try reinstalling.

If that doesn't work, re post this in the New Users section of the forums and someone will help you. This isn't the right section for newbie problems ;)

WWW Link
Reply #2 Top
I already tried reinstalling. Also, if my compy is just sitting there it doesn't fail. It's only when I try to use an object or run something.
Reply #3 Top
antivirus with script blocking maybe turned on?


sometimes: a reinstall of Windows Script 5.6 helps
Reply #4 Top
This isn't the right section for newbie problems
End of quote



DTX crashing isn't a newbie problem. A newbie problem would be more along the lines of: "Okay... I downloaded a skin, now what?" ;)

Reply #5 Top
5.6 didn't help. Right now my theme's config is:

No Windows taskbar or desktop.
A wallpaper of a jpg I like.
A desktopx taskbar with the default image, large icons, no fixed width....
A shortcut to the Programs folder.
A shortcut to the Desktop.
...and that's about it.

I'd much rather be creating my theme than dealing with the constant crashing. It seems to crash quickest when I launch programs, particularly Steam.
Reply #6 Top
you have WindowBlinds running? if so try excluding Steam in the 'change a look of a particular app'
Reply #7 Top
I can see you replied again, but I can't see the reply. They stop after #5.

Edit: I can see it now. OK, I tried that, but it crashes on almost any program I launch. I even tried stopping/unloading WindowBlinds. That didn't help either.
Reply #8 Top
Got it. I started fiddling around with launching the same programs from the hotkeys on my Logitech G11 and noticed that it didn't make DX crash when the same programs were launched from there. So I figured it was my shortcut object that was doing it. When I checked in the object's properties, I noticed the "close widget after execution" box was checked. Unchecking it fixed my problem. Thanks for the help though Bichur.
Reply #9 Top
glad you got it figured out :)