Just a quick line to mention that the Windows System File Checker tool produces logs that are nearly unreadable, and a pain to parse.
A friend of mine had some system files that did not check out, and could not be repaired. After confirming we both ran the same version down to the same patchlevel of Windows 7, he asked if I could send the original files his way, providing me only with the output of
findstr /C:"[SR]" %windir%\logs\cbs\cbs.log >sfcdetails.txtOf course, I indulged.
The following one bash one liner from hell occured:
grep -i -e "could not" -e "cannot" sfclog.txt | \awk -F ';' '{ print $1; }' | awk -F "??" '{ print $3; }' | \sed -e 's/^\\//' -e 's/"\\\[.*\]"/\\/g' -e 's/"$//' | sort | uniq | \tee -a ./win7sysfiles/FILELIST.TXT | \sed -e '/^$/d' -e 's/\\/\//g' -e 's/^C:\(.*\)$/\/media\/wsystem\1/' \-e 's/\([ ()]\)/\\\1/g' | \while read i ; do if [ -f "$i" ] ; then STATUS="ERROR" ; \cp "$i" ./win7sysfiles/ && STATUS="COPIED" ; else STATUS="MISSING" ; fi ; \printf "%-30s%-30s\n" "`basename \"$i\"`" "[$STATUS]" ; done \&& echo -n "Creating checkums..." ; for f in ./win7sysfiles/* ; do \md5sum $f > $f.md5sum ; done ; echo "done."
Horrible, yet probably semi-useful to someone.
Salut Alex,
check tes e-mail!!!
Marc