Had I used a conventional installation of Firefox then what the Sandbox crippled would have been scattered throughout Windows and the Registry,Īnd I would have needed to use my Boot Rescue CD to restore partition C:\ from an image backup. Portable Palemoon is contained within one parent folder and makes no use of the registry. I had to trawl through the browser profile and hack away removing files and folders that COULD have been the crippled remnants before I could complete a fresh install. The Sandbox modfied and permanently crippled Lastpass and FoxMarks.Ĭrippling was permanent in that with the Sandbox disabled I could still not install either.Īdditionally the crippled remnant could not be removed because the Addon required a Browser Restart to complete “installation” before the “Remove” button was active. Many Firefox Add-ons were added to Palemoon with no problem Palemoon is NOT recognised but it still browses the Internet O.K. To my secondary drive I extracted a Portable-Palemoon (source code similar to Firefox) Two months ago I had a new installation of Windows 7 Ultimate 64 bit.Ĭomodo 5.9.? was a fresh install which by default had the Sandbox active. I know that it SILENTLY cripples software installation without any indication of a problem and no way to fix the problem.
Please explain what is meant by “Modify File” in the Comodo Logs.
0 kommentar(er)
