To choose drives for VRDB

[Maria LC]

Hi,
I've recently installed another Windows XP on a new internal HD, so I have installed Avast! also in this new HD.
I'm wondering if I can choose which HD each VRDB must scan, so I can avoid the double scan of each Avast installation.
In other words: Avast on HD 0 generates VRDB only for HD 0, and Avast on HD 1 generates VRDB only for HD 1.

Thank you!
Maria

[DavidR]

There is no way to select which Drives the VRDB scans. The VRDB doesn't scan everything, it isn't a back-up process, as far as I'm aware it only monitors system files, dll, exe files, etc.

I assume (big) it is basically going to scan the windows drive and any associated drives/partitions displayed in explorer where it would have a reason to scan, in much the same way as it would for a single occurrence of XP. The VRDB would be associated to the avast program that is running.

[mauserme]

... so I have installed Avast! also in this new HD.

This is not necessary.  A single installation will protect both drives.

[DavidR]

No if you are using dual boot with two occurrences of XP

I've recently installed another Windows XP on a new internal HD, so I have installed Avast! also in this new HD.

My highlighting of 'another,' what I feel is two copies of XP to act in a dual boot role ?

[mauserme]

I read that as being just a second hard drive but I think you're right about it being dual boot.

[Maria LC]

Yes, I meant two copies of XP (one is Italian, the other one is English) in dual boot.
Like DavidR, I thought me too that VRDB scans every drives/partitions displayed in Explorer and I was trying to avoid doubles.
But now I'm puzzled, because if that's true, I expect to see the same size of the file avast.int in each HD. Instead it is 11.450 KB in XpEng (the new one) and 34.889 KB in XPIta (both generated yesterday). 

Sorry for my English and thanks for your answers!
Maria

[DavidR]

There would be differences depending what you have on both different HDs. What file are you looking at ?
The VRDB recovery file is in DriveLetter:\Program Files\Alwil Software\Avast4\DATA\integ\avast.int and mine is currently 7,870 KB (7.68 MB).

[Maria LC]

XPIta:
F:\Programmi\Avast4\DATA\integ\avast.int (over 34 MB)

XPEng:
P:\Sicurezza\Avast4\DATA\integ\avast.int (over 11 MB)

Why are they so huge, compared to yours?
Can the 34 MB one be deleted so I try to generate it from scratch?

[DavidR]

The size is dependant on how long you have had it installed and if you regularly add and remove programs. The VRDB maintains three versions to give a better means of repair after infection.

The data on my system is relatively small, nothing that isn't essential, so that could have an effect. You could try Disabling the VRDB generation and see if that helps, I doubt it, if you decide to delete the file, I would choose a different option, after disabling VRDB generation, rename avast.int to avastint.old. This would allow for changing it back if thee were any adverse reaction and/or if the file isn't created when you try the Generate Now to start rebuilding the VRDB database.

I don't know what would happen if you simply deleted on of the files (I've never tried it), avast should be able to recover from it probably by you running the Generate Now option. There is talk of some modifications to try and restrict the size of the avast.int file in a future update, when, sorry I don't know that.

[Maria LC]

ok, I think I'll let it alone.
Thank you very much for your help!

[Lisandro]

Can the 34 MB one be deleted so I try to generate it from scratch?

Yes, you can. Generate a new one will recreate the file 

ok, I think I'll let it alone.

If you have anything more that we can help, just ask 

[DavidR]

ok, I think I'll let it alone.
Thank you very much for your help!

Your welcome, glad I could help.