You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I start the 64-bit R in Windows 7 it fails because it still calls the ntdll.dll and kernel32.dll from C:\Windows\System32 vs. C:\Windows\SysWOW64.
Installed v3.2.1 - both 32-bit \i386 and 64-bit \x64
The 32-bit version opens great both from Rgui.exe and Rterm.exe.
The 64-bit version does not open from either Rgui.exe or Rterm.exe.
Verified Shortcut and Registry settings are correct.
Used the *.tmp.appcompat.txt to verify all R objects are being called from the correct \bin\x64 directory. (see attached PDF for this file and how it was verified)
Used the *.tmp.appcompat.ext to verify the ntdll.dll and kernel32.dll were both being called from the C:\Windows\System32 directory vs. the C:\Windows\SysWOW64 directory.
The attacked PDF has all Registry entries, screenshots of error messages, Windows OS verification, and other key info. It also has the content of these three files:
*.tmp.WERInternalMetadata.xml
*.tmp.appcompat.txt
*.tmp.wmi.txt
I need the 64-bit version to use with the rJava & JRI interface to compile JAVA plugins for our Datameer/Cloudera environment which is all 64-bit.
Any help you can provide would be greatly appreciated.
We have the same exact issue. R64 bit will not run at all and event viewer shows ntdll.dll as being the cause. Any help troubleshooting would be much appreciated.
We have the same exact issue. R64 bit will not run at all and event viewer shows ntdll.dll as being the cause. Any help troubleshooting would be much appreciated.
When I start the 64-bit R in Windows 7 it fails because it still calls the ntdll.dll and kernel32.dll from C:\Windows\System32 vs. C:\Windows\SysWOW64.
Installed v3.2.1 - both 32-bit \i386 and 64-bit \x64
The 32-bit version opens great both from Rgui.exe and Rterm.exe.
The 64-bit version does not open from either Rgui.exe or Rterm.exe.
Verified Shortcut and Registry settings are correct.
Used the *.tmp.appcompat.txt to verify all R objects are being called from the correct \bin\x64 directory. (see attached PDF for this file and how it was verified)
Used the *.tmp.appcompat.ext to verify the ntdll.dll and kernel32.dll were both being called from the C:\Windows\System32 directory vs. the C:\Windows\SysWOW64 directory.
The attacked PDF has all Registry entries, screenshots of error messages, Windows OS verification, and other key info. It also has the content of these three files:
*.tmp.WERInternalMetadata.xml
*.tmp.appcompat.txt
*.tmp.wmi.txt
I need the 64-bit version to use with the rJava & JRI interface to compile JAVA plugins for our Datameer/Cloudera environment which is all 64-bit.
Any help you can provide would be greatly appreciated.
METADATA
The text was updated successfully, but these errors were encountered: