Introducing AX64 Time Machine - hybrid imaging/snapshot software

Thank you noons. I received a ticket, but no logs are attached. Could you re-send? Thank you

Isso

 

Voodoo, Black Magic...

Cheers
manolito

 

The page says build 1111. The downloaded file says build 1111.

But once installed, it says build 1112.

 

I definitely didn't get build 1111. Something got slipped in?

 

No problem, I just replied to the automated response with the attachment. Will that work?

 

Thank you noons, I received the logs and replied to you via ticketing system.

Isso

 

Marc,

Sorry, this is my fault. It's the correct version, we just messed the version numbers a little, sorry.

Isso

 

I saw someone posting a screenshot showing build 1111, though.

 

Hello,

I think what Isso means is that version 1111 and 1112 are exactly the same except for the version number. Initially the version was supposed to be 1111 but inadvertently due to a mistake, a setup file labeled as 1112 (but the exact same as 1111 otherwise) was posted to the site. Basically your version can say either 1111 or 1112 but they are both identical binaries, so no need to worry...

 

Isso,

I was getting constant AX64 freezes during merging before and was forced to terminate and restart the program each time I noticed it. Just upgraded to 1112, I'm glad to see the merging errors and OS freeze after shutdown was fixed. Awesome job so far! One very minor request, could you please also have the AX64 installer remember what directory it's already installed in when doing an upgrade? I install a lot of stuff for testing, and I like to keep all programs organized. I rarely install programs directly under "C:\Program Files\XXX" as it gets really messy. As it is currently, I have to retype or browse to the path where AX64 already exists on every upgrade. Thanks!

 

And yet the setup file is still called "SetupAXTM_1_1111.exe"

No offense, but I'd rather hear from Isso himself than just a guess.

 

Hello,

He already posted that he messed up the version numbers.

I downloaded and installed it before he announced it here and ended up with version 1111. I just went back and downloaded again, reinstalled, and now have version 1112 even though the setup file and the website states 1111. Hence "we just messed the version numbers a little, sorry."...

 

Stop trying to speak for him. Let him answer.

 

Hello,

Sorry if I have somehow upset you as I was only trying to point out what Isso himself had already replied to you about the version numbers "we just messed the version numbers a little, sorry."...

I will say nothing else about the matter and let Isso repost what he has already said.

 

Guys,

The version that was supposed to be released was 1111. Then after we already released it (after noon's post) I realized that we actually used wrong sources. So I've used the correct sources, but this time I messed the version numbers (always something goes wrong when in rush). I apologize, and please don't pay attention to it. Next time we'll use more strict release procedure to avoid this kind of mistakes.

Isso

 

Thanks for the clarification, Isso. I knew something odd happened in between because there really was a build 1111 with 1111 EXE and then a build 1112 with 1111 EXE. I had a feeling that there was a reason behind all this.

Ironically, I did the same this week with a customer (didn't take all the latest source files out of the source safe). Ooops!!

 

Wow Marc so you are in software business too, I didn't know that colleague!

What complicates my work is also that fact that we are 4 developers all working remotely, in different time zones, and actually never seen each other. So it's quite difficult to get the development process right. Thus such silly mistakes sometimes.

Isso

 

Xandar,

Great to hear it, thank you for sharing good news!
Very good suggestion for the installer, thank you. Added to the feature list.

Isso

 

I can very much relate to that, Isso. At one point, I had team members in India and Australia (I'm in the MST timezone) so conference calls at 2am weren't uncommon. And as you try to establish business processes, some just come engraved in your mind and you don't think about writing a formal document on those... Well, because it is meant for only you so why instruct yourself? That is... Until a hiccup happens. And the more you scramble, the more escapes your mind to check.

As for my mess up with VSS this week, I miscliked on a context menu and didn't check the status window to ensure what I intended to happen is what happened. Instead of selecting "Get all latest version of files", I select "Get latest version of file" so only one was updated.

 

Hello Isso,

Great release! I just wanted to let you know that the freezing issue when going into hibernation that I had the ticket for is now fixed. I have gone through several hibernation cycles now with no issues whatsoever... Thank you for all the hard work and excellent software! Please send kudos from me to your team for all the excellent work they do. For me and this update, all seems perfect with this release... Thank you and your team for AX64!

 

Dearest Isso,

I am still testing the above version with excellent results. Do I need to continue testing with the above, or install the latest version 1111 and enjoy the benefit of the latest version, while testing it too?

Best regards,

Mohamed

 

Is it suggested that a new recovery disk be created for each updated version? If so it probably would be a good idea to indicate this in the e-mail alert.

 

That's just amazing you four can put it all together, and have never met. You should plan a mini convention some place nice, just to hang out and get acquainted.

 

Hi BG, Somewhere in here, I remember it being mentioned after the last version was released that we should create a new recovery disk after each update.