NTFS File Consistency Errors After Using Goback

[foolproof]

I was toying around with a Pre-installment Environment program and, upon rebooting, I got an error message saying that a NTFS file consistency check was needed and had found a few errors that it corrected. I rebooted and used Goback to revert to a safe state several hours before I started fooling around. After the required reboot though I got another NTFS consistency message. This time I aborted the consistency check before any changes were made, but noticed a significant slowdown in the system and had to abort some programs manually in order to reboot again. This time I allowed the consistency check to proceed and run its course. Everything seems normal now, but I was shaken somewhat by that consistency check after running Goback. I thought Goback would have reverted everything to a previous safe state.

 

[bcastner]

GoBack can revert named file changes and registry changes. But it is dependent on the filestore of Windows to make these changes.

It does not capture a picture of the MFN area of your NTFS drive, for example, and cannot do such low-level reversions or fixes.

I am becoming less and less enthusiastic about the use of this product under XP. I think it a good product under Windows 9x.

 

[linney]

I am not familiar with the GoBack software but maybe it is more concerned with the state of your software environment and not the physical condition of the actual partition.

This problem may occur if you have used the GoBack program on the hard disk. The problem occurs because GoBack modifies the master boot record (MBR) and changes the partition type on the hard disk.

The ChkDsk tool which runs at every boot up may need to correct some (hopefully) minor inconsistencies to the file system caused by installing GoBack.

This article contains an explanation of ChkDsk.

An Explanation of the New /C and /I Switches That Are Available to Use with Chkdsk.exe

http://support.microsoft.com/default.aspx?scid=kb;en-us;314835