Hi, Sylvander.
I've just been checking through everything this last few minutes, and so far, all appears to work now as it should. I added the 'sleep' statement into the /root/my-applications/bin 'CAV' file because I noticed that the GUI was taking a few seconds to settle down after initialization.
You can safely ignore the statement in the left-side panel that says 'Filesystem filter driver is not loaded!' As bigpup says, certain of the binaries in the /opt/COMODO directory don't appear to work as they should. It's my belief that the reason for this is quite simple.
This was originally a .deb package, before extraction, re-working for Puppy, and re-packing. I think that it's been specifically written, and set-up for the way the file manager in Debian/Ubuntu is integrated into the file-system.
Since Puppy's ROX works so very differently to the 'standard' file-managers in those mainstream distros, and, moreover, most operations in Puppy tend to be far more 'manual' and 'hands-on', I think, going along with bigpup's summary, that we can safely ignore said binaries. For Pup, they're not really applicable.
In my view, so long as the GUI starts, the database will download, and the scans work as they're supposed to (bearing in mind that most of us will be using this in 'standalone' mode, i.e., as and when we consider it necessary, rather than setting up regularly scheduled scans), I feel this is now a viable package as it stands. I also think that the 'Critical Areas' scan profile will
probably be the one that gets the most use.
As always, however, YMMV.....
Mike.