RollBack RX 8.1 build 2692839437

Hi guys,

there is a new version of Rollback RX, they released it on 19-01-2008.

This one works like a charm. It seems that is stable as a rock; even on my new raid configuration.

Panagiotis

 

What's new or changed in this build? The release notes don't appear to have been changed from those listed for the September '07 release.

 

If they bring it up to the stability and functionality of it's sister EAZ-FIX, that would be a HUGE improvement no doubt.

 

EASTER, on your copy of EAZ-FIX, do you see the last restore date & time? I only ask this because that wasn't showing in Rollback 8.1 when I tested it. They knew about it and has been fixed since, but not released, until now perhaps.

 

I'll have to mount that drive again to offer those findings but i am 90% + positive that it does. I remember that because i am always looking for that type info and more.

If they indeed like i mentioned have brought Rx up to the same level as EAZ-FIX then that would be a long awaited relief for many supporters of it, i opted away from Rx for EAZ-FIX and have no desire to even test Rx again since EAZ-FIX is working to perfection, something never realized for me with Rx any versions.

 

for my point of view using one of those programs is particular dangerous coz u can never remmber what files / programs have been installed or create
since last snap shoot.

my vote fose to DP or similar protection

cheers

 

There is no official change log but I will post the results of my findings:

1. They have changed Lockdisk=2 to Lockdisk=0. Lockdisk=2 prevented the access on the disk from external sources like floppy, PE cds, etc. On some computers would cause problems during reboot and shutdown. (I was the one to blame about this because I had found a way to eliminate Rollback RX protection when booting from an external source)

2. The preboot screen is changed

3. The log and the guide display correctly the last restore date/time.

4. An improvement in the overoll system performance.

5. Defraging (if you use the defrag command) of the disk is much inprooved. (previously I had to defrag and update the baseline twice to achieve optimal results; now I can achive oprimal results with a single pass)

6. Taking new snapshots from the guide is faster than ever. In previous versions the snapshots where faster if taken from the system tray)

7. A small improvement of the snapshot defragmenter. It seems to defragment a bit faster than in the previous version.

Panagiotis

edit: I forgot to mention that the chkdsk problems are history. I had a BSOD (not caused from Rollback RX) and although chkdsk run it fixed only the corupted ntfs indexes and the missing files. It did not influent in any way neither the Current Snapshot nor the previous snapshots.

 

True but before eliminating the obsolute snapshots you can mount them as virtual drives and check if there is something that you need to save.

 

I presume RB's Drive Image still has a 1-snapshot limitation?

 

If you mean snapshots, I think it's closer to 9999. If you really mean drive images, I suppose that would be unlimited, but I don't know how many you'd really want.

 

I'm assuming appster means that when you image a drive in RB it only backs up your current snapshot....

 

Right-on. As an RB-Pro user I'm well aware that the number of snapshots are just about limitless (from a practical viewpoint).

 

hey how to upgrade to this latest build?

do i need to uninstall my RollbackRx8.1 first?

 

Hi appster,

I have not checked, but for telling the truth, until they release a version that will permit us to update Rollback RX without uninstalling and loosing all the snapshots, I won't be interested about it.

ps. From the windows enviroment still allows you to copy only your current snapshot.

Panagiotis

 

Unfortunatly, yes; uninstalling is the only way to update Rollback RX.

 

That's why I never upgraded from v7.2.1 (final build). Until HDS gets V8.x or v9 right, I'll just continue using v7.2.1 (with Drive Snapshot to backup all RB snapshots)!

 

thanks dude!

new build works great in my PC.

btw, my firewall catch RBRx8.1 connecting to netreg everytime i restart my PC. But when i reset my KIS Firewall and catch that netreg again connecting to unknown IP I block it for good

 

In English that translates to... ?

 

Don't ask me. I deleted that post. I was running a malware at the same time testing, ugh! Looks like it did a nice number on text. I also got a testtesttest about a zillion times. So much for multi-tasking research while on the board.


Just to better clarify matters though. No one was more excited over RollbackRx then myself at first. I genuinely liked it although didn't fully understand the single baseline concept untill i bought EAZ-FIX, and now i've accepted that method and find it not so hard to live with afterall.

My only grievance is been why the makers of RollbackRx haven't been more forthright or prompt in resolving customer issues in reasonable enough time afforded them so i eventually threw in the towel.

Believe me, my stomach turned when i first tried & saw EAZ-FIX. I thought the very worse but those fears went totally unfounded and it works IMO as Rollback should have all along.

 

with this new build of RBRx8.1....i don't experience BSOD anymore when i turn my PC to Hibernate mode

 

Hi fce,
You are welcome.
hehe. you remembered about netreg.

ps. netreg connectivity is harmless. they only add it to protect from pirates.

Hi Easter,
Rollback RX and EAZ-FIX are the exact same product with different name.
You were only lucky to install the right build of Eaz-Fix. The problems that Rollback RX had with Lockdisk=0 were in EAZ-FIX too from late Jully(or August, I'm not very sure since they released 3 updates in a month). They were fixed only sometime in december.

Eaz-Fix is updated more frequently from Rollback RX (at least in the first half of 2007, it did) but this does not make it better or worst.

The first release of Rollback RX 8.1 was more stable from the first release of EAZ-Fix 8.1. Infact Rollback RX had Lockdisk=0 and EAZ-Fix had Lockdisk=2 (October 2007 builds of the two products). EAZ-Fix was the same as Rollback RX defrag version at the time.

Panagiotis

 

Interesting. And thanks for the history report.

I got mine after those issues so in that sense i suppose i was one of lucky ones.

I still find it hard to accept they are both on equal footing as concerns coding but that's not necessary to discuss anymore from this point of view, only for RollbackRx customers who have long suffered from issues with it.

I'm pleased with EAZ-FIX and it performs well, though it can never be nor was ever intended i feel to compete with the likes of FD-ISR in my opinion.

They operate entirely unlike each other and with FD-ISR (Genuine) i know i can depend on it to pull me out of any pinch, the file infector virus i unloaded on it was proof of that, so long as it's COMPLETE baselines=10 were safely kept stored off-machine.

 

Has anyone tried the defrag version of RB? When i was at the site not too long ago it offered me 3 versions for download. Server, pro and another one titled rollback-v81-defrag.

 

I've been watching this thread for a while, hoping to find some answers.

Back in November, I tried the Rx Rollback program - but it didn't install properly on my machine. The Support Team was helpful, but not successful in finding a solution. Finally, they suggested that I wait another 2 weeks when a revision was due. I agreed and waited and watched. I never was able to find a new release. I now believe that there likely was a new release - but, it was in the "Build" numbers - not the "Revision" numbers.

At any rate, a couple of days ago, Feb 6, I came to realize that there was another possibility = EAZ-FIX. My first installation try was unsuccessful.

Trying again, I un-installed it and closed unnecessary programs. I disconnected the Internet and closed my Virus/Firewall Program.
After re-installing, I allowed it to reboot. It stalled eventually and I had to turn off the computer.

Turning it back on, it completed installation and I waited for completion of the ON process. During this procedure, it told me that my 15 day trial was at an end - still Feb 6th.

Support quickly came through for me and supplied a new Activation Code. At this time all seems to be working OK. I still have to "exercise" the program, and will certainly do that in the Activation Period.

While dealing with EAZ-FIX, I inquired about the apparent commonality of the two programs, and was told, "Eaz-fix and Rollback Rx are exact same program branded with different names." Incidentally, my "version" is EAZ-FIX Professional 8.1, 2692876302.

It seems pretty obvious to me that my version is just a few steps away from the number listed in the Title of this Thread.

Another leap of faith, leads me to the conclusion that the exact same Programmers are working both programs - making adjustments for different company names, addresses, etc.

If one accepts the above, then it is not much of a jump to the belief that the same programmers are supplying Support Team efforts for both companies.

Although .... Why two companies to market the same software. One is on the West coast - the other in Penn.

-------------------------

Another question: Assuming I Do decide to buy the program - is there a reason to choose one company over the other?

As far as I can tell, EAZ-FIX can be bought from a third company for $49 and Rx Rollback from Horizon for $69 - with the possibility of a 15% discount from Horizon, as follows:

"customers that wish to purchase new/upgrade products and clients that are upgrading from any competitive product. All that is required is that you post your experiences with us."

Thanks in advance for your thoughts.

 

BINGO!

My thoughts exactly. And from real world experience most prudent and especially cautious or thrifty customers don't always accept everything thats said or claimed in brief with any certainty, so in the end we come away no more confident then before, only curious.

Irregardless of what they might have said, it's as obvious as the night separates the day on this planet, that these 2 programs are/were very different internally if even the least bit slightly, in spite of announcement or build numbers.

Your own machine's results to the program cannot tell a tail, it either works or it doesn't.