Re: norton goback
From: Dale (Dale_at_discussions.microsoft.com)
Date: 01/27/05
- Next message: plaststraw: "Re: Start Menu"
- Previous message: Ron Chamberlin: "Re: CPU Usage"
- In reply to: Vanguard: "Re: norton goback"
- Messages sorted by: [ date ] [ thread ]
Date: Wed, 26 Jan 2005 17:09:03 -0800
"Vanguard" wrote:
> "Darrell S" <dumbwid@fox.com> wrote in message
> news:UlUJd.1998$1t.11@fed1read06...
> > "Vanguard" <vanguard_stealth@yahooNIXTHIS.com> wrote in message
> > news:OiOfVB6AFHA.2540@TK2MSFTNGP09.phx.gbl...
> >> "CS" <nomail@hotmail.com> wrote in message
> >> news:ki9ev0ln7r7nh549aoo2gi455rntiq6rkm@4ax.com...
> >>> On Tue, 25 Jan 2005 20:59:01 -0800, "Dale"
> >>> <Dale@discussions.microsoft.com> wrote:
> >>>
> >>>>as anyone had trouble installing Norton Goback from SystemWorks
> >>>>2005?
> >>>>I get "Installation Failed". And guess what! No solutions from
> >>>>Symantec.
> >>>>This has been problem since Oct 2004.
> >>>
> >>> Do you by chance have Partition Magic installed on the same drive
> >>> you're trying to install Goback to?
> >>
> >>
> >> PartitionMagic would only cause a problem if BootMagic (included)
> >> were also installed. GoBack and BootMagic usurp the bootstrap area
> >> (first 460 bytes) of the MBR (master boot record) and thus will
> >> conflict with each other. However, it is unlikely the install
> >> programs care about what is currently in the MBR bootstrap area and
> >> simply overwrite it (which means whatever you install last will
> >> disable what you installed first). Other than installing BootMagic,
> >> nothing of PM is resident or effected (it's just a bunch of files
> >> sitting on your drive). If the OP isn't multibooting different
> >> instances of operating systems, there would be no reason to install
> >> BootMagic.
> >>
> >> There are also problems when using drive imaging software when GoBack
> >> is inuse, but if you have drive imaging software then you don't need
> >> GoBack.
> >
> > Hmmm. I have GoBack AND DriveImage 7.0 and use them both with no
> > problems. But I've never had to to use DI 7.0 to re-image my hard
> > drive. Perhaps the reason I don't have the problem you're discussing
> > could be that GoBack is controlling my internal hard drive and DI 7.0
> > is created the backup image on my external hard drive and that image
> > should include that current setting for GoBack.
> >
> > I use GoBack frequently. It is much more current that my DI image
> > since it keeps a running track of everything right up to the current
> > minute. If I do something to my computer I don't like I usually just
> > use GoBack to go back before I made that change. I also like GoBack's
> > file memory. If I want to see a previous version of any file I've
> > changed I can go back and see those previous versions. I can choose
> > to either overwrite my current version with a previous version or I
> > can recover the old version to a different folder or with a slightly
> > changed filename so I can compare my current version with the previous
> > one to make a choice. (or even to copy/paste portions from one to the
> > other).
> >
> > Of course all of this only goes back as far as the memory space I have
> > allocated for GoBack.
> >
> >
>
>
> http://snipurl.com/cbl9
> With DI7, it says you should disable GoBack before saving an image.
>
> Personally, I never save a disk image with the operating system running
> and with open files. It doesn't make sense to be trying to copy an
> image of an ever-changing state. I boot using the DriveImage rescue
> diskettes and then use it to save or restore images. Under that
> condition, I doubt GoBack would cause a problem.
>
> I think Symantec is more concerned regarding an image restore. You
> could end up restoring a partition but not restore the MBR that existed
> at the time you saved that partition (i.e., the drive image). If you
> had multiple partitions and created images of them at different times,
> and if DI included the MBR bootstrap code (actually all of track 0),
> then which MBR do you restore when you restore just one of the
> partitions? I've actually ran into this where the partition table for a
> saved MBR did not match the current setup of the drive (the partitions
> had been changed since then) and it took quite a bit of work to get a
> working partition table.
>
> --
> _____________________________________________________________
> Post your replies to the newsgroup. Share with others.
> For e-mail: Remove "NIXTHIS" and append "#VS811" to Subject.
> _____________________________________________________________
>
> No partioning or drive imaging software.
ngb.log bottom line says "This installation is forbidden by system policy"
luresult.log says "Install failed 16. Liveupdate install failed due to
internal error"
- Next message: plaststraw: "Re: Start Menu"
- Previous message: Ron Chamberlin: "Re: CPU Usage"
- In reply to: Vanguard: "Re: norton goback"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
