KB936357

Must relate my experience with this update that perhaps will be useful to
others.
Two identical motherboard & Intel cpu computers were updated nearly 2 months
ago by automatic mode, resulting in stoppage of the boot immediately after
the first Windows XP SP2 screen and cycling back to start. No way to boot
into the OS, either safe or last configuration, therefore I was unable to
restore. Only repair-reinstall will work, but once re-updated, the problem
was back. Manual updating with hotfixes up to and excluding those of July,
were installed and not recreating the problem. (reinstalled so many times, I
exhausted the allow number and ended requiring phone calls to activate)
Microsoft send me a script which cleaned Auto Update. No help.
Them they decided that my streamed SP2 of the two early production was the
problem and they send me a new latest version XP-Pro SP2 CD.
Same problem.
Careful study of the July updates showed the KB936357 to be a microcode for
dual core Intel cpu's. The cpus in this computers were Intel Pentiums, but
not dual core. Excluding that fix, solved the problem.
I have been attempting to advice Microsoft of this findings, but they are
not returning my messages since the incidence was close once the CD was send
to me. Too bad.
Why would Windows update offer a dual core fix to a single core cpu? If they
have a mechanism to prevent that, it certainly failed and they should revise
KB936357.
I have block the delivery of such fix, but also will pay attention to the
intent of the fixes from now on, excluding those that are not relevant to
the computer.
Hope this can be helpful and comments will be appreciated.
Cheers

--
R. E. CREAGH, MD FACS
Heartburn Center DM
Heartburn! WHY!

Well, now that I have full use of mi computers, I made a search of this
group about the KB and found others with same, as well as an extremely
elegant solution. It would have same me about 1 1/2 months of working with
MS, which in spite of my suggestion, dismissed the possibility that there
was a bad patch but I did not identify the KB until recently. By the way, my
cpu's are Pentium II.
Cheers
"Rolando E Creagh, MD FACS"


<> wrote in message
news:...
> Must relate my experience with this update that perhaps will be useful to
> others.
> Two identical motherboard & Intel cpu computers were updated nearly 2
> months ago by automatic mode, resulting in stoppage of the boot
> immediately after the first Windows XP SP2 screen and cycling back to
> start. No way to boot into the OS, either safe or last configuration,
> therefore I was unable to restore. Only repair-reinstall will work, but
> once re-updated, the problem was back. Manual updating with hotfixes up to
> and excluding those of July, were installed and not recreating the
> problem. (reinstalled so many times, I exhausted the allow number and
> ended requiring phone calls to activate)
> Microsoft send me a script which cleaned Auto Update. No help.
> Them they decided that my streamed SP2 of the two early production was the
> problem and they send me a new latest version XP-Pro SP2 CD.
> Same problem.
> Careful study of the July updates showed the KB936357 to be a microcode
> for dual core Intel cpu's. The cpus in this computers were Intel Pentiums,
> but not dual core. Excluding that fix, solved the problem.
> I have been attempting to advice Microsoft of this findings, but they are
> not returning my messages since the incidence was close once the CD was
> send to me. Too bad.
> Why would Windows update offer a dual core fix to a single core cpu? If
> they have a mechanism to prevent that, it certainly failed and they should
> revise KB936357.
> I have block the delivery of such fix, but also will pay attention to the
> intent of the fixes from now on, excluding those that are not relevant to
> the computer.
> Hope this can be helpful and comments will be appreciated.
> Cheers
>
> --
> R. E. CREAGH, MD FACS
> Heartburn Center DM
> Heartburn! WHY!
>