This is correct. In a dual boot scenario, if changes are made to a
partition where WinXP is installed and not running, all restore points
will become corrupt. Never make change to a drive that is being
monitored by System Restore when the operating system doing the
monitoring is not running.
By designed and under normal conditions System Restore will
automatically create a new restore point every 24 hours. When the
allotted disk space is reached, the oldest restore point will be
purged on a first in first out (FIFO) basis. Each one of these restore
points are chained (or linked) together with previous restore points.
When you choose a restore point, all previous restore point are
required to complete the restore. This reduces the amount of disk
space needed to hold restore points and increased performance. While
all of this is going on, in real time, a log is being created or
updated that tracks the consistency between the files System Restore
is monitoring, and the files that are actually backed up. If the log
finds an inconsistency between these files, restore point corruption
will occur. In turn this causes the chain to become broken and all
restore points to become useless, thus causing System Restore to fail
at a restore. At this point all restore points would have to be purged
to correct the corruption. So you can see, making changes to monitored
files or folders in a partition where WindowsXP is installed, and not
running would cause an inconsistency in the restore log, thus causing
System Restore to fail and the loss of all existing restore points.