Mmm,
I ask an explanation, I do not like how he behaved in my PC, I unselected all and properly installed SARDU SARDU
I checked better, if user decline the license don't install toolbars.
Force the install is illegal
The explanation is essentially your problem, but if you want me to run tests on my machine, just ask, I will gladly try and help you with troubleshooting the issue .
I simply told you what happened (and happens) on my machine, i.e. there is NO way to install SARDU if not killing the babylon toolbar installer.
You are of course perfectly free to ignore this bug report, or investigate about it/solve it.
As a side note, beside the IMHO not-so-marginal issue about the known Warez release linked to from SARDU, there is a BIG issue (REALLY NOT trivial) about the licensing.
Creative Commons licenses (in general) and particularly the "most restrictive" one you are using, the "Attribution-NonCommercial-NoDerivs 3.0 Unported" are NOT compliant with the GNU GPL under which MOST of the tools you distribute SARDU with are originally released (7-zip, Qemu, Syslinux, grub4dos to make some examples) and obviously also NOT with the much less restrictive license tools like BCDW were released under.
Please, consider how this is NOT (only) "my" opinion, it is the opinion of the actual Creative Commons guys:
http://creativecommons.org/tag/gpl
The basic idea of Creative Commons, offering free copyright tools, is copied from the free software movement. However, CC licenses are not intended to be used to release software, as our FAQ has always said.
One important reason why Creative Commons licenses should not be used to release software is that they aren’t compatible with existing free software licenses, most importantly the GPL from the Free Software Foundation, which is used by over half of free software projects. A commons fractured by legal incompatibilities is a weak commons, and it would be deeply contrary to our mission to fracture the commons of software.
http://wiki.creative...for_software.3F
Wonko