Introducing AX64 Time Machine - hybrid imaging/snapshot software

Thanks Pandlouk. I will check this as soon as I can today and report back.

 

Thanks for the explanation. I don't know if I need the program at this point.

 

My friends system is Win 7. Not sure if its 64 bit or 32. I will try contacting him again today, he was away for the weekend.

ALSO. thanks for the user manual, very nicely done.

 

I found the file under C:\Recovery. I'm running Win 7 pro 64bit

 

stapp, Xandar, twl845

Thank you very much for reviewing the manual!

Xandar: I PM-ed to you re license

Isso

 

Hi TWL. From what i gather so far you are able to create your recovery media but for educational purposes, your interested on how to access the WinRE.wim file.

You will need the tool located here.

Below is a short video which you'll have to download from Hotfiles in which i've shown how to access and rename the WinRE.dat file to WinRE.wim (Yours is probably already named correctly as WinRE.wim since your able to create a recovery disk without inserting the Windows DVD).

Renaming WinRE Tutorial

After you've done the tasks shown in the video, run the following Reagentc commands from a command prompt.

Start a command prompt with admin rights

Reagentc.exe /disable
Reagentc.exe /setosimage /path c:\recovery /target C:\Windows
Reagentc.exe /enable

This will add "Repair Your Computer" back at the F8 advanced boot options ( if it was missing) and will even fix the "a device was inaccessible error" message that occurs on some systems after they try to run "Repair Your Computer".

Your recovery enviroment should work perfectly now.

PS If you have RBRx installed (or had it installed) you must first check the hidden "C:\Recovery\{GUID}" folder and rename "Winre.dat" back to "Winre.wim" or the above Reagentc commands will fail.

EDIT: Everyones {GUID} will be different. From what i can see from previous posts, your {GUID} path located in "C:\Recovery" should be "b87f2db3-6ab3-11e0-b611-782bcb9b196c". So the full path would be "C:\Recovery\b87f2db3-6ab3-11e0-b611-782bcb9b196c". If the "b87f2db3-6ab3-11e0-b611-782bcb9b196c" folder does not exist then you'll have to create it. Then on your Windows DVD locate the file named "\sources\boot.wim" and copy it over to "C:\Recovery\b87f2db3-6ab3-11e0-b611-782bcb9b196c". Now rename it to "WinRE.wim". There is another file required called "boot.sdi" but i'm uncertain if it will be created using the Reagentc command or not. Try doing the above Reagentc commands without this file to see if it will fix itself. If it fails then locate the "boot.sdi" on the Windows DVD at "\boot\boot.sdi". I would like to stress that i'm not certain how your system will react to this file since i dont know if it has specific information that is added when Windows is installed so do this at your own risk. Perhaps someone with more knowledge could reassure you at this time.

EDIT2:

TWL, I just noticed this from your screen shot

Code:

Windows Boot Loader
-------------------
identifier {3f8fa838-0682-11e2-9c83-782bcb9b196c}
device ramdisk=[C:]\boot\macrium\sources\boot.wim,{ramdiskoptio
ns}
path \windows\system32\boot\winload.exe
description Macrium Reflect System Recovery
osdevice ramdisk=[C:]\boot\macrium\sources\boot.wim,{ramdiskoptio
ns}
systemroot \Windows
detecthal Yes
winpe Yes

I'm not an expert but it looks like Macrium Reflect(?) has modified your recovery enviroment to load from "C:\boot\macrium\sources\boot.wim". If this is the case then doing the above may break this. Just warning you...

 

I have created a description of AX64 which I plan on posting on a number of forums that I am a member of. It is loosely based in part on a description of AXTM posted on the HDS Rx forum by Froggie (I hope Froggie does not mind, if you do Froggie, please let me know and I will take steps to change it so as to not reflect any of your phrasing). Before I start posting this I would appreciate some feedback. Is it too long, have I missed something important, etc?

 

I'm running WIN 7 64x also, and there's no C:\Recovery folder in mine, thus my quest to locate it.

 

Hi Carfal, Thanks for the above info! I'll go over it as soon as I get an opportunity later today. Today is Memorial Day here, and I am in charge of the barbeque, so I'm not allowed to work on the computer until later.

 

Sorry but i added another edit (EDIT2) that you should read as well. Have a good day!

PS. I had to fix the "Renaming WinRE Tutorial" link so make sure you choose the link from my original post.

 

Thank you bgoodman. If it's Win 7 then it seems to be something unrelated to defragmentation. I'm looking forward to receive the logs.

Isso

 

WYC999,

If you don't select Automatic backup option, then there is no auto-merging of backups happening. In fact even if you select it - the merging won't touch the snapshots that you've made manually. So looks like indeed you've made 5 backups in a row at that time, and if you don't need them you can just delete them manually from Backup Browser (note Delete button or right-click and select Delete).

When you select Automatic backup option the program merges the old backups automatically - see more info here

Isso

 

Thank you MerleOne, I've added F12 option.

Isso

 

Hi Acadia,

Thank you and welcome to this thread!
AX64 is compatible with Windows built-in imaging program. For Deep Freeze - I have no information so far, sorry. If someone is using these two programs together I'd be grateful for any information on their compatibility.

Thanks!

Isso

 

THANK YOU. You and your company's dedication to getting this program right, and especially at Wilder's where any security or backup program WILL be torn to pieces to be analyzed, is awesome!

Acadia

 

Isso: Thank you

Easy to read. Pictures help a lot. Minor point but maybe at the bottom of each page, a "Next Topic" would make the manual easier to read completely through or possibly a downloadable pdf.

 

bgoodman,

Thank you so much for your help spreading the word! At this moment it's extremely important, as the first year of a new program is normally the most difficult.

I find the description flawless, and I much appreciate the work done by you and Froggie.

The only thing that I'd prefer to be changed is the name - I know I've started using AXTM acronym, but then Cyberman noticed that most of the people use AX64 and I switched to AX64 too - to avoid confusions. If you could replace AXTM with AX64 I think it would be great.

Thank you!

Isso

 

Acadia,

Yes that was the main reason to alpha/beta test the program here - because I knew if it passes Wilders test, then it's indeed working properly
Besides Wilders is just a wonderful community - very friendly and willing to help.

Isso

 

Thank you William, I've also thought about the Next topic, but there are some problems with the article editor that doesn't allow me to properly insert a link. I'll be switching to another provider of these services.

Isso

 

Hi Isso, I just spoke to my friend and it seems I had completely misunderstood the problem. What happened was he had not created the restore media so when his PC crashed Windows selected a restore point and restored to that. This restore point was prior to the installation of TU 2013 and AX64. Evidently he then reinstalled RX64 and restored from within Windows to a snapshot created with AX64. He does not recall telling me anything about defrags etc and is a bit fuzzy on exactly what happened. Bottom line is that everything is working fine and he has successfully created the restore disk.

Sorry about the confusion.

 

Consider it done and as long as Froggie has no objection to my borrowing some of his phrases I will begin spreading the word far and wide. Also, if anyone else would like to use my description to further spread the word feel free to do so (as long as Froggie is OK with it of course). I will give Froggie some time to post before I barge ahead.

EDIT: here is the revised text. Please note that if anyone uses it to spread the word the truncated links at the bottom of the description will not work. Please copy the full links to any post you make of the description.

 

Hi Carfal, Yes that represents my Macrium Reflect. So that is where my lost C:\Recovery has wound up I guess. As you warned, doing the above could break it and leave me in a predicament. As they say, if it ain't broke, don't fix it. I'll study your text and try to understand for possibly a later date. Thank you again for your extensive help!

 

twl845

Have you tried Panagiotis' suggestion from Post #2145?

bcdedit /enum all /v

 

Hi Isso, I am running my back ups manually. A few days ago I attempted to delete one of the backups in the middle of a list of about 5 backups. It instead started to do a merge, and when the merge had gotten to about 95% it said something like merge failed error no.xxxxxxx. As a result nothing was changed. You say above that if you back up manually you can just delete them. What did I do wrong?

 

I'm trying to copy it as we speak, but ctrl+C isn't doing it. I'm going to add >C:\twl.txt and try again.
update: the copy/paste isn't working, but reading the command prompt it mentions recovery in my Macrium Reflect. My discussion with Carfal thinks that Macrium put my Recovery in it's folder or something similar, so Carfal thinks that screwing with it might break it. I think I'll leave well enough alone to avoid a predicament. I am able to create a recovery disk for my AX64. Thank you for all your help. Please post me if you have another suggestion. Thanks!