Thanks LM. Comodo no longer exists in Services, so there was nothing to disable. I am long past that point, thanks to advice from other support staff.
There is no startup tab for CPF in msconfig. That would seem to make sense (what you suggested), to remove the startup engine so that new version of CPF will not believe that an old version is still installed. However, apparently I am past that point as well. No CPF representation in msconfig.
I still have a few registry entries for "Comodo Network Engine", the perpetrator. I have admin privileges, so I should have access to the entries to delete them But I can't delete them.
(1) Can I change their values somehow so that the new CPF Pro will not recognize the old registry entries? I can't change these entries with anything I know. I can't even rename them now with what I know.
(2) Can I access the uninstall file from the old version from the Comodo web site? A support person sent that file via email to a friend, who cannnot access it at this time because he has a motherboard problem or he would send it to me. Or is the uninstall file posted somewhere I can grab it? Maybe it would clean out the last few registry entries.
(3) Any other suggestions? I apparently have the engine starting at startup, with nothing to run. But the new CFP sees the engine running and determines that an old version of CPF is still installed. The file fwconfig is gone from my computer, if that counts for anything.
CFP is working SO well in my other computer. This whole issue began with an error I made with the activation code in the old version. Thank God that's gone with CFP 2.4