Hi
I have an identical problem to that solved here:
https://www.techrepublic.com.com/5208-6239-0.html?forumID=48&threadID=166524&start0
This time I have just upgraded from Norton system Works 2004 to NSW 2005. My machine is a Dell Optiplex GX270. It contains two IDE drives and 1 SATA drive. My OS is WinXP Pro SP2
I installed GoBack as follows – first I uninstalled GoBack 2004 then rebooted. Next, I disabled all non Microsoft services and disabled all startup items using msconfig. I did not disable the Intel services nor the ATI services (my computer would not boot at all until I renabled the ATI services in Safe Mode), nor the Dell iap service.
I next rebooted and installed GoBack. I noticed that when GoBack was being installed, it created a gobackio.bin file on my C: drive (IDE primary master) and my F: drive (the SATA drive). After the first reboot, the GoBack screen appeared, then the boot process continued, only to immediately stop. I got a black screen with the message ‘strike F1 to retry boot, F2 for setup utility’. Pressing F1 returns to the message, and pressing F2 causes the computer to lockup.
I assume the computer is attempting to boot from my SATA drive, as when I reboot, press F12 and choose ‘Primary Master’ (my C: drive), from the list of available boot devices, the GoBack screen appears, and the computer boots normally. Also, if I disable GoBack and reboot, GoBack saya it is removing the GoBack history from the C: drive, and then the computer boots normally from my primary master C: drive. Re-enabling GoBack, returns me to the error message.
Therefore, it seems to me that when GoBack installed the file on my F: drive it has somehow caused it to become ‘live’ again. When I look at the F: drive in Disk Management, the F: drive is not marked as active.