|Tufenuf, you rule! |
To tell the truth, I skipped grasshopper's suggestion at kelly's korner because it seemed it was just another way to restore the icon, which I had already done. Since I was able to restore the icon and the problem was no functionality, I was guessing there was something else more deeply "broken".
And I skipped your first suggestion to download the SCF file associatioon fix, since I apparently already fixed the file association with the command prompt I mentioned in my original post.
I went straight for your next suggestion, with the run command for regsvr32 /i shell32, because after Googling it I found out it re-registers a broken DLL, and that sounded like what I was trying to explain could have happened. I told you I'm no expert on this, but I knew that sounded like what I was trying to say in my first post, LOL!
Anyway, that fix worked perfectly, so I'm very happy!
Now I'm just wondering if there could be other broken DLLs that might cause problems in the future. Do you know if this could be, and if there's a simple way to fix all of them in one swoop, just in case?