Main Forum > Tweaking.com Support & Help

Registry Backup Beta

<< < (52/79) > >>

chris635:
When you get it done I'll try it out on my laptop first. I have to work tomorrow and Sunday (12 hrs both days). If you want I'll test when I can.


Chris

Shane:
Lets give this a run before Sundays release  :wink:

neroilo make sure you give it a test run as well please :-)

v1.3.0
Per user request you can now name each registry backup.
Major change to the restore process in the program. Before the user profile registry files didn't always get restored because the move file operation was written to the old system registry file. This only happened if you restored the user profiles and the system registry at the same time and only when restoring from the program. This has now been fixed :-)

Shane

Tomas_Sweden:
I did a restore with 1.3.0.

I changed a registry entry in "HKEY_CURRENT_USER" is that enough? so I see if restore have worked?
Anyway I did a backup before I change a value in the registry, then I did a restore, and the original value was there, so that worked!  :smiley:

The *.old registry file can I delete them, if I dont delete them, will they always be there till next restore?

Tomas

neroilo:
Issue fixed with 1.3.0. After a new full backup, I created a new registry key in "HKEY_CURRENT_USER". Restoring it (with all checkboxes selected), registry key is disappeared as expected.

But, as Tomas, I'd like to have some explanations about how these .old files work.

For example, UsrClass.dat.old last edit is july 8th, while UsrClass.dat last edit is 14th july.

In other old files, the day of the last edit is always the same.

EDIT: I appreciate I can set a backup name, but if I don't want it, how can I do?  :tongue:

Shane:
The .old files are safe to delete.

When the program restores the current in use reg files, they are renamed to .old. This is much safer than trying to simply delete them.

When the program does another restore it automatically deletes the .old file if it is already there since a new .old will be coming. But once restored you can delete them if you wish. But just in case they are there if you need them.

So turns out I am a little bit of a dip some times lol. The restore wasn't working properly before.

When I tested the restore of the profile registry I had tested without restoring the system registry.

When replacing the profile registry files I use this "PendingFileRenameOperations"

http://technet.microsoft.com/en-us/library/cc960241.aspx

This of course is in the registry (The SYSTEM hive file)

So when you reboot the system hive file was replaced with those keys gone the profiles didn't get replaced.

Thanks to neroilo for letting me know. Now the question was how the heck do I fix it?

First thing that came to mind was writing another exe to check it and require 2 reboots. System reg files at one reboot and the profiles at the next. I HATED this idea.

So I did some digging and found what I needed. I can load other hive files to the registry to write to them.

So I changed the restore. It now does the user profiles first and then it will then read the "PendingFileRenameOperations" regkey from the current loaded system hive reg file.

Then it will copy the system reg hive file out of the backup to a temp folder (Which it does already) and then it loads that system hive and puts in the PendingFileRenameOperations into the soon to be restore system hive.

Then when the program restores the system hive the PendingFileRenameOperations will be there and the user profiles get restored :cheesy:

So I was able to keep from having to make the restore any harder or any different on the user and got it working even better than before. :wink:


--- Quote ---EDIT: I appreciate I can set a backup name, but if I don't want it, how can I do?
--- End quote ---
Should be able to have it blank if you want.

Shane

Navigation

[0] Message Index

[#] Next page

[*] Previous page