[jbosstools-issues] [JBoss JIRA] (JBIDE-2720) Need 64-bit windows support

[David Gisbey (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-2720?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12940658#comment-12940658 ] 

David Gisbey commented on JBIDE-2720:
-------------------------------------

R6034 error with both Intel iCLS Client and Intel OpenCL SDK on Windows 8.1 64bit

I got it Visual Editor working OK by renaming instances of msvcr90.dll to msvcr90.dll.bad in the following locations:
c:\Program Files\Intel\iCLS Client
c:\Program Files (x86)\Intel\iCLS Client
c:\Program Files (x86)\Intel\OpenCL SDK\2.0\bin\x64
c:\Program Files (x86)\Intel\OpenCL SDK\2.0\bin\x86

The clash seems to happen because all of these are listed in my PATH environment variable.

After these renames, process explorer->find DLL for msvcr90.dll shows all running processes loading msvcr90.dll from the Windows Side-by-Side repository under c:\Windows\WinSxS
The javaw.exe process is now running  an amd64 version of msvcr90.dll.

javaw.exe is also loading msvcr100.dll loaded from c:\Program Files\Java\jdk1.7.0_51\jre\bin

It would be better to fix the missing manifest, but in the meantime this seems to work without having to uninstall anything and doesn't seem to have broken any of the Intel stuff components, which I expect will still work as long as there is a suitable msvcr90.dll on the system.


 

 

                
> Need 64-bit windows support
> ---------------------------
>
>                 Key: JBIDE-2720
>                 URL: https://issues.jboss.org/browse/JBIDE-2720
>             Project: Tools (JBoss Tools)
>          Issue Type: Feature Request
>          Components: visual-page-editor-core
>    Affects Versions: 2.1.0.GA, 2.1.1, 2.1.2, 3.0.0.alpha
>            Reporter: Samuel Mendenhall
>            Assignee: Konstantin Marmalyukov
>             Fix For: 4.2.x
>
>         Attachments: .mozconfig, buildlog1.log, buildlog1_x86_short.log, buildlog2.log, buildlog2_x86_short.log, buildlog3.log, build_error_when_run_x64.bat.txt, build_log_win_sdk6.log.txt, build_log_win_sdk7.log.txt, c-runtime-error.png, mozconfig1, mozconfig2, vpe-win-jdk64.png
>
>
> If you use a 64-bit JVM, the XULRunner parts of JBoss Tools does not load.
> We should look into providing a xulrunner for Windows 64-bit.
> *Update:*
> In JBoss Tools 4.1.0 and JBoss Developer Studio 7.0.0 XULRunner for 64-bit Windows is provided via experimental update site: http://download.jboss.org/jbosstools/updates/integration/kepler/core/xulrunner/
> {color:red}*Known problems:*{color}
> * XULRunner for 64-bit Windows is incompatible with Intel OpenCL SDK
> *If you get [R6034 error|https://issues.jboss.org/browse/JBIDE-2720?focusedCommentId=12771694&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-12771694] you may:*
> * Try to uninstall Intel OpenCL SDK
> * *OR* Disable XULRunner by adding the option {{-Dorg.jboss.tools.vpe.loadxulrunner=false}} to the {{eclipse.ini}} (or {{jbdevstudio.ini}} if you use JBoss Developer Studio)
> If you do not have Intel OpenCL SDK installed but still getting the R6034 error, we will very appreciate if you run Process Explorer as described in [this comment|https://issues.jboss.org/browse/JBIDE-2720?focusedCommentId=12772250&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-12772250] and help us to find conflicting library.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira