B
Bert Kinney
Hi,
My experience, System Restore has never failed me!
My experience, System Restore has never failed me!
D
Dave
I guess that's why there's no one answer for everyone. We all have our own
experiences, opinions and tastes. Now all we have to do is be content to
let others have their own opinion and not feel we have to change their
views.
experiences, opinions and tastes. Now all we have to do is be content to
let others have their own opinion and not feel we have to change their
views.
G
Gerry Cornell
Dave
It's worth trying to understand why experiences are different.
Did you ever try System Restore? Was it with Millennium Edition or
XP? Were you using a removable drive at the time?
--
Regards.
Gerry
~~~~
FCA
Stourport, England
Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~
It's worth trying to understand why experiences are different.
Did you ever try System Restore? Was it with Millennium Edition or
XP? Were you using a removable drive at the time?
--
Regards.
Gerry
~~~~
FCA
Stourport, England
Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~
B
Bert Kinney
I agreed Dave. Have a nice day.
D
Dave
Yes, I've used it. It was Windows XP. And I wasn't using a removable
drive. But like others, I've made my decision based on my experience and
am totally satisfied with GoBack which does more for me than System Restore
anyway.
drive. But like others, I've made my decision based on my experience and
am totally satisfied with GoBack which does more for me than System Restore
anyway.
D
Dave
You too.
Bert Kinney said:
D
Darrell S
Gerry said:
As long as you realize that System Restore will only restore System files to
a previous condition. This will frequently make your computer bootable and
useable once again but will not restore non-system programs/files to their
past condition. GoBack DOES do that.
J
Jim
Besides, the problem isn't with GoBack anyway. It's detecting his
system as a multiboot system, which is unsupported by GoBack. He needs
to figure out what the other boot option on his system is. Since it's
an HP, there's probably a restore partition. He needs to talk to HP
about it.
system as a multiboot system, which is unsupported by GoBack. He needs
to figure out what the other boot option on his system is. Since it's
an HP, there's probably a restore partition. He needs to talk to HP
about it.
G
Guest
Now that I've read all these responses, you are probably right about the
"HP_Recovery (D
" drive I see on my computer. Since I've never seen this on
any of my past computers, I never knew how this "recovery drive" worked.
"HP_Recovery (D
" drive I see on my computer. Since I've never seen this onany of my past computers, I never knew how this "recovery drive" worked.
D
Dave
Like I said earlier, GoBack isn't compatible with modified MBR's. I had
the same situation with my HP. I didn't like the recovery partition
anyway. So I bought a full retail version of Windows XP and did away with
the hidden recovery partition. The system has been much better since then
and GoBack works perfectly.
Mine was out of warranty anyway so it didn't make any difference.
Dave
the same situation with my HP. I didn't like the recovery partition
anyway. So I bought a full retail version of Windows XP and did away with
the hidden recovery partition. The system has been much better since then
and GoBack works perfectly.
Mine was out of warranty anyway so it didn't make any difference.
Dave
G
Guest
Hi Dave, hi Bob:
I've the same frustrating issue when I try to install GoBack in Windows 2000
environments also. Perhaps my comments could be useful in some way:
We're on a small workgroup network at home with three computers. Two are
desktops runinng Win 2K SP4 (one was an upgrade from Win 98, the other was a
clean installation) and the third is a laptop running XP SP2. None of the
computers were ever configured or partitioned for multiple partitions or for
multi-booting. For example, neither FDISK has ever been run to alter the MBRs
nor EMERGENCY REPAIR DISK been used, and the BOOT.INI files are correct.
How do you explain this? I'm not refuting the bit about GoBack not liking
modified MBRs, but my hunch is that there might be another cause (or causes)
in addition to (or in spite of) what's been previously mentioned. What other
Windows data might GoBack be reading to cause this erroneous determination?
Has anyone come up with other possibilities?
I've the same frustrating issue when I try to install GoBack in Windows 2000
environments also. Perhaps my comments could be useful in some way:
We're on a small workgroup network at home with three computers. Two are
desktops runinng Win 2K SP4 (one was an upgrade from Win 98, the other was a
clean installation) and the third is a laptop running XP SP2. None of the
computers were ever configured or partitioned for multiple partitions or for
multi-booting. For example, neither FDISK has ever been run to alter the MBRs
nor EMERGENCY REPAIR DISK been used, and the BOOT.INI files are correct.
How do you explain this? I'm not refuting the bit about GoBack not liking
modified MBRs, but my hunch is that there might be another cause (or causes)
in addition to (or in spite of) what's been previously mentioned. What other
Windows data might GoBack be reading to cause this erroneous determination?
Has anyone come up with other possibilities?
J
JoeM
A few things, first some OEMs put another partion in their machines which
GoBack has trouble reading.
Second I have had several customers whom either have deleted files or have
bad sectors on the drive, are are unable to recover the lost files or repair
the bad sectors without the removal of GoBack. I have had way to many
people having trouble with GoBack and would not recommend using it. If you
could use ghost or backup your data using, Nero, Windows Backup, or OneCare
backup.
GoBack has trouble reading.
Second I have had several customers whom either have deleted files or have
bad sectors on the drive, are are unable to recover the lost files or repair
the bad sectors without the removal of GoBack. I have had way to many
people having trouble with GoBack and would not recommend using it. If you
could use ghost or backup your data using, Nero, Windows Backup, or OneCare
backup.
D
Dave
While everyone has their experiences (good or bad) with GoBack and can make
their recommendations accordingly. Personally I use it with no problems
and love it. But doing a periodic backup isn't quite the same. GoBack is
more than a backup program.
their recommendations accordingly. Personally I use it with no problems
and love it. But doing a periodic backup isn't quite the same. GoBack is
more than a backup program.
K
Kerry Brown
I can echo JoeM's experience. I have seen several computers where the hard
drive was going bad or in one case an overheating CPU caused serious file
corruption and Goback was installed. In these cases Goback caused the
customer to loose data rather than save it. Having Goback installed greatly
hindered getting their data off the disk. Goback is great while it works. If
it goes wrong you will wish you had never heard of it. There is no
replacement for a backup to media that is stored somewhere other than on the
computer. Too many people think Goback is a replacement for a backup.
Kerry
drive was going bad or in one case an overheating CPU caused serious file
corruption and Goback was installed. In these cases Goback caused the
customer to loose data rather than save it. Having Goback installed greatly
hindered getting their data off the disk. Goback is great while it works. If
it goes wrong you will wish you had never heard of it. There is no
replacement for a backup to media that is stored somewhere other than on the
computer. Too many people think Goback is a replacement for a backup.
Kerry
J
JoeM
So true, thank god I am not the only person having these programs
D
Dave
I never suggested that GoBack was a replacement for a periodic backup. I do
them daily.
them daily.
D
Dave
"having these programs"?
JoeM said:
G
Gerry Cornell
Kerry
If the backup is on a second hard drive? Does this not help, save that there
may be a delay in recovery?
--
Regards.
Gerry
~~~~
FCA
Stourport, England
Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~
If the backup is on a second hard drive? Does this not help, save that there
may be a delay in recovery?
--
Regards.
Gerry
~~~~
FCA
Stourport, England
Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~
K
Kerry Brown
If the backup was on second hard drive there would be no problem recovering
data from the backup unless Goback was also configured to protect that
drive. The problem is that many people think that Goback is a backup and
don't do backups. If you do not have another means of backup and something
goes wrong with the hard drive such that Goback itself is corrupted it can
be very hard to get anything off of the hard drive. Goback plays with the
mbr and partition table such that many recovery utilites won't work with the
drive. Usually I can boot from BartPe or a Linux CD or install the drive in
another computer and copy files or repair the file system so that files can
recovered. With Goback installed this is much harder and sometimes
impossible to do.
Kerry
data from the backup unless Goback was also configured to protect that
drive. The problem is that many people think that Goback is a backup and
don't do backups. If you do not have another means of backup and something
goes wrong with the hard drive such that Goback itself is corrupted it can
be very hard to get anything off of the hard drive. Goback plays with the
mbr and partition table such that many recovery utilites won't work with the
drive. Usually I can boot from BartPe or a Linux CD or install the drive in
another computer and copy files or repair the file system so that files can
recovered. With Goback installed this is much harder and sometimes
impossible to do.
Kerry
G
Gerry Cornell
Kerry
Thanks for the explanation.
--
Regards.
Gerry
~~~~
FCA
Stourport, England
Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~
Thanks for the explanation.
--
Regards.
Gerry
~~~~
FCA
Stourport, England
Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~