[Bug 11490] New: Can't Initialize Scripting Environment

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

Summary: Can't Initialize Scripting Environment
           Product: Wine
           Version: 0.9.54.
          Platform: PC-x86-64
               URL: http://www.speedproject.de/enu/speedcommander/index.html
        OS/Version: other
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: -unknown
        AssignedTo: [e-mail]
        ReportedBy: [e-mail]

Created an attachment (id=10641)
 --> (http://bugs.winehq.org/attachment.cgi?id=10641)
Terminal output

Installing Speed Commander 12.01 never finished, but I was able to copy over
the install directory from a windows machine.  When I run Speed Commander the
gui and everything work perfectly!  However, I don't see any of my directories
and I get the error 'Can't Initialize Scripting Environment' I have attached
the terminal output.  Hopefully it's an easy fix?

[Bug 11490] Can't Initialize Scripting Environment

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

Alexander Nicolaysen Sørnes  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

--- Comment #1 from Alexander Nicolaysen Sørnes   2008-02-06 11:47:06 ---
This might be an msxml problem, but could you file a bug report for the
installer first, if you have not done so already?  This helps us to rule out
that the application is missing some required files or registry settings.

[Bug 11490] Can't Initialize Scripting Environment

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

--- Comment #2 from Thom   2008-02-06 14:30:14 ---
Created a bug report for the installer.  FYI, I also copied the windows install
dir to another Windows machine that didn't have the program installed and it
ran fine, not sure if that matters.  Thank you.

[Bug 11490] Can't Initialize Scripting Environment

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

Austin English  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
           Keywords|                            |download

--- Comment #3 from Austin English   2008-06-03 15:09:50 ---
Is this still an issue in 1.0-rc3?

[Bug 11490] Can't Initialize Scripting Environment

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

--- Comment #4 from Thom   2008-06-03 16:30:57 ---
Yes, this is still an issue, would be great if it could be fixed before 1.0

Install still is not working correctly even though someone posted a patch.

[Bug 11490] Can't Initialize Scripting Environment

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

--- Comment #5 from Thom   2008-06-07 11:09:37 ---
Still a problem with 1.0 rc4, thank you.

[Bug 11490] Can't Initialize Scripting Environment

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

Thom  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
  Attachment #10641|0                           |1
        is obsolete|                            |

--- Comment #6 from Thom   2008-07-16 12:27:57 ---
Created an attachment (id=14845)
 --> (http://bugs.winehq.org/attachment.cgi?id=14845)
terminal output - better!

[Bug 11490] Can't Initialize Scripting Environment

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

--- Comment #7 from Thom   2008-07-16 12:28:46 ---
Created an attachment (id=14846)
 --> (http://bugs.winehq.org/attachment.cgi?id=14846)
all font not showing

[Bug 11490] Can't Initialize Scripting Environment

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

--- Comment #8 from Thom   2008-07-16 12:29:09 ---
Created an attachment (id=14847)
 --> (http://bugs.winehq.org/attachment.cgi?id=14847)
all font not showing 2

[Bug 11490] Can't Initialize Scripting Environment

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

--- Comment #9 from Thom   2008-07-16 12:30:13 ---
I'd just like to thank you guys for working on this.  I've upgraded to 1.1.1
and it's working MUCH better!!  When I start up SpeedCommander, I only get one
pop up saying can't initialize.  BUT, if I click ok, it goes into the app and
actually shows the directory tree's!!  However, now you can't see all the stuff
(see pic for what I mean).  And now closing the application doesn't give a
bunch of can't initialize errors either!!  So it's getting damn close!!  Thank
you again.

ps.  I have attached the debug as well

[Bug 11490] Can't Initialize Scripting Environment

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

--- Comment #10 from Thom   2008-11-25 12:51:07 ---
Been a while since anyone's looked at this but just want you to know that it's
still happenning with 1.1.9, using a x86 linux distro (Ubuntu) not sure if it's
causeing the problem in bug 16203 that I just entered last night.

[Bug 11490] Can't Initialize Scripting Environment

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

Austin English  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
     Ever Confirmed|0                           |1

--- Comment #11 from Austin English   2010-06-04 22:16:33 ---
Still present in wine-1.2-rc2-111-g9aa9a12. Native msxml3 doesn't help. Looking
at the terminal output, there's:
err:ole:CoGetClassObject class {603d3800-bd81-11d0-a3a5-00c04fd706ec} not
registered

which looking up that uuid:
http://mikolajapp.appspot.com/uuid/query?q=603d3800-bd81-11d0-a3a5-00c04fd70...

says:
Results for 603d3800-bd81-11d0-a3a5-00c04fd706ec
Found in Windows 98 registry

* Registered class: Background Task Scheduler
          o Inproc sever: C:\WINDOWS\SYSTEM\BROWSEUI.DLL

Found in Windows Vista registry

* Registered class: Background Task Scheduler
          o Inproc sever: C:\Windows\system32\browseui.dll (product: Microsoft®
Windows® Operating System,version 6.0.6000.16386)

which I thought may be related, but using a native one and regsvr32'ing it
didn't help.

[Bug 11490] Can't Initialize Scripting Environment

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

Vijay Kamuju  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

--- Comment #12 from Vijay Kamuju  2011-09-13 17:44:11 CDT ---
please test it again with wine 1.3.28

[Bug 11490] Can't Initialize Scripting Environment

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

Bruno Jesus  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

--- Comment #13 from Bruno Jesus  2011-09-13 20:09:10 CDT ---
Seems fixed in 1.3.28. There are no error popups and the directories are
showing up correctly, it's possible to browse without problems.

[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

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

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

Alexandre Julliard  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |CLOSED

--- Comment #15 from Alexandre Julliard  2011-12-16 13:29:42 CST ---
Closing bugs fixed in 1.3.35.