L
Leslie Milton
I rely on the attribute bit for dailly backups of files in work on my XP
professional laptop, using XCOPY to copy only files with A set. I've noticed
lately that, after a cold boot (START as opposed to HIBERNATE), the A bit
reappears as set for many of the files for which it has been cleared by the
XCOPY transfer. I have a batch file CHECKATTR.BAT that checks for files that
would be transferred according to the A bit (Dir *.* /S/A:A ). After running
my XCOPY backup file, CHECKATTR.BAT reveals zero files. But after a re-boot,
it comes up with a list of most of the files in my INWORK folder, so it'd be
a lengthy process copying them all to my USB drive. It seems that somehow XP
is remembering the files that had A cleared and sets them back. I thought
at first this might be yet another irritating feature of my Norton 360
anti-virus program, but In a chat session with a tech, I was assured that
there's no use of the A bit.
I hope someone has a clue to this mystery.
professional laptop, using XCOPY to copy only files with A set. I've noticed
lately that, after a cold boot (START as opposed to HIBERNATE), the A bit
reappears as set for many of the files for which it has been cleared by the
XCOPY transfer. I have a batch file CHECKATTR.BAT that checks for files that
would be transferred according to the A bit (Dir *.* /S/A:A ). After running
my XCOPY backup file, CHECKATTR.BAT reveals zero files. But after a re-boot,
it comes up with a list of most of the files in my INWORK folder, so it'd be
a lengthy process copying them all to my USB drive. It seems that somehow XP
is remembering the files that had A cleared and sets them back. I thought
at first this might be yet another irritating feature of my Norton 360
anti-virus program, but In a chat session with a tech, I was assured that
there's no use of the A bit.
I hope someone has a clue to this mystery.