Introducing AX64 Time Machine - hybrid imaging/snapshot software

Hi MerleOne,

I think this might be a problem that Brian found out, and it happens when you have a non-standard boot loader on the machine that you are creating the USB stick on. We'll fix it in upcoming update.

Isso

 

Quick question:
Is build 998 which can be downloaded from the AX64 site considered stable?



Cheers
manolito

 

That part will be already missing in the trial version. So they will have to buy a license to download a fully working version as you say below.

The certificate and the key will be per user. If they do buy a license and make a crack based on that certificate or release it to public you'll now which customer went "rogue" you can easily ban the user, certificate and key.
So in the next release the crack, keygen or patch won't work.
He will have to buy another license to get the new,updated full version, a new user key and a new certificate.

And the most important thing is that part of the protection will be injected inside the images. If a user wants to take the illegit route, he will have also to take the very high risk that a future update will make all his snapshots worthless data since he won't be able to load them or restore them.
(Trial demo/version should not be able to load the images where a certification is injected)

Panagiotis

 

manolito,

No, please do not use any version that is not announced on the website. These are untested intermediate releases that we use during the development.

Isso

 

Oh, ok now I see the idea, very smart indeed! Of course I'm not going to implement it, but will have it in mind. I'm wondering if any of the imaging programs use such approach.

Isso

 

Thank you noons, we are half way with GPT support, I think within two weeks I'll be able to release the beta.

Isso

 

Maybe you should prevent people from viewing the /temp/ directory then.

 

I just often need an easy way to share the files without requiring passwords, so I just upload the releases there. But you are right, I'll remove this release from there and consider something else

Isso

 

TerabyteUnlimited use (for IFD, IFL and BIBM, but not for IFW) key + an encrypted file "cdboot.f35" that differs in trial and in full versions (full versions can only be downloaded from legit users). They do not take it to the extremes as to personalize "cdboot.f35" per user and I do not believe it gets injected in the images.
But occasionally they do ban some user keys that get in the wild.
For IFW they use another key protection that allows the 32bit version to run with custom keys but when those are used in the 64bit version the program crashes.They do have a built-in mechanism to easily ban keys. The following can be used by a user to permanently ban a license from a windows installation
http://www.terabyteunlimited.com/ucf/viewtopic.php?f=4&t=901&start=10#p4349

Panagiotis

 

I'm using all but LV and there's no issues for me using those and AX64.

 

Is it save to run Image for Windows on the same machine as AXTM? Problems?

 

None on my system, but I have not tried to perform an IFW image recently.

 

Isso, a few days ago I installed AX64 on my son's PC (WinXP-SP3) and it seems to be performing great but he is experiencing a strange problem ever since I installed AX64.

He has been running Microsoft Security Essentials for years without any issues. However, for the past few days MSE's tray icon is orange on each startup/restart and when the mouse hovers over the icon it says "PC Status: Potentially Unprotected". My son tells me that MSE is updating properly, but it reports that a scan is overdue and when he runs a scan the icon turns green until the next startup/restart when it doesn't seem to recognize that the scan was run and the icon's color is again orange.

Could AX64 be causing this issue, or do you think that the timing of this is just a coincidence?

 

To be sure you probably need to uninstall AX64 and see if the issue with MSE is resolved. Since it's easy to reconfigure, I don't think you will lose any important config info after reinstalling it. That's the way I would do it on my system.

 

Can someone tell me how to cleanly uninstall (want to first uninstall Acronis clean and then reinstall it).

Do i have to do something with the driver that was installed during installation?

@Merle: just saw you answer for my question concerning IWF. thanks. Im interested in it, so tell me if an image with IWF caused problems on a machine with AXTM on it...

 

Isso, my son tells me he just discovered a conflict with Shadow Defender that you should be made aware of. When AX64 runs an incremental image while C: is in Shadow Mode, the time to create that image is about the same as the time it took to create the baseline image (whereas an incremental takes a much shorter time when C: is not in Shadow Mode).

I realize that Panagiotis (who is usually spot-on) reported compatibility between the two programs, but after my son noticed this I ran an AX64 incremental on my system (W7-x64) with the C-partition in Shadow Mode and my incremental also took much longer to complete.

 

Merle, I had already suggested that to my son (great minds think alike).

 

Hi WYC999,

No problems have been reported so far. You can check the compatibility information with IFW and other programs in our Knowledge Base, Compatibility section

Isso

 

The Shadow,

I doubt AX64 might interfere with MSE. Moreover you say that a simple reboot triggers the problem. AX64 does pretty much nothing between reboots.
If this problem happened after restore, or after backup, I would think it's AX64, but now I believe it's just a coincidence.

However the best will be to uninstall AX64 as MerleOne suggested and see.

Isso

 

Hello,

This sounds more like a conflict with SD than with AX64 IMHO... Committing changes in SD will cause issues with AX64 and not committing changes in SD will result in MSE not "remembering" its scans...

 

The Shadow,

Normally the program displays the reason of long backup in the header. Could you let me know what's displayed there? Or just send to me the logs (email to info@ax64.com, or file a ticket on feedback.ax64.com). To cget the logs click on the top left corner, select About... then Collect Logs. Thank you

Isso

 

Totally agree - MSE "loses" its state, which is what ShadowDefender is supposed to do on reboot.

Isso

 

Thanks for the heads up range of first release for this compatibility. That should be more then enough time for my OEM manufacturers recovery discs x 3 to arrive by mail.

And another very good reason AX64 is going to be in high demand IMHO. GPT issue already where not even Windows 8 usb full recovery media will do either a refresh or reset. I found the same similar issue spread all over the net with no concrete solution. Repeated looping to system repair screen, "windows could not repair the system" etc. Pfffft.

Thank goodness for Linux Mint while i wait.

Regards Easter

 

Sorry I cannot be of more help there, I have no plan to perform any more backup with IFW, I switched to other imaging programs even if I leave it installed (uninstalling can sometimes triggers issues).

 

There are no special steps to cleanly uninstall AX64 - just run the normal Uninstallation, it will clean everything up.

Isso