I auto-run a backup program every shutdown that just copies new or changed files to a second drive, using XXCopy. Code: :: Backup new & changed files with XXCopy to F drive :: C: cd C:\Windows\System32\ :: Includes websites, music, pictures xxcopy "E:\Howard\My Documents\" "F:\Data Backups\Howard\My Documents" /E/BI/Q/Y/R/V2 :: Downloaded programs xxcopy E:\Downloads F:\Downloads /S/BI/Q/Y/R/V :: etc Usually works fine, usually only takes a few seconds extra to shut down. Sunday night, starts copying every single file in the source folders, several gig of music, photos, all the other data. Only thing I can think is putting the clocks forward has made WinXP think the timestamps are newer on all the source files. Source drive is FAT32, target is NTFS. Anybody any info?
Let me get this ironed out. You use a backup program that coppies all files that have a timestamp change that is past the time of its most recent coppy. Something went haywire and it coppied EVERYTHING from its target folder, including the things that have not changed? If it did coppy everything then I dont think you can call it a timestamp problem. did you try reinstalling XXCopy?
It worked fine Monday night, the only time it's gone wrong is when XP put the clock forward an hour. Small changes, like adjusting the clock from a time server, don't affect the back-up routine. I think this explains the problem
More likely nobody bothered to FIX the bug in development. Is there something thats keeping you from using a FAT32 backup drive? or an NTFS main drive?
I converted the slave to NTFS to try some XP slip-streaming recovery program that needed that system (& started a 6-page thread here ), left the main drive FAT32 so DOS boot disks would see it OK. Now I know what causes it I can stop wondering wtf?
you could use bartPE and make a new startup/recovery disk, scrap the DOS floppies and convert the fat32 to NTFS.
