Error Message(s) DesktopX

I've been trying to load 3 different DesktopX themes, Airlock, Destruction and Toxic, all without success. I did have them running AND MODIFIED a few months ago but am not able now. The problem being, whenever I try to modify the properties in ANY of the theme menus to my application, DesktopX shuts down. I do get an error message but cannot find the log file DesktopX creates. I'm not able to modify any of the themes I've mentioned. Any specific suggestions would be appreciated.

-SD:
5,494 views 9 replies
Reply #1 Top
There definitely seems to be compatibility problems with these and the new alpha builds. I'll check into it further.
Reply #2 Top
I've checked a bunch of other htemes and they don't seem to have a problem. I wonder what is special about those particular themes.
Reply #3 Top
GRR, and this time when I loaded Airlock it worked fine. If it crashes on you, let us know which module it's doing it in. Thanks!
Reply #4 Top
Humm ...

I have NO problem LOADING the themes I mentioned in my previous message. The problem is, WHEN I try and MODIFY a particular item in the menu DesktopX crashes and burn(s). For example, if I right click on Explorer or the Email Client in the menu and try to CHANGE them to use MY applications, DesktopX crashes. This happens right after I select browse and navigate to my Email Clients' directory (Eudora) and select eudora.exe OR the same thing happens when I try and configure for Firefox.

On the other hand, if I load the Toxic theme an "additional problem" occurs. Some script (DXScript) keeps trying to load Outlook.
to load Outlook and its stuck in a loop. ActiveX component can't create object: Outlook.application' Line: 63

Anyway, when I load the "other two themes" (Airlock/Destruction) I eventually get the following messages:

DesktopX.exe has generated errors and will be closed by Windows. You will need to restart the program. An
error log is being created.

DesktopX does not appear to have exited corectly. This could be the fault of a corrupt theme or a
buggy plugin. Would you like to start with a new, empty theme (Yes) or attempt to load the current
theme again (No)?

WFT,
-SD:
Reply #5 Top
So is it safe to assume there's a bug in DesktopX causing the problems I've outlined? If so, just let me know and I'll crawl back into my hole until it's fixed.

Cheers,
-SD:
Reply #6 Top
I realize you're busy but I would appreciate an answer ......

So is it safe to assume there's a bug in DesktopX causing the problems I've outlined? If so, just let me know and I'll crawl back into my hole until it's fixed.

Cheers,
-SD:
Reply #7 Top
Would someone out there (support or another enduser) please answer my questions above. If there are bugs in DesktopX fine, I'll wait untill they're fixed. I just want to know if it's me or the program.

-SD:>0
Reply #8 Top
Are you using 2.40f[a].002? It should be fixed.
Reply #9 Top
Alberto,

Thanks for lending a hand. I finally figured it out. I dropped back to v2.30.032 and everything is working fine with the theme(s) I've mentioned above. I tried going back to v2.21.029 (if I remember correctly)and it wouldn't install ...... got error messages. That pretty much tells me the latest offical verions was the problem. Gesh, that's all I wanted someone to tell me.

Cheers,
-SD: