Introducing AX64 Time Machine - hybrid imaging/snapshot software

You apparently/clearly would like to make AX64 more complex which is against its stated purpose. AX64s target main market is those folks who do not do any imaging because its too complicated. I think you would have better luck getting this functionality in RealCopy as its to be the "Bells and Whistles" big brother of AX64 but I would hate to see AX64 get pushed for a relatively few advanced users.

 

This feature would not affect AX64 at all, just add drivecryptor support to the recovery disk
It would not even be noticeable to the average user.

 

Got the point. Then I'd rather not mess with the MBR and hope that AX developers would not either. The beauty of AX64 is also in its transparency and simplicity and I hope it stays that way. To fully uninstall e.g. Acronis programs from the system (mainly their drivers) is a real pain in the ass.

As a long time Rollback Rx and (mostly) EAZ-FIX user I used to be pretty content with them modifying MBR until... the disaster struck also to myself in not being able to start the system whatever the effort. The last version that failed so badly with me was the currently latest build of RBrx 10.2_2699300877. Then I said to myself - done, never again, irrespective how I liked this program and irrespective of so many years of its quite reliable performance (here EAZ-FIX 9.x was the most stable, with that one I never had any issue; perhaps could have been just more lucky...). I somewhat disregarded one observation of someone on this forum earlier back that Rollback Rx would fail sooner or later on each system by an unavoidable flaw in its design. So a reliable alternative that I found in AX64 appeals to me very much. The beauty of this speedy snapshot-like imaging is that if everything fails you can at least reach your data from the outside and save it copying it on another medium. And it doesn't store its backup data on the very drive it is supposed to protect... Not so much with Rollback Rx type of progs as in the case of disaster the best you can hope for is to return to the baseline state of your PC. With a couple of months back having it updated last time and massive file creating/copying activity after that, one may easily get into a pretty nice mess, unless a fresh backup using an imaging program was made. But then why to rely on Rollback Rx type of progs in the first place?!

Looking forward very much to the next AX64 (v2) release...

 

Completely agree, there must be a massive market for an imaging software that isn't intimidating with multiple options and tech jargon filled options and radio buttons....They'd be of no use to me, I just want to be able to restore my computer if I have a serious problem with its operations....I'm convinced that there is a bigger market for AX64 as it is (current issues resolved) for ordinary Joes rather than the smaller 'I'm a techy\nerd\super certified renown worldwide security expert' ... market who needs extra features not because I need them but I know how to use them'

 

1+! Thumbs up

I find FreeOTFE to be even better animal than TrueCrypt. It allows you to enter your password not only by keyboard or clipboard, but also using drag-and-drop. (It also saves your preferred drive letter in the container's system data so you do not have to set it on each mount.) If you drag your password directly from a program like KeePass hidden by asterisks, I guess you are pretty safe and immune to keyloggers, clipboard loggers as well as silent snapshot makers (even hidden cameras behind your back...). In fact, significantly safer.

 

Hi Mr Frog,

You missed my disclaimers, didn't you?

Let's say that my system is a bit disposable.

Since some advise not to use AX64 at all, I just want to offer a contrasting view.

 

Ooooops... I guess I did.

Oooo...Ooo...Oooo, I want one of those plastic and paper computers, too! You know the kind... where if your disk fails, you just draw a picture of another, cut it out and put that in the system.

Clearly understood... nighty, nite!

 

I understand and respect everyone's opinion on this, but:

FDE is a personal choice, and some people have reasons for using it.
Implementing diskcryptor into the AX64 recovery disk would not effect any of you in any way shape or form.
This would be extremely easy for AX64 developer(s) to implement, due to diskcryptor already providing the plugin module for the winpe/bartpe that AX64 already uses for recovery.

I have already seen several users on these forums alone attempting to use AX64 with FDE and know I am not alone. Not to mention the users on other forums.

To me, voting against this is like telling someone not to eat organic food, what they eat doesn't effect you and is a personal choice.

 

Apparently you are only looking at the negatives. Being a Wilders mod, it should be clear how much info Windows (and programs running on it) gathers and can be used against you. Those folks are the same folks who can't use the computer anymore after an AX64 hot restore fails, frankly incompetent. Please don't lump them together with knowledgeable people who RTFM. Lastly, if that fingerprint sensor decrypts encrypted data, good for you as long as the finger stays whole. If not, one can just remove the hard drive from the laptop, and everything except the critical data you haven't missed is theirs.

I know this is detracting from the original purpose of this thread, but this level of dismissal of fellow customers (from a mod no less) is unacceptable. AX64 Time Machine is fine the way it is, but that doesn't mean it can't be improved. Whether that is encryption support I don't know, only the owners can determine that, but that is another possibility and isn't as far-fetched as some are making it be. Truly one more optional feature that can helps some folks recover their computer, is that really a bad thing? Sure it can be added to RealCopy instead, but simplicity alone shouldn't be inhibiting progress.

 

John, at this stage of AX64 development, they do not offer a homebuilt WinPE to use as their recovery media. What they do is extract the WinRE (Recovery MEdia) from the user's RECOVERY folder and make minor modifications to the WinRE.wim that was put there by the system build... some systems don't even have it, depends on what the OEM did to the system. The only changes they make is to add their BROWSER system modules and Explorer+ to the WIM's SYSTEM32 folder and an additional INI file so that the BOWSER starts automatically after the RECOVERY BOOT. These are very simple WIM manipulations that are made on the fly when you ask for an ISO or RECOCERY MEDIA. Incorporating a driver system in this manner is not very practical... providing a properly built WinPE is the right way to go, but there is a cost involved now that MicroSloth is no longer licensing that facility for free, they license by copy issued.

It actually may be easier for an interested user to produce his own WinPE and add the necessary plug-ins mentioned above (it's a job that requires some learning along the way, it's not simple). Once you're there, just add the AX64 normal running environment and you should be able to do what you want. HOT/WARM RESTORE will not be available do the lack of the needed tracking file under the WinPE's OS, but COLD RESTORE should be fully operational (I have AX64 installed on my "Active@ BOOT Disk" and COLD RESTORE runs just fine).

 

Making a seperate WinPE is one thing, but how to 'add the AX64 normal running encrionment'?
If you or anyone could help me with this I would greatly appreciate it!

 

John, I would also suggest you stop by the AX64 FEEDBACK area and specifically ask for this capability. That way it gets on a list for consideration and maybe implementation.

 

Remember, the normal running environment under a WinPE will only be COLD RESTORES, the BACKUP module will give errors due to the lack of a tracking file.

All you need to do is carry over the Windows installed AXTM program folder (don't need the uninstall.exe module but most of the rest are needed) and place it somewhere you can get access to. I put mine under the Program Files area inside the WIM but it can be at the ROOT level of the BUILD (CD or DVD) as long as you have some sort of file explorer to get to it.. Once I reach a desktop of sorts, I just drill down to that folder and run "AXTMImageBrowser.exe."

 

I have a philosophical of sorts question! I need to qualify it first by admitting there aren't many more obsessive updaters/upgraders than me. Always have to have the latest and greatest only to have it occasionally bite me in the butt because of an unexpected issue.
Having said that, since AX64 v1.3.0.7 hot restores never, never, ever fail on x64 W7 SP1 PC and if I plug in a PS/2 I can cold restore too, plus having other boot restore options, should I even think about, let alone risk a new version? Although I suppose I could image with another program and return to here if I had to. Anyway, should I not just be satisfied with this version? Thank you!

 

I have the same set up as you and am using V1.3.0.7 also. Given the current situation, waiting for the new version, I figure I can keep this version at least until I upgrade to WIN9 some day. If the new version sounds really great I'll make a snapshot and upgrade so I can retreat if necessary.

 

Same set up as you as well with the same results. I will watch others using the new version and when the majority of users give it a thumbs up I will upgrade. That would be after the official release BTY.

 

I believe that as long as you do not use Win8 or Win8.1 any AX64 version starting with 1.3.0.7 is rock solid. At least this is the case for me (Win7 32bit).

Cheers
manolito

 

Et al... Manolito, nail, head.

Almost all the changes since v1.3.0.7 have been for W8 & W8.1... and even the latest "ofishul" release, v1.4.1.24, has issues with the RECOVERY MEDIA as far as the "Open Other Backups" option is concerned. I didn't know that until I went to use it a while back (W7proSP1x86)... then while troubleshooting, discovered none of the BETAs (after v1.3.0.7) until I reached v1.4.1.48 had that function operational, v1.4.1.48 does work.

Prior to extensively using v1.4.1.36, all worked well 'til I tried the "Open Other Backups." v1.3.0.7 was rock solid for me for a long time until I started using v1.4.1.24 & 36 during a W8/W8.1 development period.

As Manolito has recommended... stay with v1.3.0.7 if you're a W7 user, it should be solid... except maybe a rare failed HOT RESTORE depending on your system configuration

 

Ratchet... wipe that UPGRADE froth off your mouth and let your blood pressure return to normal

You've been very lucky doing what you've been doing, congratulations. The plain fact of the matter is, if an application upgrade (which you should really treat like BiOS) provides nothing in the way of fixing anomalies *YOU* may have seen, or provides no real additional capability that *YOU* need, there really is no reason to install it. Remember, the last version you installed has the most run time associated with it which should make it well used and fairly solid... for what you do with it. Any upgrade will have little run time associated with it and a much greater chance at failure... somewhere in the user community.

What you should be frothing about (at least I am) is the pending BETA release of the WARM RESTORE upgrade... due in appx. 5-days. And actually, since you've experienced NO failures with v1.3.0.7, you should probably wait until the rest of us occasional HOT RESTORE FAILers put that puppy through its paces. I know if I was in your position, I sure would.

 

Thanks Frog! You've convinced me to lie low and I needed that. I have to tell you too, I beat the hell out of AX64. It were a car your son or daughter were driving you'd have to be all over them!

 

Twice as long as Macrium? Say, if your system doesn't boot anymore, is it faster using AX64 cold restore or Macrium cold restore + AX64 hot restore? Or do you bother with hot restore at all?

 

Thank goodness I don't need encryption!.....No state secrets on my rig, mind you maybe their is so I'm being coy

 

Yup, and nothing more valuable than some time and $$$ when stolen. Or lost. Or when extorted (not just by "bad guys"). Or (temporarily) given to any third-party. Or just not paying attention while others access it.