so add some and replace Norton with Avast free or pay Antivirus. since the checkdisk takes days, I assume your system is starving for RAM. Money spent on Norton is better spent on faster hardware. and since the backup is useless there is no reason to keep Norton. Replacing Norton is the first thing I would have done. Backups, meaning REAL backups, will continue to be done with DiskWizard, which takes a complete image and saves it, thereby avoiding the hundreds of hours required to reinstall all the applications and the OS onto a new drive. In the meantime, I'm going to flush Norton Security Suite and replace it with something else, provided I can find something adequate. when scrap metal prices go up a bit more, I'll scrap 'em. I have a pile of scrap hard drives that purportedly contain data, none of which I can access. I find it both stupid and silly that the Symantec people think that a copy is a backup, and that a backup on the very drive that's being backed up is of any value. Then, if there's another occurrence of the re-enabling of backup, it will show up on the NAS, where I can more easily dispose of it, because it will be small.
However, I've set it to backup a small USB drive to my NAS, whjich is where the backups I actually use reside. Norton Security Suite keeps on complaining that a backup hasn't been done, despite the fact that "Backup" has been disabled. I don't know whether it will arise again. Now, I have solved this problem to limited extent. The result is that I have to run the three-day chkdsk followed by a four-day delete, during which time so much of the processing bandwidth is used that the computer is entirely useless until it's complete. Once that's done, Norton can't perform its ultra-slow delete. FUrther, because of the large size of the "backup" set, it takes several days just to figure out that it's too large for the "recycle bin." Deleting it requires that I first run chkdsk on the drive onto which Norton has written the backup, which XP thinks is corrupt. This means I can't move it, which is something I attempted. One accompanying issue is that the OS interprets the "backup" set as being corrupted, hence, won't operate on it.
0 kommentar(er)
