Rollback RX v10.x (Home & Professional)

Good luck with that...

-By the way, I am running a similar test with yours...
I am running Windows Media Player and try to defrag with it my hard disk... but all it does till now is to play videos. It must have a bug somewhere... I'll keep testing it until it defrags something and then I'll report back...

Panagiotis

 

Wondering how it can take so long when individuals here can test it quickly in a day..?

 

Here is a re-read,

Here are my statements, and your replies to them, as I said, clear as mud.

Kurtis answered: "We are, still no updates".

Barry: What does that mean? "We are" what?

Barry: You did not respond to this at all.

Not very clear even with a re-read, and a selective reply too. Did you try it or not. No ambiguity in the question and there should be no ambiguity in the ans. If you tried it, did it work? If not just say so.

Also, what sort of testing is required, either it worked or it did not. Froggie provided proof that it does not work, how many times must this be tested before the conclusion that it does not work is reached. Sort of like the 'unOfishul" FAQ. You have to determine that the listed issues are in fact issues. Really? You do not grant that if the MBR is compromised or if the drive with Rx protecting it becomes a door stop, that Rx will fail to recover the system? I do not think these are issues that need close examination. Do the developers really need to test these?

 

How many hours has the 'team' spent testing the 'Froggie' test scenario?
Simply to say you're testing tells us nothing really.
For example: You may be testing, but only 5 man minutes once a month, which means that you'll never really test it, but you can tell the world that you're testing, with a clear conscience that you're not telling a lie (although I'd say it would be very close to a lie).

 

Well our team has more than one project on the go. We have Drive Cloner's Version 6 (which is nearing release), Version 11 of our software, and testing Froggie's theory. We have said before, and this doesn't change, that if someone proposes a problem we thoroughly research it before we make an official stance on it. Just because a handful of users test something doesn't make it official. I mean, a few people thought the Earth was flat and they were totally right

For the amount of research involved for testing this theory, and the othe rprojects we're working on (on top of regular technical support issues) I don't think anyone should be surprised that we don't have an official verdict yet. So calm your horses, because there's no point on rushing to an assumption without thorough testing (and I mean all environments, not just the ones proposed on here)

 

The reply you provided is what I expected but really its nonsense.

No mystery as to testing and no extensive testing required. Simply test TRIM with Rx not installed, then install Rx and test again. Thats it, end of story. There is no need to test a myriad of system configurations, Froggie showed TRIM does not work with Rx installed, end of story.

 

They are too busy to deal with this or the "unOfisul" FAQ issues. Thats always been the excuse in the past and no doubt will continue to be the excuse in the future.

Kurtis was wrong about something though,,,,,,HDS marketing has changed and I believe it was due to pressure from forums like this one. HDSs website no longer claims that Rx can recover from any conceivable problem. They now list a bunch of examples of problems that Rx can triumph over,,,,one of which is that it can recover from a failed MS Update,,,,,just not that Rx may fail due to the update itself. Of course the problems of corrupt or compromised MBR, failed hard drive, etc (as listed in the "unOfisul" FAQ) are not mentioned.

 

There is a huge difference between updating a program that currently works with an OS (most programs) and updating a program because it causes your computer to not boot (RRX). Most programs update to improve or enhance them not to make them compatible.

 

Hi Barry,

I didn't expect that he'd provide any substantive answer, I just wanted to ask a question that would show him for what he is when he answered it as he did.

 

I wish that an HorizonDatasys representative as Kurtis existed in these forums back in 2007-2008. It would have saved me some money.

On the good side is that not all Canadian software companies are like HorizonDatasys...
Tracker Software Products LTD and LSoft Technologies Inc. for example are two canadian companies that value their customers, with great support and actually deliver what they promise...

Panagiotis

 

According to this recently released Rollback RX ROADMAP, the product isn't expected for use with Windows 10 until after January 2016... followed by its companion products (Drive Vaccine, Drive Cloner Rx <ahhhh... yet another year in the tank>, and Reboot Restore Rx). If you plan to upgrade your OS to the FREE Windows 10 at the end of July 2015, you must remove all current Horizon DataSys Rollback companion products until after January 2016.

 

The link if not working for you:
http://blog.horizondatasys.com/a-road-map-for-windows-10-and-rollback-rx/

Edit: feels like they asked their (part-time?) dev "how long will it take?" and he said "dunno, maybe six months?". I suppose it might work for them if most of their customers are corporate and will take at least 6 months to change over to 10.

 

FRoggie, the link you provided is not working for me. Regardless, given HDSs track record the time frame for a compatible set of HDS products BY Jan 2016 will be missed by a wide margin. Here is the statement from HDS.

I am surprised to see Drive Cloner on the list of "dangerous to install on 10" HDS programs. I did not realize that HDS considers this to be an instant restore program.

I wonder how many HDS program users will not be aware of this and will end up with problematic results,,,,,,,,No doubt HDS will blame the user for not checking first if and when its OK to install the program on 10.

 

BG, sorry 'bout that... it's been fixed (Thanks, Taotoo!)

 

Your source is correct Froggie

I'm surprised Froggie, Drive Cloner is a Windows application, it can be updated VERY easily.

 

I do my best not to "make up" my sources...

 

That is the point I was making in my posts. RRX will prevent you from installing W10 due to it being Incompatible. Then somewhere down the road a compatible version will be released. Then a DC7? compatible version will be released sometime after that. But before RRX, W10, and DX7 are working together, there will likely be a W10+ update which will render RRX and DX7 Incompatible with it. RRX will never catch up. That's the history and that's the future.

 

Not so easily updated evidently given its been so difficult for you guys to get the fully Rx compatible program released for use with 7 & 8. You might want to worry about that before you worry about updating it for 10.

 

We are releasing Windows 10 compatible versions of all software in January 2016.

 

One can only hope.

 

ALL SOFTWARE??

I guess we will see in Jan but I have my doubts about HDS being able to do this given the terrible record they have of meeting stated release dates.

What is it for DC (with the ability to capture all Rx snaps), 5 years and counting since it was first promised?

 

It *is* possible for them to correct their errant & slacking ways. Anything is possible. Guess we will know in 2016!

 

You know, back in the day, on the Apple II.. We had all kinds of custom patches for DOS. And each patch was version specific for the most part. If the DOS version was changed, our hacks and patches and mods would not always work. So fast forward to today, everytime Windows gets an update, the OS (DOS) is changed and RBRX (patch/hack/mod) may not always work. This is common sense.

One other thing they still continue to lie on their website like so:
"Reverse any system crash within seconds (even if Windows cannot startup)."

Any system crash? No!

A blatant example is a head crash on an HDD. Is the HDD not an integral part of the system? In fact it contains the information that defines and makes the system.

Kurtis, please explain how this is not false advertising.

 

It would be truthful if they said any SOFTWARE system crash. Any Software. because system can mean hardware of software.

 

Let me start of by saying that this question has been brought forth quite a few times already, and I’ve answered it plenty of times already. I’ll answer it one last time, then if anyone wants an answer, know that this is the definitive answer.

The reason we don’t change our marketing is because our statements are primarily true. When people have an issue or problem, it’s usually because of their configuration. Most times, it’s not the product itself. No software can be guaranteed to work on your system, that’s why we have a ticketing system and log files. So when/If someone has a problem, we evaluate it and fix it. Many issues that people have here aren’t always wide-spread issues. I mean, you can assume so all you want, but numbers, statistics, facts – they all say otherwise.

I’ve said since Day 1, if you have an issue, bring it to my attention, or Sam’s over at our forum, or any of our staff; and we’ll do our best to resolve the issue. We’re not just going to drop everything and uproot our entire website because a handful of users have an issue. That’s laughably nonsensical to assume that we’re going to do so.

So in summary, we aren’t changing the marketing. If you have an issue; file a support ticket and you can even PM me the Ticket ID and I’ll help get it to a Sr. Technician ASAP. In our eyes, it’s a more productive system then simply raising our arms and being like “Well one user had an issue…”

If you don’t want to submit a ticket, then there’s really not much that I can do for you.