Today I decided to convert the data partition to FAT32, to work around the CTM protection. Somehow I had the idea that protection was only available for NTFS.
So I uninstalled CTM, after first backing up my downloads and documents, then I selected to revert to the baseline. It all went without a problem and the result was just like I would expect.
Then I converted my data partition to FAT32 and reinstalled CTM.
Interestingly enough, now I do have an indication and progress bar at boot time, with the message to press the home key if I want to start the subsystem. (not tested yet)
Well, it turns out that the FAT32 file system is protected too, so I didn’t gain anything more than successful uninstall/install.
Here is some more of interest,
After I uninstalled CTM, I decided to schedule boot time chkdsk for both partitions. And then I forgot to reboot, but instead installed CTM right away. After the installation and reboot of CTM, a boot time chkdsk was performed with success: no errors.
Now, I notice that every time I switch to baseline, I get a boot time chkdsk as bonus!
It wasn’t intended that way, but I think it’s pretty neat. The baseline has now automatic boot time chkdsk build in. (until I decide to update the baseline, which is not likely)
I’m impressed, CTM seems light weight and gentle with the file system. I also mounted the partitions from a Linux live cd, and all I found was the status of the current snapshot. I do wonder where the other snapshots are stored? What would happen if I copy the files, format the partition and restore the files? Because when I access the disk offline, it seems harmless to do that.
Are the snapshots file based, or are they disk sector based? Based on my experience I prefer file based snapshots.
Again, I will build a tree of snapshots and I like to find out what happens when I delete early snapshots from these branches…
[attachment deleted by admin]