R
Robert Miles
I've been seeing problems with significant slowdowns on
both of my Vista Home Premium SP2 machines lately
whenever the amount of physical memory used, as reported
by Windows Task Manager, gets much over 50% of the
total present. I first saw this problem on my 64-bit machine
with 8 GB, and therefore guessed that the problem was
due to the 4 GB limit for a program running in 32-bit mode.
However, I'm now seeing the same problem on my 32-bit
machine with 2 GB, so I'd now guess something else.
The Back Up Files program is now running on my 32-bit
machine, with about 75 hard faults per second. Is that
program using hard faults as part of its way of reading the
files to back up, or does it have a problem with using
memory efficiently?
Neither my 32-bit machine nor my 64-bit machine has
completed a backup successfully lately, regardless of
whether it was a full backup or an incremental backup -
something about a problem with the Windows Catalog
Files.
I notice that the autorun.wbcat file included in the top
level of the last few backup sets has length zero bytes;
is this normal?
both of my Vista Home Premium SP2 machines lately
whenever the amount of physical memory used, as reported
by Windows Task Manager, gets much over 50% of the
total present. I first saw this problem on my 64-bit machine
with 8 GB, and therefore guessed that the problem was
due to the 4 GB limit for a program running in 32-bit mode.
However, I'm now seeing the same problem on my 32-bit
machine with 2 GB, so I'd now guess something else.
The Back Up Files program is now running on my 32-bit
machine, with about 75 hard faults per second. Is that
program using hard faults as part of its way of reading the
files to back up, or does it have a problem with using
memory efficiently?
Neither my 32-bit machine nor my 64-bit machine has
completed a backup successfully lately, regardless of
whether it was a full backup or an incremental backup -
something about a problem with the Windows Catalog
Files.
I notice that the autorun.wbcat file included in the top
level of the last few backup sets has length zero bytes;
is this normal?