[Bug 11490] Speed Commander 12 reports "Can't Initialize Scripting Environment" error on startup

http://bugs.winehq.org/show_bug.cgi?id=11490

Anastasius Focht  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
                 CC|                            |[e-mail]
         Resolution|                            |FIXED
            Summary|Can't Initialize Scripting  |Speed Commander 12 reports
                   |Environment                 |"Can't Initialize Scripting
                   |                            |Environment" error on
                   |                            |startup

--- Comment #14 from Anastasius Focht  2011-12-14 08:44:12 CST ---
Hello,

initial problem about scripting environment error is fixed.

The problem about not displaying folder/contents (along with CLSID
603d3800-bd81-11d0-a3a5-00c04fd706ec spam) seems to be specific to Speed
Commander v13.

http://www.sp-download.de/sc13/sc13.exe

Speed Commander v12 ("found" an old version for testing) and v14 don't exhibit
this problem (probably different approach or the author worked around Wine
insufficiency?):

http://www.sp-download.de/sc14/sc14.exe

You could make the v13 issue a separate bug if it bothers you.

Regards