![]() I can see from the MPSigStub.exe file info that this file was updated on. So the problem is not with MSDaRT, it is in fact with the update file and where, when uncompressed, it is placed. Updates" which if course is the drive we want to scan, which has plenty of room. On further investigation, using an old update, we discover that they should go to "c:\windows\standalone system sweeper\definition with all this it seems that the updates do not actually go into the Ramdisk (X:) and should in fact go somewhere else. This in itself is strange, as when the disk was created, we opted to download the latest version. But of course the update version is very old. Looking at the mpavbase.vdm file already in 7.0 image, that is considerably smaller. However, looking at an update in August 2011, that file mpavbase.vdm was 47,046KB in size, making it too big then as well. This is of course, too big for the 30Mb Ramdrive. There is one file, mpavbase.vdm which is currently 47,385KB. ![]() ![]() ![]() Looking at the definition updates that have been issued, they haven't really changed much in size. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |