Sample Report? Script Error?

[WacoJohn]

Windows XP Home SP3 running Immunet 3.0 free version.

 

Seem to have TWO problems. I opened 'quarantined history' and noticed a 'tag' at the top 'Sample Report'. I clicked on it and got a script error. See attachment.

 

I closed Immunet window. Reopened it and now the 'Sample Report' tag is not even there.

[sweidre]

Windows XP Home SP3 running Immunet 3.0 free version.

 

Seem to have TWO problems. I opened 'quarantined history' and noticed a 'tag' at the top 'Sample Report'. I clicked on it and got a script error. See attachment.

 

I closed Immunet window. Reopened it and now the 'Sample Report' tag is not even there.

Hi WacoJohn,

Please, read instructions given by Anthony (admin) how to handle Immunet Bugs:

http://forum.immunet.com/index.php?/topic/909-how-to-post-an-effective-bug-report/page__pid__4797&do=findComment&comment=4797

Cheers,

sweidre

[WacoJohn]

Please, read instructions given by Anthony

 

OK .. here are his instructions with responses:

 

1.List the version of Immunet Protect that you were using. If you have upgraded from previous versions list those versions too.

 

I think I did that.

 

2.List the version of Windows that you are using, including the language version and service pack number.

 

Did that except for language ... ENGLISH

 

3.List other antivirus software that you have installed, and the versions for those.

 

MS Security Essentials v. 2.0.657.0, Antimalware Client Version 3.0.8107.0, Engine Version 1.1.6702.0, Antivirus definition 1.101.1143.0, Antispyware definition version 1.101.1143.0

 

PREVX 3.0.5.220

 

4.Describe the flaw in as much detail as possible, attach screenshots of the issue if you can.

 

I believe I did that.

 

5.After you post the bug report to the forum, run the System Diagnostic Tool (SDT) and email the result to support@immunet.com, make sure to reference your bug report on the forum in the email message.

 

I will do that now.

 

Edit: Wow .. that diag file .. 16MB!!

[Rob.T]

Thanks John, your bug has been logged. I've seen a few different javascript error popus from time to time, but this is the first time I've seen one with a misplaced button.