Unable to install Rollback Rx 9.1 in VMware

[salvor]

I have 4 Rollback Rx v9 licenses and am trying to install my 3rd unused license to VMware Player 3.1.3 with Windows 7 64-bit guest OS.

After installing, I get the following message during boot, and Rollback Rx automatically uninstalls itself:

Testing memory 8160400 ...
The disk's total sectors is not consistent with the disk size.
Setup cannot continue.


My vmware disks are:
1. "C:" 127.90 GB, 97.81 GB Free, NTFS,
(we tried both "growable" and "preallocated" 128 GB .vmdk for C
2. "System Reserved" 100 MB, 72 MB Free
(created by Windows 7 automatically)

During installation, I only check "C:" in the "Select partition(s) you would like to protect:" question.

NOTE: We tried both "dynamic" and "preallocated" .vmdk for C: -- both failed with same error.

Here's my setup:

Version: 9.1
Build: 2695569418 (according to web page)
Released: November 15, 2010
Guest OS: Windows 7 Home Premium 64-bit (VMware Player 3.1.3)
Host OS: Windows 7 Professional 64-bit
CPU: AMD Phenom II X3 720

Since VMware Player 3.1.3 is free, and can create virtual machines, I hope the Rollback Rx team can help me resolve this quickly.

Two of our developers are waiting for this problem to be fixed so they can use their new VM, so this is rather urgent for us.

Thanks in advance for any help.

[Jimmy]

hello,

i have rollback installed on a VM from virtualbox, XP SP3

with dynamically expanding disks.

works fine

it should also work in vmware player, and also with win 7 as VM

so its not the product, it has something to do with your specific setup

the question is what ?

did you make the disk "writetrough" so that all changes are lost if you close the VM ?

is your VM clean ?

Jimmy

[HDS-Jacob]

Originally Posted by salvor

I have 4 Rollback Rx v9 licenses and am trying to install my 3rd unused license to VMware Player 3.1.3 with Windows 7 64-bit guest OS.

After installing, I get the following message during boot, and Rollback Rx automatically uninstalls itself:

Testing memory 8160400 ...
The disk's total sectors is not consistent with the disk size.
Setup cannot continue.


My vmware disks are:
1. "C:" 127.90 GB, 97.81 GB Free, NTFS,
(we tried both "growable" and "preallocated" 128 GB .vmdk for C
2. "System Reserved" 100 MB, 72 MB Free
(created by Windows 7 automatically)

During installation, I only check "C:" in the "Select partition(s) you would like to protect:" question.

NOTE: We tried both "dynamic" and "preallocated" .vmdk for C: -- both failed with same error.

Here's my setup:

Version: 9.1
Build: 2695569418 (according to web page)
Released: November 15, 2010
Guest OS: Windows 7 Home Premium 64-bit (VMware Player 3.1.3)
Host OS: Windows 7 Professional 64-bit
CPU: AMD Phenom II X3 720

Since VMware Player 3.1.3 is free, and can create virtual machines, I hope the Rollback Rx team can help me resolve this quickly.

Two of our developers are waiting for this problem to be fixed so they can use their new VM, so this is rather urgent for us.

Thanks in advance for any help.

Hi salvor,

Welcome to the Horizon DataSys forum. Feel free to also submit a ticket and contact support at http://support.horizondatasys.com

Best,
Jacob

[Jimmy]

here i am again

posted your error into google en see what i have found

with the sisterprogram eazfix it seems to be a common problem

they write on the FAW following solution:

Solution

Press any key to restart the computer. Windows will load.

Please check the following conditions:

1. The PC does not have the latest service pack. Please apply the latest service pack before setup EAZ-FIX.
3. Apply the fix provided by Microsoft for the 137GB limit.
2. The PC has an old BIOS which do not report correct disk size for large hard disks.

Please collect the following three log files and send them to support@eazsolution.com for technical assistance:

setup.log (c:\program filese\azfix)

subconsole.log (c:\program files\eazfix)

128.dat (c:\program files\eazfix)

so, it has something to do with your OS not being up to date

jimmy

[Jimmy]

and there is more...

you should check the forum from commodo time machine, also a similar product

there is a thread conceirning your post

jimmy

[salvor]

Originally Posted by HDS-Jacob

Hi salvor,

Welcome to the Horizon DataSys forum. Feel free to also submit a ticket and contact support at http://support.horizondatasys.com

Best,
Jacob

Jacob,

Thanks, I submitted a ticket and included the license number in the ticket.

[salvor]

Originally Posted by Jimmy

here i am again

posted your error into google en see what i have found

with the sisterprogram eazfix it seems to be a common problem

they write on the FAW following solution:

Solution

Press any key to restart the computer. Windows will load.

Please check the following conditions:

1. The PC does not have the latest service pack. Please apply the latest service pack before setup EAZ-FIX.
3. Apply the fix provided by Microsoft for the 137GB limit.
2. The PC has an old BIOS which do not report correct disk size for large hard disks.

Please collect the following three log files and send them to support@eazsolution.com for technical assistance:

setup.log (c:\program filese\azfix)

subconsole.log (c:\program files\eazfix)

128.dat (c:\program files\eazfix)

so, it has something to do with your OS not being up to date

jimmy

Jimmy,

Thanks for the suggestions!

I also came across the eaz post while Googling. I tried changing a vmware bios setting from "DOS" to "Other" for large disks but it didn't help. I also tried booting from C: instead of the hidden 100 MB partition created by Windows 7 64-bit. Now I have a 100 MB "unallocated" partition, but I didn't see an easy way to delete that and resize the main partition on top of it (fearing Windows 7 uses non-standard MBR, etc. for "system reserved" partitioning) But I backed up the .vmdk before trying all the experiments (it just takes so darned long compared to RollBack Rx).

I installed all the important updates from Microsoft, activated Windows 7, installed Visual Studio 2008 SP1, checked for updates again and rebooted several times before installing Rollback Rx.

Thanks again for the suggestions, I submitted a ticket and hope to get a solution soon.

[salvor]

Support responded quickly to my ticket, and suggested that I try increasing the disk size, and that fixed the problem.

The problem was caused by having less than 128 GB free space during installation.

IMHO, the installer should check for this before at the beginning of installation (before writing to HD) in the next release of Rollback Rx. The cryptic error message during boot resulted in avoidable lost time & frustration.

My final VMware Player 3.1.3 setup is:

160 GB virtual disk (100 MB System Reserved, 159.9 C
Actual size of .vmdk is about 37 GB (no need to preallocate disk space.)

My "system reserved" partition was restored from backup before installing Rollback Rx. So I'm assuming installation will be smooth as long as there's more than 128 GB free space during installation on a default Windows 7 partition setup.

Happy holidays!

[HDS-Jacob]

Thanks for the feedback and updates!

Best,
Jacob

[Owl]

And to think my first hard drive was 20Mb!