New ContributorI have downloaded the install archive several times, un-installed, and re-installed Questa, and when I start the program, it gives me a command shell and exits out. Here is the install log. I need assistance ASAP as it is for an important deliverable.
Sincerely,
David
New ContributorWindows IP Configuration
Host Name . . . . . . . . . . . . : DJDEADNUTS
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
Ethernet adapter Ethernet:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Realtek USB GbE Family Controller
Physical Address. . . . . . . . . : 64-C9-01-B7-48-DF
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IPv6 Address. . . . . . . . . . . : fdf3:3d70:bcf6:c006:4197:b02a:b5c6:ed4f(Preferred)
Temporary IPv6 Address. . . . . . : fdf3:3d70:bcf6:c006:c5d0:80a7:338d:e55f(Preferred)
Link-local IPv6 Address . . . . . : fe80::c845:ba1b:95fd:e140%22(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.68.63(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.252.0
Lease Obtained. . . . . . . . . . : Sunday, March 3, 2024 9:22:45 PM
Lease Expires . . . . . . . . . . : Monday, March 4, 2024 12:22:56 AM
Default Gateway . . . . . . . . . : 192.168.68.1
DHCP Server . . . . . . . . . . . : 192.168.68.1
DHCPv6 IAID . . . . . . . . . . . : 375703809
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-2A-BC-1D-B1-8C-1D-96-CC-3F-3F
DNS Servers . . . . . . . . . . . : 75.75.75.75
75.75.76.76
NetBIOS over Tcpip. . . . . . . . : Enabled
Super ContributorDone sending the newly generated license file to your email personally. Let me know if any further update or concern.
New ContributorIt is working now. I had to change the setx command to reference the exact file name, not just license.dat. This was never specified in the instructions on the Licensing Center. Thank you for your time.
Super ContributorI think both command prompt (setx) and Edit the system environment variables should work. Most probably the problem at the license.
Btw, I’m glad that your question has been addressed, I now transition this thread to community support. If you have a new question, Feel free to open a new thread or login to ‘https://supporttickets.intel.com’, view details of the desire request, and post a feed/response within the next 15 days to allow me to continue to support you. After 15 days, this thread will be transitioned to community support. The community users will be able to help you on your follow-up questions.
Occasional ContributorI had the same problem with Questa.
For the current poster it now probably works because now there has been given a "Guaranteed-to-work reality" through the effort of the Intel support engineer.
In my case, I had the same command shell popping up and out without a Questa starting up. I went through the same of obtaining a license through the licensing self-center to no avail.
Then, I thought, let's be clever and pull out an old fashioned DOS trick (no not the cyber attack; the disk operating system instead). And made a batch file that set the environment variable and would then start the Questa executable. This miraculously worked!
For reasons, I later ununstalled that version of Quartus and Questa and went back to version 20.1.1 for both, then called ModelSim.
Yet again later, I installed the latest again. Including the latest of Questa. No luck running Questa, same deal with the command shell. Then I thought, let's create the batch file again since that was a workable solution. Only to find out this trick no longer worked for me, no matter what I did. Given my prior experience and given this topic, it looks and feels like there is some sort of "progressive learning" at work.
Whenever I decide to install Questa again, I may request support to have this "guaranteed-to-work reality" through supplying system name and MAC to Intel.
