It seems the problem was empty options in Virscan.ini, ie tag=value and no value supplied.  Changing these lines into comments seems to have solved the problem. BTW a comment is a line starting with a semi-colon.

Martin

Hi,

I have Pegasus Mail 4.52 on an Acer Aspire One under MS-Windows XP SP3.

It starts up OK if Virscan 4.92 is in Pmail's programs directory, but with 
Virscan 4.98, it gives windows saying Access violation in virscn32.DLL

Thanks for help. 

Sheldon

In order to help with this, I need your Virscan.log in your Newmail directory and Virscan.ini from your executablesl directory. Please mail them to me, at irelam@telus.net. I will also need to know which AV product you are using. If you don't have a Virscan.log, just create one with Notepad

The posting in Usenet had a response that suggested that you try another AV. I don't think that poster undestood that Virscan is not an AV but a pipeline from Pegasus Mail to the AV of your choice.

Martin

[quote user="irelam"]In order to help with this, I need your Virscan.log in your Newmail directory and Virscan.ini from your executablesl directory. Please mail them to me, at irelam@telus.net. I will also need to know which AV product you are using. If you don't have a Virscan.log, just create one with Notepad.[/quote]

Thanks a lot, Martin.  I will do that, hopefully tomorrow.

Thanks again,

Sheldon