mike-r

That these little virtual device drivers don't work in real operating systems has been ongoing since NT arrived yonks ago and I've never heard of anything which allowed VXDs to function in NT, and I have looked. (Just trying to keep this topic alive and move it up to the top so someone might spot it and have a better view from a programming perspective.)

Yet another in a long line of dubious (and anonymous) 'reviews' graces the apps pages. I have twice installed McAfee VirusScan 4.5 on my Win2K system without any problems at all and certainly with no worse a performance hit than 4.02 presented (i.e., almost negligible). I can only imagine that the reviewer in this case has a distinct issue with something common to all the machines tested and not necessarily with this software. Currently, I have 33 processes in task manager, 158 out of 196 MB physical memory in use and with MCShield.exe itself only using 3MB. Control panel loads in about a second (all icons visible a split second later). I can run scans on anything I want without any problem whatsoever. This is with the latest engine and DAT installed (via SDAT4082.EXE) but it was fine before too. I have all options enabled (System Scan, Email Scan, Download Scan & Internet Filter) along with comprehensive heuristics and macro-virus detection and all files are being scanned, not just programs. Kit - Tyan 1696DLUA (onboard dual-channel Adaptec 3940AUW) 2 x 333 Celerons on MSI 9605 Adapters 3 x 64MB DIMMs Yamaha 4260 1 x Seagate (badged Compaq) 34572W 4.5GB SCSI FireGL 1000 (8MB) SB AWE64 Intel PCI network card Diamond SupraExpress 56e (external).