Problem with the file aswMonVd.dll

Hello everybody,

since my rebooting, I installed Avast Home Edition and I am trying to install an electronic dictionnary called “Oxford SuperLex” but I am encountering an error message. This error message says basically that the installation of the driver has failed and a screen shot is available here
http://images.photomania.com/172410/1/_radB58E0.jpg

This problem did not happen before I use Avast as the antivirus software. I do not know if someone has already experienced the problem and has found the solution. This software is quite important for me because I am working on my project so thank you for your answers.

Cédric

Try to make a link to it where both the file path and the start folder where written on short names, like:
C:\PROGRA~1\Superl~1\

Check out this thread and see if some of the possible solutions can help you with the 8.3 issue.
http://forum.avast.com/index.php?topic=28199.0

I am sorry but I forgot to mentioned that I am not a specialist and I have some difficulties to understand what you are suggesting. I am really sorry :frowning:

Can you post this screenshot?
To know how to post a screenshot, see http://forum.avast.com/index.php?topic=8982.0
You can use Gadwin PrintScreen to get a screenshot (http://www.gadwin.com/printscreen/) or the free version of WinSnap 1.1.10 (http://www.filehippo.com/download_winsnap/?2173).

What is the full path of the executable file, something like:
C:\Program files\Oxford\Superlex.exe

If think that now, the screenshot is available :smiley: In my previous message, I expected to write the URL from a website but it did not work.

The path file for the exutable file is: C:\BILING

I tried also to install this software on the same partition than Avast but nothing change. The path file for Avast is: D:\Program Files\Alwil Software\Avast4

Cédric

I forgot to say but I do not know if it is important. My computer is running with XP SP2 and I installed ZoneAlarm and Spybot Search & Destroy. I am sorry for the screenshot and the error message in French but the meaning is on my first post.

Cédric

Can you post the contents of the following files:
C:\WINDOWS\SUPERLEX.INI
C:\WINDOWS\system32\CONFIG.NT

Open them on Notepad, copy & paste here.

Ok, here you are for the C:\WINDOWS\SUPERLEX.INI

[Thames Language Resource]
ResFileName=slex33f3.oxr
[Thames Preferences]
WndSizeX=2
WndSizeY=30
WndSizeWidth=637
WndSizeHeight=420
ExitBook=0
StartupMax=0
StartupBook=0
UseStartupBook=1
[Thames Bookshelf]
DefaultDirectory=D:\PROGRA~1\OXFORD~1\BOOKS
Book1=C:\BILING\OHD.AND>>0>>Le Dictionnaire Hachette-Oxford
Book2=C:\BILING\ODG.AND>>0>>The Oxford-Duden German Dictionary
Book3=C:\BILING\OSD.AND>>0>>The Oxford Spanish Dictionary
[Thames History]
PinState=1
[Thames FindDialog]
WndSizeX=451
WndSizeY=243
[Thames Picture Window]
PinState=0

And here you are for C:\WINDOWS\system32\CONFIG.NT

REM Fichier de démarrage MS-DOS sous Windows NT
REM
REM CONFIG.SYS ou CONFIG.NT
REM CONFIG.SYS n’est pas utilisé pour initialiser l’environnement MS-DOS.
REM CONFIG.NT est utilisé pour initialiser l’environnement MS-DOS à moins
REM qu’un fichier de démarrage différent ne soit spécifié dans le fichier
REM PIF d’une application.
REM
REM ECHOCONFIG
REM Par défaut, aucune information n’est affichée lors de l’initialisation
REM de l’environnement MS-DOS. Pour afficher les informations de CONFIG.NT
REM et AUTOEXEC.NT, ajoutez la commande “echoconfig” au fichier CONFIG.NT
REM ou au fichier d’initialisation concerné.
REM
REM NTCMDPROMPT
REM Lorsque vous retournez à l’invite de commandes depuis un programme
REM résident en mémoire (TSR), ou exécutez une application MS-DOS, Windows
REM exécute COMMAND.COM. Ceci permet au programme résident de rester actif.
REM Pour exécuter CMD.EXE (l’invite de commandes de Windows), au lieu de
REM COMMAND.COM, ajoutez la commande “ntcmdprompt” au fichier CONFIG.NT
REM ou au fichier d’initialisation concerné.
REM
REM DOSONLY
REM Par défaut, vous pouvez démarrer n’importe quel type d’application sous
REM COMMAND.COM. Néanmoins, si vous exécutez une application non basée sur
REM MS-DOS, les programmes résidents (TSR) en cours d’exécution risquent
REM d’être interrompus. Pour assurer que seules des applications sous
REM MS-DOS puissent être exécutées, ajoutez la commande “dosonly” au fichier
REM CONFIG.NT ou au fichier d’initialisation concerné.
REM
REM EMM
REM Vous pouvez utiliser la ligne de commandes EMM pour configurer EMM
REM (Expanded Memory Manager). La syntaxe est la suivante :
REM
REM EMM = [A=AltRegSets] [B=BaseSegment] [RAM]
REM
REM AltRegSets
REM Spécifie le nombre total de paramètres d’inscription de mappage
REM alternatifs (Alternative Mapping Register Sets) que le système
REM doit gérer. 1 <= AltRegSets <= 255. La valeur par défaut est 8.
REM BaseSegment
REM Spécifie l’adresse du segment de démarrage en mémoire DOS
REM conventionnelle que le système doit allouer pour les
REM trames de pages EMM. La valeur doit être donnée en hexadécimal.
REM 0x1000 <= BaseSegment <= 0x4000. La valeur est arrondie à la
REM valeur inférieure de la limite de 16Ko.
REM La valeur par défaut est 0x4000.
REM RAM
REM Spécifie que le système ne devrait allouer qu’un espace d’adresse
REM de 64Ko depuis la zone du bloc de mémoire haute (Upper Memory Block
REM ou UMB) pour les trames de pages EMM et laisser le reste (s’il existe)
REM être utilisé par DOS pour gérer les commandes loadhigh et devicehigh.
REM Par défaut, le système allouerait tout le UMB disponible pour les
REM trames de pages.
REM
REM La taille EMM est déterminée par le fichier PIF (soit celui associé à
REM votre application soit _default.pif). Si la taille du fichier PIF est
REM nulle, EMM sera désactivé et la ligne EMM sera ignorée.
REM
dos=high, umb
device=%SystemRoot%\system32\himem.sys
files=40
device=D:\PROGRA~1\ALWILS~1\Avast4\aswmonds.sys

I hope that is right.

I know that if you write REM before one line and boot it will work…

REM device=D:\PROGRA~1\ALWILS~1\Avast4\aswmonds.sys

But this is not a solution, just a workaround that will leave your 16bit system unprotected by avast.
I need some time to research…

OK there is no problem for me. Thank you for your time and patience.

Can you read the long post number 3 of me a long time ago here: http://forum.avast.com/index.php?topic=738.msg3628#msg3628

There is explained why this problem occur, the workaround I’ve posted before and the solution.
Did you have Norton Antivirus in this computer before?
Can you post the contents of these Windows Registry keys in your system?

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\VirtualDeviceDrivers\VDD
HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\VirtualDeviceDrivers\VDD
HKEY_LOCAL_MACHINE\SYSTEM\ControlSet002\Control\VirtualDeviceDrivers\VDD
HKEY_LOCAL_MACHINE\SYSTEM\ControlSet003\Control\VirtualDeviceDrivers\VDD

About aswMonVd.dll and s32evnt1.dll in registry keys, see this very old thread about me:
How to NOT solve the problem: http://forum.avast.com/index.php?topic=259.msg3478#msg3478
How to SOLVE it: http://forum.avast.com/index.php?topic=738.msg3628#msg3628

I was introducing my 1st post here in avast! forums with the same problem:
http://forum.avast.com/index.php?topic=707.msg3417#msg3417

The first antivirus was Norton. I did not install it, it was in the computer when I bought it.

Unfortunately, I made several researches for the Windows Registry keys you mentioned but I did not find them. So if I well understand, I have to modify the file as descried in the attached post and reboot my computer?

Bingo! It’s the culprit here for sure…

You must have that keys, at least the first one… check carefully. Norton is avoiding you to have a good avast installation.

OK fine, but now it is me who needs time for research :smiley:

Thank you very much.

Just to make it clear…

Run > Regedit

Search for key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\VirtualDeviceDrivers
Value: VDD

Right click it and click Modify.

Better if you use another Registry tool like Registrar Lite (http://www.majorgeeks.com/download469.html).

I found those Registry Keys but I have only:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\VirtualDeviceDrivers\VDD
HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\VirtualDeviceDrivers\VDD
HKEY_LOCAL_MACHINE\SYSTEM\ControlSet003\Control\VirtualDeviceDrivers\VDD

The Registry Key mentionned as: HKEY_LOCAL_MACHINE\SYSTEM\ControlSet002\Control\VirtualDeviceDrivers\VDD does not exist on my computer. Do you think it could be the problem?

Follow http://forum.avast.com/index.php?topic=738.msg3628#msg3628

No. The problem is that Symantec add - stupidly - an extra zero after their driver path.