Vice Versa is using cache information, not scanning drive.

[Frankieplus]

Here's what i did - Will re create my steps.

1. Plugged in my external backup drives, booted up and ran VVEgine as I usually do Monday morning. VVEgine worked well and mirrored my source to target.

2. I responded to a few emails and did a bit of web surfing, then decided to delete 4 files from my E:\ Folder. This drive has 160 gig free of 270gig.

3. I ran Vice Versa Pro (Not VV Egine which I use manually anyway) and did a compare from E:\Source to E:\Target in hope that Vice Versa would delete those 4 files from target. I did NOT run the actual Profile that I do in VV Engine, but I scanned the same drive that the profile does anyway - i.e., I selected the source and target manually.

Instead of Vice Versa scanning my drives as usual, it returned a 'Source and Target are Identicle' within a flash of a second. No hard drive scanning noises, no hard drive lights flickering. It's as if Vice Versa got its information from cache and didn't bother to actually do a real physical scan.

Can anyone shed any light on this?

I then thought I might try loading the profile into Vice Versa Pro (Nothing to do with VVEngine) and low and behold, it ran it properly just like it did in VVEngine.

THEN

I tried it the manual way again with no profile selected and this time it did it properly again. I can't re create that 'cache' effect I first noticed.

Can anyone shed any light on this or has anyone else experienced a 'compare' result that seems to have come from memory cache rather than a physical drive scan?


-Frankie



-Frankie

[TGRMN Software]

Hello, never heard of this before, but please let us know if this happens again. Is E:\ an external USB drive? What brand? thanks
_________________
--
TGRMN Software Support
http://www.tgrmn.com
http://www.compareandmerge.com

[Guest]