TF_E_PDETS: problem with .dat files in TF

Hi guys,

I'm trying to TF_GetHandle() with TurboFloat. The .DAT file is in the same folder as the application executable and TurboFloat.dll. But I'm always getting 0.

I tried to specify the full path with TF_PDetsFromPath() but it always return a TF_E_PDETS error code (8).

Full read/write access is given to the file. No permission issues.

(When I tried to use my actual .DAT file (pre-TF era) to start the TF Server it always refused. I downloaded afresh the .DAT file (post-TF era) from LimeLM for the desired version and then TF Server started. But either using the previous .DAT file (actually used with TurboActivate) or the freshly downloaded one that helped starting TF Server, this is not working. I'm thrown always the same error.)

I have no clue of what to try or to do to fix that.

Thank you very much for your help an input on this,Alexandre Leclerc

PS: Thank you for the new DateTime picker in the Web Interace!

PS: Thank you for the new DateTime picker in the Web Interace!

You're welcome. I'm glad you like. More usability improvements are coming down the pipe now that a majority of the work for TurboFloat has finished.

I downloaded afresh the .DAT file (post-TF era) from LimeLM for the desired version and then TF Server started.

Right -- that's the solution to the problem. When you re-download the TurboActivate.dat file it will work with TurboFloat, TurboFloat Server, and TurboActivate (even the old versions).

We had to make internal changes to the TurboActivate.dat file -- that's why the old ones don't work with TurboFloat. But the new *.dat files are completely backward compatible with the old versions of TurboActivate. So you can just use the new TurboActivate.dat files across all your product combinations.

I'm thrown always the same error

We'll, if you use the new TurboActivate.dat file then what do TF_PDetsFromPath() return? Does it succeed? If it succeeds and TF_GetHandle() is still returning 0, then you might be passing in the wrong Version GUID into TF_GetHandle().

Hi Wyatt,

I don't know what I did wrong yesterday, but this morning I deleted the previous .DAT and put in place the new one (instead of downloading over the previous) and it just worked. No more problems at all.

Thank you for your answer: it made me test again with more precautions and it just worked! I should have tried that yesterday because I was pretty sure it was a .DAT issue again.

Thanks again and best regards!Alexandre

Great -- I'm glad to help.

Reply
Discard post