Thanks Wyatt,
Another question about this. I'd like to use the same method of having the user enter the product key in the installer. I'm taking a look at the TurboActivate functions in the InnoSetup tutorial you have. It looks like:
[Files]; Install TurboActivate to {app} so we can access it at uninstall time; Also, notice we're putting the TurboActivate files at the top of the file; list. This is so that if you're using "SolidCompression=yes" your installer; can still start relatively quickly.Source: "TurboActivate.dll"; DestDir: "{app}"Source: "TurboActivate.dat"; DestDir: "{app}"
If we're doing this with TurboFloat, should we use TurboFloat.dll rather than TurboActivate.dll? The reason I ask is because it looks like later on in the example, you are calling a function from within that library. I'm wondering if TurboFloat.dll contains those same functions. Here is what I'm referring to specifically:
// functions for activationfunction IsActivated(versionGUID: WideString): longint;external 'IsActivated@files:TurboActivate.dll,TurboActivate.dat cdecl setuponly';
function CheckAndSavePKey(productKey: WideString; flags: UINT): longint;external 'CheckAndSavePKey@files:TurboActivate.dll,TurboActivate.dat cdecl setuponly';
function Activate(): longint;external 'Activate@files:TurboActivate.dll,TurboActivate.dat cdecl setuponly';
For TurboFloat, I'm thinking that I would only use "CheckAndSavePKey" but I may be wrong. Are all of those functions still relevant for setting up an installer for TurboFloat? Any help you can provide is appreciated.
Thanks,Arie