I have an issue regarding the installtion of scilab 64 bit.
Currently I am using the 32 bit versions of (6.1.1) without any problems.
My newest project (xcos electrical circuit) is quite big. A scilab error "out of memory" pops up.
I tried to fix the problem by using the 64 bit versions of scilab.
Folloing error occurs while running of any xcos model (demos included)
-------Modelica translator error message:----
"c_pass1: build the modelica meta-block failed"
"xcos_simulate: Error during block parameters update."
Scilab and compiler installation with following procedure
installation Scilab
installation of the gcc compiler (mingw package atoms)
restart pc
atomsInstall('mingw')
restart scilab
loading of the libary (happen automatically)
32 bit versions works perfect
64 bit version doesnt work
I didn't change anything in the environment variables
The problem occurs on both of my pc (windows 10 pro, newly setup)
I hope someone can help me
Kind regarads
Niki
Related
I am trying to install the CUDA toolkit in order to be able to use Thundersvm in my personal computer.
However I keep getting the following message in the GUI installer:
"You already have a newer version of the NVIDIA Frameview SDK installed"
I read in the CUDA forums that this most probably results from having installed Geforce Experience (which I have installed). So I tried removing it from the Programs and Features windows panel. However I still got the error, so my guess is that the "Nvidia Corporation" folder was not removed.
In the same question, they also suggested performing a custom install. However I could not find any information on how to do a custom install of the CUDA toolkit. I would really appreciate if someone could explain how to do this custom install or safely remove the previous drivers. I thought of using DDU but I read that sometimes it may actually lead to trouble.
I had the same problem while I was trying to get TensorFlow to use my NVIDIA GTX1070 GPU for calculations. Here's what allowed me to perform the CUDA Toolkit installation on my Windows 10 machine.
As the error message in the installer says - you already have a newer Frameview SDK installed. It was the case for me.
Go to Settings/Uninstall or modify programs.
Remove the NVIDIA Frameview program. It should be there with GeForce Experience, PhysX, etc.
Uninstalling only this NVIDIA program didn't cause any driver problems for my machine and I was able to progress through the CUDA Toolkit installation.
I just met the same problem and fixed it now.
This problem occurred because you chose the default installation configuration, which might contain many installed parts. In my situation, I have installed NVIDIA Nsight Compute, which is the culprit during the first few installs.
Unchecking the redundant parts should be helpful.
I was trying to reinstall Anaconda on my Windows machine but have been running into a lot of issues. The installation gets stuck at extracting packages.
I have tried multiple time with available recommendations but to no avail. Prior to installation, I've always cleaned the entire path and directories but I end up on with the same issue. The installer gets stuck at various points at different install instances.
Another thing that I noticed is that although I am using a 64 bit installer, Task Manager lists it as 32 bit. I am attaching a few screenshots too.
Thank you for the help.
Current Scenario
On OSX Mountain Lion I'm able to compile mach_inject and the included test project. That works as expected with injection functioning perfectly.
I'm now trying to use the same mach_inject framework from a Qt project, compiled from QtCreator. I've tried both clang and gcc compilers.
Everything compiles and the application runs, but when calling mach_inject, I get the error:
mach_inject failing.. (os/kern) invalid address
Tracing mach_inject, the failure occurs at the last step, when it calls thread_create_running.
Does anyone know what the problem is here? I'm assuming it's something to do with the compiler options provided by Qt against those used by XCode, but could be totally wrong!
Thanks.
The problem turned out to be a 32 / 64 bit incompatibility - as (naturally) you can't inject a 64bit bundle into a 32 bit app!
If anyone else has similar problems, debugging into the mach_inject_bundle_stub can be of use, as the same error from the kernel can be presented due to other issues.
I've been using clang successfully on Windows XP and Windows Vista using the 'experimental' builds for MinGW, but now that I try on my new Windows 7 64-bit laptop it simply crashes. Even if I just run "clang++" or "clang" it crashes, and I can't figure out how to get windows to give me more detailed crash info (I will edit that in if I can). I've redownloaded clang and reinstalled MinGW, and I've tried running clang.exe in compatibility mode, but it still doesn't work. This is the first time I am using it on 64-bit, I hope that's not the issue (if it is, I still have another computer I can use).
I've looked around and can't find anyone else having this same problem with clang crashing before even giving any output or processing any input, I really feel lost.
This has now happened multiple times on various system and I have found the solution. Reinstall MinGW using the prepackaged files, the 'latest' ones have a tendency to be unstable in relation to clang. Make sure you haven't also installed a newer version of gcc on top of the MinGW installation, as that will cause issues too.
I've been trying to get my installation of matlab working but for some reason even the simplest functions don't work.
When I call 'ver'
I get the error:
Undefined function 'ismembc' for input type double...
I assume that there is something wrong with my installation, but exactly what? How can I trouble shoot this?
the problem is that I've installed it on a portable SSD. The SSD runs matlab perfectly fine on my 64bit laptop. It just hasmajor problems with a 32bit desktop. My version of matlab comes with both 64 and 32 bit directories.
ismembc is a mex-function, which means it's a 32-bit/64-bit problem. You need to install the 32-bit and 64-bit versions separately, or just the 32-bit version.