Since they’re hard to find on-line, and sometimes I need them when not having access to my collective browser or email history:
- http://downloads.smartbear.com/AQALicenseManager.exe
- http://downloads.smartbear.com/AQtimeDemo.exe
- http://downloads.smartbear.com/AQtime824.exe
- http://support.smartbear.com/troubleshooter/?prod=Licensing
Notes:
- The AQTimeDemo.exe is the same as the latest AQTime###.exe (functionality depends in license).
- The installation from Windows Explorer sometimes fails with the below message. Installation from the command-prompt works, but you need to run it from an Administrator command-prompt:
---------------------------
E:\TEMP\AQtime824.exe
---------------------------
Windows cannot access the specified device, path, or file. You may not have the appropriate permissions to access the item.
---------------------------
OK
---------------------------
To get going for my special case, I watched some sample videos (which I did get to work in Internet Explorer but not in Chrome forty-something):
- Profiling Windows Services With AQtime.
- AQtime: Attaching to Process (showing the same service from the first video).
- All: AQtime Screencasts and Videos.
I needed it to do some profiling comparisons of services running under different configurations.
The catch was that the startup of the services took a huge time and was not relevant for the profiling result. So I had to skip the solution from the first video and resort to the second one:
- Open the executable
- Ensure the mode is set to “Normal” (not “Service”!)
- Select a profiler (in this case Coverage)
- Run -> Attach to Process
- Check “System Processes” checkbox so the services show up
- Click the “Get Results” button (camera icon) to get the results while the service is still running.
- AQTime cannot get the results upon program termination, as the service keeps running in the background.
- The “Stop Profiling” button (red circle with cross line) will kill the service (I don’t like that as restarting the service takes tens of minutes)
Always compile with debug info. For Delphi executables, ensure you have your debug information setup as follows:
- Compiling:
- Enable “Stack frames”.
- Enable “Debug information”.
- Enable “Local symbols”.
- Enable “Use debug .dcus”.
- Linking:
- Enable “Debug information”.
- Enable “Place debug information in separate TDS file” (older Delphi versions call this “Include TD32 debug info” which are included in the .EXE and work fine: no need to strip it into a separate TDS file).
- Packages:
- Disable “Link with run-time packages”.
Running
- Ensure you have the License Manager Service running at least locally, and if you have a license manager machine also on that machine:
This will enable this local web page: http://localhost:1947/ to view your license usage provided by 3rd party HASP.
- Ensure you have Intel SpeedStep disabled (usually you need to do this in the BIOS, though some Windows versions allow you to specify this in PowerCfg.cpl as well). When you have done that, you can ignore the below warning.
--------------------------- AQtime --------------------------- Your processor supports the SpeedStep technology. We recommend that you disable the dynamic CPU frequency mode, because the timing results may be inaccurate if this mode is active. Continue profiling? --------------------------- Help No Yes ---------------------------
- On many systems you can safely ignore this message as well:
--------------------------- AQtime --------------------------- You have selected a counter other than Elapsed Time. Using this counter may cause a crash or the Blue Screen of Death (see Help for details). Do you want to continue? --------------------------- Help No Yes ---------------------------