More quitting forever

[Paul2]

Occasionally, in particular after a script does not run because the computer was turned off, Retrospect will start immediately on power-up the next morning and try to run the missed script. I click the Cancel button before the backup starts, then tell Retrospect to skip this run and wait until the next scheduled backup. So far, so good.

 

Then I tell it to quit. It won't. It sits there, with "Quitting..." in the status bar, forever as far as I can tell. I let it sit for an hour once, and there was no change. Even the Task Manager has difficulty making it go away.

 

I am running Retrospect 6.0 on Windows XP with a P4 2.4 GHz, backing up to a file on a different hard disk. I saw your advice earlier about turning off System Restore, but I'm not convinced that's a good idea overall. I could turn it off for the disk the backup file is on, because I don't use that disk for anything else. But would that help? And why doesn't Retrospect work properly if System Restore is turned on?

 

 

 

[AmyJ]

See the following KB article for more information on System Restore and Retrospect:

 

http://www.dantz.com/index.php3?SCREEN=kbase&ACTION=KBASE&id=27294

 

You can try turning it off for only the destination drive.

[Mayoff]

If turning system restore off solved your problem, please join this notify mailing list to be emailed when a fix is available.

 

http://list.dantz.com/mailman/listinfo/xp_system_restore

[Paul2]

Turning it off only for the destination drive seems to have fixed the problem. I don't mind turning it off for that drive because there's nothing important on there except the backup file.