Floppy Drive Access During Scan

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Well I seem to be having the same problem that a lot of you have – when I do
a scan the A(floppy) Drive runs and the Defender seems to stall at that
point. My way around it is to put a floppy in the drive – this is a quick fix
but want is the repair from Microsoft????
On a custom scan I only have “C†checked but it still seeks the A drive.
Windows XP Home
Defender 1.1.1347.0 engine 1.1.144.0
 
i also have this going on with a full system scan , but after about 1 min; he
goes on after (trying) scanning my floppy drive without a floppy in it , this
is something with the new engine i think , because in the past i dit not have
the problem , and i do a full scan aubout once every 2 a 3 weeks....
so i think it a bug....
 
FWIW - I don`t think it relates only to the new build because I recall seeing
this error way back for some people and the solution then seemed to be -
insert a floppy. However, I haven`t seen it posted for some time until now. I
have an external albeit not permanently linked to a notebook (can`t recall
when I used it last), but have never been able to produce the same symtoms
when I have. I have a theory it may be related to the `seek order` set in
your BIOS settings at boot time. Its just a theory and I may be way off base.
 
I'm not sure whether you are seeing a bug, or something more subtle. Even a
custom scan does a quickscan first. So, if a quickscan would reference
something off a floppy, this would happen. I'm inclined towards bug,
though...
 
FYI Mr Sanderson. The first major upgrade to the engine changed things. If
nothing is found in the custom folder, then additional scanning is bypassed.
 
with a quick scan there is no problem

only with a full scan then my light from my floppy goes on and there is a
noise for a few seconds and then te scanner goes on

never ever found anything from spyware during a scan

never happend with the older engine , only with the new one.
 
Back
Top