Is TA_PDetsFromPath()
succeeding?
Are you using the correct TurboActivate.dat? Download it again, and make sure the .dat you download matches the GUID you use.
When running the example.c it is failing to get handle.
I have checked to see if the dat is loading.
I have also checked my guid and dat file. They are still working in a different code.
I have attached the part of the code where it is failing.
if(TA_PDetsFromPath(L"TurboActivate.dat") == TA_OK)
printf(".dat loaded\n");
taHandle = TA_GetHandle(_T("555My555Guid555"));
if (taHandle == 0)
Is TA_PDetsFromPath()
succeeding?
Are you using the correct TurboActivate.dat? Download it again, and make sure the .dat you download matches the GUID you use.
Yes, TA_PDetsFromPath()
is succeeding.
I have tried redownloading the dat file.
Everything works fine for us. Much more information is needed. If you're getting compiler warnings, don't ignore them.
It's either:
1. Wrong .dat file (doesn't match the GUID).
and/or
2. The GUID being passed in is wrong. Either it's blatantly wrong (i.e. copy&paste directly from LimeLM – don't try to transcribe it or read-it-off) or you're using the wrong char
-type. Namely, you're trying to use char*
on Windows or wchar_t*
on Unix (those are wrong).
this line:
taHandle = TA_GetHandle(_T("18324776654b3946fc44a5f3.49025204"));
gives this warning and error:
TurboActivate.c
TurboActivate.c(103): warning C4133: 'function': incompatible types - from 'char [32]' to 'STRCTYPE'
TurboActivate.c(271): warning C4133: 'function': incompatible types - from 'char [35]' to 'STRCTYPE'
Microsoft (R) Incremental Linker Version 14.33.31629.0
Copyright (C) Microsoft Corporation. All rights reserved.
/out:TurboActivate.exe
TurboActivate.obj
C:\Users\Admin\Downloads\TurboActivate\bin-windows\x86\additional\linker\TurboActivate.lib
C:\Users\Admin\Desktop\Wear>TurboActivate
.dat loaded
Failed to get the handle for the Version GUID specified. Make sure the Version GUID is correct, and that TurboActivate.dat is in the same folder as your app.
Or use TA_PDetsFromPath() to load the TurboActivate.dat first before getting the handle.
we tried:
typedef const wchar_t * STRCTYPE;
const wchar_t * guid = (const wchar_t*)_T("XXXXXXXXXXXXXXXXXXXXXXX.YYYYYYYYYYYYYYYYYYYYYYYYYYYY");
and we get:
TurboActivate.c
TurboActivate.c(274): warning C4133: 'function': incompatible types - from 'char [35]' to 'STRCTYPE'
Microsoft (R) Incremental Linker Version 14.33.31629.0
Copyright (C) Microsoft Corporation. All rights reserved.
/out:TurboActivate.exe
TurboActivate.obj
C:\Users\Admin\Downloads\TurboActivate\bin-windows\x86\additional\linker\TurboActivate.lib
C:\Users\Admin\Desktop\Wear>TurboActivate
.dat loaded
Failed to get the handle for the Version GUID specified. Make sure the Version GUID is correct, and that TurboActivate.dat is in the same folder as your app.
Or use TA_PDetsFromPath() to load the TurboActivate.dat first before getting the handle.
That GUID is not correct. That's the example one. Like I said several times already, copy&paste the GUID from LimeLM.
Rather than trying to piecemeal step-by-step what you need to do on the forum, just follow the articles and examples we've already written: https://wyday.com/limelm/help/using-turboactivate-with-c-plus-plus/
TurboActivate.c(103): warning C4133: 'function': incompatible types - from 'char [32]' to 'STRCTYPE'
TurboActivate.c(271): warning C4133: 'function': incompatible types - from 'char [35]' to 'STRCTYPE'
OK. Don't ignore those warnings (I have no idea what is is on those lines, but again, read what I wrote above about incompatible string types):
2. The GUID being passed in is wrong. Either it's blatantly wrong (i.e. copy&paste directly from LimeLM – don't try to transcribe it or read-it-off) or you're using the wrong
char
-type. Namely, you're trying to usechar*
on Windows orwchar_t*
on Unix (those are wrong).
Long story short: follow the example article and example code. Don't skip any step.
Howdy Wyatt,
Thanks for the timely responses. We are using our GUID, we just did not paste it on the forums. Was not sure if it is a security issue. We will go back over the example article for windows to see if we missed anything.