v3.4.6 causing issuesSolved

I updated everything in my two applications with the current v3.4.6. I was running v3.4.4 previously. I allow one client a virtual machine license and that ended up having an issue with v3.4.4 (as related here in this forum), which is why I upgraded.

After upgrading to v3.4.6 I found in testing that my applications would not start. They compiled fine and I included the v3.4.6 TurboActivate.exe and the TurboActivate.dll files in the same folder with my application executable as always. I also "updated" my TurboActivate.dat file by downloading a new one just to be certain everything was up to date. Upon debugging using Delphi XE , I would get an access violation message while stepping through my code and reaching the source code file (my Main form) which has the LimeLM activation (isGenuine, etc.) in it.

When I reverted back to v3.4.4 everything worked normally again on my development machine. Of course, my one client will still end up having issues with his Virtual Machine unless I can get the v3.4.6 working properly.

I don't see anything in this forum which indicates anyone else is having an issue but neither of my two commercial applications will start up with v3.4.6 while they will with v3.4.4.

Any ideas?

J.B. Ferguson

Are you using the correct files? For example, access violation errors will occur if you try to use x64 dlls with x86 exe. So, if your exe is x86 (which it probably is if you're using an older version of Delphi), then you must use the x86 versions of TurboActivate.dll and TurboActivate.exe.

I'm sure I was using all the correct files, but I will try again today.

I can understand getting access violations with the incorrect files but the applications would not even start (although I'm sure some parts of them got loaded into memory because I would have to reboot to clear it out before I could try compiling it differently.)

I will try again and will advise.

Wyatt...

The incorrect files appears to have been the issue. Although I have not yet compiled these two applications with any 64 bit libraries of any type (these are specialized applications for several clients who are not yet running 64 bit systems, hence running DXE instead of DXE7 as I am with other newer applications), I must have somehow had a brain incident where I grabbed the wrong files.

Thanks for clearing my head and pointing me in the right direction.

Great, I'm glad it was an easy fix. 🙂