Hi Steve,

> You got it.
>
> So I would use 'my' log file ... which I suppose would need to be named on
> a version-based schema (so that the installer knew *which* to read, in the
> event there was one or more left undeleted... although a deletion would
> normally be the last step, if all converters were successful).
>
> Clarify for me if you would: "you can use the same function to handle
> this" - you mean that you can use the 'Handle text Fie..' feature for both
> read & write, yes?
>
> It occurs to me that the program in question *does* have a lightly-used
> INI file... I could even create a new 'section' in there for the version
> (eg "[File Conversion v5.501]") and use the single item entry (eg
> "LastConvertStep=3").
>
> Any reason occur to you why not to use the (SB) INI functions as opposed
> to the (SB) 'Handle Text File..'.. functions?
>
> Thanks for the consult <g>



I suggested to use the "Handle Text File Operation..." because with this
function you are not bound on a specific format. And yes, you can use
it to both read/write.

But if you plan to use the INI format (good idea)

[File Conversion v5.501]
LastConvertStep=3

then of course, the "Edit INI File..." and "Get INI Value..." script
functions work perfect.

At the end of the conversion process (if all converters were successful),
use the "Delete File(s)..." function to remove the converter .log. At the
beginning of your installation, use "If File/Folder Exists..." to check for
the converter .log. If it is found, you know that one of the previous
converters failed.

Friedrich

--
Friedrich Linder
Lindersoft
www.lindersoft.com
+1.954.252.3910

SetupBuilder "point. click. ship"
Create Windows Vista ready installations in minutes

-- Official Comodo Code Signing and SSL Certificate Partner