Introducing AX64 Time Machine - hybrid imaging/snapshot software

Whoops.... Sorry.

 

Hi Guys,

We're pushing one more beta out build 693.

Please shoot info@ax64.com.

All shall be revealed in the return e-mail.

If no serious issues arise, this will be stable release under the new name.

Understand it's been a little delayed, but it's important we take the time to test as thoroughly as we can.

Thanks!

Regards,

Waj

 

I have not used a single backup app in a very long time (since the 90s when Acronis True Image failed and I had to do a new installation). I used to use Rx with Paragon, then I was using Paragon with Ax64, now MR6 with AX64.

AX64 was never intend for tech savvy people, take a look at the opening posts in this thread, take a look at what the user has to do with the program. They have to instal it and then let it run. Thats it. I have 4 friends using Rx who I was not able to get to use any other backup program. They have never had a problem with the program either.

I will respect the moderators wish to terminate the discussion with you at this point. You are entitled to your opinion as am I. Lets leave it at that.

 

If memory serves there is not a return policy. You were supposed to test it before you bought it. I would suggest you contact HDS to confirm if I am correct or not.

Now,,,,back to AX64

 

Hi all,

Thankyou bgoodman4 and Oliverjia, and all for the sincere dialog.


We understand the app has been in beta quite sometime - it's amazing how long you guys have stuck with us and appreciate it big time.

To be clear, we've always since the beginning just been about making it as easy as possible to protect your data, so you can just focus on other important stuff in life.

Our product is targeted towards professionals who aren't super tech savy - like a pro freelance designer who runs his life on his PC, who simply can't afford the downtime when his HDD breaks.

It's aimed to be a set and forget solution that just gets the job done, no bells and whistles. A few clicks and you're backing up automatically, checking your files back in time or restoring your entire PC.

Our user base is made up primarily of these kind of folks and small businesses. Similar to the home users backing with crash plan or backblaze.

Our greatest challenge has not been the speed of our restores or backup - but reliability.This is the most important thing.

And as some of our most recent testers here have testified - the latest build is very robust and you can really turn your machine inside our and still restore successfully.

We're a small team, but super passionate about the support we get from our users. Wr never imagined our little app could foster such a diligent following. It's amazing.

Isso, Waj, Iurie and some new members are working hard to push a new release with a new name really soon.

Some folks are already testing the latest build.

As always, we thank everyone for their patience and understanding.

Sincerely,

Waj

 

Hmmm... guess what I FOUND...

 

There exists a media company that have exactly the same name that AX64 is going to change to, a company that has been aroud for c:a 40 years. Lets hope they do not give them a hard time .

 

Knowing this group... that media company may have "acquired" them...

 

Flashback is a pretty good name, well done.

 

If they still exist, they have absolutely NO Internet presence that I can come up with.

 

Still wish we had a "better" make of v1, in this new flashback....Love hot restore and hot image. I can make a supposedly more reliable cold backup with Macrium or Acronis, plus there are tons of software that do the cold imaging. Why not have one that is not like all the rest. That is what AX64 V1 was all about.

 

They have the Company base, Flashback international inc, in US of A but the sites they run is only existing in Sweden - https://www.google.se/search?q=goog..._rd=cr&ei=D1c2VtmTHcuo-wa-w4uQAw#q= Flashback

Good joke above .

 

There were a really interesting argument in the e-mail for why they changed from AX64 to Xeroweight, as if Xeroweight would be easier to remember . I could not hinder myself from l.o.l when i read it.

 

LOL
I have to admit, it's a good name for AX64's pitch point.

 

RodneyM, your wish will go unenjoyed I'm sorry to say. The original AXTM v1 method was seriously flawed and allowed for no way to unflaw (is that a word ) it. It tried to write the surface of your disk system with tons of active processes still running on the system... with the most active being Windows itself. That was never going to work reliably... many users have found that to be the case.

This time, with what they call "Native Restore," they are arriving on the scene just before Windows itself is even started. At this point an unencumbered library of System routines is available with enough of them to do what operations "FlashBack" needs to get done for its restoration task. The restore may not have quite the most efficient Input/Output operations that would be available from a LIVE Windows system, and it may have to reBOOT your system to get to that point in the overall process... but I s'pect it to be a much more reliable method of restoration than any of its previous methods ('cept for COLD maybe) and a bit faster than an original WARM restore due to the fact that WinRE doesn't have to be loaded.

 

Hi,

Froggie, it's not like you stumbled on it, we gave you the URL!

And Oliverjia, thanks for the compliments.

An official announcement regarding the new names can be found

HERE

Thanks for testing.

Regards,

Waj
ps: @rodneym we understand v1 had a live restore within Windows. However, as Froggie stated, it may lead to an interrupted restore. This fails to achieve the reliability we strive for.

With FLASHBACK we believe we have found the right balance between stability and speed.

• Warm restore (boots into recovery environment and performs a quick restore)
• Native restore (as Froggie describes) is almost as quick as hot restore, only a few moments longer due to needing to reboot.

We have both of these methods of restore in FLASHBACK. Which is going through what we hope is the final beta testing round.

 

The change of AX64 owner/ leader is rather fishy to me from day one. And the day it happened, since then the development of AX64 is stalled. Frankly I am not much hopeful that this project will ever succeed.

 

Hi Aigle,

We're far more optimistic

Waj

 

I can only wish all the best for you, Isso and the rest of the team.

 

@aigle Thanks!

 

@wajamus
Talking about Set & Forget: when the Automatic option is set to OFF, you should reflect this in the icon in the System Tray. Now you have no clue whether backups are running or not..unless you look at the system tray icon at the full hour and you don't see anything happening.

 

@cloggy49

Thanks for the suggestion. Well, as it works now - simply set it to on in the main window and it'll just work.

If it's off, it is because someone clicked it off on purpose (as by default it is on).

Other feedback we have got Is to prompt user on first install to give choice whether to switch on/off auto backups as well as ask to build rescue media.

 

+1 .


When i download the 693 beta i get a file not an exe. Do i have to manipulate it in some way ?

 

@wajamus

Trying to upgrade to the latest beta, from 665 to 693.

Per the Flashback instructions email, tried to uninstall first. Uninstall program doesn't work, however. Will sit at the tmapp /uninstall prompt forever. After numerous tries, safemode, etc.

Tried installing 693 on top of this. Upon first reboot, AXDBus Enumerator driver error pops up. "Device driver software was not successfully installed." Is this due to the left over files from the faulty uninstall?

Running the first baseline image now.

On Win 7 64 Pro.

EDIT:
Received suggestion from their support to try re-installing and uninstalling using an earlier version. After several earlier betas with the same result, went back almost a year and installed an expired beta, which finally uninstalled properly. Also, found that the latest 693 Flashback uninstall does suffer the same issue of the uninstaller failing to finish.