floppy device I/O error

Avast Free Antivirus / Premium Security
1

If I try to read from a 3.5" floppy disk for the VERY first time AFTER a system boot, an error message says:
A:\ is not accessible.
The request could not be performed because of an I/O device error.

I am running:
Windows XP professional SP2.
Avast Home edition version 4.6.623 with VPS version 0515-6.
My basic hardware configuration is AMD Sempron 2300+ with 512 MB RAM.
I connect to internet via cable.
E-mail client is Outlook.
I use ZoneAlarm.

Things I tried so far:

  • other floppy disks.
  • another floppy disk drive.
  • another floppy disk drive cable.
  • remove diskette and diskette controller from device manager and reboot.
  • http://support.microsoft.com/kb/811840/EN-US/ for the following times: 250 ms, 500 ms, 750 ms, 1000 ms, 1250 ms, 1500 ms, 2000 ms, 5000 ms.
  • uninstalled Avast => problem disappeared!
  • installed Avast => problem reappeared!
  • renamed aavmker4.sys => problem disappeared, but Avast was probably killed in the process.
  1. Can anyone confirm this issue?
  2. Is there a solution? Because I find this unacceptable, I will have to revert to another antivirus if this cannot be resolved.

Regards,

Alfred

2

Hello Alfred, does it mean you’re not able to work with the floppy only after Windows starting - or at all ? Yes, Standard shield provider (aswMon2.sys) monitors floppy devices to block formating (if you set it up in the provider’s settings).

3

Hello pk,

The error appears when I try to read from a floppy for the first time after a reboot. If I click the error message away, I can access the floppy. So it’s mainly irritating.

4

Did you change the behavior blocker settings (into avast! Standart Shield settings)?

5

I did not change the behaviour blocker settings. I have this problem with the typical, standard settings. I haven’t been able to solve the problem by changing these different settings (among others floppy bootsector scan).

6

Alfred, I thought I’ve sent you an email about this earlier today… :wink:

7

Yes you did Vlk, so I replied ;). Unfortunately, your suggestion did not help.
I am considering to do a clean install of XP SP2 with only Avast on it, although I suspect the problem will still be there. Have you been able to reproduce it?

8

I have same problem here… please help!! ???

XP PRO SP2
P4 2.4GH
HD 40GB
256MB DDR 333
AVAST4.6.652 HOME

9

I finally did a clean install of XP SP2 with only Avast, and had no problem at all!
So far I have not been able to reproduce it, grrrrr. (eh… I should be happy about that I guess.)

It appears that Avast may have a compatibility issue with some program or driver on the original installation (or vice versa). That reminds me of the fact that the original installation was not a native installation, but an upgrade from Windows 98 2nd. ed. to XP SP2. This might very well have something to do with it. B.t.w. I installed Avast after the upgrade.

I might have been too quick blaming Avast. Will investigate this further if time permits (or give up and reinstall the whole damn thing from scratch).