| Forum Home | ||||
| Press F1 | ||||
| Thread ID: 43952 | 2004-04-01 21:22:00 | Install/Uninstall question. Just curious. | Allblack (4982) | Press F1 |
| Post ID | Timestamp | Content | User | ||
| 226588 | 2004-04-01 21:22:00 | Hi all, Can anyone please explain the following to me. I installed Go Back from my Norton disk the other night, took about 20 seconds and all's good. Last night I uninstalled it, and the process took two hours and three minutes!!! Suffice to say there were anxious times, I could just see my PC being wiped clean! Anyway, everything's cool, but: Why did it take over TWO HOURS to uninstall a programme that loaded off the disk in under 30 seconds? Dying to know the answer to this if anyone can help. Cheers Tim |
Allblack (4982) | ||
| 226589 | 2004-04-01 21:51:00 | This apparently can be normal for Go Back. You can read all the details here (service1.symantec.com ton%20GoBack&ver=3.5%20Personal%20Edition&src=sg&pcode=ngb&svy=&csm=no). I can certainly understand your concern about this excessive uninstalling time - I wonder how many people stop this process halfway through thinking their machine has frozen and ended up with a bit of a mess left over. |
Jen C (20) | ||
| 226590 | 2004-04-01 21:55:00 | Hi Allblack. Also just curious... why did you uninstall GoBack? I had it for a couple of years and found it very useful on 98SE. Now moved on to XP and it does not like GoBack because it has Revert procedure. | Scouse (83) | ||
| 226591 | 2004-04-01 21:55:00 | > You can read all the details here OK, no you can't. That link worked fine under preview, but not now (must be session based). I will quote what they said instead in the the Symantec Knowledge Base article: Quote: Uninstalling or disabling GoBack takes a long time Situation: You are trying to uninstall or disable GoBack, but the process is taking a very long time--sometimes several hours. It may even appear that the computer or the program is no longer responding. Solution: During the disable or uninstall process, GoBack transitions recently-changed data to the hard disk. GoBack must complete its pending data swapping before the disable or uninstall can be finished. To achieve a high performance level, GoBack optimizes its history data during system idle time. When GoBack is disabled or uninstalled soon after an application puts a heavy demand on the hard drive, GoBack must finish transitioning the data. The time required to disable or uninstall is proportional to the amount of data recently changed. Examples of disk-write intensive operations are copying large amounts data, defragmenting, and performing a thorough ScanDisk. Disabling and uninstalling GoBack can take a long time to perform after massive amounts of disk activity. |
Jen C (20) | ||
| 226592 | 2004-04-02 00:35:00 | Thanks Jen C, that's awesome. Scared the buggery out of me last night, I can tell you! Got rid of it because I ended up with GoBack windows everywhere when I booted up the PC, and it took longer to load etc etc. The Restore function in XP seems great, so didn't see the need for it. Cheers Tim |
Allblack (4982) | ||
| 226593 | 2004-04-02 01:41:00 | I used to use it myself but these days just rely on using a image backup using drive image less HDD thrashing and cpu usage . | kiwibeat (304) | ||
| 1 | |||||