Windows File Protection Gets In The Way
I've been doing this for many, many years. I use a geezer technique: a batch file! I use Map Network Drive to map by laptop's C: drive to L: (for laptop) and then the batch file copies things from C: to L:. For the actual copying, I used to use the XCOPY command; now I use ROBOCOPY.
All was well in Mudville until I migrated to Windows XP. Now I find that XP won't let me mess with files in the Windows directory. This is unfortunate because there are several .INI files in \Windows that I would like to sync over to my laptop.
I can understand why Windows would want to be protective of \Windows, but geez, I just want to copy a few .INI files! Do you know of a way around this? ---Rex Swain
All versions of Windows after Windows 98 feature a
program that protects Windows system files--- called Windows File Protection (WFP)
in Windows 2000 and Windows XP, and System File Protection (SFP) in Windows ME.
It runs in the background, and protects key system files from being overwritten,
deleted or modified by malware or users.
There are a couple ways around this protection. The first and best known is a
Registry hack that's pretty ugly, and requires the use of a hex editor. This
method ( http://tinyurl.com/qdl9a ) has
been covered extensively, so I won't reproduce it here.
The second method is to use a freeware tool called Windows File Protection
Switcher ( http://tinyurl.com/sxkal ).
This program does only one thing: It toggles WFP on and off. If you want to run
WFP most of the time, you might even trigger Windows File Protection Switcher
from your batch files, flipping it off at the beginning of your process, then
flipping it back on at the end.
You also can move the INI file contents by using Notepad to edit both INI files, and copy/paste the contents from one to the other; or by renaming a copy of the original INI file to TXT, and then moving that TXT file where you want; and then either renaming it INI or using Notepad to move the TXT contents to the INI file.
Lots of options!
