Rollback RX Users - Have U Seen This?

At a minimum, you have at least one partition; it likely is one large partition for the entire disk as many prefer (although I use separate partitions for system, data,photos only, & downloads.)

Not necessarily -
I have experienced problems with both v7(purchased a year ago) and v8(recent upgrade.) I was willing to try it again for a while with image files on external drive. In all instances for the past year, I have monitored only my C: drive.

Without a doubt, FDISR is the lifesaver - Rollback has been good for quick, structured testing of various software, but wouldn't ever consider it to be a lifesaver.
Rob

 

yes i just have the one small(19 gig) drive.How does FDISR compare to rollback in features and ease of use?.Do you think the problems encountered with rollback are inherent or conflicts with other software?.I am tempted to download the trial version (i guess id have to uninstall rollback first)but am a little wary on how user friendly and easy it would be to setup and use for a novice.It as easy to setup and use as rollback for instance?.I didnt have to read any helpfiles with rollback (ok i know i should have),but it is that easy to use.Is FDISR just as idiotproof setiing up and running?
tia
ellison

 

Interesting read in HDS Knowledge Base: The Absolute Last, Final Word on CHKDSK

Btw, they published this article 2 days ago and today the link was pulled from the KB navigation...

Maybe they got cold feet at the last moment?

Edit: Oops, it seems you have to click here first HDS Support Portal, otherwise the deep link above gives just some "session expired" error page.

 

Silver0066 I do believe you. Over at the horizon forum I confirmed that the "chkdsk" problem exists and that windows always report errors.
But it will not cause a disk failure because of this unless you run it during the boot time or from the installation disk or from a bart PE enviroment.
The problem is that the driver does not load or does not load correctly during the boot time. And if you perform a "check disk" before windows is up and running it will result in a damaged partition.
Rollback RX does not mess the disk. "CHKDSK" during the boot time cause the problem.
And the developers should find a way or to properly protect the disk during the boot, or to prevent chkdsk from running.

 

In spite of all these problems, HDS is still selling RollbackRx as a ROBUST system restore software and for alot of money : $70.
Make it work first and then sell it or call it RollbackRx BETA.

 

Just curious, has anyone that has had problems with Rollback Rx, be it V7 or V8, CHKDSK problem or any other problems have uninstalled Rollback Rx and any and all of the problems go away ?
Just wondering if you were left with anything after uninstall.

 

Uninstalling Rollback removed the problems I was experiencing at the time.

Uninstalling usually left me as I had expected it to - in the snapshot I was in when uninstall took place but losing all the other snapshots. However, no overall computer problems...Except for the last time when I didn't initiate the uninstall. At that time Rollback totally froze the entire system making it necessary to use an image from Paragon Drive BackUp to get things back in order.

 

That article is a bunch of marketing hype by Horizon. They know they have the problem and they are acting like ostriches with their heads in the sand.

They are in total denial.

The chkdsk problem is caused by Rollback. It is done automatically by Rollback without user intervention when you boot the system. It does not happen that often, but it happens every now and then. If you have two partitions on your system drive, it will trash them both. It will leave you with no pre-boot screen.

 

In my case, there was no way to uninstall Rollback and there was no boot screen. Not only that it trashed all of my data on my d: partition. The only fix was a StorageCraft boot disk recovery, and then uninstall Rollback. I use a Synchonizer to backup my D: partition so I did not lose data.

But, it still took a few hours to get everything back in order. This type of behavior by any program is just unacceptable and not worth the quick snapshots. In the long run you are much better off with FDISR. It will take a little more time for a snapshot and a little more space, but you won't be spending the time using an imaging program to recover your disk every month or so.

 

When the crash occurs, Rollback automatically causes the "chkdsk" problem without user intervention when you reboot.

 

Apart from waiting for the developers to take action, is there a way to tweak XP and prevent chkdsk from running automatically? If yes, wouldn't this solve the problem - at least this specific one?

 

Originally Posted by pandlouk
Hi silver0066,

The above statement is not true.
1. If you have selected to protect only the C: drive it will not affect any other partition. I have performed a lot of tests on Rollback RX and this never happens. The only possibile way that it could happen is if you have modified your partitions after you have installed Rollback RX.
2. Actually it does not resides in the MBR. During the install only a small modification happens on the mbr. The preboot screen of Rollback resides in your partition.

Maybe I am out of my depth, but from the above my understanding is:
1. as long as RB is set to protect only partition C: there should be no consequence to the data drive, unless
2. RB also thrashes the partition table, in which case
3. the partition table has to be deleted before restoring an image
Question: in this case, wouldn't a tool such as Partition Table Doctor http://www.ptdd.com/ do the job rather than having to delete/restore?

 

The problem is that HDS don't develop the software (or at least didn't with version 7), and so are powerless to fix any problems. All they can do is report them to the developer and hope they fix them.

HDS simply sell a re-branded version of another software product.

 

The checkdisk is not trigered by Rollback; it starts because windows found errors on the snapshot. The problem is that Rollback does not load its driver properly at the boot time.
Rollback does not mess up the disk by itself; but it is to blame because it does not protect the disk as it should during the boot time.

ps. silver if you like pm me and I will tell you how to perform a very simple test, which will convince you that Rollback does not mess up the disk.

 

Yes, it can be done. Check here http://www.ocmodshop.com/ocmodshop.aspx?a=874

But is not a solution. This is a bug and EAZ Solution, the developer of Rollback, should fix this!

 

Hi Peter,
I just pmed you about this.