when i install modelsim10.4SE in my windows10 completed. but when run modelsim there comes an error.could sameone help me ?enter image description here
The first Modelsim 10.4 version was released back in 2014 and had no Windows 10 support, perhaps more importantly it also didn't support Windows 8.1 yet, so I think you simply stumbled upon a Windows compatibility issue.
Try to run Modelsim (vsim/vcom/vlib/etc) in Windows7/8 compatibility mode, try the 32bits version or if you have the license install a later version of Modelsim SE.
Good luck,
Hans.
This thread is a bit old, but I've encountered the same issue and I think that I've found a way to solve it.
In my case another program was blocking the install (Skype/lync). After closing it the installation wizard kicked in as it was supposed to do.
To find the program that was causing the issue I used the new option added to the task manager called "Analize wait chain" and eventually got to lync.
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'm running the Qt Open Source installer on Windows 7.
It's at 46% during the "Retrieving meta information from remote repository" step. It quickly got there and got stuck there 55 minutes already.
I tried restarting the installer and this time it got stuck again at the same step, but at 64%.
Any ideas?
Notes:
The installer name is qt-unified-windows-x86-2.0.3-1-online.exe
I believe the Qt version it's going to install is Qt 5.7, as that's the latest Qt version as of now
I'm going to try the offline installer now
The solution that worked for me was to download and use the offline installer instead of the online one.
I had the same problem and added this as custom repo in the Maintenance Tool Settings -
http://download.qt-project.org/online/qt5/windows/x86/online_repository/
After this it updated all the build-in repos and synced.
But I too really really think Qt should fix it, I have this problem every time on every machine.
It is probably due to some network issues, as mentioned by some other users.
Just play around with your network and it should work.
In my case, I disconnected my WiFi and connected again and it worked.
I'm attempting to install Java 8 JRE on Window 10, and it's failing. The purpose of this is so that I can install SQLWorkbenchJ on my Windows machine. This is my personal machine, and I have complete access privileges. Please let me know if I can provide any additional information to answer this question (e.g., logs).
I've downloaded Java 8 from Oracle, specifically the offline 64 bit version for windows. When I download it, it places the following icon on my desktop:
When I double click on this icon, the following image pops up:
After I click "Yes" and the popup box disappears, nothing happens. Windows continues operating as if nothing happened. The only trace of activity is in the task manager, which shows the following:
Does anyone have any suggestions on how to fix this? I'm at a loss for how to push the installation process forward.
Update: I was able to solve this issue by installing the x86 version (32 bit) instead. I'm not sure why the x64 version doesn't work on Windows 10, but I'd seen this solution subtly referred to elsewhere on the internet as a solution. Would be interesting if someone could figure out why the x64 version itself doesn't work.
We have two concerns here - 1. JRE 8u101 (64-bit) fails to install without an error message and 2. JRE 8u101 (64-bit) fails to install on Windows 10.
The first one seems similar to http://bugs.java.com/view_bug.do?bug_id=8148167 which is a known issue.
However, it would be appropriate to take a look at jusched and JavaDeploy log files to confirm the same.
The second concerns with 64-bit JRE installation in Windows
Microsoft Edge on Windows 10 is not supported a supported browser.
For Internet Explorer 11 on Windows 10, see:
Related bug ID: http://bugs.java.com/view_bug.do?bug_id=8162523
For a solution related to 64-bit installation, suggest you to follow the instructions from the comment in the above bug report.
Hope this helps.
This is known issue https://bugs.openjdk.java.net/browse/JDK-8148167 , this has already fixed in 8u111/8u112, early access builds are available here - https://jdk8.java.net/download.html, you can download and try to install the same. Do let us know your feedback?
I was having this issue as well and the 8u112 worked from this page
Thank you
Can anyone tell me what to do. I'm trying to install XDK 2366 on windows 10. When i click the xdk_web_master_2366.exe file it says Installing Intel XDK then after 5-10 seconds it just disappears and the installation stops. No error message. I've tried to turn off the firewall and disable windows defender but still facing the same problem. If anyone can assist i would greatly appreciate it.. Thanx
See the instructions on this Intel XDK forum post for doing a complete uninstall, in case you have a partial install that is getting in the way. Do everything up to the "finally" step. Those instructions were written for people that wanted to stay with a previous version of the XDK.
Do not install that older version that is posted in that thread, it will be obsolete very soon.
I have had basic tests for meteor on a Windows7 PC.
But there the application crashed too often.
Before this, I tested meteor on PC running Windows8. There, crashes happened much less often and generally they were recovered when I shutdown and rebooted the meteor.
Is Meteor unstable on windows7?
Or is there any way to avoid this?
The version packaged to the MSI installer that can be found on win.meteor.com is not official. If you want a more stable, try the virtualized option I've described on the site. I've been using that for a month without issues.
Please could you be specific about what problems you are seeing, for example, what do you mean by 'crash'.
You can certainly raise issues on SO, but if they appear to be specific to the windows port, please raise a ticket at: https://github.com/sdarnell/meteor
The only difference between Win7 and Win8 meteor, is that the installer sets the Win7 compatibility mode for the node.exe executable on Windows 8.
There are also relatively few differences between the windows port of meteor and the official linux/mac release. So there is a possibility that the issue is either environmental (e.g. you have different things installed on the two machines), or it may even be a core issue that just happens to appear more often Win7 due to timing issues (there was a case of this in 0.6.3).