Problem Solved !
Before I upgraded to Tiger, I was using Safari 1.3, I had the Safari Cashe Folder set to READ ONLY since I have Broadband High Speed, 6MB, because I didn't want that folder ballooning out of control and eating up disk space. Apparently that causes a conflict with Safari 2.0.2. Returning the Safari Cache folder to Read & Write solves the problem. You can't use Safari Enhancer to deactivate cache either as the problem returns.
This seems like a bug to me. You should be able to deactivate cache if you want too without having major conflicts expecially since it worked fine under OS 10.3.9 and Safari 1.3.
Doug