GoBack again but worse

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Third crash with GoBack.
Both bootdisks. I thought I was safe with two disks.
Its just double problems at least with any Nortons program on disk.
I will not use any Norton program again.

GoBack reboot at start up to protect the disk from being corrupted.
As I can see with recovery tools nothing wrong exept for (probably)
goback.sys.

No way to access my disks or disable GoBack.

I tried to boot on a new installed HD but as masterfile and partion is
changed there is no disks.
Installing GoBack on the new one makes three unuseable disks but on the last
one it is possible to disable GoBack.

So, there is some minor error (probably goback.sys) on one HD and this will
lock up ALL HD with GoBack installed.
If I boot without GoBack there is no disks.

Can someone solve this problem?

Problem is I do not know exactly what GoBack does .... it change masterfile
and partioninformation I think, but how and how to reverse it?
 
I can't help with your specific problem but you've got part of the solution.
After many heartaches I finally got rid of all the Norton programs on my PC.
Long story. I presume someone must be satisfied with them but I have read
this sort of thing many times before.
 
Add my name to the list of "No Norton Software".



I can't help with your specific problem but you've got part of the solution.
After many heartaches I finally got rid of all the Norton programs on my PC.
Long story. I presume someone must be satisfied with them but I have read
this sort of thing many times before.
 
So where are the Recovery images from GoBack? Same drive? Same
partition?[hope not]
Does it not prompt you to make a DOS start-up disk, like Ghost 2003?
What about CD images?

Only trouble with Norton I had was letting it run automatically. [AV]
Otherwise, Imaging software seems fine, to me. But then, I image and then
shut it off.
 
I have installed GoBack on a few computers (for people who are not
knowledgeable and don't care to be) and have not seen any problems. And
remember, these people were not, and still are not, knowledgeable about
computers - yet they are able to use GoBack to save their collective
keisters from the flames of the fire.

But, because of the type of program it is there are rules and regulations
that MUST be followed. One of the main rules is that you "must" uninstall
GoBack if you are changing your present hard drive out for a new one and
still plan to keep the older drive in the system as a slave.

You did not clearly list the "exact" sequence of thing that you did to get
you to your present state, so it is hard to say where you went wrong. All I
can suggest is that you read (really read it now) the extensive help section
that is supplied with GoBack. By doing so, you may find out where you went
wrong and find steps to correct for it.

BTW: I do NOT recommend GoBack for a knowledgeable user. It's a "dummy"
tool, to be used by dummies - but administered by someone who knows
computers well.

--
Regards,

Richard Urban
Microsoft MVP Windows Shell/User

Quote from George Ankner:
If you knew as much as you think you know,
You would realize that you don't know what you thought you knew!
 
GoBack is similar to System Restore - but on steroids! It runs all the time.

--
Regards,

Richard Urban
Microsoft MVP Windows Shell/User

Quote from George Ankner:
If you knew as much as you think you know,
You would realize that you don't know what you thought you knew!

st.daniel said:
So where are the Recovery images from GoBack? Same drive? Same
partition?[hope not]
Does it not prompt you to make a DOS start-up disk, like Ghost 2003?
What about CD images?

Only trouble with Norton I had was letting it run automatically. [AV]
Otherwise, Imaging software seems fine, to me. But then, I image and then
shut it off.


Bjorn said:
Third crash with GoBack.
Both bootdisks. I thought I was safe with two disks.
Its just double problems at least with any Nortons program on disk.
I will not use any Norton program again.

GoBack reboot at start up to protect the disk from being corrupted.
As I can see with recovery tools nothing wrong exept for (probably)
goback.sys.

No way to access my disks or disable GoBack.

I tried to boot on a new installed HD but as masterfile and partion is
changed there is no disks.
Installing GoBack on the new one makes three unuseable disks but on the
last
one it is possible to disable GoBack.

So, there is some minor error (probably goback.sys) on one HD and this
will
lock up ALL HD with GoBack installed.
If I boot without GoBack there is no disks.

Can someone solve this problem?

Problem is I do not know exactly what GoBack does .... it change
masterfile
and partioninformation I think, but how and how to reverse it?
Click to expand...
Click to expand...
 
Thanks. Funny thing, I was just considering GoBack for my latest XP install.
Cancel THAT! Ghost 2003 it is.

Richard Urban said:
GoBack is similar to System Restore - but on steroids! It runs all the time.

--
Regards,

Richard Urban
Microsoft MVP Windows Shell/User

Quote from George Ankner:
If you knew as much as you think you know,
You would realize that you don't know what you thought you knew!

st.daniel said:
So where are the Recovery images from GoBack? Same drive? Same
partition?[hope not]
Does it not prompt you to make a DOS start-up disk, like Ghost 2003?
What about CD images?

Only trouble with Norton I had was letting it run automatically. [AV]
Otherwise, Imaging software seems fine, to me. But then, I image and then
shut it off.


Bjorn said:
Third crash with GoBack.
Both bootdisks. I thought I was safe with two disks.
Its just double problems at least with any Nortons program on disk.
I will not use any Norton program again.

GoBack reboot at start up to protect the disk from being corrupted.
As I can see with recovery tools nothing wrong exept for (probably)
goback.sys.

No way to access my disks or disable GoBack.

I tried to boot on a new installed HD but as masterfile and partion is
changed there is no disks.
Installing GoBack on the new one makes three unuseable disks but on the
last
one it is possible to disable GoBack.

So, there is some minor error (probably goback.sys) on one HD and this
will
lock up ALL HD with GoBack installed.
If I boot without GoBack there is no disks.

Can someone solve this problem?

Problem is I do not know exactly what GoBack does .... it change
masterfile
and partioninformation I think, but how and how to reverse it?
Click to expand...
Click to expand...
Click to expand...
 
Thanks Richard,
thanks to others too.
I follow your tip from Symantec site.
Using ctrl-alt-G at boot. I have tried before.
Seems to me that this can work one time of 4-5 times.
I can not press the keys early, must wait close to when GoBack should start
at boot and keep the keys down.
I have never before got that screen with F option.
One disk was bootable after first try, the primary disk was acceccable after
pressing F 2 times. Boot is still not recovered on C:\.
I get windows blue screen saying there is some problem with goback.sys.

Thanks for that tip from Symantec. Its good.
 
I have used GoBack for years on my last 3 computers. I disagree that it is
for dummies only. It is an excellent tool if used correctly (like any
tool). It is not simply System Restore on steroids. It keeps track of all
activity (not just the operating system) within it's allotted memory. It
even allows you to restore files you have overwritten to a new file
condition. You can locate previous versions of a file (within GoBack's
memory) and overwrite the existing file or restore it to a different folder
or slightly change the filename to allow you to open both versions and cut &
paste.

That said, I also use DriveImage 7 which (I heard) was bought by Ghost in
its later versions. I maintain several images of my hard drive on an
external USB hard drive. If I am unable to access my hard drive to run
GoBack I can boot to the DI 7.0 CD and access my USB drive to re-image my
hard drive. (as long as it is still physically intact.
 
Hi,

Ghost is a Norton product now also. I would suggest going with Acronis
True Image
http://www.acronis.com/homecomputing/products/trueimage

--
Regards,
Bert Kinney MS-MVP Shell/User
http://bertk.mvps.org

st.daniel said:
Thanks. Funny thing, I was just considering GoBack for my latest XP
install. Cancel THAT! Ghost 2003 it is.

Richard Urban said:
GoBack is similar to System Restore - but on steroids! It runs all
the time.

--
Regards,

Richard Urban
Microsoft MVP Windows Shell/User

Quote from George Ankner:
If you knew as much as you think you know,
You would realize that you don't know what you thought you knew!

st.daniel said:
So where are the Recovery images from GoBack? Same drive? Same
partition?[hope not]
Does it not prompt you to make a DOS start-up disk, like Ghost 2003?
What about CD images?

Only trouble with Norton I had was letting it run automatically.
[AV] Otherwise, Imaging software seems fine, to me. But then, I
image and then shut it off.


:

Third crash with GoBack.
Both bootdisks. I thought I was safe with two disks.
Its just double problems at least with any Nortons program on disk.
I will not use any Norton program again.

GoBack reboot at start up to protect the disk from being corrupted.
As I can see with recovery tools nothing wrong exept for (probably)
goback.sys.

No way to access my disks or disable GoBack.

I tried to boot on a new installed HD but as masterfile and
partion is changed there is no disks.
Installing GoBack on the new one makes three unuseable disks but
on the last
one it is possible to disable GoBack.

So, there is some minor error (probably goback.sys) on one HD and
this will
lock up ALL HD with GoBack installed.
If I boot without GoBack there is no disks.

Can someone solve this problem?

Problem is I do not know exactly what GoBack does .... it change
masterfile
and partioninformation I think, but how and how to reverse it?
Click to expand...
Click to expand...
Click to expand...
 
Darrell, I use GoBack in exactly the same way using Ghost 10 to make daily
images to an external drive.. I've never had a problem with it and wouldn't
be without it. But I also agree that if you don't understand how it works
and don't follow the instructions it could be bad.
 
Have you tried the procedure on the Symantec site for booting from a floppy
and removing the modification that GoBack made to the mbr?
 
I've never used that procedure on my newest computer (3 years old) since I
don't use a bootable floppy any more now that the XP CD is bootable. But I
remember you couldn't boot to a floppy and have it work right if you didn't
first allow the hard drive boot sequence to go to the GoBack display and hit
the space bar. That brings up a menu allowing you to choose to boot from a
floppy disk. This allows you to then place the floppy in the drive and it
will boot to allow you access to the C: drive. Without having done that
preliminary step if you just place the bootable floppy in the drive it will
boot from the floppy but you will not be able to access the C: drive.
 
Interesting link. I've never had that problem since my computers came with
GoBack installed (Gateways). But I've copied your post to my Saved folder
for future reference. Thanks.
 
Back
Top