ContributionsMost RecentMost LikesSolutionsRe: Intel Visual FORTRAN support I just compiled our large 64-bit application using Visual Studio 2015 native C++ and Intel Fortran 2016, under Windows 8.1. I was able to start the application under AQTime Pro 8.24, run it, and gather and view Performance Profiler information. So on the surface it seems towork fine and support these two compilers, although of course neither is listed as being officially supported. As I said, we have been using AQTime to profile Intel Fortran code for some years now. Works well. (We used to use Rational Purify and Quantify, but all their tools crash on encountering ANY Fortran code, with no support ever planned) The report does include some methods, such as __acrt_unlock and _fread_nolock_s, which I guess are usually excluded, but that is minor. I have not tried other AQTime profilers such as the allocation profiler. Also integration into the Visual Studio 2015 IDE is probably absent, but that is minor, you just start your application up under AQTime. Re: Intel Visual FORTRAN support We compile some of our code using Intel Fortran 12, and AQTime now works fine with it. It used to crash during profiling, but I sent some DLLs to support and they fixed it right up. So it is close! We are about to upgrade to Intel Fortran 2016, so I guess we shall if it still all works. Re: Windows 8.1Albert, I am able to use the allocation profiler successfully under Windows 8.1 on a large 64-bit C++/Fortran application. It does make our application crash on any strcat call and one other method that makes use of a lot of Windows API structures. I did take this up with SmartBear, but they were convinced the issue was not on their side while I was convinced it was. Fortunately not a lot of code was involved, and I was able to change/simplify the code so it now runs under the allocation profiler without crashing.Re: Windows 8.1I am using AQTime 8.20.960.7 under Windows 8.1 (64-bit, Build 9600, up to date). AQTime seems to work fine now, I was using the performance profiler on a 64-bit application and got results fine. Thank you for fixing it! (The allocation and resource profilers cause a crash, but this was also experienced in previous versions of AQTime with our application, and is of lesser interest to us, though we have taken it up with SmartBear. Some day I shall have time to get to the bottom of it. Maybe. I can work around the issue and get the allocation profiler to work, so I think Windows 8.1 is supported now.) Re: Windows 8.1When I recently renewed our licenses, I raised this issue with them and they said on 22 Jan 2014: "We are expecting to support Windows 8.1 in the next month or so. Please stay tuned." Re: Windows 8.1Nope. I asked and also asked support to notify me when support does become available.Re: Windows 8.1Indeed so. AQTime crashes under Windows 8.1 and I sent in a crash report and they told me this: "The crash is caused by the fact that you run AQtime on Windows 8.1. Currently, AQtime 8.10 doesn't support Windows 8.1 officially. The support should become available in the next product update. Meanwhile, I suggest that you profile your application on Windows 7 or Windows 8.0." Re: Windows 8.1Unfortuantely when I start the profiling run, aqtime crashes and submits a dump file. I chose to send it and will see what SmartBear support has to say about that. However, I also have a version running under Windows 7 and there the AQTime 8.10 update seems to run fine. So it is possible that the Windows 8.1 problems may be more than the Sentinel licensing related. I shall update this post when I hear back. I have had crashes in AQTime before and they usually fixed them quite quickly.Re: Windows 8.1I just recently upgraded from Windows 8 to Windows 8.1 (part of required me to run "haspdinst.exe -purge") and when I ran AQTime 8 today it was unable to obtain a license (using a local license file). I ran the AQTime8 installer and chose the repair option and it told me: "This driver cannot be used due to compatibility issues: Hardlock Device Driver for Windows x64. Aladdin Knowledge Systems Ltd." So I decided I would download and run the latest AQTime810.exe installer. It did not give me any error messages and appears to work. After running that, I was able to run AQTime 8.10. SmartBear support also told me this (but I did not have to do it, likely only applicable if you use older AQTime versions): "The Sentinel License Manager service version 12.49 and licensing system modules AQtime installs, does not support Windows 8.1 Download and Install the latest SmartBear License Manager utility: http://downloads.smartbear.com/SmartBearLicenseManager.exe This utility installs the License Manager service version 15 which uses the HASP licensing system v6.60, that seems to work fine on Windows 8.1 (our R&D team have tested it)." I love AQTime, the best profiler ever! And I have tried them all! Just to confirm, if I go to the page "http://localhost:1947/_int_/diag.html" it says: License Manager Version 15.0 Build 36539