I’ve installed Windows XP SP2 with Avast! Pro v4.1.
Before upgrade the Windows XP to SP2, everything work fine including command.com or any 16 bit program like FoxPro 2.6
However, after upgraded the Windows XP SP2. Most 16 bit program not work at all and show NTVDM encounter problem and need to close immediately. At first, I just wonder if it is the problem of WinXP SP2 only. However, after I’ve search around at Microsoft Knowledge Base. I find one solution.
It seems that some device driver at C:\WINDOWS\SYSTEM32\CONFIG.NT cause this problem.
I’ve checked my config.nt and find the following line which is added by avast! installation:
device=C:\PROGRA~1\ALWILS~1\Avast4\aswmonds.sys
After I remark (rem) this line, save the config.nt file. All 16 bit program work fine again including my foxpro 2.6 and command.com etc.
So, I think maybe avast! need to work a patch or auto-update to tackle this issue due to the release of Windows XP SP2?
Did you install avast before SP2?
Did avast work at that time?
Did you ever installed Norton in your system? Some Registry Key of Symantec could mess the config.nt file and the scanning of the 16bits programs…
If you did so, you won’t be protected… 16bits programs won’t be scanned under XP
NO, DEFINETIVELY NOT!
Its not avast. Its a Symantec problem.
Do not remove the line from config.nt file because you will be unprotected for 16bits applications (DOS under XP).
How is this a symantec problem? I have never had any symantec software on my computer. I installed Avast after a clean install of SP2, tell me exactly how this is a problem with software that was never installed on my computer?
Pick a thread were we can discuss this since there are two threads on the same subject.
Did you read my post about the ‘two groups of zeros’ in the Registry keys?
Well, some software added these groups of zeros into your Registry. I don’t know which one… You mentioned a clean installation in SP2. Maybe avast!?! :
The group of zeros change all you add after them into comments
Do you have a program called Registrar Lite? It’s a very good Registry Editor (free). There you can edit the keys in the format REG_MULTI_SZ:
The fact that I blame into Norton comes from the previous installation of Norton SystemWorks into my system. I have all utilities except NAV. The Norton key have two groups os zeros and avast could not add the driver there. I just change the lines, avast before and Norton after.
Again, if you change config.nt files you won’t be protected.
You can have problems to run 16bits applications (old pkzip for instance).
You can have (in theory) infections by applications running in DOS under XP.
I’m just trying to help not to make avast advertisement 8)
Regedit works fine, its what I always use, and I finally added the full path of the file to those registry entries as I missed that information. I was able to allow the device to load again, and 16 bit dos apps are working again with everything enabled.
As far as this install goes, it appears that Avast didn’t write the registry entry for some reason, and I haven’t been installing/uninstalling software either so if it wasn’t avast, why would anything edit those entries when they don’t use them?
And in the above case I haven’t install any Symantec/Norton related software.
If it is to edit the registry to solve the problem, I think it is not a good solution as I think WinXP SP2 already released and more and more people will use it.
