This is a follow-up to my entry on 4/19/13. I did a system restore on my computer, going back to before when the wow.dll incident first happened. This did the trick. A key feature of a system restore is that Windows resets the registry to the way it was on that particular date and time (in my case, I went back to April 11). The price I had to pay was that Windows (my system is Windows 7 Home Premium) reinstalled the six updates of April 11th (no big deal; just waited about 10-15 minutes for the updates to install after shutting down) and that Norton Internet Security had to do a Live Update and reset its anti-virus, anti-spyware & sonar.
In fact, it was Norton's quarantining of the wow.dll trojan that caused the pop-up message problem, i.e., while NIS quashed the trojan's phishing effects (it looks for personal banking & related info), it did not erase or correct the side effects of the trojan's invasion. Norton has yet to admit that their software is to blame (at least it deserves a co-blame along with the perpetrator of the trojan). I will drop all the gory details on Norton when I complete their survey. In short, they need to update their NIS software so that if correctly eliminates threats without messing up the registry. I know they continually update their software, so hopefully they'll take my upcoming feedback correctly.
Finally, I am not saying that BD Advisor's recommendation of using Kaspersky's TDSSKiller doesn't work. In fact, if my attempt of doing the system restore did not work, this was going to be my next step. I am just leery of going into the registry to do manual edits - I'm not that computer savvy.