I'm running Win2k on an AMD 3400+.  I have been working with support
on this since March, and they haven't delivered anything except b.s.
and a patch that didn't work.  BTW, my drives have been scanned every
way possible and my memory ran Memtest for a full day with no errors.
The system is utterly reliable except for this.

Problem 1:  The thing leaves vsnap.idx files on one or more drives
it's backing up.  It does this about once or twice a week if you do
one wall-to-wall backup and then an incremental twice a day.  When you
reboot, you get a BSOD when the system is coming up complaining about
pqv2i.sys.  Sometimes you get a BSOD on the way down.  To cure it, you
better be able to access all the drives from DOS, because the only
cure is to remove the vsnap.idx files.  They denied the problem
existed for a month despite something very like it being in their
knowledge base.  They asked for copies of my vsnap.idx files, which I
sent them.  They then turned around and gave me a patch to 2.0.4.403.
This accomplished nothing except wasting a CD and my time.  It took a
15 minute backup to produce more vsnap.idx files, which I zipped up
and forwarded to them (again).  I then heard nothing from them for 1
1/2 months (despite prodding) and then today I discovered that all
references to the problem are now missing from the knowledge base.
They say they're having difficulty converting the knowledge base and
that they're really working on the patch.  Right.

Problem 2:  The program occasionally refuses to honor the instruction
to limit the backups on the output.  Mine is set to one.  It does this
silently, no external warning at all.  When your drive fills up, guess
what?  No backup gets done.  To discover the problem you have to run
the program and examine the log or constantly check the output drive
to see if it's full.  That one cost me a few files.

Problem 3:  The program frequently enters a loop when browsing for an
output drive during the creation of a job.  At least that's obvious
and usually it works after a few tries.  Sometimes going to task
manager kicks it out of its' funk, sometimes not.

If you buy it, good luck.

[ Post a follow-up to this message ]