If you, Comodo coders, CANT backtrace\fix this bug or WOULDNT fix it for whatever reason, let me know please. >:(
I don’t want to talk with myself anymore about this bug (that’s what i do since June of 2008)
PS. It caused me quite a lot of trouble, imagine what it can do (already done) to users which:
do not know that OS lockdown is caused by Defense+ driver;
do not know the name of the file of D+ driver;
cannot use (reason irrelevant) LiveCD\Safe mode(?)\3rd party OS to neutralize that driver.
How the fact that this option is turned off by default is related to bug which takes place when its turned on :o
If feature (mentioned option) is present under GUI than it should work without such consequences >:(
All other options seem to be irrelevant because when i didn’t turn that option ON before resizing system’s NTFS partition or capturing image of that partition, then i didn’t face mentioned consequences :-\
Comodo’s settings were always different, but the bug was triggered only when i turned ON that option and opposite:
Comodo’s settings were always different, but the bug was NOT triggered if i didn’t change that option (leaving it at default OFF mode).
Is it still the same system that it happens on? Can you make it happen on a different system also?
Three systems: XP Pro SP2 and two XP Home SP3, all 32 bits.