TeraByte Unlimited

I have two hard drives on a XP Pro system; both are partitioned, and each has a system partition. I have found that when I switch from one system to the other and work on documents or do other work on files in my data partitions, when I boot back to the other system, CHKDSK runs on one or more partitions. This suggests to me that rather frequently, work done on a partition, meaning anything involving files, results in changes in the file structure that are seen as errors by the other system. CHKDSK corrects these "errors," and then what happens is files become unusable. CHKDSK never runs, though, on the system partitions, only the data partitions.

FYI, SYS2 was created with an IFW image of the original SYS1. SYS1 now comes from an IFW image of SYS2. I am using BIBM 1.08 and IFW 2.68.

Any ideas on why I am getting the errors?

do you hibernate and share different partitions? if you do, don't or use
bootnow with the /hibernate option.

"Bill" wrote in message news:2400@public.bootitbm...

I have two hard drives on a XP Pro system; both are partitioned, and each
has a system partition. I have found that when I switch from one system to
the other and work on documents or do other work on files in my data
partitions, when I boot back to the other system, CHKDSK runs on one or more
partitions. This suggests to me that rather frequently, work done on a
partition, meaning anything involving files, results in changes in the file
structure that are seen as errors by the other system. CHKDSK corrects these
"errors," and then what happens is files become unusable. CHKDSK never runs,
though, on the system partitions, only the data partitions.

FYI, SYS2 was created with an IFW image of the original SYS1. SYS1 now comes
from an IFW image of SYS2. I am using BIBM 1.08 and IFW 2.68.

Any ideas on why I am getting the errors?

I was hibernating and then booting a different OS; I didn't know that could cause problems. I will stop doing that. Thanks.

Bill