Setups received through this will have co-branded version as 3.0.18.X, where X is build count which keeps incrementing for every new build.
All the binaries used in this setup are the same, which were released with version 3.0.18.309. Any future updates will be available to these setups also and will maintain co-branded status of it.
64-setups received through this won’t be compressed, so size of those will be approximately 49.7 MB (52,162,808 bytes). Just in case you wonder why 64-setup size has increased through this. We will rectify this by monday or before.
Thanks
-umesh
EDITED on 23-Feb-2008
64-bit setup size received by users should be around 30 MB, it has been fixed.
Wow, how did you manage to make this all automated? The script that makes this would have to be able to read and recompile the source of cfp to include the new skin during installation.
Hi Ewen,
As now user can export skin as .skn format. In future we may provide an optional input during signup to take this .skn file, which will be built into setup and upon installation will be the default theme.
As we are polishing the skinning tool and also CFP for that, you can expect this feature by March end.
So you should be able to have everything customized not just name.
I have a question about Co-Branding Comoodo Firewall Pro and my question is: when the firewall is is updated will it still be Co-Branded or will it have to be reco-branded again and any ideas?
Ive posted this question in Help for v3, No response lol… Anyway:
When a new update comes for CFP 3, and you have your Co-branded CFP installed, Will you need to co-brand again? What if auto updates don’t work and you need to uninstall and reinstall new version?
As far as if you manually uninstall and install CFP, that I don’t know. It would probably be dependent on a registry key(s) or files in one of the user profile directories.