Main Forum > Tweaking.com Support & Help
Registry Backup Beta
Ztruker:
Rebooted with 0.9.7 and there is a problem with the dos_restore.cmd file.
IF EXIST K:\WINDOWS\System32\Config\sam set WindowsDrive=K:
IF EXIST J:\WINDOWS\System32\Config\sam set WindowsDrive=J:
IF EXIST I:\WINDOWS\System32\Config\sam set WindowsDrive=I:
IF EXIST H:\WINDOWS\System32\Config\sam set WindowsDrive=H:
IF EXIST G:\WINDOWS\System32\Config\sam set WindowsDrive=G:
IF EXIST F:\WINDOWS\System32\Config\sam set WindowsDrive=F:
IF EXIST E:\WINDOWS\System32\Config\sam set WindowsDrive=E:
IF EXIST D:\WINDOWS\System32\Config\sam set WindowsDrive=D:
IF EXIST C:\WINDOWS\System32\Config\sam set WindowsDrive=C:
I have Win 7 on C: and Win 8 Customer Preview on I. I guess this will work as it will see the one on C: last and set the WindowsDrive variable correctly, but I think a better method would be for you to look at the HOMEDRIVE environment variable then set WindowsDrive to that value when building the batch file. Should always work.
Ran a manual backup and it worked. Checked C:\Windows\temp and not I have two sets of vss files:
--- Quote ---C:\Windows\Temp>dir vss*
Volume in drive C is D370_C
Volume Serial Number is C89E-70E8
Directory of C:\Windows\Temp
05/24/2012 08:51 PM 308 vss-setvar.cmd
05/24/2012 09:24 PM 308 vss-setvar553.bat
05/24/2012 08:50 PM 518 vss.bat
05/24/2012 09:23 PM 529 vss553.bat
05/24/2012 08:50 PM 290 vss_start.bat
05/24/2012 09:23 PM 296 vss_start553.bat
--- End quote ---
That works but will end up leaving more and more vss* files there over time. You need to figure out why you were not replacing the vss files before then go back to just the single instance of each.
Were you deleting them before writing new ones previously or just trying to write over them?
Shane:
Does the HOMEDRIVE environment work in the windows vista and 7 repair environment?
And on the vss bat files. Here is the thing, I have the vss_start.exe set to when it closes it is deleting the files. So it shouldn't be building up. For some reason something is different in yours.
Can you do a check and post a screen shot of the security on the bat files? There has to be a reason for them not getting removed.
Shane
Ztruker:
I don't know, but what I meant was when you create the dos_restore.cmd file, use the HOMEDRIVE variable then, or is the cmd file already built and not being generated on the computer when backup is run?
Next time I get a chance I'll start the Recovery Console and see what environment variables are set.
Shane:
Yeah it is built after the backup runs.
Xp was a nightmare to do. VERY limited, I added some reg keys to allow the "set" command in the xp recovery console. I will have a how to on that when out of beta. So you can do
set allowallpaths = true
Without it you cant get to any other folders.
None of the normal commands work in the xp recovery. So it builds a VERY basic copy file just like erunt.
But when I got into vista and 7 they finally have all the commands and I was able to build a much better restore file. :-)
I just built all that code today, so a good run through for any tweaks is always welcome.
Shane
Ztruker:
Another possibility would be to add a line to backup_info.txt:
WindowsDrive=C: (or whatever the boot drive actually is)
then you could read that from the dos_restore.cmd file but that's a lot more work. Easiest just to use the HOMEDRIVE variable when creating the cmd file.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version