Knowledge Base Glossary       Exit
(how to) Search  

Browse by Category
Knowledge Base > Archive > Products > BootIt Next Generation > General Information > Using GoBack with BootIt NG

Using GoBack with BootIt NG

BootIt NG version 1.29+ is aware of, and can be used with, Roxio's GoBackŪ 3.11b59 product. It's been reported that it also works with GoBack 4. Although not officially supported by TeraByte Unlimited,  this section will give you an example of how you could setup a multi-boot system using both products, as well as some issues that may occur.

To install BootIt NG 1.29+ to a system already using GoBack, you'll need to first disable GoBack. Once BootIt NG is installed, you'll have the option to enable GoBack when you boot back into the operating system.

To add another operating system to your system you must first disable GoBack. Once disabled you simply use BootIt NG to setup the new operating system as you normally would. If the operating system you are installing is supported by GoBack, then you can and should install GoBack to it; otherwise, once GoBack is enabled, Win9x/ME systems will run in compatibility mode and NT/2K/XP systems will not boot with an inaccessible boot device error. If you are adding another OS or want to install GoBack to another previously-installed OS, then you simply repeat the procedure of disabling GoBack and then installing GoBack. Be sure that you have a common partition on each hard drive for the GoBack history file. This partition or volume must be accessible and available for for use by the OS for each OS using GoBack.

If you boot an OS that is not in a FAT/FAT32 or NTFS partition or you're booting OS/2, then BootIt NG will automatically disable GoBack. You'll have the option to enable it once you boot back into an OS using GoBack. This will cause the history file to be reset.

One issue you can setup that will be a little confusing until GoBack is changed (if ever) to acknowledge drive mappings to a partition's physical location is if you have your multi-boot setup so each OS you boot is in its own primary partition (so that whichever OS booted is C:) then that the history file won't be able to tell if "c:\somefile.txt" is part of the currently booted OS or another partition. If you try to recover it, it will not find it unless it is indeed part of this partition. Since GoBack works at the sector level (according to documentation), the file information is simply for display and if you roll back the system it will still roll back through all OS's.

For those interested:  This file display problem could probably be fixed internally in GoBack by adding a system startup record to the history file (in the 32-bit OS drivers) which indicates the current partition layout/drive lettering/volume id and/or volume label. The drive letter could then be used as a lookup index or the drive letter could be replaced by a byte index to map where the file actually was and then displayed however the programmer wanted. (i.e. [vollabel]\somefile or  [vollabel]c:\xyz or simply remap to the current lettering if different, such as z:\somefile).

You cannot use BootNow with GoBack enabled. The BootNow version on the BootIt NG download page will simply abort with a write error. There is a version of BootNow which will run with GoBack installed, but GoBack will internally cause problems on the reboot by overriding the boot partition. In addition, if you try to apply the purchased registration codes while GoBack is active, then all settings will be corrupted (you'll need to boot from the diskette/CD and reset all the settings).


How helpful was this article to you?


powered by Lore