When I performed a backup, the utility's software reports errors for two eEye files. Seems obvious (now) that my having left eEye Blink Personal running when I ran the backup was the real error, but I re-ran the utility so it would update only new or changed files (hoping the eEye files would then be 'closed' and that the backup wouldn't still list the errors, but no soap).
Maybe the errors are of no consequence and the backed up system will/would still restore things w/o issues (if I ever needed the backup), but hey, I'm doing good just to use the backup utility as much as I have, and likely as not if ever using the backup, it might create an issue with the system and/or eEye?
File "C:\Program Files\Common Files\eEye Digital Security\Application Bus\REM Client\Queue\00000002.MMF": can't read, error -1020 (sharing violation)
and
File "C:\Program Files\Common Files\eEye Digital Security\Application Bus\REM Client\Queue\file.lck": can't read, error -1020 (sharing violation)
What 00000002.MMF is, I'm not sure as the only place that file lists is in eEye's folder. The only .mmf's I've ever before seen (and just recently) were/are some files that Samsung's EasyGPRS program's software had, and while yesterdaqy I uninstalled that prog, I kept a fewof that prog's .mmf audio files w/hopes of maybe figuring out how to convert them to something of use on other than mobile phones.
As for the file.Ick, that one's anybody's guess.
Maybe re-booting, assuring eEye BP's not running and another backup of new/changed files will result in the backup not listing the errors, just haven't tried that. But it looks like as much as I'd like to avoid another 6 hours creating good backup, the only other thing I might try is to somehow delete those two file from the backup, if that's even possible, ref. RetroExpress Retrospect software utility. I''l try to see if there's a forum for that too.
Advanced thanks for potential replies,
Best regards and hap-e-trails,
wguru