GoBack won't install, freshly built system

[NeverLift]

After a horror story of simultaneous disk crashes -- which is not
germane -- I have a freshly rebuilt system on my Dell 2400 with a new
WD 120gb master. Win 2k, all patches and updates. The usual
applications -- Office 2000, Verio, Norton System Works 2003, Zone
Alarm.

Trying to install GoBack from the Norton SystemWorks 2003 CD, I get
the message -- which I've found posted, but no solution -- "GoBack is
unable to determine which of your hard drives is the boot drive."
I've turned the second drive off in the BIOS setup, and physically
disconnected it, resetting the jumper as required by WD, same message
occurs.

It's a single partition basic drive -- not dynamic -- and, being a
fresh build from zero, has never had GoBack on it.

I have a second non-Dell white box system, same WD drive as master,
two other drives, all sorts of software on it, GoBack is installed and
working just fine.

The prior drive on the Dell was an 80gb Hitachi which I took down to
zeros and also rebuilt using Win2k etc etc, and GoBack installed on it
just fine, as it did on the second drive, a Maxtor 80gb. Both of
these, BTW, are history -- one mechanical failure, the other surface
failure.

Symantec site has nothing useful to say about the matter.

Any suggestions?

 

[PA20Pilot]

Hi,

Might you have your CD in the BIOS boot sequence? I don't know if Norton
could get confused with a setting in there or not, but it's pretty easy
to change and see if anything different happens when you try to install
again.


---==X={}=X==---


Jim Self
AVIATION ANIMATION, the internet's largest depository.
http://avanimation.avsupport.com

Your only internet source for spiral staircase plans.
http://jself.com/stair/Stair.htm

 

[NeverLift]

Not the issue. The system is already running, as it should be, when I
put the Norton 2003 SystemWorks CD in the drive. The CD autostart
starts up just fine when it spins up. It's clicking on "Install
GoBack" that (1) unpacks all the files it needs, then (2) gives me the
Symantec equivalent of "in your ear, buddy" message.

Symantec acknowledges there is a problem on the page at their Web site
discussing this message, but offers no workaround or hope of a fix. I
have since heard from others who've had this experience.