Re: Repairing Usn Journal

Tech-Archive recommends: Fix windows errors by optimizing your registry



On Fri, 09 Sep 2005 01:31:33 -0400, Mark V <notvalid@xxxxxxxxxxx>
wrote:

>In microsoft.public.win2000.registry Bob wrote:
>
>> On Tue, 06 Sep 2005 18:20:30 -0400, Mark V
>> <notvalid@xxxxxxxxxxx> wrote:
>>
>>>> I could do an "In-Place Upgrade" which is essentially the same
>>>> as starting over. But I will wait until I am forced to
>>
>>>Not really. Although "in-place upgrade" / "install over"
>>>/repair installation" do reset a lot to as-installed, I would
>>>not say they are essentially the same when used in a situation
>>>such as this.
>>
>> I reinstalled a recent version of SP4 and now I can't do an IPU.
>> The setup disk won't copy certain files with the extension
>> ".icn", likely because they are not on the setup CD.
>>
>>>Hopefully you will find the problem one way or another.
>>
>> I found out that Norton Protection was not the culprit, so I
>> reinstalled it, because it is useful. The rest is crap.
>>
>> I also found out that disabling the Write Cache does not help.
>> As those Microsoft articles pointed out, the write cache problem
>> was fixed with SP3 and anyway it only applies to SCSI drives - I
>> have IDE drives.
>>
>> As mentioned above I reinstalled a recent version of SP4 so
>> maybe there was something in there that fixed the problem.
>>
>> I did one other thing that may have solved this problem. I have
>> a spam filter that fetches the mail on startup. It does this
>> when the system is still installing itself, which may have
>> caused the corruption. I turned that option off and now I am not
>> experiencing any corruption whatsoever. I have rebooted at least
>> 20 times since I made the changes, and not once did anything
>> happen.
>>
>> I suppose I could turn the mail fetch back on at startup to see
>> if that is really the cause, but I need to move on. I have spent
>> far too much time chasing this problem.
>
>Good to hear that "bottom line" all is working now as designed and
>expected.

I would have liked to find out what it was that was causing the
problem. I contacted the tech guys at the spam filter and they claim
that running it at startup cannot possibly cause disk corruption. So
maybe it's SP4 that fixed it.

But now I have a different problem, which I suspect is caused by
having installed a recent version of SP4. Now when I do an In-Place
Upgrade, the setup application fusses about not being able to load
*.icm files. Those files are color drivers which apparently are not
available on the distribution disc.

Windows reminds me of an old Three Stooges gag where one of them shuts
the top drawer on a chest of drawers and the bottom drawer flies open
wacking him on the shins.


--

Greatest Movie Line Ever
http://home.houston.rr.com/rkba/MovieLine.wmv

"Rightful liberty is unobstructed action according to our will within
limits drawn around us by the equal rights of others. I do not add
'within the limits of the law,' because law is often but the tyrant's
will, and always so when it violates the rights of the individual."
-- Thomas Jefferson
.