May have solved the problem.
I have two "Terminal Services" in my Windows Services. One was set to Auto and one Manual. The manual one was the Terminal Services Configuration Service. It deals with remote desktop configurations and certificates. I am on a laptop connected to a wireless router. I set the service to auto like the other one. I don't why it affected the start up with CF and NOD32, but it seems it may have. Perhaps it was taking time to activate the service from manual to on.
Anyway, this may be a solution for others who have had CF initialize longer than normal. I shut down and rebooted three times now and the time from logon to internet connection and having CF and NOD32 up and running is back to five seconds or so.
Time will tell if this fixed it. But, this the first time it has started this fast in weeks or maybe months.
I know awhile back I disabled and/or set to manual several things I thought I didn't need. That may have been when things started to slow down, and I never made the connection.
I will follow with a final post if this works. And, may reinstall Vista SP2.
Thanks for all the inputs,
Ken