oneAPI Registration, Download, Licensing and Installation
Support for Getting Started questions related to download, Installation and licensing for Intel oneAPI Toolkits and software development tools.
1446 Discussions

move PS XE FORTRAN 2019 to new Win11 machine impossible, 2016 is running but threatens extinctione

mjp1747
Novice
2,452 Views

Have Fortran 2016 running on Win10 machine.  Tried to move onto new Win11 HP with plenty of SSD drives.  I have license for 2020 but that always fails to install after splash screen disappears.  I could not get VS 2019 earlier version (only most recent) and that appears to be a known bug.  So my 2020 license is useless.  

I went back to 2016 FORTRAN (and VS 2013) for which I have a older license.  It was near impossible to get a working copy of VS 2013 Community without paying $$$$ in licensing.  That is ridiculous, since I already owned a copy for my Win10 install.  Finally got VS2013 installed.

Now my command line fortran works (yeah!) using v16.0.1.146 but threatens to cut me off in 30 days.  How/where to I put in the license key number Kxxx-NBX7xxxx ?

 

thanks, mjp1747

Labels (1)
0 Kudos
1 Solution
mjp1747
Novice
2,146 Views

Arpan,

 

OK, we can close this out.  I just installed oneAPI the the classic compiler works just fine

and seem stable!   I will give up on my legacy compilers and move on....

 

Michael

 

 

 

 


F:\My Drive\J-codes\Cloud-J\CJ_v80c>ifort CJ80c.f90 *.obj /check:bounds
Intel(R) Fortran Intel(R) 64 Compiler Classic for applications running on Intel(R) 64, Version 2021.10.0 Build 20230609_000000
Copyright (C) 1985-2023 Intel Corporation. All rights reserved.

Microsoft (R) Incremental Linker Version 14.29.30151.0
Copyright (C) Microsoft Corporation. All rights reserved.

View solution in original post

0 Kudos
13 Replies
ArpanB_Intel
Moderator
2,432 Views

Hi, we have contacted you internally to gather some information. Please check your inbox and respond to us internally as the information is non-public in nature.


0 Kudos
mjp1747
Novice
2,393 Views

Dear ArpanB_Intel,

 

I sent you  what you asked for on the internal respons.

Is there any additional info that you need? 

 

thanks for your help, mjp1747

0 Kudos
ArpanB_Intel
Moderator
2,379 Views

Michael, do you have a license file for the license serial number? If you do, please delete the older license files from the path: C:\Program Files (x86)\Common Files\Intel\Licenses and put the academic license file there.


0 Kudos
mjp1747
Novice
2,370 Views

Arpan, thanks for getting back.

 

I found the license in my windows machine with the working compiler, called 'w_NBX7BKJH.lic'

 

It reads as follows

PACKAGE I2007DD7A INTEL 2017.0116 6B4947F7BE04 COMPONENTS="Comp-FW \
Comp-OpenMP Comp-PointerChecker DAAL-W FCompW MKernW" \
OPTIONS=SUITE ck=100 SIGN=93C7B9A65778
INCREMENT I2007DD7A INTEL 2017.0116 permanent uncounted CFD9E3970400 \
VENDOR_STRING="SUPPORT=ACAD \
https://registrationcenter.intel.com" HOSTID="ac2b6ed3ce17 \
dcfe07d2b41e" PLATFORMS="i86_n ia64_n x64_n" ck=117 \
SN=SMSANBX7BKJH TS_OK SIGN=370BCCA21644
PACKAGE I2007DD7A INTEL 2017.0116 6B4947F7BE04 COMPONENTS="Comp-FW \
Comp-OpenMP Comp-PointerChecker DAAL-W FCompW MKernW" \
OPTIONS=SUITE ck=100 SIGN=93C7B9A65778
INCREMENT I2007DD7A INTEL 2017.0116 permanent uncounted ADB76076FF9F \
VENDOR_STRING="SUPPORT=ACAD \
https://registrationcenter.intel.com" HOSTID="ac2b6ed3ce17 \
dcfe07d2b41e" PLATFORMS="i86_n ia64_n x64_n" ck=122 \
SN=SMSANBX7BKJH SIGN=0AD8A3781384
#
# SerialNumber=
#
#
# SerialNumber=
#

 

 

I put it into  C:\Program Files (x86)\Common Files\Intel\Licenses  (which was empty at the time)

rebooted

 

still get:


C:\>ifort
Intel(R) Visual Fortran Intel(R) 64 Compiler for applications running on Intel(R) 64, Version 16.0.1.146 Build 20151021
Copyright (C) 1985-2015 Intel Corporation. All rights reserved.

ifort: NOTE: The evaluation period for this product ends on 23-aug-2023 UTC.
ifort: command line error: no files specified; for help type "ifort /help"

C:\>

 

any further ideas?

can I get the 2020 compiler working?  That would be nice since I bought that one also.

 

Michael

 

0 Kudos
ArpanB_Intel
Moderator
2,323 Views

Michael, could you please share the log files with us:


The default path for a log file for a Parallel Studio XE installation is: %temp%\pset_tmp_PSXE<version>_<username>


We would like to know.


0 Kudos
mjp1747
Novice
2,317 Views

Gladly.  Thanks for the directory, would not have guessed it.

 

The 3 log files for the 3 different versions I tried are attached here.

for PSXE2016 there are four subdirectories with a sequence of times, the last one (the copy below) is in \2023.07.24_16.03.36_00001578

 

I am pasting my PATH below just in case ti ai messed up, but I tried to copy it from the Win10 machine that works.

 

thanks, Michael

 


F:\My Drive>Path
PATH=C:\Program Files (x86)\IntelSWTools\parallel_studio_xe_2016.1.051\compilers_and_libraries_2016\windows\bin\intel64;C:\Program Files (x86)\IntelSWTools\parallel_studio_xe_2016.1.051\compilers_and_libraries_2016\windows\redist\intel64\compiler;C:\Program Files (x86)\IntelSWTools\parallel_studio_xe_2016.1.051\compilers_and_libraries_2016\windows\redist\intel64_win\compiler;C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\IDE\CommonExtensions\Microsoft\TestWindow;C:\Program Files (x86)\MSBuild\12.0\bin\amd64;C:\Program Files (x86)\Microsoft Visual Studio 12.0\VC\BIN\amd64;C:\Windows\Microsoft.NET\Framework64\v4.0.30319;C:\Program Files (x86)\Microsoft Visual Studio 12.0\VC\VCPackages;C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\IDE;C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\Tools;C:\Program Files (x86)\HTML Help Workshop;C:\Program Files (x86)\Microsoft Visual Studio 12.0\Team Tools\Performance Tools\x64;C:\Program Files (x86)\Microsoft Visual Studio 12.0\Team Tools\Performance Tools;C:\Program Files (x86)\Windows Kits\8.1\bin\x64;C:\Program Files (x86)\Windows Kits\8.1\bin\x86;C:\Program Files (x86)\Microsoft SDKs\Windows\v8.1A\bin\NETFX 4.5.1 Tools\x64\;C:\Program Files (x86)\IntelSWTools\parallel_studio_xe_2016.1.051\compilers_and_libraries_2016\windows\mpi\intel64\bin\..\..\intel64\bin;C:\Program Files (x86)\IntelSWTools\parallel_studio_xe_2016.1.051\compilers_and_libraries_2016\windows\redist\intel64\tbb\vc_mt;C:\Program Files (x86)\IntelSWTools\parallel_studio_xe_2016.1.051\compilers_and_libraries_2016\windows\redist\intel64\mkl;C:\Program Files (x86)\IntelSWTools\parallel_studio_xe_2016.1.051\compilers_and_libraries_2016\windows\redist\intel64\compiler;C:\Program Files (x86)\IntelSWTools\parallel_studio_xe_2016.1.051\compilers_and_libraries_2016\windows\redist\intel64_win\daal;C:\Program Files (x86)\IntelSWTools\parallel_studio_xe_2016.1.051\compilers_and_libraries_2016\windows\redist\intel64_win\tbb\vc_mt;C:\Program Files (x86)\IntelSWTools\parallel_studio_xe_2016.1.051\compilers_and_libraries_2016\windows\redist\intel64_win\compiler;C:\Program Files (x86)\Common Files\Intel\Shared Libraries\redist\intel64_win\mpirt;C:\Program Files (x86)\Common Files\Intel\Shared Libraries\redist\ia32_win\mpirt;C:\Program Files (x86)\Common Files\Intel\Shared Libraries\redist\intel64_win\compiler;C:\Program Files (x86)\Common Files\Intel\Shared Libraries\redist\ia32_win\compiler;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Windows\System32\OpenSSH\;C:\Program Files\MATLAB\R2023a\bin;C:\Program Files\MATLAB\R2020a\bin;C:\Program Files\MATLAB\R2012b\bin;C:\Program Files (x86)\Windows Kits\10\Windows Performance Toolkit\;C:\Program Files (x86)\Windows Kits\8.1\Windows Performance Toolkit\;C:\Program Files\Microsoft SQL Server\110\Tools\Binn\;C:\Program Files (x86)\Microsoft SDKs\TypeScript\1.0\;C:\Program Files\Microsoft SQL Server\120\Tools\Binn\;C:\Users\Michael Prather\AppData\Local\Microsoft\WindowsApps

F:\My Drive>

0 Kudos
ArpanB_Intel
Moderator
2,304 Views

Michael, thank you for sharing the log files with us. We will check them and share our findings soon.


0 Kudos
mjp1747
Novice
2,238 Views

ArpanB,

 

Morning, did you find any clues in the log files?

VS2013 seems to be running OK.

 

Michael

 

0 Kudos
mjp1747
Novice
2,176 Views

Dear ArpanB @ Intel,

 

Do you have any idea why my 2016 or 2020 Intel PSXE will not work on my new windows 11 desktop?

It has installed and worked seamlessly on my aging HP desktop and new Surface Pro (both Win 10)

I would even consider paying for a new Fortran compiler so I can move fully to the new desktop, but am unsure that it would work.

Please do not give up on me,  Michael

 

OS Name Microsoft Windows 11 Home
Version 10.0.22000 Build 22000
Other OS Description Not Available
OS Manufacturer Microsoft Corporation
System Name PRATHER5
System Manufacturer HP
System Model HP Pavilion Desktop TP01-2xxx
System Type x64-based PC
System SKU 20W69AA#ABA
Processor 11th Gen Intel(R) Core(TM) i7-11700 @ 2.50GHz, 2496 Mhz, 8 Core(s), 16 Logical Processor(s)
BIOS Version/Date AMI F.10, 7/29/2021
SMBIOS Version 3.3
Embedded Controller Version 112.06
BIOS Mode UEFI
BaseBoard Manufacturer HP
BaseBoard Product 8860
BaseBoard Version A (SMVB)
Platform Role Desktop
Secure Boot State On
PCR7 Configuration Elevation Required to View
Windows Directory C:\Windows
System Directory C:\Windows\system32
Boot Device \Device\HarddiskVolume5
Locale United States
Hardware Abstraction Layer Version = "10.0.22000.1696"
User Name Prather5\Michael Prather
Time Zone Pacific Daylight Time
Installed Physical Memory (RAM) 32.0 GB
Total Physical Memory 31.7 GB
Available Physical Memory 24.0 GB
Total Virtual Memory 36.5 GB
Available Virtual Memory 28.6 GB
Page File Space 4.75 GB
Page File C:\pagefile.sys
Kernel DMA Protection On
Virtualization-based security Not enabled
Device Encryption Support Elevation Required to View
Hyper-V - VM Monitor Mode Extensions Yes
Hyper-V - Second Level Address Translation Extensions Yes
Hyper-V - Virtualization Enabled in Firmware Yes
Hyper-V - Data Execution Protection Yes

0 Kudos
ArpanB_Intel
Moderator
2,167 Views

Michael, please note that Windows 11 is a latest OS release and is not tested to be compatible with our Intel® Parallel Studio XE compiler suites. Intel® Parallel Studio XE 2016 or Intel® Parallel Studio XE 2020 is not supported on Windows 11. It might work on some systems, but it also might not work. However, if it does not work, Intel® will not be able to support you further on the issue.


In terms of your license, we see it is a Academic license type which was supposed to end on 1/16/2017(MM-DD-YYYY). Could you confirm the version/update of Intel® Parallel Studio XE 2016 release you are using? We would need it to check the build date of the product.


0 Kudos
mjp1747
Novice
2,156 Views

Dear Arpan,

 

OK, we are getting somewhere (but not the most wonderful place).  So, D__n, my old compiler will likely just not work on Win11.

So be it.  The version that I get with 'ifort' is below.  It works fine on my Surface Pro and this old HP Desktop (i7-6700 CPU @ 3.40GHz, 3408 Mhz, 4 Cores).

I will leave the legacy PSXE on the legacy machines and try to run one API classic compiler - that should meet my needs.  Should have warned me about Win11 and the earlier PSXE's.

 

thanks for babysitting, will not pester you more if the one API works.

Michael

 

Intel(R) Visual Fortran Intel(R) 64 Compiler for applications running on Intel(R) 64, Version 16.0.1.146 Build 20151021
Copyright (C) 1985-2015 Intel Corporation. All rights reserved.

0 Kudos
mjp1747
Novice
2,147 Views

Arpan,

 

OK, we can close this out.  I just installed oneAPI the the classic compiler works just fine

and seem stable!   I will give up on my legacy compilers and move on....

 

Michael

 

 

 

 


F:\My Drive\J-codes\Cloud-J\CJ_v80c>ifort CJ80c.f90 *.obj /check:bounds
Intel(R) Fortran Intel(R) 64 Compiler Classic for applications running on Intel(R) 64, Version 2021.10.0 Build 20230609_000000
Copyright (C) 1985-2023 Intel Corporation. All rights reserved.

Microsoft (R) Incremental Linker Version 14.29.30151.0
Copyright (C) Microsoft Corporation. All rights reserved.

0 Kudos
ArpanB_Intel
Moderator
2,132 Views

Michael, thank you for sharing the update. We are glad that the issue is resolved.


If you have any further queries, please post a new question as this thread will no longer be monitored by Intel®.


0 Kudos
Reply