http://bugs.winehq.org/show_bug.cgi?id=20651
Anastasius Focht focht@gmx.net changed:
What |Removed |Added ---------------------------------------------------------------------------- Keywords| |dotnet CC| |focht@gmx.net Component|-unknown |wmi&wbemprox
--- Comment #12 from Anastasius Focht focht@gmx.net 2010-08-31 14:49:56 CDT --- Hello,
yes WMI insufficiency.
--- snip --- Unhandled Exception: System.Exception: Cannot create ActiveX component. at Microsoft.VisualBasic.Interaction.GetObject(String PathName, String Class) at setsdaff.GetRunningProcesses.GetAllRunningProcesses(String strPrefix, String& strFound) at setsdaff.SetStardockAffiliate.Main() wine: Unhandled exception 0xe0434f4d at address 0x7b835c02 (thread 003e), starting debugger... --- snip ---
Stupid they didn't wrap chained instance creation in exception handler (hence the crash) ... though somewhat expectedly from people using Visual Basic .NET ;-)
--- snip managed code --- object objectValue = RuntimeHelpers.GetObjectValue(NewLateBinding.LateGet(RuntimeHelpers.GetObjectValue(Interaction.GetObject(@"winmgmts:\" + str + @"\root\cimv2", null)), null, "ExecQuery", new object[] { "Select * from Win32_Process" }, null, null, null)); --- snip managed code ---
The only purpose of the app seems to be in extracting a sub string from all running processes named "impulse_setup_XXX.exe" (XXX = affiliate id) and write it to registry.
"HKLM\Software\Stardock\ComponentManager" -> "AffiliateID" + extracted string value.
Regards