> > > Ok, I think I understand what you are saying. In other words, use
> > > something like Firebird0941Setup.exe and
> > > InterBase6016OpenEditionSetup.exe, right?
> >
> > Yes
>
> Please don't. Automatic archiving procedures would then have to be
> modified according to the version of the installation script. I think
> that if one needs to store different versions of the same exe, he/she
> may well create subfolders and go with it.
> I dare to say that, on windows, the install file name should be named
> nothing else than "setup.exe".
> My 0.02€

And there we start the problem. The last thing it should be called is simply
"setup.exe". Since windows is so crap at maintaining file detail information,
we MUST have some means of identifying the program by the file name.

Do a search for setup.exe on your machine!!! I came up with 35 I could not
tell you what many of them were, let alone which one to use.

If automatic archiving is overwriting a good version with an untested version
then good luck to you. None of this should be automatically archived, it
should be controlled in a recoverable manor. Some of us are required to meet
ISO9002 standards and that almost dictates identifiable files.

--
Lester Caine
-----------------------------
L.S.Caine Electronic Services