What is the specific problem(s) you're encountering?

Do you know if KB935200 had been applied at all? DesktopX will crash with this hotfix applied and we have been trying to resolve that issue.

-Mike
[Stardock Support]

Pronunciation: \ˈkil\
Function: verb
Etymology: Middle English, perhaps from Old English *cyllan; akin to Old English cwellan to kill — more at quell
Date: 14th century
transitive verb
1 a: to deprive of life : cause the death of b (1): to slaughter (as a hog) for food (2): to convert a food animal into (a kind of meat) by slaughtering
2 a: to put an end to b: defeat, veto c: to mark for omission; also : delete d: annihilate, destroy
3 a: to destroy the vital or essential quality of b: to cause to stop c: to check the flow of current through
4: to make a markedly favorable impression on
5: to get through uneventfully ; also : to get through (the time of a penalty) without being scored on
6 a: to cause extreme pain to b: to tire almost to the point of collapse
7: to hit (a shot) so hard in various games that a return is impossible
8: to consume (as a drink) totally
intransitive verb
1: to deprive one of life
2: to make a markedly favorable impression
synonyms kill, slay, murder, assassinate, dispatch, execute mean to deprive of life. kill merely states the fact of death caused by an agency in any manner . slay is a chiefly literary term implying deliberateness and violence but not necessarily motive . murder specifically implies stealth and motive and premeditation and therefore full moral responsibility . assassinate applies to deliberate killing openly or secretly often for political motives . dispatch stresses quickness and directness in putting to death . execute stresses putting to death as a legal penalty .

DesktopX fails to start up, gadgets that I've built/downloaded all crash before loading. KB935200 has not been installed. This is essentially my before/after experience after installing the SP1 beta. Things worked before, not so much after.

And, yes, Phoon's nicely provided definition of "kill" is quite appropriate.

This is the error that dektopx apps cause with SP1. I have filed reports with microsoft on this subject.


Problem signature
Problem Event Name: APPCRASH
Application Name: Magic Clock.exe
Application Version: 0.0.0.0
Application Timestamp: 471555a5
Fault Module Name: DXAxHost.dll
Fault Module Version: 2.0.0.0
Fault Module Timestamp: 44a44547
Exception Code: c0000005
Exception Offset: 000208e8
OS Version: 6.0.6001.2.1.0.256.1
Locale ID: 1033
Additional Information 1: 4bcf
Additional Information 2: a56f5a514f33f151841fb2f6e374df0e
Additional Information 3: b853
Additional Information 4: b01c87be2c1dc4ccaa49b88cb332c6d7

Extra information about the problem
Bucket ID: 541332418

I use onecare v2 on one machine and Nod 32 on another. Everything works fine if you uninstall sp1.

Workaround (you will need to have access to a RTM version of Vista to copy a dll)

1. Enable Dll/Com redirection
Add a DWORD key in the registry and set it to 1: HKLM\Software\Microsoft\WindowsNT\CurrentVersion\Image File Execution Options!DevOverrideEnable

2. Reboot for the change to take effect

3. Copy oleaut32.dll (windows/system32) from the RTM install of Vista to the DesktopX installation folder

4. Add an empty .local file for each exe to be redirected (typically, DesktopX Builder.exe, DXWidget.exe, DesktopX Helper.exe)

Ex: to redirect DXWidget.exe, create a new empty file named DXWidget.exe.local

For standalone widgets, it's a bit more complicated as they are first extracted to a temp directory, but you might try to put the files there.

I have Vista and SP1 and desktop works fine for me as long as UAC is turned on. If I turn off UAC then widgets crash.


Its not that a big issue. Keep UAC on and Desktop X works FINE


Long Live VISTA!!




Anne

Here is a rundown of the registry change

1. Open regedit.exe
2. Navigate to HKEY_LOCAL_MACHINE\Software\Microsoft\WindowsNT\CurrentVersion\Image File Execution Options
3. There should be a "(Default)" value
4. Choose Edit -> New -> DWORD(32-bit) Value
5. Use "DevOverrideEnable" as the name
6. Double-click on it, use "1" as value data
7. You should now see a "DevOverrideEnable" value of type REG_DWORD with the data set to "0x00000001(1)" in addition to the "(Default)" value
8. Reboot and continue with the next step

Windows then looks in the current directory when loading dll files. That way you can use the old "working" version instead of the SP1 version.

Make sure you get the right version of oleaut32.dll. My RTM version is 6.0.6000.16386. Using the one from the current SP1 installation will not work.

As said above this is only necessary if you have UAC turned off.