Contributions
Re: 8.70 License Failure
Thanks Alex, I had already tried raising a support ticket, but that seemed to go wrong (no confirmation email). I probably did something wrong. I tried again and got an instant confirmation. They gave me a new registration number which did allow me to get it going again. During activation I got this: It seemed familiar, so I think I may have accepted it before under Windows 8.1 on the machine. Knowing it was difficult, I recall I returned the license under Windows 8.1 and re-activated it on Windows 10 without any problem. If that is the case, I don't think it was creators update that broke it. Recently I concluded my WiFi card was faulty and I had it replaced under warranty. If the hasp/gemalto system looks at the MAC addresses of all the network hardware, I could see it breaking it. I wonder whether re-configuring the VMWare Workstation network adapter might also break it. I think that my returned license could only be activated with my old WiFi card installed and that was in the possession of Lenovo It looks as if recent versions of Windows are always seen as virtual machines. That means that once you have activated a node-locked license under Windows 10 it will be locked to the hardware. You cannot move it to new hardware without help. So, I don't think you need worry about creators update - just don't have a hardware fault! Eric7 years agoPlace AQtime QuestionsAQtime Questions4.4KViews0likes1Comment8.70 License Failure
I think 8.6 was running after the Windows Creators update (but I don't use it heavily, and the update was fairly recent so maybe not.) It was certainly running on this machine under Windows 10 before the creators update. VS2015 told me there was an update to AQTime so I ran it. Licensing failed with message that I am running on a Virtual Machine (which I am not) and a node-locked license does not allow that. I returned the license the long way using the HASP_RUS_AQA route uploading and downloading files. But the new key still would not register. I have all the Hyper-V options disabled in Windows. Now I can only get the license to load if I go into UEFI and disable Intel Virtualization Technology. Doing that prevents VMWare Workstation running 64-bit guests, which is fatal for much development work. I've tried putting 8.6 back, but I have the same problem with that. Having the change the UEFI settings every time I want to use AQTime and the put it back to get on with normal work is just too much of a hassle. It looks as if the node-locked license system is not viable with current releases of AQTime and Windows 10. The floating license system is just too expensive for single-user single-machine use, especially as I would have to run a dedicated machine somewhere with hardware configured specially for the license server. Maybe this is the end of the line for AQTime for me. Has anyone else experienced problems with Windows creators update and AQTime licensing?Solved7 years agoPlace AQtime QuestionsAQtime Questions4.4KViews0likes3CommentsHow to get latest update
On starting AQTime I get a notification that there is an update to 7.10.380.64 available. I am running 7.0.318.64. On the client services web page, the listed products do not include AQTime version 7, but the maintenance subscription reports 305 days left. How do I download the update? I can find no way tonavigate toany equivalent of the original download page which gave me the downloadlinks andmy registration code. Do I have to unregister the installed product andthen requesta new registration code?14 years agoPlace AQtime QuestionsAQtime Questions10KViews0likes2Comments- 14 years agoPlace AQtime QuestionsAQtime Questions3.3KViews0likes0Comments
Re: AQTime 6.40: Integration with RAD Studio 2010
Thanks for letting us know that we are not all going mad. Those of us that posted here seem to have slightly different versions of D2010installed despite all of us running updates 4 and 5. If you should get to a stage where you think you have fixed it but don't have all the D2010 versions at hand, I for one would be happy to try a test installation before a formal release. Eric15 years agoPlace AQtime QuestionsAQtime Questions3.2KViews0likes0CommentsRe: AQTime 6.40: Integration with RAD Studio 2010
I see the same problem as Thomas. I have tried it on my current Windows 7 x64 installation and on the previous Vista 32 bit installation and I get the same result on both. I have also tried completely uninstalling AQTime and re-installing without success. Both the x64 and the x86 installers behave the same. Myversions don't quite matchThomas's because I did not install Update 2: Embarcadero® RAD Studio 2010 Version 14.0.3615.26342 Installed updates: Delphi and C++Builder 2010 Help Update 1 Delphi and C++Builder 2010 Update 4 Delphi and C++Builder 2010 Update 5 (Database Pack Update) C++Builder 2010 Boost Update A red herring is the fact thatthe registry entries for 2010 have two spaces between ther word "Delphi" and the word "and" whereas the D2009 entries have only one space. Changing the D2010 entries to match does not fix it. Eric15 years agoPlace AQtime QuestionsAQtime Questions3.2KViews0likes0Comments