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

wine-bugs at winehq.org wine-bugs at winehq.org
Wed Dec 14 08:44:12 CST 2011


Anastasius Focht <focht at gmx.net> changed:

           What    |Removed                     |Added
             Status|NEW                         |RESOLVED
                 CC|                            |focht at gmx.net
         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 <focht at gmx.net> 2011-12-14 08:44:12 CST ---

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.


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


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


Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
Do not reply to this email, post in Bugzilla using the
above URL to reply.
------- You are receiving this mail because: -------
You are watching all bug changes.

More information about the wine-bugs mailing list