After installation of W7 and accepting many W7 updates and patches, we installed CCleaner and removed junk and installed Acronis 2010 and made a backup image to fall back on.
There was only built in W7 security, plus a Netgear Router/Modem DG834G set for Outgoing only.
UAC was disabled for the first attempt, and set for minimum warnings at the second attempt.
I agree that a freak disaster on first attempt might prevent success on a second attempt if the installation deduced from remnants that Comodo was already installed, but why would it abruptly disconnect the Internet at the same point the second time ?
Whatever damage was done to the Internet was cured by a reboot - which suggests that Comodo kernel drivers already installed had done no permanent damage to the Internet.
Is it definite that an internal conflict could by itself stall the installation at the same point each time ?
I regret that due to extreme pressure of time we only made two attempts at Comodo before my son installed Norton Beta (free for 120 days) so he could get me started on using W7 before he went back home.
He is keen to migrate me to W7. My new bootloader is defaulted to XP.
When I have more information upon what could go wrong with the installation, or a later version of Comodo appears, I will be trying again.
Is it possible that for some reason the installation program might have gone to the Internet to download a driver etc. from Comodo or Microsoft or ACER, and lack of progress was not due to detecting a remnant (which should give a Comodo error message) but that it was waiting to receive the file ?
What are these Kernel Drivers, and where are the held ?
On version 3.13 I have only seen a small number of Comodo items in Windows/system32.
I have an adaptation of the Cleanup script which processes everything three times.
The second time is KILL TIME when it zaps what needs to go.
I will skip the first two stages and run the third stage which shows all the Comodo remnants it detects.
Then I will report back what it finds.
This is all proven on version 3.13 and 3.14.
Does version 4.1 have the same kernel drivers as 3.13, or will the existing cleanup tool be ignorant of what appears to be a vast number of new kernel drivers ?
Regards
Alan