Dalai wrote:Shalimar wrote:However that really does not solve the problem for many users that don't want to have to rebuild a custom installer every time you release an updated version.
You can still use the old installer if needed. Every time a new version is released you can edit the install.inf (and optionally recreate the archive). If you need to use the new installer and make it easier for yourself, you might want to give my script a shot
that I posted here (the post is in German, the script itself is in English). The script can automate the creation of TC setups, without the need to edit any TC settings (ZIP compression set to 0), copying any files (SFX) or any other annoying stuff.
Regards
Dalai
Hi Dalai
I'm aware of that as well.. however that again really is not the point. which has been brought up by others as well more than once.
Ultimately the addition of a switch and/or auto override by having an ini in the same dir will be the best solution regardless since it gives the most choices and also eliminates most if not all of the added changes needed not only for the ini but also for the package and/or naming of the package as well.
This is particularly good for those situations where it's all to be dedicated unattended installs via scripting. The file name changing with each version is easy enough to adapt for in scripting so no editing is needed for updated versions. Just a straight dump of the new installer into X location and poof all is good that way. However with the current setup system that simply is not possible and the idea of an unattended install is simplicity in the end for the most part. Therefore aiming for a solution that eliminates added work after it is implemented is the best goal IMO
If it was not and I was going through all of the work w/each release of remaking the installer I'd instead just rework it to use 7zip's sfx instead and an semi-auto creation setup... (Added bonus as well of being much smaller end file though size is not that big a deal on this scale usually). But again that is not the end goal since that would be more limited to my particular setups here and would not be as easily adopted by everyone that downloads TC.
A change in the code directly by Christian however to adopt the 2 changes necessary for those options would achieve that and in the end would make tc's implementation / distribution easier for those users beyond the basic manual install. (And also bypass this bug of the current setup not behaving well with one of the most common unattended install methods TC will ever be used with which in turn impacts a large % of those using TC.. which are in my experience more power users and techs than mom/pop users. Though I typically install TC by default on virtually every system I work on and/or build..)
The really unusual part is TC of all the various apps I've worked with and even tested for unattended install is the only one so far to throw these sorts of errors with this unattended method which like I said before is insanely common since it's a M$ system built into winbloze install/setup for many many years now.
Also don't get me wrong.. i appreciate your response and your script offer as well. But ultimately that is not the best end goal/solution in the long run.
