J
Josef Stalin
Comrade,
Mother Russia calls upon your loyal dedicated services once again.
I loaded a different version of a bootdisk from bootdisk.com that had
scandisk on it. The version that I've been using for years only had chkdsk.
I ran scandisk on my 'C' drive and found a bunch of problem that chkdsk
never found. Moral of the story is that if you don't have NTFS, use
scandisk instead of chkdsk.
One curious problem that scandisk detected was the existence of the file
\\winnt\system32\colbaXt.dll where 'X' is actually the heart shaped
character. Doing a directory search of dir /s c:\colba?t.dll to find out
what the actual file name was, I found 2 instances of colbact.dll where the
2nd instance was in C:\WINNT\ServicePackFiles\i386. There was a recent
thread how one should never remove the ServicePackFiles directory since SFC
needs that directory to protect your critical system files but apparently
SFC wasn't working as advertised I went to another one of my home computers
and found 3 instances of that file. So I ran SFC /scannow to make sure that
everything was fine and SFC asked me to put in my W2K disk. What's the point
of all this redundancy if SFC still needs the W2K disk anyway? Why not just
blow the extra directories away?
BTW: I couldn't seem to understand what function colbact.dll serves. From
what I read, it sounds like a critical file but my system "seems" to be
running fine without it anyway.
Uncle Josef
Mother Russia calls upon your loyal dedicated services once again.
I loaded a different version of a bootdisk from bootdisk.com that had
scandisk on it. The version that I've been using for years only had chkdsk.
I ran scandisk on my 'C' drive and found a bunch of problem that chkdsk
never found. Moral of the story is that if you don't have NTFS, use
scandisk instead of chkdsk.
One curious problem that scandisk detected was the existence of the file
\\winnt\system32\colbaXt.dll where 'X' is actually the heart shaped
character. Doing a directory search of dir /s c:\colba?t.dll to find out
what the actual file name was, I found 2 instances of colbact.dll where the
2nd instance was in C:\WINNT\ServicePackFiles\i386. There was a recent
thread how one should never remove the ServicePackFiles directory since SFC
needs that directory to protect your critical system files but apparently
SFC wasn't working as advertised I went to another one of my home computers
and found 3 instances of that file. So I ran SFC /scannow to make sure that
everything was fine and SFC asked me to put in my W2K disk. What's the point
of all this redundancy if SFC still needs the W2K disk anyway? Why not just
blow the extra directories away?
BTW: I couldn't seem to understand what function colbact.dll serves. From
what I read, it sounds like a critical file but my system "seems" to be
running fine without it anyway.
Uncle Josef