Hello,
In first, please excuse me for my very approximate English
I have 2 machines under Windows 98SE in network with division of discs. When Avast! is configured in level high on the machine whose discs are divided, at the time of assembling the discs on the second machine⌠the first plants itself systematically!!!
If I regulate Avast! in average protection, all is OK.
A solution?
So, to make sure I understand it correctly (if not, correct me, please):
[*]You have 2 computers (letâs call them A and B, for example), both running Windows 98 SE and avast! 4.1 Home Edition, latest build (357).
[*]Computer A has a shared drive.
[*]The resident protection of avast! (Standard Shield provider) on computer A is set to âHighâ.
[*]When computer B is trying to read a file from the shared drive of computer A, computer A crashes and must be restarted.
[*]When you lower the level of resident protection on computer A to âNormalâ, everything works correctly.
Is it right?
If the information above is correct, I would like to ask:
[*]How exactly does computer A crash? Does a bluescreen appear, does it reboot immediatelly, does it freeze? Is there any error message?
[]Does the problem happen every time when you access the drive for the first time? Or, does it happen only sometimes⌠allows to read a few files from the drive maybe? Does it make any difference what file exactly you are accessing - some files can be accessed, the other cannot? (and if you are reading the file or writing)?
[]You say you have used avast! HE for a few months - was the problem always there, or has it appeared with the recent update?
Afflicted for my English
You understood well.
I use the last version. The problem appears systematically when I try to access the shared drive of computer A for the first time from the computer B.
The computer A freeze without message.
I do not know if that is due to the last version. I noted it since I wanted to regulate protection to âHighâ.
Igor, you understood⌠Just to write my experience: a network with Windows XP (computer A) and Windows 98 (computer B) worked fine for me. Both with avast! Home Edition 4.1.357.
Can you download HijackThis, run it on computer A and post its log here? Maybe we can find something suspicious running on the machineâŚ
Btw, you only moved the âsliderâ of the Standard Shield configuration from âNormalâ to âHighâ, right? No other changes to the Standard Shield configuration?
Absolutely, no other changes to the Standard Shield configuration.
I have to test again yesterday evening, that freeze each time
I run HijackThis and i post log tomorrowâŚ
Unfortunatelly, I donât see anything syspicious eitherâŚ
For the Standard Shield, setting the level of protection to âHighâ means just turning on the scanning of âcreated/modifiedâ files for default extensions.
Can you try to go to the detailed settings of the Standard Shield provider, uncheck the âDefault extension setâ box on the second page and put only some bogus extension into the âAdditional extensionsâ (for example BLAH). Now, try to access the drives⌠if itâs OK, try to create a file something.BLAH somewhere and access it (from the other computer). Weâll see if itâs really the access that causes the freeze, or if the option itself is causing troublesâŚ
Btw, you donât have the advanced option âShow detailed info on performed actionâ turned on for the Standard Shield, right?
OK, letâs forget about High/Normal for a while and focus on the particular options of the Standard Shield provider.
Please, open the resident protection control window (on computer A), select âDetailsâ (if itâs not chosen already), select the Standard Shield provider and press âCustomizeâ button (it doesnât matter if the level is set to âHighâ or âNormalâ) and go to the second page of the settings.
So, do you say that if you set exactly the same options as shown on the left image, it will freeze when you access the disk of this computer from the other one - and if you set the options displayed on the right image (i.e. you turn off the âScan created/modified filesâ option) - it will work correctly?
Itâs rather strange⌠because even with the setting on the left image, no extensions are selected to be scanned⌠so the behavior should be the same ???