After having a problem with a pseudo-virus found by Avast, I seemed to have developed a scripts problem. I can't print on the web or fill out forms without the following:

Error occurred in the script on this page; line 639; Char 1, Error-invalid argument, Code 0, URL res ://c\windows\system\SHDOCLClDLL/preview.dlg.

I don't know if it is Windows, IE, or whatever. I reinstalled the printer, but no luck. Is there anyone out there who can help. Also, I noticed in my log with PG as HP being blocked. Could that be sabotage? Maybe I'm being paranoid.

One thing, I do like AVG. Avast gave me a virus report because it doesn't recognize Panda Software signature or something like that.

Help!

Did avg remove the virus. If it does not recognize the virus I am not sure it can. If you haven't already I would get in touch with avast support and ask.

__________________










A little common sense goes a long way

Later Grandpa

Yes Grandpa, we got rid of the virus. Only it wasn't a virus at all. I happened to go to AVG and downloaded that. I was having problems with the virus, AVG told me not to run to AV's at the same time. Then they told me that the virus that I described wasn't a virus at all. It was a false-positive. I'm steamed!

I contacted Avast and they said to just wait and see if my system was running all right for about a week and then to put the contents into my systems again. Now I just don't understand that kind of logic. I ran with AVG and got rid of the Avast and the contents in their chest (by mistake) and now I am left with the scripts error as I described above. I think the contents may have included the dll. If you or anyone else can help me with this one, it would be appreciated. Hewlett Packard is trying to help, but they gave me instructions on running a scrubber.exe. I had to uninstall my printer, but after the pseudo-virus was gone, so was HP in my start programs. So I had to reinstall over it so I could uninstall. This is getting complicated. They are trying to help, but I can't print out the instructions.

I know this doesn't have anything to do with viruses per se; I believe it's due to Avast's false postive though. So now I can't seem to get my system back in order. These errors pop up all over the place if I try to print or fill out a form.

I was wondering if a scan disc and fix errors would help, or maybe the PC pitstop, or REGISTRY MECHANIC software would help. I just don't know. If anyone does, please help.

If you are running Window XP go to start/all programs/accessories/system tools/system restore choose a restore point that is prior to when your problems started this should restore your computer to the way it was before you started having the problems. I Did a search with Norton using the word pseudo the URL below are the results.

http://search.symantec.com/custom/us/query.html

The link below is a link for a security check and virus scan by Norton I recommend you run them after you restore just to make sure you are not infected.

http://security.symantec.com/sscv6/h...PITSMJUIVFHPCN

when I clicked on the top link it just took me to the search page you will have to type the word pseudo in and do a search

__________________










A little common sense goes a long way

Later Grandpa

Thanks Grandpa,

You see, I'm not running XP, just Windows 98SE.


"Pseudo" is my coined phrase for a virus that wasn't a virus. AVG explained to me that Avast had identified the virus, described as WIN32:CTX, File name PSKAVS.dll File ID.4, as being a virus when in fact it isn't one at all but it was connected with Panda software. Avast, per AVG, is unable to recognize the signature on Panda and therefore gave me a false-positive.

So, I still need help with the scripts error. I installed some software from PCPitstop that cleaned out the registry. I am not getting the scrips error now, but I don't have the printer re-installed yet either.

I'll try re-installing the printer and see what happens. If its not okay, then I'm back to square one.

Thanks again.

What it came down to was a dll - iepeers.dll. Gee, wonder how that happened. Anyway, I was able to retrieve the dll from a google site, put it into my system, hit "run" and type in "regsvr32," cross my fingers, did a dance to cast a spell and the registration was successful! The google site had two iepeers.dll files and one of them would not install, so I went to door number two.

The info did appear on Micro's site, but it was for IE5. It did work for IE6 though.

UK Bob, if you're around and read this, I was just about to have to go to drastic measures as you suggested. But then, I read someone who did that and it still didn't work. I guess it's not just getting the dll file, it is the registering that does it.

Of note, Hewlett Packard is a site blocked by PG. When I contacted them for help, they didn't point me to the Microsoft support section until the end of their correspondence. I didn't try it on their suggestion until I had read about it elsewhere. Interesting, huh.

Thanks you wonderful people!

Hi U2btrfly

Man, you sure had a problem but that's what happens when a dll gets zapped.

Glad you worked it out.

Live long and proper.



UK Bob