Fixing a partition that contains open files.

[Richard]

The problem seemed to start when I converted from FAT32 to NTFS on my C: In
fact, I reverted back to FAT32, because BootMagic only works from a FAT32
partition.

Anyway, how do I solve the open files error?

Thing is, I've run CHKDSK / R on all my primary and logical partitions. That
is given as the usual fix. So any fixes by this program have been done, but
to no avail.

I even uninstalled, then re-installed PartitionMagic to see if that removed
the error message - (993). It did not.

I just done the following:

I made what was unallocated disk space allocated, and it became P: I cut and
pasted my data from O: into P: Checking the partition of P: was okay, no
open files error. That's BEFORE I rebooted. After rooboot, P: is now
reported as containing open files.

Anyone know what cause a partition to have the "open files" error? Is it
anything to do with drive letters? TIA.

 

[Richard]

I just done the following:

I made what was unallocated disk space allocated, and it became P: I cut
and
pasted my data from O: into P: Checking the partition of P: was okay, no
open files error. That's BEFORE I rebooted. After rooboot, P: is now
reported as containing open files.

Anyone know what cause a partition to have the "open files" error? Is it
anything to do with drive letters? TIA.

In a nutshell, I can create a new partition (with PartitionMagic). I can
then run a check for errors on the partition, and get no error. Then I
switch off and reboot, but then P.M. reports "open files error.

BTW, whenever XP check disk utility runs just before booting (which it does
if I do something that calls for it) I get the message "An unspecified error
has occurred". But CHKDSK never fixes it.

 

[Richard]

In a nutshell, I can create a new partition (with PartitionMagic). I can
then run a check for errors on the partition, and get no error. Then I
switch off and reboot, but then P.M. reports "open files error.

BTW, whenever XP check disk utility runs just before booting (which it
does
if I do something that calls for it) I get the message "An unspecified
error
has occurred". But CHKDSK never fixes it.

Why does CHKDSK not fix?

Does the boot record need fixing, but CHKDSK does not get to fix an open
files problem for some reason becausethe boot record cannot be altered?

I checked BIOS and it has boot antivirus protection is disabled, so BIOSs
ought to allow change in boot record.

I wonder if Grisoft Antivurus runs right at start of bootup and this stops
CHDSK fixing the partition(s). I ought to disable any antivirus and see what
I get then.