Introducing AX64 Time Machine - hybrid imaging/snapshot software

Hi Norman,

1. An interesting suggestion. For other partitions (not system) you can restore from within Windows using hot restore without a re-start. If using rescue media, it is assumed you probably cannot get into Windows and so you are restoring your system image. After you're back into your system, you can then begin restoring your other partitions from within Windows itself.

2. Icon will be dealt with in a future build.

In future if you want a quicker response, please send your questions to info@ax64.com.

Thanks for these comments.

 

I can confirm that the ability to install into a chosen directory is now working correctly. I still have the same problem of a mounted drive not being assigned a drive letter.

 

Hi Gjbth,

That's good to hear. Can you please send your logs to info@ax64.com

The latest version has better logging. To save logs:

1. click on "backup tools"
2. click on "click on about"
3. save logs.

Thank you!

 

I just looked through some log files and noticed some words like... "WARNING:AXMainLogic.cpp(2305)"
"[1188:1192:0811/210012:ERROR:AXCommonStuff.cpp(756)]GetStorageDeviceInfo->DeviceIoControl failed, device \\?\Volume{d9b257fc-684e-4dcb-ab79-03cfa2f6b750} error 1" ...in various logs. Not all but some.

Everything seems to work perfectly but was a little concerned to see things like error, failed, and warning in some logs. Anyone know if that's normal or is something going wrong that I'm not aware of?

 

Latest logs just sent

 

Yes, that probably would be the way to do it. But I can envisage situations where a user would prefer restoring all partitions using the rescue CD, and returning control to the Backup Browser should not be too difficult for you to implement.

Norman

 

So I need some help folks! For a year or more I'd assumed that the missing cursor from my Microsoft 5000 mouse was a USB issue since a PS/2 mouse worked. For whatever reason, several months ago I plugged a USB laptop mouse in while the media booted GUI was up and woa and behold there was a cursor and I had a functioning mouse.
I recently tried v2 and the issue still exists. Today, however, there is a Macrium Reflect update and I quote the possible pertinent change log, "If the source driver files are marked as 'Read Only' this could cause a copy failure when building the Windows PE." Please note the word "could" as the cursor has always been visible and functional with Macrium, Paragon and W7's boot media, however, may not be with AX.
So can someone please explain how I get to that driver in x64 W7 SP1. I believe it's in System 32 etc. but not sure. If indeed it is 'read only' I'll change it, build the media again and see if that is the issue.
Thank you!
Disregard, as I found the driver and deselected 'Read Only' to no avail!

 

Dear Wajamus,

May I make two modest suggestions to improve the lot of us multipartition customers, now that we are approaching the commercial release date?
1. You assign a 16 hexadecimal-digits number to each partition. How about using just the last 15 and assigning to the first digit the drive letter used by Windows (C, D, ...)?
2. When performing a backup, it would be nice if the backup screen indicated which partition was being backed-up.

Norman

 

I was referring to drive letters; my labels, for the reasons you mention, are chosen to make the drives readily identifiable regardless of the letter assigned to them by the current environment.

Norman

 

Pete, I believe Norman was talking about the backup file naming convention, which is now the 16HEX-DateTime convention. This way, if the file being actively saved was shown in the display, a user could easily tell which partition was actually being saved at that time.

Not something I much care about but apparently Norman has a use for it.

 

Hi Norman,

Can you please provide clarification on the first point of what exactly you mean. As much detail as possible would be of great benefit (any mockups, screens or even providing your own logs would be of use).

Regarding your second point, the software displays which partition it is backing up, as it backs up. Can you please clarify, or are we missing something?

Your responses posted to info@ax64.com is easier to follow up!

Thanks Norman.

 

Hi Guys!

We're aiming for the final commercial release of ax64 v2 by close of business Monday! (Tomorrow).

Some celebratory sales and more info will be announced shortly. Stay tuned.

Best regards,

Wajamus

 

will it be in same format as Version 1.4124 which is simple and super efficient ?

 

I've been getting "11:44:36 PM: Couldn't create a timer (error 1400: invalid window handle)" errors with the latest build. Also, a bunch of .tmp files are being generated in the directory where its backups are being stored.

 

Zero3K, thanks for your report. Please send your ax64 logs to info@ax64.com

to save logs go to:

1. Backup tools tab
2. Click on about
3. Export logs

Also remember to write in the mail what occurred.

Please, all users experiencing any issues, do please write info@ax64.com. We can respond far more quickly there.

 

Hi Demoneye,

V2.0 quite a number of changes, but have kept bells and whistles to a minimum. We want to keep this app as simple and easy to use as possible and are continually fine tuning.

Check out the major changes to v2.0 here:

http://unbre4kab1e.w.pw/versions/time-machine-v2-0-public-beta-its-about-time/

note: do not download the version advertised in this post.

 

You mean that i shouldnt down load the beta version from the link you post ?...

 

no i didnt , i use some time the one from ax64 web site (1.4214) and i liked it much , simple fast and no tons of useless , never uses option features like in acronis for example.

 

Hi Waj

Sounds go...and I am sure a relief for you and the team. My testing with beta 3 has gone well, and PD being installed as well has caused me no noticeable issue.

Looking forward to the 'celebratory sales' and also what offers there are available to existing v1 license holders.

Regards



Baldrick

 

Hi Demoneye

Rest assured that v2 is faithful to the ethos and approach of v1...whilst it would be easy to say that just the GUI has changed given what features are seen as available...thgat would be completely incorrect as Waj & the team have a large number of improvements under the hood.

But if just looking from the outside I think that you would clearly recognise v1 simplicity & complete lack of bloat/useless features.

Regards


Baldrick

 

Will V2 be compatible with V1 images/snapshots throughout its lifetime? Basically I have a baseline of Windows 8.1 in a folder taken with V1 and I restore that whenever I want to re-install Windows to a clean state, will I be able to use that snapshot in V2 all the time or will the support for that disappear in the future and I should redo the snapshot with V2?

 

I don't want to jump the gun, but can I ask how existing V1 licenses will be handled? Do I uninstall V1 and download V2 inserting my existing key? why don't you publish simple instructions here for current members with V1 to avoid confusion when the V2 release is sent out? Thanks