Hi, I had someone from the technical team go over this, to clarify. Here is what he has to say:
The reason that we install something is that we need a process to run during the start-up phase. We do this so that when the machine has booted we confirm that the repair took place properly. At this point, if needed, the user may undo the repair and claim their money back if not satisfied. The user gets a refund in return for a feedback on their experience so we can perfect the user experience and the repair quality. After the first reboot this will no longer be in the start-up, for obvious reasons.
Hope it makes sense.
Sincerely,
Nicholas Black
Marketing Director
www.reimage.com
nico at reimage dot com
Office: +972 (3) 575-9-757 x104
Mobile: +972 (54) 250-9-777
Fax: +972 (3) 521-2-361
It seems to me that "the user may undo the repair and claim their money back if not satisfied," means that the "repair" must be removed and the system restored to its condition before the "repair" started.
This is just a bit scary. In my 17 years on computers, I've seen too many times that an "undo" fails to put a system exactly like it was unless it's not an "undo" but an image restore.
I find it hard to believe you create an image and restore it because that is where a significant cost would be, proportionate to the data size of the install partition, which I'm sure you'd have to store on your server.
Which is it? An "undo," or do you take an image before the "repair" and restore it?
It
must be an "undo." Therefore, frankly, I'd be just a bit suspect about the quality of the "undo."
What kind of time frame does the user have to evaluate the improvements? It's it's 30 days and the user installs several programs, is the "undo" going to remove or affect those programs?
Home
Help
Chat
Connect
Posts
Login
Register
Author