Rollback Rx Version 10 is out

Thanks

 

OK... so now that some have downloaded the new V10, can anyone give a review of any sort?

Has it casued any crashes? ANy problems installing it ?

Any other comments ?

 

Just bought it and its running fine

 

As you might expect with a new version release that incorporates major rewrites some folks have had problems and others have had it work fine.

 

Rollback Rx discount coupon "techbuzz" get 50 % discount.Use this coupon code when buying through this link

 

I accessed the link and entered the coupon name "techbuzz" on the sale page, but it says that code does not exist. I contacted Support and was told that coupon code had been pulled down, and the new coupon code is "GOLDUPTOV10". It worked for me. No problems with the installation.

 

Its also recommended to uninstall Rollback RX when you do a Windows Service Pack upgrade.

You can reinstall it after you've completed the Service Pack upgrade.

 

yet another secret code (50%)... GOLDUPTOV10

Use it quickly...

 

Yes, use it quickly and buy the most crappy program.

My sentiments,

P.S. Do a search on this forum what most of the members says about Rollback Rx.

 

Ahhhh... Mohamed's secret agenda rears its ugly head once again

Clearly, for some reason, you can't seem to move on from your recent experience with Rollback. I thought you had moved on (to "Deep Freeze," I believe... or something else since then), I guess I was wrong.

Many people have had problems with both Rollback, the application, and Horizon Data Systems, the vendor... and many have not. From my observations and perusings, most of those problems were due to misunderstanding the product and its interactions with the system and other applications... so this can easily be expected. It's can be a difficult application to understand and even manage at times. Even those of us who think we know the product well have seen anomalies along the way that make very little sense to us.

But I can tell you, there are many users of Rollback RX that are very satisfied with their use of the product and probably will continue to be as time moves on, including me. BUT... I have decided to move on from Rollback RX, mainly because I want an even simpler solution that doesn't require the understanding Rollback does. I want something that I don't even have to think about... it just does the job, and if I have to wait a couple of extra minutes for the "fix to be in," so be it.

There are many existing solutions to the problem most of us are looking at... reliable backup and repositioning of the system without complete Windows restoration, and many work very well, but they all have their anomalies. So perfection continues to be pursued.

Since Brian has helped you finally move on with your Rollback disturbed laptops, I would think this is a good time for you to move on also as it pertains to Rollback. We all know you've had a bad experience and wish it could have been much better... but now lets get you on that "path to perfection" (unless you're already there )

Peace, Mohamed...

 

TheRollbackFrog,

since there are so many RBRX vocal fans/promoters in this forum I do not see why is so bad to have also a vocal member that opposes them.
And I completly disagree that most of the problems caused with/by RollBackRX are due to misunderstanding of the program from the users.
They are caused from the attitude of HorizonDatasys and how they handle those problems (by denying, hiding the truth or even eliminating their forum archives as it happened form 7->8 and 8->9).
examples:
https://www.wilderssecurity.com/showthread.php?t=184940
https://www.wilderssecurity.com/showthread.php?t=341033
A responsible company that respects their customers, admits, warns them and tries to fix the issues. Horizondatasys deceives them and let their fans to take care of the rest (=most of the problems are caused by the user misunderstanding the program...).

Panagiotis

 

Amen brother. While I do not take every opportunity to climb on the anti-RBRx bandwagon, every once in a while (like now) I want to say that I am convinced RBRx was responsible for trashing my system last year to where it would not even bootup to the RBRx subconsole. Then in the face of my disaster HDS did nothing other than insist that there was no way their program could ever corrupt a system to where it would do that.

So I would say to prospective buyers of RBRx, when it works it is seemingly miraculous, or it just could be a disaster waiting to happen!

Cruise

 

Just a thought,,,,,

It might be the case that most users of RX are not geeky. That is they are not using other sophisticated strategies to protect their systems and thus a number of the conflicts that the geekier folks here on Wilders have experienced such as which order imaging software is installed relative to Rx, or the HitMan Pro issue, never crop up. As evidence that most users do not have issues I refer to the Rx forum itself where there are not a lot of people reporting disasters. I used to use Acronis True Image and I had a terrible time with it. If you visit the ATI forum the number of complaints from users is amazing, so I would suggest that this MIGHT indicate that Acronis is more deeply flawed than Rx (if Rx is flawed at all - the problem is not with the software IMO but with the publisher). As froggie has said (more or less), if you do not try every light virtualization program, multiple imaging programs, etc, Rx should work very well for you. I agree with him. It has worked flawlessly for me and it has worked flawlessly for many others. NO program of any substance works on every system and there is bound to be issues from time to time, some of them serious, but the fact that some folks have had a problem with a particular piece of software does not by default make it crap.

 

IMO, alot of problems occur because some folks can't leave well enough alone and have to tweek their apps, RB included. The boys at Horizon just spent over a year putting V10 together, and I'll bet there are some people trying to modify some aspect of their copy already. That's not to say bad stuff can't happen any way, even if like me, you just let RB do its thing, but I think the odds of no problems are in my favor. (crossing my fingers)

 

Pray tell, how does one tweak RB? -- whereas there's little question that RB tweaks Windows!

Cruise

 

Not being a sinner myself, I don't know. Maybe I mis-spoke And should have said how people argue about things like to defrag or not, or to uninstall to image or not etc. I'm sure some folks may get confused and cause a problem, not necessarily on those two points but others that I can't think of. I remember a year ago when the threads here were long and winded about theories of how to handle RB.

 

Indeed

I own 4 copies of RB don't use any on a daily basis anymore - I remember excitedly testing beta and exchanging emails with the developers in the early days but ... for me it was never 100% reliable.

I still use the product that I expected to replace with RB - FDISR. Whilst this does occasionally fail the system can usually be recovered easily. This is not my experience of RB


Never found HDS support very helpful or capable ... but I guess milage varies

 

If you are referring to how one should (or can) do a disk defrag with RB, or a backup & restore with RB, or resizing partitions with RB, or running a check-disk with RB or...... please understand that none of those are tweaks, just ordinary Windows operations (except when RB is installed)!
Why is that? -> because RB tweaks Windows (and not the other way around).

Cruise

 

Exactly.

 

Froggie,

You have lost objectivity long time ago, and now you have lost my respect too.

1. Have you heard of F8, the Windows Recovery Environment. I am sure that you have and you know that it breaks Rollback Rx. If Windows fail, press F8 and then try to recover Windows. Guess what, I am pretty sure you know that Rollback Rx renames winre.wim to winre.dat, thus disabling Windows Recovery. It does that for those people too, who are just trying Rollback Rx for 14 days. Guess what again? After the trail it doesn't rename winre.dat back to winre.wim again, so from there on the Windows Recovery doesn't work on their systesm. F8 doesn't work.

From Rollback Rx v7 to v9, for many, many years this problem persisted and they knew about. Supposedly, it is now taken care in their newly released v10. My nine machines with Windows 7 x64 (one with Windows 7 x86) suffered from this. Both Pandlouk and Brain both tried to help, but without success. Eventually, I had to reinstall Windows 7 x64 on four machines with the help of Pandlouk which is not an easy task as reinstalling Windows XP. The remaining five machines suffered until yesterday, when Carfal pointed a solution in Isso's thread.

2. You are well aware that I had massive problems with Rollback Rx and my three machines with SSDs. In this process I discovered that Rollback Rx enables TRIM is to put the SSD in fake software RAID. I posted my concerns in Rollback Rx forum. You came out with massive tests and gave a glaring thumps up to Rollback Rx, and how perfectly it works with SSDs. I can quotes these posts of yours from the Rollback Rx forum, if need be.

Again, recently I brought these concern of mine in Isso's thread about this fake software RAID. Others took on this and opened a thread, which Pandlouk has referenced above. Pandlouk referenced a program, where one can check if the TRIM is really enabled or not. Guess what? Everyone found out that the makers of Rollback Rx claim that TRIM is enabled under Rollback Rx, but in reality it is not. Under the fake software RAID, it shows the fake TRIM being enabled, but the program shows otherwise, along with yours' thumbs up

You have lost credibility with me long time ago, now you have lost my respect too.

Peace, Froggie...

 

Guys, guys, guys. Lets stop bickering....allow me to take over.

As you all probably know, I love RB.

Having said that, I am the first to admit that it is not perfect.

But, it seems that RB is sometimes labeled as crap, dangerous and unreliable and people tell their disaster story and feel justified with their opinion. And their right. I know how they feel because there was one time when i was suffering from random corruption issues that had me at my wits end and i was ready to give on on RB. I even posted on their forums something to that effect but Horizon contacted me and worked with me to resolve this dangerous bug. As a result a fix was found and this was posted on their forums.

Where am i going with this? For every bad support story i can show you a good support story. In a perfect world their would only be good support stories but we're not that nieve are we? Besides, people have always had the freedom of voting with their feet as is the case with some of you. I say fair enough.

There's been alot of talk about the reliability of RB. The first thing i would say is that people sometimes forget that RB is a snapshot program. It is NOT an imaging or backup program. The distinction is vital in preparing for the worst. RB is designed to recover from PC disasters really fast. In this regard it excels. To achieve this it uses cutting edge sector tracking technology that the competion is only now catching up on. The achilles heel of RB is that it hooks into the MBR and also uses a driver to maintain a database which sits a layer above the windows file system (WFS). Disk read/writes are intercepted by the RB driver and directed to the RB database to read/record the sectors its going to use and then redirect the read/writes to the WFS. This is why the WFS cant see where the snapshot files are located. So understanding this helps us to understand why data loss is so prevailent when RB fails.

So is this sector based method reliable? In my experience it's been very reliable. But because of its design, when it fails, it fails monumentally. This is why external imaging and/or backups are vital.

Let me remind everyone again. RB is not a backup solution. When i hear of people losing their data because RB failed i feel for them but at the same time i cant believe that in this day and age people do not image. Even without RB's involvement, it's only a matter of time before you would've been burned. Unfortunately, RB cops the after math of such unpreparedness.

 

Not on this point in my experience.

 

And you are objective?

 

Aladdin. You and i are no strangers for butting heads.

If i can make an observation about you without getting into another argument.

You definitely seem to show some unhealthy hatred toward RB.

Reading your thread to Froggie, it reads like your attacking him because you hold him responsible for all the issues you outlined. That's rediculuous.

At the end of the day, we are all just sharing our thoughts and ideas and yes every now and then we'll disagree with each other. But it doesnt excuse the personal attack that you just portrayed. It's uncalled for. It seems that he struck a nerve with his first sentence

It doesnt show in the quote but did you notice the smiley. Reading the rest of Froggies post i got the impression that he was making a very diplomatic point of "you moving on (about RB)". I thought it was said with kindness.

Repectfully though, it clearly has offended you. All im saying is you could have handled it more calmly and maybe less drama.

 

It sometimes appears that BGoodMan4, Carfal and Froggie work for Rollback Rx. Mind you, I said appears!

YES, I AM OBJECTIVE. THE KNIVES ARE ALREADY OUT!

I posted two things.

1. F8. Rollback Rx messing up the Windows Recovery Environment for even those who try Rollback Rx for 14 days trails, for many, many years and they neither own up to it or fix it.

2. Claiming till today that TRIM for SSDs works under Rollback Rx. Basically, they make fake software RAID, which gives the fake result that TRIM is on.

Having said above, ARE YOU OBJECTIVE?